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

Jean-Daniel Cryans updated HBASE-7325:
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.95.2
                   0.98.0
         Assignee: Gabriel Reid
     Release Note: ReplicationSource won't backoff sleeping time if it can 
correctly read from the WAL even though it's not replicating anything. In that 
kind of situation it will put more load on the NN. 
replication.source.sleepforretries can still be tweaked to set the minimal 
sleep time.
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Committed to branch and trunk, thanks Gab!
                
> Replication reacts slowly on a lightly-loaded cluster
> -----------------------------------------------------
>
>                 Key: HBASE-7325
>                 URL: https://issues.apache.org/jira/browse/HBASE-7325
>             Project: HBase
>          Issue Type: Bug
>          Components: Replication
>            Reporter: Gabriel Reid
>            Assignee: Gabriel Reid
>            Priority: Minor
>             Fix For: 0.98.0, 0.95.2
>
>         Attachments: HBASE-7325.patch, HBASE-7325.v2.patch
>
>
> ReplicationSource uses a backing-off algorithm to sleep for an increasing 
> duration when an error is encountered in the replication run loop. However, 
> this backing-off is also performed when there is nothing found to replicate 
> in the HLog.
> Assuming default settings (1 second base retry sleep time, and maximum 
> multiplier of 10), this means that replication takes up to 10 seconds to 
> occur when there is a break of about 55 seconds without anything being 
> written. As there is no error condition, and there is apparently no 
> substantial load on the regionserver in this situation, it would probably 
> make more sense to not back off in non-error situations.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to