jvanlightly

4 ms·

1. 1.▲
   by jvanlightly 3y ago

   Author here: Regarding point 3, it was my understanding that inserts are synchronous but updates may be asynchronous. Is that the case?
2. 2.▲
   by jvanlightly 3y ago

   Protocol Aware Recovery is really needed if you want Raft to tolerate disk corruption. https://www.usenix.org/conference/fast18/presentation/alagap...
3. 3.▲
   by jvanlightly 3y ago

   These instances can manage up disk throughput up to 2 GB/s (400K IOPS) and network throughout of 25gbps or ~3.1 GB/s. There are so many dimensions, with configurations, CPU architecture, hardware resources plus all the workloads
4. 4.▲
   by jvanlightly 3y ago

   It's a common misconception about Kafka and fsyncs. But the Kafka replication protocol has a recovery mechanism, much in the same way that Viewstamped Replication Revisited does (except it's safer due to the page cache), which all
5. 5.▲
   by jvanlightly 3y ago

   Well, that just isn't accurate really. Kafka would need simulteanous VM failure across all AZs. That just doesn't happen in the real world often enough to worry about. It has never happened in Confluent Cloud. RP have a similar is
6. 6.▲
   by jvanlightly 3y ago

   Author here. Anyone can run these tests. It's available for anyone to run and check my results.
7. 7.▲
   by jvanlightly 3y ago

   Author here. Yes both Kafka and Redpanda were deployed on identical hardware: three i3en.6xlarge.