[jira] [Commented] (HBASE-20835) Document how to get replication reporting

["Duo Zhang (JIRA)" <ji...@apache.org>]

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

Duo Zhang commented on HBASE-20835:
-----------------------------------

I think the only problem is that we do not create the zk node immediately after creating the peer? There is no other difference. To be honest I do not fully understand what is the real problem for you, as there is no way to disable replication in 2.0?

> Document how to get replication reporting
> -----------------------------------------
>
>                 Key: HBASE-20835
>                 URL: https://issues.apache.org/jira/browse/HBASE-20835
>             Project: HBase
>          Issue Type: Task
>          Components: Replication
>    Affects Versions: 2.1.0
>            Reporter: Mike Drob
>            Assignee: Duo Zhang
>            Priority: Critical
>             Fix For: 2.1.0
>
>
> Based on my questions at the tail end of HBASE-19543
> bq. We have some tooling that checks on replication queues and reads the znode as the source of truth. When replication is disabled, it's expected that the node was still there, but just empty. Is there a better way to get this same information?
> I understand that with table based replication it doesn't make sense to check ZK for status. However, losing the ability to inspect the data and get information is a tough hit for operators. Do we have APIs that expose the same sort of metrics?
> bq. how many peers/queues, queue size, position in the queue, and age of last op
> Assigning to you for now, Duo, since you were both primary implementor and RM for 2.1.0 and I'm not sure who else would know the answers. If the docs already exist, then nothing to do but we should include them in the RN. Maybe this will need additional code, but I hope it's already there and is something we can write a workaround for.



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