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

Ming Ma commented on HBASE-4492:
--------------------------------

Here are the sequence of events how this could happen. It applies to any region.

T1. After AM sent openRegion RPC to RS1, RS1 set ZK state as OPENING.
T2. RS1 is stopped.
T3. ZK callbacked is delayed with ZK state OPENING. AM skip the processing 
given RS1 is offline. Thus region's state in AM is still PENDING_OPEN.
T4. During RS1's ServerShutDownHandler, it tries to assign the region by 
setting it offline first. This isn't allowed given the state isn't CLOSING or 
CLOSED.

                
> TestRollingRestart fails intermittently
> ---------------------------------------
>
>                 Key: HBASE-4492
>                 URL: https://issues.apache.org/jira/browse/HBASE-4492
>             Project: HBase
>          Issue Type: Test
>            Reporter: Ted Yu
>            Assignee: Jonathan Gray
>         Attachments: 4492.txt
>
>
> I got the following when running test suite on TRUNK:
> {code}
> testBasicRollingRestart(org.apache.hadoop.hbase.master.TestRollingRestart)  
> Time elapsed: 300.28 sec  <<< ERROR!
> java.lang.Exception: test timed out after 300000 milliseconds
>         at java.lang.Thread.sleep(Native Method)
>         at 
> org.apache.hadoop.hbase.master.TestRollingRestart.waitForRSShutdownToStartAndFinish(TestRollingRestart.java:313)
>         at 
> org.apache.hadoop.hbase.master.TestRollingRestart.testBasicRollingRestart(TestRollingRestart.java:210)
> {code}
> I ran TestRollingRestart#testBasicRollingRestart manually afterwards which 
> wiped out test output file for the failed test.
> Similar failure can be found on Jenkins:
> https://builds.apache.org/view/G-L/view/HBase/job/HBase-0.92/19/testReport/junit/org.apache.hadoop.hbase.master/TestRollingRestart/testBasicRollingRestart/

--
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

        

Reply via email to