reddycharan opened a new pull request #1532: (WIP) ISSUE #1527: Make ExplicitLAC persistent URL: https://github.com/apache/bookkeeper/pull/1532 Descriptions of the changes in this PR: For persisting explicitLAC, we can follow the same approach as followed in persisting fencing information / stateBits (d69986c) in FileInfo file and special marker entry in Journal. ### Motivation ExplicitLAC is kept in the memory and it can be lost in bookie reboot. Though it is an extreme corner case scenario, it can break one of the BK guarantees. " If you read once you can always read it". If all the bookies of the Write stripe were rebooted, it can loose its explicitLAC value and the client which was able to read the entry before the reboot, can't read it anymore. Master Issue: #1527
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
