You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2019/02/01 19:56:01 UTC

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

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

Andrew Purtell updated HBASE-18549:
-----------------------------------
    Fix Version/s:     (was: 1.5.0)

> 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: 3.0.0, 2.2.0, 1.4.8, 2.1.1
>
>         Attachments: HBASE-18549-.master.001.patch, HBASE-18549-.master.002.patch, HBASE-18549-.master.003.patch, HBASE-18549-.master.004.patch, HBASE-18549.branch-1.001.patch, HBASE-18549.branch-1.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)