hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17822) Set maxBadRows and outputDirectory option for VerifyReplication
Date Thu, 23 Mar 2017 07:37:41 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937866#comment-15937866

Phil Yang commented on HBASE-17822:

We should find all  inconsistent rows at the most cases, so if sometimes we really need maxBadRows,
its default value should be no limit to prevent changing current behavior. 
Output to a file is same, I think we can not change the default behavior. Can it be configurable?

> Set maxBadRows and outputDirectory  option for VerifyReplication
> ----------------------------------------------------------------
>                 Key: HBASE-17822
>                 URL: https://issues.apache.org/jira/browse/HBASE-17822
>             Project: HBase
>          Issue Type: Improvement
>          Components: mapreduce
>            Reporter: zhangshibin
>             Fix For: 2.0.0
>         Attachments: HBASE-17822-master.patch
> Currently,this tool will print too many rowkey as badrows  if source and peer table have
many inconsistent row.So,it is necessay to set maxBadRows to print.
> Also,look for badrows rowkey is inconvenient  in MR job log .It might be useful to set
a reduce to aggregate badrowkeys which will be print in MR job output file.

This message was sent by Atlassian JIRA

View raw message