[
https://issues.apache.org/jira/browse/HDFS-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinayakumar B updated HDFS-8270:
--------------------------------
Resolution: Fixed
Fix Version/s: 2.7.1
Release Note: Proxy level retries will not be done on
AlreadyBeingCreatedExeption for create() op.
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed to trunk, branch-2 and branch-2.7
Thanks [~andreina] for taking up the issue and contributing the fix.
Thanks [~jingzhao], [~octo47] for discussions.
cc: [~vinodkv]
There was a conflict while cherry picking to branch-2.7 as HDFS-8403 was not
available in branch-2.7.
So attaching the branch-2.7 committed patch for reference.
> create() always retried with hardcoded timeout when file already exists with
> open lease
> ---------------------------------------------------------------------------------------
>
> Key: HDFS-8270
> URL: https://issues.apache.org/jira/browse/HDFS-8270
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Affects Versions: 2.6.0
> Reporter: Andrey Stepachev
> Assignee: J.Andreina
> Fix For: 2.7.1
>
> Attachments: HDFS-8270.1.patch, HDFS-8270.2.patch, HDFS-8270.3.patch
>
>
> In Hbase we stumbled on unexpected behaviour, which could
> break things.
> HDFS-6478 fixed wrong exception
> translation, but that apparently led to unexpected bahaviour:
> clients trying to create file without override=true will be forced
> to retry hardcoded amount of time (60 seconds).
> That could break or slowdown systems, that use filesystem
> for locks (like hbase fsck did, and we got it broken HBASE-13574).
> We should make this behaviour configurable, do client really need
> to wait lease timeout to be sure that file doesn't exists, or it it should
> be enough to fail fast.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
