[
https://issues.apache.org/jira/browse/HBASE-13829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14576135#comment-14576135
]
Ashish Singhi commented on HBASE-13829:
---------------------------------------
bq. I want modify the doc in a new issue, so forgot it in this patch. I will
take your advice and add it in the next update of this patch.
Yeah better to capture doc changes also here only.
{quote}
Then we set quota for write number, but the avail will be always the
Long.MAX_VALUE, because the new limit is smaller than the old limit
(Long.MAX_VALUE). As you know, the patch of HBASE-13686 have not be committed.
So the refill bug will cause the canExecute() always return true. So the quota
of write number will not work.
{quote}
OK got your point. I think we can get wait for HBASE-13686 to get committed
which will be done by monday as [[email protected]] said in the
other jira. So that we can avoid this change here.
Also I would suggest to wait for next patch update till Monday so that patch
rebase efforts can be saved.
Thanks.
> Add more ThrottleType
> ---------------------
>
> Key: HBASE-13829
> URL: https://issues.apache.org/jira/browse/HBASE-13829
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Fix For: 2.0.0
>
> Attachments: HBASE-13829-v1.patch, HBASE-13829.patch
>
>
> HBASE-11598 add simple throttling for hbase. But in the client, it doesn't
> support user to set ThrottleType like WRITE_NUM, WRITE_SIZE, READ_NUM,
> READ_SIZE.
> REVIEW BOARD: https://reviews.apache.org/r/34989/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
