[
https://issues.apache.org/jira/browse/HBASE-24524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-24524:
---------------------------------
Fix Version/s: (was: 2.4.0)
Affects Version/s: (was: 2.4.0)
> 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.2.5
> Reporter: Wellington Chevreuil
> Assignee: Wellington Chevreuil
> Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.3.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)
