[
https://issues.apache.org/jira/browse/HDFS-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427625#comment-13427625
]
Todd Lipcon commented on HDFS-3755:
-----------------------------------
Attached patch fixes the issue.
The behavior with this patch is still a little strange: if you call
{{create(overwrite=false)}} on a file open for write but with expired
soft-lease, you will trigger lease recovery of that file because we still call
{{recoverLeaseInternal}} even for {{overwrite=false}}. Fixing this would
involve a bit more surgery of the FSNamesystem code, so I wanted to fix the
behavioral regression here and leave further improvements for another JIRA.
> 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
