[
https://issues.apache.org/jira/browse/HDFS-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502511#comment-13502511
]
Hadoop QA commented on HDFS-4213:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12554581/HDFS-4213.003.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/3554//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3554//console
This message is automatically generated.
> When the client calls hsync(), allows the client to update the file length in
> the NameNode
> ------------------------------------------------------------------------------------------
>
> Key: HDFS-4213
> URL: https://issues.apache.org/jira/browse/HDFS-4213
> Project: Hadoop HDFS
> Issue Type: New Feature
> Affects Versions: 3.0.0
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: HDFS-4213.001.patch, HDFS-4213.002.patch,
> HDFS-4213.003.patch
>
>
> As per discussion in HDFS-3960 and HDFS-2802, when clients that need strong
> consistency update the file length at the NameNode, a special sync is
> required for getting the length of the being written files when snapshots are
> taken for these files. This jira implements this sync-with-updating-length by
> 1) calling ClientProtocol#fsync(), and 2) adding a new field to
> ClientProtocol#fsync() to indicate the length information.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
