[
https://issues.apache.org/jira/browse/HDFS-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15116846#comment-15116846
]
Hudson commented on HDFS-8071:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9186 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9186/])
HDFS-9690. ClientProtocol.addBlock is not idempotent after HDFS-8071.
(szetszwo: rev 45c763ad6171bc7808c2ddcb9099a4215113da2a)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
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/server/namenode/FSDirWriteFileOp.java
> Redundant checkFileProgress() in PART II of getAdditionalBlock()
> ----------------------------------------------------------------
>
> Key: HDFS-8071
> URL: https://issues.apache.org/jira/browse/HDFS-8071
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 2.0.3-alpha
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Fix For: 2.7.0
>
> Attachments: HDFS-8071-01.patch, HDFS-8071-02.patch,
> HDFS-8071-branch-2.7.patch
>
>
> {{FSN.getAdditionalBlock()}} consists of two parts I and II. Each part calls
> {{analyzeFileState()}}, which among other things check replication of the
> penultimate block via {{checkFileProgress()}}. See details in HDFS-4452.
> Checking file progress in Part II is not necessary, because Part I already
> assured the penultimate block is complete. It cannot change to incomplete,
> unless the file is truncated, which is not allowed for files under
> construction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
