Return-Path: 
 <common-user-return-31254-apmail-hadoop-common-user-archive=hadoop.apache.org@hadoop.apache.org>
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 8C95F73CB
	for <apmail-hadoop-common-user-archive@www.apache.org>;
 Sat, 19 Nov 2011 09:16:08 +0000 (UTC)
Received: (qmail 85924 invoked by uid 500); 19 Nov 2011 09:16:05 -0000
Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org
Received: (qmail 85848 invoked by uid 500); 19 Nov 2011 09:16:05 -0000
Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-user@hadoop.apache.org>
List-Id: <common-user.hadoop.apache.org>
Reply-To: common-user@hadoop.apache.org
Delivered-To: mailing list common-user@hadoop.apache.org
Received: (qmail 85834 invoked by uid 99); 19 Nov 2011 09:16:05 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Nov 2011 09:16:05 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of harsh@cloudera.com designates
 209.85.210.176 as permitted sender)
Received: from [209.85.210.176] (HELO mail-iy0-f176.google.com)
 (209.85.210.176)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Nov 2011 09:15:57 +0000
Received: by iakh37 with SMTP id h37so6530479iak.35
        for <multiple recipients>; Sat, 19 Nov 2011 01:15:36 -0800 (PST)
Received: by 10.42.135.66 with SMTP id o2mr6180138ict.0.1321694136679;
        Sat, 19 Nov 2011 01:15:36 -0800 (PST)
Received: from [192.168.1.23] ([59.92.62.52])
        by mx.google.com with ESMTPS id g16sm14320620ibs.8.2011.11.19.01.15.33
        (version=TLSv1/SSLv3 cipher=OTHER);
        Sat, 19 Nov 2011 01:15:35 -0800 (PST)
Subject: Re: How many files can a hdfs client can access simultaneously
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Harsh J <harsh@cloudera.com>
In-Reply-To: 
 <CANAqB2hOQ=q1O+PwdB9oR6-qauZaB0sqndk+5=_iOgnGGa-gdw@mail.gmail.com>
Date: Sat, 19 Nov 2011 14:45:24 +0530
Cc: hdfs-user@hadoop.apache.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D4173EBF-0D76-4CC0-930C-4D12058F2D93@cloudera.com>
References: 
 <CANAqB2heL+dA3QfAM6rfgUFhc31QCgpPHa8qgsT2r_JWcQnNqQ@mail.gmail.com>
 <8619A7C1-7771-40D5-9F10-FB16949A6D2C@cloudera.com>
 <CANAqB2hOQ=q1O+PwdB9oR6-qauZaB0sqndk+5=_iOgnGGa-gdw@mail.gmail.com>
To: common-user@hadoop.apache.org
X-Mailer: Apple Mail (2.1084)
X-Virus-Checked: Checked by ClamAV on apache.org

Oops, s/you're/you. I rephrased half-way.

On 19-Nov-2011, at 2:02 PM, kartheek muthyala wrote:

> Thanks harsh for the confirmation and for referring me to this dl. :)
>=20
> On Sat, Nov 19, 2011 at 12:20 PM, Harsh J <harsh@cloudera.com> wrote:
>=20
>> Kartheek,
>>=20
>> (Moving to hdfs-user@. Bcc'd common-user@. Please use the right lists =
for
>> reaching to the proper audience :))
>>=20
>> Writing multiple files from a single DFS client instance should not =
be a
>> problem at all. You get one output stream per file creation, leaving =
you're
>> free to write to a number of them in parallel and to also expect an =
amount
>> of gain.
>>=20
>> On 19-Nov-2011, at 11:26 AM, kartheek muthyala wrote:
>>=20
>>> Hi all,
>>> I know that while writing the file, a hdfs client writes the blocks =
in
>>> sequential fashion, writing one block only at one time and when this
>> block
>>> is acknowledged as a complete write then the next block write =
happens.
>> But
>>> can a hdfs client write two or three files at a same time, ideally =
it
>>> should do, can i get a confirmation on this?
>>> ~Kartheek
>>=20
>>=20