[
https://issues.apache.org/jira/browse/HBASE-25694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909121#comment-17909121
]
Hudson commented on HBASE-25694:
--------------------------------
Results for branch branch-2
[build #1214 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1214/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1214/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1214/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1214/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1214/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1214/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop ${HADOOP_THREE_VERSION} backward compatibility
checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1214/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop ${HADOOP_THREE_VERSION} backward compatibility
checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1214/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk17 hadoop ${HADOOP_THREE_VERSION} backward compatibility
checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1214/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
> Improve the shell's 'status replication' command output
> -------------------------------------------------------
>
> 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
> Assignee: xi chaomin
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2
>
> Attachments: HBASE-25694-2.4.patch
>
>
> The output of the shell's 'status "replication"' command could use some
> cleaning up.
> The basic format is:
> version VERSION
> N live servers
> SERVER_1:
> SOURCE: PeerID=PEERID, 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.
> - Age is printed as long and timestamp is string (local TZ) format. I think
> the string formatting of the timestamp makes it difficult to read. Lets just
> print timestamps as longs. Or provide a non-default option for string
> formatted timestamps.
> - There is no sense of effective rate or bandwidth. Each source and sink line
> emitted should provide some sense of current workload: rpcs/sec, bytes/sec,
> cells/sec... something.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
