hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15930) Make IntegrationTestReplication's waitForReplication() smarter
Date Fri, 12 May 2017 22:24:05 GMT

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

Mike Drob commented on HBASE-15930:

Hey [~dimaspivak] - I recently ran into issues with this test and was looking at making some
improvements. Do you mind if I take this on while I'm in the area?

> Make IntegrationTestReplication's waitForReplication() smarter
> --------------------------------------------------------------
>                 Key: HBASE-15930
>                 URL: https://issues.apache.org/jira/browse/HBASE-15930
>             Project: HBase
>          Issue Type: Improvement
>          Components: integration tests
>            Reporter: Dima Spivak
>            Assignee: Dima Spivak
>             Fix For: 2.0.0
> {{IntegrationTestReplication}} is a great test, but can improved by changing how we handle
waiting between generation of the linked list on the source cluster and verifying the linked
list on the destination cluster. [Even the code suggests this should be done|https://github.com/apache/hbase/blob/master/hbase-it/src/test/java/org/apache/hadoop/hbase/test/IntegrationTestReplication.java#L251-252],
so I'd like to take it on. [~mbertozzi] and [~busbey] have both suggested a simple solution
wherein we write a row into each region on the source cluster after the linked list generation
and then assume replication has gone through once these rows are detected on the destination
> Since you lads at Facebook are some of the heaviest users, [~eclark], would you prefer
I maintain the API and add a new command line option (say {{\-c | \-\-check-replication}})
that would run before any {{--generateVerifyGap}} sleep is carried out as it is now?

This message was sent by Atlassian JIRA

View raw message