[
https://issues.apache.org/jira/browse/HDFS-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428333#comment-13428333
]
Todd Lipcon commented on HDFS-3755:
-----------------------------------
bq. This patch just changes the user-visible behavior back to what it was in
branch-1. It's fixing a bug that was inadvertently introduced in branch-2.
True, this fixes a behavior regression in the case that the old writer had in
fact lost its lease.
BUT: the branch-1 behavior, if the old writer is in fact active and renewing
its lease, would be that the "overwriter" client would fail with
AlreadyBeingCreatedException after 5 minutes. So, this patch does change
behavior in this case, but I believe in the correct direction.
So, I'm in favor of marking it incompatible, so it shows up in the release
notes, but putting it in branch-2 nonetheless.
The question is whether we should also change this behavior in branch-1 itself.
I think given the stability level of that branch, we should leave it alone.
> Creating an already-open-for-write file with overwrite=true fails
> -----------------------------------------------------------------
>
> Key: HDFS-3755
> URL: https://issues.apache.org/jira/browse/HDFS-3755
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 2.0.0-alpha
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hdfs-3755.txt
>
>
> If a file is already open for write by one client, and another client calls
> {{fs.create()}} with {{overwrite=true}}, the file should be deleted and the
> new file successfully created. Instead, it is currently throwing
> AlreadyBeingCreatedException.
> This is a regression since branch-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
