hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Stepachev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8270) create() always retried with hardcoded timeout when file already exists
Date Thu, 14 May 2015 09:31:01 GMT

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

Andrey Stepachev commented on HDFS-8270:

I'd remove that at all.
I think that this retries can be useful in case of dead client holding lease,
so I think the idea was to wait to be sure, that file really not exists anymore.

But it seems should be userlevel implementation, not hdfs level, we should
refuse file creation immediately.

> 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

View raw message