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 9CF3A7608 for ; Tue, 1 Nov 2011 08:20:57 +0000 (UTC) Received: (qmail 57077 invoked by uid 500); 1 Nov 2011 08:20:57 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 57037 invoked by uid 500); 1 Nov 2011 08:20:56 -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 57018 invoked by uid 99); 1 Nov 2011 08:20:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2011 08:20:55 +0000 X-ASF-Spam-Status: No, hits=-2001.2 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2011 08:20:54 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id BD3A832B731 for ; Tue, 1 Nov 2011 08:20:34 +0000 (UTC) Date: Tue, 1 Nov 2011 08:20:34 +0000 (UTC) From: "Hadoop QA (Commented) (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1084830355.44965.1320135634776.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1668676054.2706.1309927696724.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HDFS-2130) Switch default checksum to CRC32C 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-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141020#comment-13141020 ] Hadoop QA commented on HDFS-2130: --------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12501737/hdfs-2130.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 11 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 1 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hdfs.TestDataTransferProtocol org.apache.hadoop.hdfs.TestFileCreationClient org.apache.hadoop.hdfs.TestSetrepIncreasing +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/1512//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/1512//artifact/trunk/hadoop-hdfs-project/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/1512//console This message is automatically generated. > Switch default checksum to CRC32C > --------------------------------- > > Key: HDFS-2130 > URL: https://issues.apache.org/jira/browse/HDFS-2130 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: hdfs client > Reporter: Todd Lipcon > Assignee: Todd Lipcon > Attachments: hdfs-2130.txt > > > Once the other subtasks/parts of HDFS-2080 are complete, CRC32C will be a much more efficient checksum algorithm than CRC32. Hence we should change the default checksum to CRC32C. > However, in order to continue to support append against blocks created with the old checksum, we will need to implement some kind of handshaking in the write pipeline. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira