[HBASE-12636] Avoid too many write operations on zookeeper in replication

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Abandoned
• Affects Version/s: 0.94.11
• Component/s: Replication
• Labels: replication
• Assignee: Unassigned
• Reporter: Shaohui Liu
• Created: 04/Dec/14 12:51
• Updated: 17/Jun/22 18:35
• Resolved: 11/Jun/22 19:40

Description

In our production cluster, we found there are about over 1k write operations per second on zookeeper from hbase replication. The reason is that the replication source will write the log position to zookeeper for every edit shipping. If the current replicating WAL is just the WAL that regionserver is writing to, each skipping will be very small but the frequency is very high, which causes many write operations on zookeeper.

A simple solution is that writing log position to zookeeper when position diff or skipped edit number is larger than a threshold, not every edit shipping.

Suggestions are welcomed, thx~