[jira] [Commented] (HDFS-8270) create() always retried with hardcoded timeout when file already exists

["Vinayakumar B (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HDFS-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543219#comment-14543219 ] 

Vinayakumar B commented on HDFS-8270:
-------------------------------------

This behaviour is only with NonHA. In HA it wont retry for {{AlreadyBeingCreatedException}}.

I see it strange. Retry for 5 min,. thats really not acceptable.

IMHO, by changing the SOFT_LEASE_TIMEOUT and and number of retries although we just working around this problem, but also changing the lease behaviour itself.
If this configurations changed only in client side to small value ( ex: 200ms), Same exception will be thrown as Lease still exists at NN. 

Why to keep this behaviour change only in case of Non-HA?

Any thoughts?


> 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
>
> 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)