You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Xu Cang (JIRA)" <ji...@apache.org> on 2018/08/23 07:23:00 UTC

[jira] [Comment Edited] (HBASE-18549) Unclaimed replication queues can go undetected

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

Xu Cang edited comment on HBASE-18549 at 8/23/18 7:22 AM:
----------------------------------------------------------

partially related to: https://issues.apache.org/jira/browse/ZOOKEEPER-2101


was (Author: xucang):
Possibly related to: https://issues.apache.org/jira/browse/ZOOKEEPER-2101

> Unclaimed replication queues can go undetected
> ----------------------------------------------
>
>                 Key: HBASE-18549
>                 URL: https://issues.apache.org/jira/browse/HBASE-18549
>             Project: HBase
>          Issue Type: Bug
>          Components: Replication
>            Reporter: Ashu Pachauri
>            Assignee: Xu Cang
>            Priority: Critical
>             Fix For: 1.5.0, 1.3.3, 1.4.8
>
>         Attachments: HBASE-18549-.master.001.patch
>
>
> We have come across this situation multiple times where a zookeeper issues can cause NodeFailoverWorker to fail picking up replication queue for a dead region server silently. One example is when the znode size for a particular queue exceed jute.maxBuffer value.
> There can be other situations that may lead to this and just go undetected. We need to have a metric for number of unclaimed replication queues. This will help in mitigating the problem through alerting on the metric and identifying underlying issues.



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