kezhuw commented on PR #2164:
URL: https://github.com/apache/zookeeper/pull/2164#issuecomment-2368107479
This pr will change the server side data format. I think it does not fit a
patch release.
> If it is `1k/s` ops, then as long as $2^{32} / (86400 * 1000) \approx
49.7$ days ZXID will exhausted.
https://github.com/apache/zookeeper/pull/262#issue-230567070
> Thinking about some abnormal situations, maybe 24 bit for epoch and 40 bit
for counter is more better choice: M a t h . m i n ( 2 24 / ( 24 ∗ 365 ) , 2 40
/ ( 86400 ∗ 1000 ∗ 365 ) ) ≈ M a t h . m i n ( 1915.2 , 34.9 ) = 34.9 years.
https://github.com/apache/zookeeper/pull/262#issuecomment-303276951
> So i offered a better solution is 24-bit epoch in second comment. Even if
the frequency of leader election is once by every single hours, we will not
experience the epoch overflow until 1915.2 years later.
https://github.com/apache/zookeeper/pull/262#issuecomment-351886573
Given above, I think it is promising. It promotes rollover rate from `49.7`
days to `34.9` years assuming `1k/s` ops. The best is that it demands no
protocol change at the price of zxid format change.
Before finalizing this path, I may want to taste whether leadership
inheritance is feasible.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
