hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-17026) VerifyReplication log should distinguish whether good row key is result of revalidation
Date Mon, 07 Nov 2016 15:42:58 GMT

     [ https://issues.apache.org/jira/browse/HBASE-17026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ted Yu updated HBASE-17026:
---------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 1.4.0
                   2.0.0
           Status: Resolved  (was: Patch Available)

Thanks for the review, Jianwei.

> 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
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: 17026.v1.txt, 17026.v2.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)

Mime
View raw message