[
https://issues.apache.org/jira/browse/HADOOP-8365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eli Collins updated HADOOP-8365:
--------------------------------
Attachment: hadoop-8365.txt
Updated patch.
1. Renames the config to dfs.durable.sync and flips the polarity, the previous
name was to be consistent with allow.broken.append, and because if you disable
this option you're breaking sync (!).
2. Reintroduced this check around the BBW directory reporting. I left it out of
the previous patch because BBW handling is independent of sync (even if you
don't persist blocks you'll still have BBW).
> Provide ability to disable working sync
> ---------------------------------------
>
> Key: HADOOP-8365
> URL: https://issues.apache.org/jira/browse/HADOOP-8365
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 1.1.0
> Reporter: Eli Collins
> Assignee: Eli Collins
> Priority: Blocker
> Attachments: hadoop-8365.txt, hadoop-8365.txt
>
>
> Per HADOOP-8230 there's a request for a flag to disable the sync code paths
> that dfs.support.append used to enable. The sync method itself will still be
> available and have a broken implementation as that was the behavior before
> HADOOP-8230. This config flag should default to false as the primary
> motivation for HADOOP-8230 is so HBase works out-of-the-box with Hadoop 1.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
