You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Steven Hancz (JIRA)" <ji...@apache.org> on 2017/01/10 22:27:58 UTC

[jira] [Created] (HBASE-17446) replication status

Steven Hancz created HBASE-17446:
------------------------------------

             Summary: replication status
                 Key: HBASE-17446
                 URL: https://issues.apache.org/jira/browse/HBASE-17446
             Project: HBase
          Issue Type: New Feature
          Components: Replication
            Reporter: Steven Hancz
            Priority: Minor


I have a multi tenant database where I have set up multiple namespaces one for each project. Each namespace/project has it's own replication peer. So that I can enable or disable replication for each project as it is needed. Not all projects/namespaces will replicate to the same peer. 

The output of the replication command (status 'replication', 'source') on the source side includes the peer id. So I can see how each replication peer is doing.

However on the target side the replication status command (status 'replication', 'sink') only sows that there a number of sinks going on but no explanation as to where they are originating from.

It would be extremely useful to see where each sink is originating from 
so that I could take the appropriate action. For example if the tables for one namespace are lagging say 5 minutes it might be a concern but it is possible that 5 minutes lagging for some other tables is OK.
If I had the source cluster/peer information I could create a monitoring script for each source and acct accordingly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)