You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Phabricator (Updated) (JIRA)" <ji...@apache.org> on 2011/12/15 20:50:32 UTC

[jira] [Updated] (HBASE-5029) TestDistributedLogSplitting fails on occasion

     [ https://issues.apache.org/jira/browse/HBASE-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Phabricator updated HBASE-5029:
-------------------------------

    Attachment: HBASE-5029.D891.1.patch

khemani requested code review of "HBASE-5029 [jira] TestDistributedLogSplitting fails on occasion".
Reviewers: stack, nspiegelberg, JIRA

  had to make the test kind of toothless. Now on a rs abort it checks not only the error paths but also the success paths.

  difficult to ensure that the splitting doesn't finish before abort or that master doesn't preempt on seeing rs abort.

TEST PLAN
  the test passes

REVISION DETAIL
  https://reviews.facebook.net/D891

AFFECTED FILES
  src/test/java/org/apache/hadoop/hbase/master/TestDistributedLogSplitting.java

MANAGE HERALD DIFFERENTIAL RULES
  https://reviews.facebook.net/herald/view/differential/

WHY DID I GET THIS EMAIL?
  https://reviews.facebook.net/herald/transcript/1881/

Tip: use the X-Herald-Rules header to filter Herald messages in your client.

                
> TestDistributedLogSplitting fails on occasion
> ---------------------------------------------
>
>                 Key: HBASE-5029
>                 URL: https://issues.apache.org/jira/browse/HBASE-5029
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: Prakash Khemani
>         Attachments: HBASE-5029.D891.1.patch
>
>
> This is how it usually fails: https://builds.apache.org/view/G-L/view/HBase/job/HBase-0.92/lastCompletedBuild/testReport/org.apache.hadoop.hbase.master/TestDistributedLogSplitting/testWorkerAbort/
> Assigning mighty Prakash since he offered to take a looksee.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira