Hi tobe, yes we are replicating during verify.
So as I understand, the problem is that during the verify job the one key is updated (with new timestamp) while this key will be verified. So on one side the key timestamp is in the verify timerange but on the other side no more. So the key is "missing" there and the next key will be compared. Maybe I am totally wrong and someone has a good description of what happens ;-) Regards Hansi > Gesendet: Dienstag, 26. August 2014 um 13:22 Uhr > Von: tobe <[email protected]> > An: "[email protected]" <[email protected]> > Betreff: Re: Re: Hbase verifyrep compares different key's > > @hansi Are you running replication or updating data during verification? If > so, a little inconsistency is reasonable because the replication is final > consistent. > > But if you compare these two cluster which will not update, you should not > get BADROWS. This tool is well for static comparison. > > > On Tue, Aug 26, 2014 at 6:25 PM, Hansi Klose <[email protected]> wrote: > > > Hi Tobe, > > > > ok, this is why there are so many, but this means that in the job with > > BADROWS > > there is minimum one row missing at that time on one side. > > > > Right? > > > > Regards Hansi > > > > > Gesendet: Dienstag, 26. August 2014 um 10:20 Uhr > > > Von: tobe <[email protected]> > > > An: "[email protected]" <[email protected]> > > > Betreff: Re: Hbase verifyrep compares different key's > > > > > > It's the bug of VerifyReplication, please refer to [HBASE-10153] > > > <https://issues.apache.org/jira/browse/HBASE-10153>. > > > > > > Need someone to review and fix it. > > > > > > > > > On Tue, Aug 26, 2014 at 4:10 PM, Hansi Klose <[email protected]> wrote: > > > > > > > Hi, > > > > > > > > I run periodically verify jobs on our hbase tables. > > > > One some tables i have problems with many BADROWS. > > > > > > > > I looked into the job log file and recognized that > > > > the job started to compare different key. > > > > > > > > I looks like the job missees on key on one the replication target side > > > > and from that point each key in that job produces BADROWS. > > > > > > > > Like this: > > > > > > > > A - A > > > > B - B > > > > C - > > > > D - C > > > > E - D > > > > F - E > > > > > > > > Even when I go 3 days back with my --starttime and --endtime > > > > I have this problem too. > > > > > > > > I do not really understand why that happens. > > > > > > > > The hbase tables have a high volume of write action. > > > > > > > > We use Hbase 0.94.2-cdh4.2.0. > > > > > > > > Regards Hans > > > > > > > > > >
