[
https://issues.apache.org/jira/browse/HBASE-8321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633132#comment-13633132
]
Jimmy Xiang commented on HBASE-8321:
------------------------------------
Yes, that's also my concern. I reduced the period by 1 sec in the first patch.
We can't make it too short. Otherwise, there may be too many ZK actions. How
about SplitLogManager.TIMEOUT/2.5 or 3?
> Log split worker should heartbeat to avoid timeout when the hlog is under
> recovery
> ----------------------------------------------------------------------------------
>
> Key: HBASE-8321
> URL: https://issues.apache.org/jira/browse/HBASE-8321
> Project: HBase
> Issue Type: Bug
> Components: wal
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Attachments: trunk-8321_v1.patch, trunk-8321_v2.patch
>
>
> Currently, hlog splitter could spend quite sometime to split a log in case
> any HDFS issue and recoverLease/retry opening is needed. If distributed log
> split manager times out the log worker, other log worker to take over will
> run into the same issue.
> Ideally, we should not need a timeout monitor. Since we have a timeout
> monitor for DSL now, the worker should heartbeat to avoid wrong/unneeded
> timeouts.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
