3 ms·
Two comments here. 1) What about Kafka + KRaft, doesn't that suffer the same problem you point out in Redpanda? If so, recommending to your customers to run KR
by galeaspablo 3y ago
Two comments here.
1) What about Kafka + KRaft, doesn't that suffer the same problem you point out in Redpanda? If so, recommending to your customers to run KRaft without fsync would be like recommending running with a Zookeeper that sometimes doesn't work. Or do I fundamentally misunderstand KRaft?
2) You mention simultaneous power failures deep into the fsync blog post. I think this should be more visible in your benchmark blog post, when you write about turnning off fsyncs.
- ocadaruma 3y ago1) KRaft is only for metadata replication, and data replication is done in ISR based even in KRaft, so it doesn't change the conclusion
- galeaspablo 3y agoNah, I dug deeper into this. Right conclusion, wrong reasoning. The reason KRaft turns out to be fine is because the KRaft topic does fsync! Source: https://cwiki.apache.org/confluence/display/KAFKA/KIP-595%3A+A+Raft+Protocol+for+the+Metadata+Quorum#KIP595:ARaftProtocolfortheMetadataQuorum-QuorumState https://cwiki.apache.org/confluence/display/KAFKA/KIP-595%3A... KRaft is used for metadata replication in the same way that Zookeeper is used for metadata. I.e., in a very meaningful way.