Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ACDF99991 for ; Tue, 8 Nov 2011 08:42:32 +0000 (UTC) Received: (qmail 31915 invoked by uid 500); 8 Nov 2011 08:42:31 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 31835 invoked by uid 500); 8 Nov 2011 08:42:31 -0000 Mailing-List: contact hdfs-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-user@hadoop.apache.org Delivered-To: mailing list hdfs-user@hadoop.apache.org Received: (qmail 31827 invoked by uid 99); 8 Nov 2011 08:42:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Nov 2011 08:42:31 +0000 X-ASF-Spam-Status: No, hits=-0.6 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of donal0412@gmail.com designates 209.85.210.50 as permitted sender) Received: from [209.85.210.50] (HELO mail-pz0-f50.google.com) (209.85.210.50) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Nov 2011 08:42:23 +0000 Received: by pzk4 with SMTP id 4so829626pzk.9 for ; Tue, 08 Nov 2011 00:42:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=7VbeIKNVw6ABlgYYVvfxzmVZeh/cSPbLt4QgayCg8dk=; b=eYJ8TuE+ooeRwVa8IsgQ1od1igdaGRIpNOVUR3Yt6vt3EMZYD9YdfDlQmf1AZY1vcg OS0MLrVoaKDAj+PcnHv7eK8MRDAeSWx/+mFkObaSlv4bzmTo4AfSSHEvlVJp5Epa2wC5 49vQ1wKwochUme6xpUYr8OqB8u8+m5xH9bDhc= Received: by 10.68.62.136 with SMTP id y8mr5963325pbr.87.1320741723167; Tue, 08 Nov 2011 00:42:03 -0800 (PST) Received: from [192.168.32.57] (gwfw.ihep.ac.cn. [202.122.32.131]) by mx.google.com with ESMTPS id s4sm2626396pbq.8.2011.11.08.00.42.00 (version=SSLv3 cipher=OTHER); Tue, 08 Nov 2011 00:42:02 -0800 (PST) Message-ID: <4EB8EB58.5090607@gmail.com> Date: Tue, 08 Nov 2011 16:42:00 +0800 From: donal0412 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: harsh@cloudera.com, tdunning@maprtech.com CC: hdfs-user@hadoop.apache.org Subject: Re: dfs.write.packet.size set to 2G References: <4EB8DB0D.8020400@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Thanks! That's exactly what I want. And Ted, what do you mean by "snapshots and mirrors" ? On 2011/11/8 16:21, Harsh J wrote: > Block sizes are per-file, not permanently set on the HDFS. So create > your files with a sufficiently large block size (2G is OK if it fits > your usecase well). This way you won't have block splits, as you > desire. > > For example, to upload a file via the shell with a tweaked blocksize, I'd do: > > hadoop dfs -Ddfs.block.size=2147483648 -copyFromLocal localFile remoteFile > > Packet sizes are not what you want to tweak here. > > On Tue, Nov 8, 2011 at 1:02 PM, donal0412 wrote: >> Hi, >> I want to store lots of files in HDFS, the file size is<= 2G. >> I don't want the file to split into blocks,because I need the whole file >> while processing it, and I don't want to transfer blocks to one node when >> processing it. >> A easy way to do this would be set dfs.write.packet.size to 2G, I wonder if >> some one has similar experiences or known whether this is practicable. >> Will there be performance problems when set the packet size to a big number? >> >> Thanks! >> donal >> > >