You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2016/11/04 19:51:58 UTC
[jira] [Updated] (HBASE-17026) VerifyReplication log should
distinguish whether good row key is result of revalidation
[ https://issues.apache.org/jira/browse/HBASE-17026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu updated HBASE-17026:
---------------------------
Attachment: 17026.v1.txt
> VerifyReplication log should distinguish whether good row key is result of revalidation
> ---------------------------------------------------------------------------------------
>
> Key: HBASE-17026
> URL: https://issues.apache.org/jira/browse/HBASE-17026
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Minor
> Attachments: 17026.v1.txt
>
>
> Inspecting app log from VerifyReplication, I saw lines in the following form:
> {code}
> 2016-11-03 15:28:44,877 INFO [main] org.apache.hadoop.hbase.mapreduce.replication.VerifyReplication: Good row key: X000 X
> {code}
> where 'X' is the delimiter.
> Without line number, it is difficult to tell whether the good row has gone through revalidation.
> This issue is to distinguish the two logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)