[
https://issues.apache.org/jira/browse/HBASE-8434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641721#comment-13641721
]
Nicolas Liochon commented on HBASE-8434:
----------------------------------------
Yep, v5 is just a way to have a known but bad behaviour until we fix the issue
for real. But to declare it fixed, we need to test with real failures.
Imho, requiring the stale mode is not a big issue for HBase. If you don't have
it, you will go to dead datanodes during the split, and this will lead you to a
bad MTTR anyway...
> Allow users to trade lease recovery for MTTR
> --------------------------------------------
>
> 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 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
