[
https://issues.apache.org/jira/browse/HADOOP-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267691#comment-13267691
]
Todd Lipcon commented on HADOOP-8230:
-------------------------------------
Couldn't the same be said for any new feature? Given that sync was fixed prior
to the 1.0 release, I don't see why this should be considered an incompatible
change. Many much bigger incompatible changes went into 1.0 when compared to
earlier 0.20.20x or 0.20.x releases (e.g tarball layout entirely changed, for
example). This doesn't affect any of the existing APIs, only the underlying
implementations.
Given this is committed for 1.1, not 1.0.x, I don't buy the reasoning that it's
too much risk. We've had sync on by default in hundreds of our customer
clusters for almost two years now and have yet to see a related data-loss
event. The only bugs we've seen have been bugs where sync() wouldn't provide
the correct semantics, but for installs which don't use sync, that doesn't
matter.
> 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
