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

Hudson commented on HDFS-8270:
------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk #2163 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2163/])
HDFS-8270. create() always retried with hardcoded timeout when file already 
exists with open lease (Contributed by J.Andreina) (vinayakumarb: rev 
54f83d9bd917e8641e902c5f0695e65ded472f9a)
* 
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestFileCreation.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/NameNodeProxies.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSClient.java


> 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-branch-2.7-03.patch, 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)

Reply via email to