[BOOKKEEPER-1093] Piggyback LAC on ReadResponse

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.5.0
• Component/s: bookkeeper-client, bookkeeper-server
• Assignee: Sijie Guo
• Reporter: Sijie Guo
• Created: 02/Jun/17 20:17
• Updated: 22/Jun/17 13:26
• Resolved: 21/Jun/17 17:58

Description

Currently LAC is only updated when the reader explicitly calls #readLastAddConfirmed(). In tailing-read use cases, it will not wise to keep calling #readLastAddConfirmed, especially when the traffic is huge.

The idea here is piggy-back LAC along with the read responses. so the client will get advanced LAC along with read responses. so it will reduce calling #readLastAddConfirmed.

Issue Links

• blocks: BOOKKEEPER-1092 Ledger Recovery - Add Test Case for Parallel Ledger Recovery
• links to: GitHub Pull Request #180