[
https://issues.apache.org/jira/browse/HADOOP-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269360#comment-13269360
]
Eli Collins commented on HADOOP-8230:
-------------------------------------
Suresh, Sanjay, the rationale is discussed in HDFS-3120. In short:
# We shouldn't provide a flag that enables append because we know append has
data loss issues
# HBase and other programs have data loss when running against a default Hadoop
1.x install
The rationale is pretty clear - this prevents data loss.
Per my earlier comment, I'm open to having an option to disable durable sync if
you think that use case is important, but what is that use case? Given that
the sync code path is well tested and debugged, why would you want to run with
a buggy sync implementation?
> Enable sync by default and disable append
> -----------------------------------------
>
> Key: HADOOP-8230
> URL: https://issues.apache.org/jira/browse/HADOOP-8230
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 1.0.0
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 1.1.0
>
> Attachments: hadoop-8230.txt
>
>
> Per HDFS-3120 for 1.x let's:
> - Always enable the sync path, which is currently only enabled if
> dfs.support.append is set
> - Remove the dfs.support.append configuration option. We'll keep the code
> paths though in case we ever fix append on branch-1, in which case we can add
> the config option back
--
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
