HackerTrans
TopNewTrendsCommentsPastAskShowJobs

ocadaruma

no profile record

Submissions

Kafka-on-Pulsar Got Archived

github.com
2 points·by ocadaruma·vor 2 Jahren·0 comments

comments

ocadaruma
·vor 3 Jahren·discuss
As far as read the blog post, I understand that it assumes the scenario that "a replica dies (and loses its log prefix due to no fcyns) and came back instantaneously (before another replica catches up to the leader)".

Then, in Kafka, what if the leader dies with power failure and came back instantaneously?

i.e.: Let's say there are 3 replicas A(L), B(F), C(F) (L = leader, F = follower)

- 1) append a message to A

- 2) B, C replicas the message. The message is committed

- 3) A dies and came back instantaneously before zk.session.timeout elapsed (i.e. no leadership failover happens), with losing its log prefix due to no fsync

Then B, C truncates the log and the committed message could be lost? Or is there any additional safety mechanism for this scenario?
ocadaruma
·vor 3 Jahren·discuss
1) KRaft is only for metadata replication, and data replication is done in ISR based even in KRaft, so it doesn't change the conclusion