You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2021/03/25 02:05:00 UTC

[jira] [Created] (HBASE-25694) Shell's 'status replication' command could use some cleanup

Andrew Kyle Purtell created HBASE-25694:
-------------------------------------------

             Summary: Shell's 'status replication' command could use some cleanup
                 Key: HBASE-25694
                 URL: https://issues.apache.org/jira/browse/HBASE-25694
             Project: HBase
          Issue Type: Task
          Components: Operability, Replication, shell
    Affects Versions: 2.4.2
            Reporter: Andrew Kyle Purtell
             Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3


The output of the shell's 'status "replication"' command could use some cleaning up.

The basic format is:

version 2.4.2-sfdc-1.0.0
N live servers
SERVER_1:
       SOURCE: PeerID=1, AgeOfLastShippedOp=160347, SizeOfLogQueue=49, TimeStampsOfLastShippedOp=Thu Mar 25 01:55:21 UTC 2021, Replication Lag=161013
       SINK  : AgeOfLastAppliedOp=0, TimeStampsOfLastAppliedOp=Thu Mar 25 01:49:53 UTC 2021
...

Issues:
- Per line format is KEY=VALUE, ... . Most KEYs are CamelCase but some have spaces. Should all be camel case for consistency.
- Timestamp values are printed both in long and string (local TZ) format. Pick one. Lets just emit them as long values. 
- There is no sense of effective rate or bandwidth. Each source and sink should provide some sense of current workload: rpcs/sec, bytes/sec, cells/sec... something. 





--
This message was sent by Atlassian Jira
(v8.3.4#803005)