[
https://issues.apache.org/jira/browse/ZOOKEEPER-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flavio Paiva Junqueira updated ZOOKEEPER-719:
---------------------------------------------
Status: Open (was: Patch Available)
I'm not happy with this patch for two reasons:
# In this current form, it is not possible to set the maximum number of
outstanding operations;
# Because of the use of a semaphore, I had to catch InterruptedException in a
few places. The most critical ones for me are the ones in the procedure to
recover a ledger. I believe in the way I have currently implemented, it could
cause problems if an instance of InterruptedException is raised when recovering
a ledger, since the procedure could complete successfully. I need to
investigate this further and either determine that it isn't a problem or find a
better way.
Any suggestion would be appreciated.
> Add throttling to BookKeeper client
> -----------------------------------
>
> Key: ZOOKEEPER-719
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-719
> Project: Zookeeper
> Issue Type: Bug
> Components: contrib-bookkeeper
> Affects Versions: 3.3.0
> Reporter: Flavio Paiva Junqueira
> Assignee: Flavio Paiva Junqueira
> Fix For: 3.4.0
>
> Attachments: ZOOKEEPER-719.patch
>
>
> Add throttling to client to control the rate of operations to bookies.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
