You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2015/01/10 03:14:35 UTC

[jira] [Resolved] (HBASE-5890) SplitLog Rescan BusyWaits upon Zk.CONNECTIONLOSS

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

Andrew Purtell resolved HBASE-5890.
-----------------------------------
    Resolution: Later

Resolving as Later. Reopen when motivated

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