[
https://issues.apache.org/jira/browse/HBASE-8434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709084#comment-13709084
]
Enis Soztutar commented on HBASE-8434:
--------------------------------------
I am still -1 on this patch as it is. We cannot just default to possible data
loss out of the box. I am not objecting to introducing the param, but we cannot
default to bypassing recovery.
If we get HBASE-8670 in 0.94, and backport HDFS-4721 to hadoop-1.3, that would
solve most of the problems for the hbase-0.94.10|0.96.0 + hdfs-1.3+|2.1 stack,
right?
> 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.10
>
> 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
