[
https://issues.apache.org/jira/browse/HBASE-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269125#comment-14269125
]
Hadoop QA commented on HBASE-5890:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12524903/HBASE-5890.patch
against master branch at commit 645fbd7d87450b31b67b1e535cdb9c1cf50ffd16.
ATTACHMENT ID: 12524903
{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/12359//console
This message is automatically generated.
> SplitLog Rescan BusyWaits upon Zk.CONNECTIONLOSS
> ------------------------------------------------
>
> Key: HBASE-5890
> URL: https://issues.apache.org/jira/browse/HBASE-5890
> Project: HBase
> Issue Type: Bug
> Reporter: Nicolas Spiegelberg
> Priority: Minor
> Attachments: HBASE-5890.patch
>
>
> We ran into a production issue yesterday where the SplitLogManager tried to
> create a Rescan node in ZK. The createAsync() generated a
> KeeperException.CONNECTIONLOSS that was immedately sent to processResult(),
> createRescan node with --retry_count was called, and this created a CPU
> busywait that also clogged up the logs. We should handle this better.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
