4 ms·

So, I assume you use a journal in the cache server. A few related questions: * Do you use a single leader for a specific file system, or do you have a cluster

So, I assume you use a journal in the cache server. A few related questions: * Do you use a single leader for a specific file system, or do you have a cluster solution with consensus to enable scaling/redundancy? * How do you guarantee read-after-write consistency? Do you stream the journal to all clients and wait for them to ack before the write finishes? Or at least wait for everyone to ack the latest revisions for files, while the content is streamed out separately/requested on demand? * If the above is true, I assume this is strictly viable for single-DC usage due to latency? Do you support different mount options for different consistency guarantees?

huntaub 2y ago
These are questions that are super specific to our implementation, that I'm hesitant to share publicly because they could change any at any time. I can share that we're designed to horizontally scale the performance of each file system, and our custom protocol will enable Lustre-like scale out performance. As for single- vs. multi-DC, I think that you'd be surprised at how much latency budget there is (a cross-DC round trip in AWS can be anywhere from 200us-700us, and EBS gp3 latencies are around 1000us).