[
https://issues.apache.org/jira/browse/HBASE-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263880#comment-13263880
]
Nicolas Spiegelberg commented on HBASE-5890:
--------------------------------------------
The original idea is to have a timeout when we encounter this error. Since we
have a recoverable ZK, it seems okay to retry after connection loss; but we
should have some sort of dampening so that this isn't a CPU & log hog.
> 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
>
> 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
