hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prakash Khemani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5890) SplitLog Rescan BusyWaits upon Zk.CONNECTIONLOSS
Date Fri, 27 Apr 2012 22:30:50 GMT

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

Prakash Khemani commented on HBASE-5890:

Most likely, it isn't a good idea to sleep in the zookeeper callback thread. (isn't the zk
client single threaded?)

Can these be queued in a DelayedQueue(socket-timeout) and retried from SplitLogManager.TimeoutMonitor.chore()
> 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
>             Fix For: 0.94.0, 0.96.0, 0.89-fb
>         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 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


View raw message