Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E1137D737 for ; Wed, 28 Nov 2012 20:27:58 +0000 (UTC) Received: (qmail 62564 invoked by uid 500); 28 Nov 2012 20:27:58 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 62509 invoked by uid 500); 28 Nov 2012 20:27:58 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 62427 invoked by uid 99); 28 Nov 2012 20:27:58 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Nov 2012 20:27:58 +0000 Date: Wed, 28 Nov 2012 20:27:58 +0000 (UTC) From: "Hadoop QA (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1258226720.35202.1354134478576.JavaMail.jiratomcat@arcas> In-Reply-To: <1288797301.8360.1353439858253.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (HDFS-4213) When the client calls hsync, allows the client to update the file length in the NameNode MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505870#comment-13505870 ] Hadoop QA commented on HDFS-4213: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12555217/HDFS-4213.008.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:red}-1 core tests{color}. The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs: org.apache.hadoop.hdfs.server.balancer.TestBalancerWithEncryptedTransfer {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/3572//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3572//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, HDFS-4213.004.patch, HDFS-4213.005.patch, HDFS-4213.006.patch, HDFS-4213.007.patch, HDFS-4213.008.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/flush 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