Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 683EA6534 for ; Sat, 2 Jul 2011 04:07:07 +0000 (UTC) Received: (qmail 14070 invoked by uid 500); 2 Jul 2011 04:07:02 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 13518 invoked by uid 500); 2 Jul 2011 04:06:48 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 13500 invoked by uid 500); 2 Jul 2011 04:06:44 -0000 Delivered-To: apmail-hadoop-core-user@hadoop.apache.org Received: (qmail 13497 invoked by uid 99); 2 Jul 2011 04:06:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Jul 2011 04:06:42 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=FREEMAIL_FROM,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Jul 2011 04:06:36 +0000 Received: from isper.nabble.com ([192.168.236.156]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1QcrTD-00009l-44 for core-user@hadoop.apache.org; Fri, 01 Jul 2011 21:06:15 -0700 Message-ID: <31978009.post@talk.nabble.com> Date: Fri, 1 Jul 2011 21:06:15 -0700 (PDT) From: Raja Nagendra Kumar To: core-user@hadoop.apache.org Subject: HDFS custer and file trunkation time changes of last and first record corruption MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: Nagendra.Raja@tejasoft.com X-Virus-Checked: Checked by ClamAV on apache.org Hi, When a large file gets stored in HDFS with in Hadoop Clusters, would there be a chance that, when the file gets truncated, the end record of one machine and begin record of next machine cluster may get corrupted. If no, could any one pl. let me know, how each cluster would have intact records with right split happening end of a record (as recognized by EOL char) etc. Regards, Raja Nagendra Kumar, C.T.O www.tejasoft.com -Hadoop Adoption Consulting -- View this message in context: http://old.nabble.com/HDFS-custer-and-file-trunkation-time-changes-of-last-and-first-record-corruption-tp31978009p31978009.html Sent from the Hadoop core-user mailing list archive at Nabble.com.