[ https://issues.apache.org/jira/browse/HBASE-8099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602090#comment-13602090 ]
Hadoop QA commented on HBASE-8099: ---------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12573684/8099-example.txt against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/4812//console This message is automatically generated. > ReplicationZookeeper.copyQueuesFromRSUsingMulti should not return any queues > if it failed to execute. > ----------------------------------------------------------------------------------------------------- > > Key: HBASE-8099 > URL: https://issues.apache.org/jira/browse/HBASE-8099 > Project: HBase > Issue Type: Bug > Reporter: Lars Hofhansl > Assignee: Himanshu Vashishtha > Priority: Blocker > Fix For: 0.95.0, 0.98.0, 0.94.6 > > Attachments: 8099-example.txt, HBase-8099-94.patch, > HBase-8099-94-v2.patch, HBase-8099-94-v3.patch, HBase-8099-trunk-2.patch, > HBase-8099-trunk.patch, HBase-8099-trunk-v3.patch > > > We just ran into an interesting scenario. We restarted a cluster that was > setup as a replication source. > The stop went cleanly. > Upon restart *all* regionservers aborted within a few seconds with variations > of these errors: > http://pastebin.com/3iQVuBqS -- 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