hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "HBase Review Board (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3013) Tool to verify data in two clusters
Date Thu, 28 Oct 2010 23:43:20 GMT

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

HBase Review Board commented on HBASE-3013:

Message from: "Jean-Daniel Cryans" <jdcryans@apache.org>

This is an automatically generated e-mail. To reply, visit:

Review request for hbase.


This new mapreduce job called VerifyReplication compares the data between two clusters that
are replication-enabled. Its usage is relatively simple when you already use replication,
and even let's you pass the peer id instead of the cluster key for the target cluster.

This addresses bug HBASE-3013.


  /trunk/src/main/java/org/apache/hadoop/hbase/mapreduce/Driver.java 1028470 
  /trunk/src/main/java/org/apache/hadoop/hbase/replication/ReplicationZookeeper.java 1028470

  /trunk/src/test/java/org/apache/hadoop/hbase/replication/TestReplication.java 1028470 

Diff: http://review.cloudera.org/r/1111/diff


Unit test (one new included) and this has been running for a month here.



> Tool to verify data in two clusters
> -----------------------------------
>                 Key: HBASE-3013
>                 URL: https://issues.apache.org/jira/browse/HBASE-3013
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.90.0
> It would be useful to have a tool to easily compare the data between tables in different
clusters, at least to make sure that replication is working correctly. I'm thinking of building
that inside CopyTable, kind of an option à là --verify that could be run independently or
after the copy (or not at all). The fact that we can already pass start/stop times is pretty
useful too when you don't want to check the whole tables, do incremental verifications, etc.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message