[
https://issues.apache.org/jira/browse/HBASE-8394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13638763#comment-13638763
]
stack commented on HBASE-8394:
------------------------------
bq. But if we wait for one particular recovery without limit on duration, we
may incur penalty due to various failure scenarios such as stale primary Data
Node, etc.
The above does not make sense. It paints bad scenario but does not say what
our way out is? Is the way out a call to isFileClosed or something?
(I should have to click on a bunch of links to read comments from another
context to figure this out. If a JIRA's raison d'être can't be stated in a
terse sentence or two w/o recourse to links off-issue, then there is a
lazyness/sloppyness afoot and the issue should be put away until there is
clarity).
> Utilize isFileClosed() so that the wait for lease recovery can be optimized
> ---------------------------------------------------------------------------
>
> Key: HBASE-8394
> URL: https://issues.apache.org/jira/browse/HBASE-8394
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
>
> In HBASE-8389, there was discussion for utilizing isFileClosed() to optimize
> the wait time for lease recovery.
> Subsequent lease recovery request for the same Path would preempt outstanding
> recovery. But if we wait for one particular recovery without limit on
> duration, we may incur penalty due to various failure scenarios such as stale
> primary Data Node, etc.
> This JIRA continues the work for 0.95 / trunk.
--
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
