hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Liu Shaohui (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12636) Avoid too many write operations on zookeeper in replication
Date Wed, 18 Mar 2015 09:50:39 GMT

    [ https://issues.apache.org/jira/browse/HBASE-12636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366894#comment-14366894
] 

Liu Shaohui commented on HBASE-12636:
-------------------------------------

[~lhofhansl] [~stack]
Any suggestions about this patch?
The write operations to zookeeper from replication decrease to several hundreds from 5 thousands
per second in our cluster with this patch.

> 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
>    Affects Versions: 0.94.11
>            Reporter: Liu Shaohui
>            Assignee: Liu Shaohui
>              Labels: replication
>             Fix For: 1.1.0
>
>         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
(v6.3.4#6332)

Mime
View raw message