[
https://issues.apache.org/jira/browse/HBASE-8434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642016#comment-13642016
]
Enis Soztutar commented on HBASE-8434:
--------------------------------------
bq. Okay - but then we need synchronous lease recovery for 0.94 - in HBASE 8389
- the patch v5 makes us skip lease recovery. I think either we revert that
patch or we provide an option to force lease recovery
As Nicolas said, patch v5 at HBASE-8389 is just a temp fix until the real fix
comes through. Ted is working on bringing isFileClosed() to Hadoop branch-1, so
we might be able to have this functionality in all latest versions of hadoop
branches. The remaining discussion we should have is what to do when
isFileClosed() is not there.
Agreed, let's move the discussion back to HBASE-8389 first, then we can decide
what to do here.
> Allow enabling hbase 8354 to support real lease recovery
> --------------------------------------------------------
>
> Key: HBASE-8434
> URL: https://issues.apache.org/jira/browse/HBASE-8434
> Project: HBase
> Issue Type: Improvement
> Components: MTTR
> Reporter: Varun Sharma
> Assignee: Varun Sharma
> Fix For: 0.94.8
>
> Attachments: 8434.patch
>
>
> Please see discussion in HBase 8389.
> For environments where lease recovery time can be bounded on the HDFS side
> through tight timeouts, provide a toggle for users who want the WAL splitting
> to continue only after the lease is truly recovered and the file is closed.
--
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
