hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8270) create() always retried with hardcoded timeout when file already exists
Date Mon, 01 Jun 2015 18:00:18 GMT

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

Vinod Kumar Vavilapalli commented on HDFS-8270:
-----------------------------------------------

This came up on the dev lists. Did a quick scan. Seems like HDFS-6478 which broke the functionality
went into 2.6.0. Given that, I don't this should block 2.7.1, but if you can get it in in
a day or two, I'm all good.

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

Mime
View raw message