[BOOKKEEPER-36] Client backpressure

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: bookkeeper-client
• Labels: ghmigrated iktriage0
• Assignee: Flavio Paiva Junqueira
• Reporter: Flavio Paiva Junqueira
• Created: 29/Jul/11 13:52
• Updated: 17/Oct/17 21:29

Description

The way we currently throttle on the client is by counting the number of outstanding operation on LedgerHandle, and having the application select what an appropriate value is. This is not a good way of doing it because the application has to guess what a good value is. We need to implement some form of backpressure instead to make sure we throttle only when the system is saturated.