Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 98A7C1153D for ; Mon, 14 Apr 2014 10:06:45 +0000 (UTC) Received: (qmail 25605 invoked by uid 500); 14 Apr 2014 10:06:41 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 25528 invoked by uid 500); 14 Apr 2014 10:06:41 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 25516 invoked by uid 99); 14 Apr 2014 10:06:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Apr 2014 10:06:40 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [212.227.15.4] (HELO mout.web.de) (212.227.15.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Apr 2014 10:06:34 +0000 Received: from [213.61.69.122] by 3capp-webde-bs27 with HTTP; Mon, 14 Apr 2014 12:06:12 +0200 MIME-Version: 1.0 Message-ID: From: "Hansi Klose" To: user@hbase.apache.org Subject: replication verifyrep Content-Type: text/plain; charset=UTF-8 Date: Mon, 14 Apr 2014 12:06:12 +0200 Importance: normal Sensitivity: Normal X-Priority: 3 X-Provags-ID: V03:K0:vOi5KzgKk5RQr5zYSOSTKz2U+zt3CfkomXwiNlzGvVp LznP6FOrtEWJ0GrgPWW2FCWpBS1+2n2a+8wzOF1c2cF6PyBGvz PfGb8N7qf7SFBUW1hgkgHVpJ3BuDHqPDPBvqh+BRTPROd2zbdZ LGuFLCtCndGIrZ3z20eBHZZy5V8ebgIoOFHmS8uXp+aS2Otbgv XywZ7YVF0SekgjMHqUrB/i0arM1KOcHIkeSkTy/5/JJhvAIPEk GyjzFIPN1yDn4UjngZiJpT8nRK/aso4ROGRfld8NyrQejDtJ9F 6vIucVI7AUBOeEAGEx5NcCfvOB7 X-Virus-Checked: Checked by ClamAV on apache.org Hi, I wrote a little script which should control the running replication. The script is triggered by cron and executes the following command with the actual time stamp in "endtime" and a time stamp => endtime - 10800000 milli seconds. So the time frame is 3 hours. hadoop jar /usr/lib/hbase/hbase.jar verifyrep --starttime=1397217601927 --endtime=1397228401927 --families=t 1 tablename 2>&1 After some running's the script found some BADROWS. 14/04/11 17:04:05 INFO mapred.JobClient: BADROWS=176 14/04/11 17:04:05 INFO mapred.JobClient: GOODROWS=2 I executed the same command 20 Minutes later in the shell and got : hadoop jar /usr/lib/hbase/hbase.jar verifyrep --starttime=1397217601927 --endtime=1397228401927 --families=t 1 tablename 2>&1 14/04/11 17:21:03 INFO mapred.JobClient: BADROWS=178 After that I run the command with the same start time and the actual timestamp an end time, so the time frame is greater but with the same start time. And now I got : hadoop jar /usr/lib/hbase/hbase.jar verifyrep --starttime=1397217601927 --endtime=1397230074876 --families=t 1 tablename 2>&1 14/04/11 17:28:28 INFO mapred.JobClient: GOODROWS=184 Is there something wrong with the command? In our metrics i could not see that three is an Issue at that time. We are a little bit confused about the endtime. In all documents they talk about stoptime. But we found that in the job configuration there is no parameter called stoptime. We found the "verifyrep.startTime" which hold the value of the starttime in our command and "verifyrep.endTime" which is alway 0 when we use stoptime in the command. So we decided to use endtime Even in the code http://hbase.apache.org/xref/org/apache/hadoop/hbase/mapreduce/replication/VerifyReplication.html they use: "static long endTime = Long.MAX_VALUE;" Which name is the right on? endtime or stoptime? We use cdh 4.2.0. Regards Hansi