[
https://issues.apache.org/jira/browse/HBASE-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264205#comment-13264205
]
Ted Yu commented on HBASE-5890:
-------------------------------
Prakash made a good point.
{code}
this.timeoutMonitor = new TimeoutMonitor(
conf.getInt("hbase.splitlog.manager.timeoutmonitor.period",
1000),
{code}
TimeoutMonitor runs at interval longer than socket timeout. If the default 1
sec interval (for TimeoutMonitor) is acceptable for the delay, this approach
would work.
> 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
