[HBASE-12769] Replication fails to delete all corresponding zk nodes when peer is removed

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.99.2
• Fix Version/s: 1.3.0, 2.0.0
• Component/s: Replication
• Hadoop Flags: Reviewed
• Assignee: Jianwei Cui
• Reporter: Jianwei Cui
• Created: 29/Dec/14 13:22
• Updated: 17/Jun/22 18:41
• Resolved: 28/Oct/15 22:43

Description

When removing a peer, the client side will delete peerId under peersZNode node; then alive region servers will be notified and delete corresponding hlog queues under its rsZNode of replication. However, if there are failed servers whose hlog queues have not been transferred by alive servers(this likely happens if setting a big value to "replication.sleep.before.failover" and lots of region servers restarted), these hlog queues won't be deleted after the peer is removed. I think remove_peer should guarantee all corresponding zk nodes have been removed after it completes; otherwise, if we create a new peer with the same peerId with the removed one, there might be unexpected data to be replicated.

Issue Links

• is related to: HBASE-11392 add/remove peer requests should be routed through master
• relates to: HBASE-15888 Extend HBASE-12769 for bulk load data replication