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

Hudson commented on HDFS-7835:
------------------------------

FAILURE: Integrated in Hadoop-Yarn-trunk #873 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/873/])
HDFS-7835. make initial sleeptime in locateFollowingBlock configurable for 
DFSClient. Contributed by Zhihai Xu. (yzhang: rev 
15612313f578a5115f8d03885e9b0c8c376ed56e)
* 
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDFSClientRetries.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSOutputStream.java
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java
* hadoop-hdfs-project/hadoop-hdfs/src/main/resources/hdfs-default.xml
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSClient.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt


> make initial sleeptime in locateFollowingBlock configurable for DFSClient.
> --------------------------------------------------------------------------
>
>                 Key: HDFS-7835
>                 URL: https://issues.apache.org/jira/browse/HDFS-7835
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: dfsclient
>    Affects Versions: 2.7.0
>            Reporter: zhihai xu
>            Assignee: zhihai xu
>             Fix For: 2.8.0
>
>         Attachments: HDFS-7835.000.patch, HDFS-7835.001.patch, 
> HDFS-7835.002.patch
>
>
> Make initial sleeptime in locateFollowingBlock configurable for DFSClient.
> Current the sleeptime/localTimeout in locateFollowingBlock/completeFile from 
> DFSOutputStream is hard-coded as 400 ms, but retries can be configured by 
> "dfs.client.block.write.locateFollowingBlock.retries". We should also make 
> the initial sleeptime configurable to give user more flexibility to control 
> both retry and delay.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to