hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-4499) [replication] Source shouldn't update ZK if it didn't progress
Date Thu, 29 Sep 2011 23:43:45 GMT

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

Jean-Daniel Cryans resolved HBASE-4499.

      Resolution: Fixed
        Assignee: Chris Trezzo
    Release Note: ReplicationSource keeps track of its previous location and won't update
ZK if it doesn't need to.
    Hadoop Flags: Reviewed

I tested the patch and it works as advertised, committed to 0.92 and trunk. Thanks Chris!
> [replication] Source shouldn't update ZK if it didn't progress
> --------------------------------------------------------------
>                 Key: HBASE-4499
>                 URL: https://issues.apache.org/jira/browse/HBASE-4499
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.90.4
>            Reporter: Jean-Daniel Cryans
>            Assignee: Chris Trezzo
>            Priority: Minor
>             Fix For: 0.92.0
>         Attachments: 4499.txt
> A relatively minor optimization to be done in ReplicationSource, currently it calls ReplicationSourceManager.logPositionAndCleanOldLogs
whether it made progress or not, generating more load on ZK than necessary. The last position
should be kept around so that we can compare.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message