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

Jean-Marc Spaggiari commented on HBASE-7824:
--------------------------------------------

Has anyone been able to run all the tests successfuly? I tried 3 times today 
and always TestReplicationQueueFailoverCompressed was part of the failed tests.

However, I'm not sure it's realy related to this fix. I will try again tomorrow.

Tests in error: 
  
queueFailover(org.apache.hadoop.hbase.replication.TestReplicationQueueFailoverCompressed):
 test timed out after 300000 milliseconds

Tests in error: 
  
queueFailover(org.apache.hadoop.hbase.replication.TestReplicationQueueFailoverCompressed):
 test timed out after 300000 milliseconds
  
queueFailover(org.apache.hadoop.hbase.replication.TestReplicationQueueFailover):
 test timed out after 300000 milliseconds

Tests in error: 
  
queueFailover(org.apache.hadoop.hbase.replication.TestReplicationQueueFailoverCompressed):
 test timed out after 300000 milliseconds

                
> Improve master start up time when there is log split work
> ---------------------------------------------------------
>
>                 Key: HBASE-7824
>                 URL: https://issues.apache.org/jira/browse/HBASE-7824
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>             Fix For: 0.94.6
>
>         Attachments: hbase-7824.patch, hbase-7824_v2.patch
>
>
> When there is log split work going on, master start up waits till all log 
> split work completes even though the log split has nothing to do with meta 
> region servers.
> It's a bad behavior considering a master node can run when log split is 
> happening while its start up is blocking by log split work. 
> Since master is kind of single point of failure, we should start it ASAP.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to