[
https://issues.apache.org/jira/browse/HADOOP-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269845#comment-13269845
]
Eli Collins commented on HADOOP-8230:
-------------------------------------
@Suresh, I understand that someone said they want to run their installation w/
broken sync the question is *why* they want to run an installation with broken
sync. I filed HADOOP-8365 for such a flag here, but there's currently no
rationale for why you'd want to do that. Also, someone choosing to upgrade from
1.0.x to 1.1 is going to pick up new changes - and even new features - and most
of them don't have a flag to disable them. Nothing new there.
@Koji, per your comment..
bq. Before moving all of our non-HBase clusters to 2.0, we might use 1.1 for
some time. During this period, I do not want some production projects to start
relying on the sync features then find some regression/difference on 2.0
blocking our upgrade schedule.
There may be a misunderstanding: the dfs.support.append flag never controlled
whether sync was enabled. DFSClient#sync and NN#fsync have always been
available - *enabling sync by default does not expose any new APIs to your
users that were not previously available*. The difference is that this fixes
bugs for your users that were already using sync, which I think you'll want.
> 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
