[
https://issues.apache.org/jira/browse/HBASE-8321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628363#comment-13628363
]
Jimmy Xiang commented on HBASE-8321:
------------------------------------
bq. The regionserver is already controlled by a heartbeat, so if the process
dies we will know.
That's a good point. That's why I considered to remove the timeout thing in the
log split manager. However, it is not so intrusive to make the status reporting
time-based.
bq. if we stop the recovery, the region will just be unavailable.?
If a hlog can't be split, the region will be unavailable. Sometimes, the
cluster can't even start if the whole cluster is restarted and the master can't
complete the log splitting.
> Log split worker should heartbeat to avoid timeout
> --------------------------------------------------
>
> 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
>
> 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
