[
https://issues.apache.org/jira/browse/HBASE-16096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph updated HBASE-16096:
---------------------------
Status: Open (was: Patch Available)
Overriding ReplicationPeerZkImpl.nodeCreated() without calling the super method
caused the watcher to fail as ReplicationPeerZkImpl.nodeDataChanged()
eventually called nodeCreated(). This also led to an infinite recursive loop.
Fixed this in the newest patch and ran the failed test cases.
> Replication keeps accumulating znodes
> -------------------------------------
>
> Key: HBASE-16096
> URL: https://issues.apache.org/jira/browse/HBASE-16096
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Affects Versions: 1.2.0, 2.0.0, 1.3.0
> Reporter: Ashu Pachauri
> Assignee: Joseph
> Attachments: HBASE-16096.patch
>
>
> If there is an error while creating the replication source on adding the
> peer, the source if not added to the in memory list of sources but the
> replication peer is.
> However, in such a scenario, when you remove the peer, it is deleted from
> zookeeper successfully but for removing the in memory list of peers, we wait
> for the corresponding sources to get deleted (which as we said don't exist
> because of error creating the source).
> The problem here is the ordering of operations for adding/removing source and
> peer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
