-
Type:
Improvement
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.5.0
-
Component/s: bookkeeper-client, bookkeeper-server
-
Labels:None
Current client API piggy-backs LAC with a write. This is keeps reader one behind the writer. In order to keep reader up to date with writer even when there is a pause in write, proposing the following:
Writer sends explicit LAC on a configured timeout if there is no write within that period.
- is related to
-
BOOKKEEPER-1019 Support for reading entries after LAC (causal consistency driven by out-of-band communications)
-
- Resolved
-
- links to