[ https://issues.apache.org/jira/browse/HBASE-24524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17130736#comment-17130736 ]
Hudson commented on HBASE-24524: -------------------------------- Results for branch master [build #1753 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1753/]: (x) *{color:red}-1 overall{color}* ---- details (if available): (/) {color:green}+1 general checks{color} -- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/master/1753/General_20Nightly_20Build_20Report/] (/) {color:green}+1 jdk8 hadoop2 checks{color} -- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/master/1698/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/] (x) {color:red}-1 jdk8 hadoop3 checks{color} -- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/master/1753/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/] (x) {color:red}-1 jdk11 hadoop3 checks{color} -- For more information [see jdk11 report|https://builds.apache.org/job/HBase%20Nightly/job/master/1753/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/] (/) {color:green}+1 source release artifact{color} -- See build output for details. (/) {color:green}+1 client integration test{color} > SyncTable logging improvements > ------------------------------ > > Key: HBASE-24524 > URL: https://issues.apache.org/jira/browse/HBASE-24524 > Project: HBase > Issue Type: Improvement > Affects Versions: 3.0.0-alpha-1, 2.3.0, 2.4.0, 2.2.5 > Reporter: Wellington Chevreuil > Assignee: Wellington Chevreuil > Priority: Minor > Fix For: 3.0.0-alpha-1, 2.3.0, 2.4.0, 2.2.6 > > > While troubleshooting mismatches in replication deployment, SyncTable logging > can provide some insights on what is diverging between two clusters. One > caveat, though, is that it logs diverging row key as hexdecimal values, which > is not so useful for operators trying to figure out which rows are > mismatching, ideally, this info should be human readable, so that operators > could have the exact value they could use for querying the tables with other > tools, such as hbase shell. > Another issue is that while rows mismatches are logged as info, cell values > mismatches are only logged as debug. In general, any of the mismatches would > already be quite verbose, so ideally both should be logged in debug level. -- This message was sent by Atlassian Jira (v8.3.4#803005)