Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 47EF99244 for ; Wed, 21 Mar 2012 21:10:17 +0000 (UTC) Received: (qmail 47816 invoked by uid 500); 21 Mar 2012 21:10:16 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 47771 invoked by uid 500); 21 Mar 2012 21:10:16 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 47763 invoked by uid 99); 21 Mar 2012 21:10:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Mar 2012 21:10:16 +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 (athena.apache.org: domain of eli@cloudera.com designates 209.85.217.176 as permitted sender) Received: from [209.85.217.176] (HELO mail-lb0-f176.google.com) (209.85.217.176) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Mar 2012 21:10:10 +0000 Received: by lbom11 with SMTP id m11so1631508lbo.35 for ; Wed, 21 Mar 2012 14:09:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=V0O/wqvYgw9BHG9FKgS6lF6X0Cnx5ixLzWP1b64j5lo=; b=I6QgGosa34IZtgDUoGTOXVbwZ88oKF4kT7K6u1Yk9G7A1zm8aunvzQAKNCMLKZOUEi XLJ4MLQMGPuwKVYilqWExrGob0EpZ74cYA7N46EziTNT5uXefkPOf51byHRSVveJKeTh iDXu/XhHV/6rbfWsiwarAMY772WNeWes7jvtzazjJ+XxKrmsoXZLiT/WqnDhgY0LqL35 9uwErZjk1FMkEOVM9quB3LDlMWl2tTKuyhQ7NAKVjBfl6FrDF1stcInEGBxYWaE9a2ET Vyo77vrrsMHWVEz4YOAYJCadKr/iIcdzF41HmolTqiBWpGCveXiM5Krz/d11fCA5z1ra kS6A== MIME-Version: 1.0 Received: by 10.112.42.134 with SMTP id o6mr2135711lbl.70.1332364189338; Wed, 21 Mar 2012 14:09:49 -0700 (PDT) Received: by 10.112.102.136 with HTTP; Wed, 21 Mar 2012 14:09:49 -0700 (PDT) In-Reply-To: References: Date: Wed, 21 Mar 2012 14:09:49 -0700 Message-ID: Subject: Re: [DISCUSS] Remove append? From: Eli Collins To: hdfs-dev@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQk7t2kuJ7oYwY1ulGSGrxn76G1uLnoMTvkN7r/wYGW5V6yY//roGs/h7g08ZPSiBpGjSgP0 X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Mar 21, 2012 at 12:48 PM, wrote: > Eli, > > To clarify a little bit, I think HDFS-3120 is the right thing to do, to > disable appends, while still enabling hsync in branch-1. > > But, going forward, (say 0.23+) having appends working correctly will > definitely add value, and make HDFS more palatable for lots of other > workloads. > > Of course, I have a vested interest in this, because our team is working > on a project that requires append and truncate, and we will be testing it > thoroughly at scale in Q2 this year. Would it be okay to wait for the > results of this testing ? Absolutely, I'd like to learn more about what append/truncate buys us. Thanks, Eli > > Thanks, > > - milind > > --- > Milind Bhandarkar > Greenplum Labs, EMC > (Disclaimer: Opinions expressed in this email are those of the author, and > do not necessarily represent the views of any organization, past or > present, the author might be affiliated with.) >