You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Chris Trezzo (Commented) (JIRA)" <ji...@apache.org> on 2011/09/29 22:52:45 UTC
[jira] [Commented] (HBASE-4499) [replication] Source shouldn't
update ZK if it didn't progress
[ https://issues.apache.org/jira/browse/HBASE-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117601#comment-13117601 ]
Chris Trezzo commented on HBASE-4499:
-------------------------------------
@J-D
Here is a simple sketch patch. I have not tested it yet.
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
> Priority: Minor
> Fix For: 0.92.0
>
>
> 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