You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Biju Nair (JIRA)" <ji...@apache.org> on 2019/05/14 02:05:01 UTC

[jira] [Updated] (HBASE-12636) Avoid too many write operations on zookeeper in replication

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

Biju Nair updated HBASE-12636:
------------------------------
    Component/s: Replication

> Avoid too many write operations on zookeeper in replication
> -----------------------------------------------------------
>
>                 Key: HBASE-12636
>                 URL: https://issues.apache.org/jira/browse/HBASE-12636
>             Project: HBase
>          Issue Type: Improvement
>          Components: Replication
>    Affects Versions: 0.94.11
>            Reporter: Liu Shaohui
>            Assignee: Liu Shaohui
>            Priority: Major
>              Labels: replication
>         Attachments: HBASE-12635-v2.diff, HBASE-12636-v1.diff
>
>
> 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~



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)