[ 
https://issues.apache.org/jira/browse/HBASE-27881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xiaolin Ha updated HBASE-27881:
-------------------------------
    Description: In theory the sleep time when checking quota failed in 
replication WAL reader should match the consume ability of the memory. But at 
the very least we should isolate the configuration here with the sleep time for 
common circumstances when replicating, e.g. sleep before reading from the head 
of the WAL, to avoid a little bit larger but reasonable sleep time(e.g. 3s) 
making consume speed always blocked by checking quota.  (was: In theory the 
sleep time when checking quota failed in replication WAL reader should match 
the consume ability of the memory. But at the very least we should isolate the 
configuration here with the sleep time for common circumstances when 
replicating, e.g. sleep before reading from the head of the WAL, to avoid a 
little bit bigger sleep time(e.g. 3s) making consume speed always blocked by 
checking quota.)

> The sleep time in checkQuota of replication WAL reader should be controlled 
> independently 
> ------------------------------------------------------------------------------------------
>
>                 Key: HBASE-27881
>                 URL: https://issues.apache.org/jira/browse/HBASE-27881
>             Project: HBase
>          Issue Type: Improvement
>          Components: Replication
>    Affects Versions: 3.0.0-alpha-3, 2.5.4
>            Reporter: Xiaolin Ha
>            Assignee: Xiaolin Ha
>            Priority: Minor
>
> In theory the sleep time when checking quota failed in replication WAL reader 
> should match the consume ability of the memory. But at the very least we 
> should isolate the configuration here with the sleep time for common 
> circumstances when replicating, e.g. sleep before reading from the head of 
> the WAL, to avoid a little bit larger but reasonable sleep time(e.g. 3s) 
> making consume speed always blocked by checking quota.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to