[
https://issues.apache.org/jira/browse/HDFS-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14568506#comment-14568506
]
Vinayakumar B commented on HDFS-8270:
-------------------------------------
bq. The only concern is whether directly removing this retry may break some
existing applications which depend on this retry.
I agree with you. But, till HDFS-6478 was in, this retry was not working AFAIK,
and only after this real issue of waiting for long time started showing up. I
will re-confirm again anyway. In that case I don't think removing would be
problem to existing applications.
> create() always retried with hardcoded timeout when file already exists
> -----------------------------------------------------------------------
>
> 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
> Attachments: HDFS-8270.1.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)
