Return-Path: X-Original-To: apmail-hadoop-general-archive@minotaur.apache.org Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B7E8BDD7B for ; Tue, 4 Sep 2012 00:31:43 +0000 (UTC) Received: (qmail 15364 invoked by uid 500); 4 Sep 2012 00:31:42 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 15256 invoked by uid 500); 4 Sep 2012 00:31:42 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 15246 invoked by uid 99); 4 Sep 2012 00:31:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2012 00:31:41 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.160.48] (HELO mail-pb0-f48.google.com) (209.85.160.48) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2012 00:31:34 +0000 Received: by pbbrq13 with SMTP id rq13so10166058pbb.35 for ; Mon, 03 Sep 2012 17:31:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:mime-version:content-type:subject:date:in-reply-to:to :references:message-id:x-mailer:x-gm-message-state; bh=yXnljf9hUfnAI5TvdW0zfMoxziIf1EFjuHvxS1XeYIQ=; b=lnZKBTLQeIxR9B+qAS8GrYiNOUrnBOM3qorO7l14AeamISwsjTY4Kn7M+Ht5xj8loq KU7DZpLqiT/H6qG2QzJ2/KzQUDzBeHYdrceqikZnJZSim+M625VqbRAgBlOTn3SlJ0LK dfGQpYuM2xOkl0co/9YZeqeL1oad2ZsxRKG2u8UPBYVedIhQD13F9g/xY6yWca+ETU91 dr2UkaIusUC2nYRQCPbSvUUH+iWgV9Jjh/0nurPL7c1D0l+Sxj8eZuWMCspTNgND2Sni 3EnYOOKty1cgNQLJvQx9XycAgMxHwFdlVDBjqhKlSTt1+qpaW1XeE/Weq0oWZYRE/4TT Wrtg== Received: by 10.68.234.99 with SMTP id ud3mr41352330pbc.166.1346718672892; Mon, 03 Sep 2012 17:31:12 -0700 (PDT) Received: from [10.0.1.10] (c-98-234-189-94.hsd1.ca.comcast.net. [98.234.189.94]) by mx.google.com with ESMTPS id gf3sm10896767pbc.74.2012.09.03.17.31.11 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 03 Sep 2012 17:31:12 -0700 (PDT) From: Arun C Murthy Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-681--955715767 Subject: Re: Large feature development (YARN vs HDFS) Date: Mon, 3 Sep 2012 17:31:11 -0700 In-Reply-To: To: general@hadoop.apache.org References: <751827D1-0353-45E3-B5AA-14E0556CDCEE@hortonworks.com> <-7917683134968972508@unknownmsgid> Message-Id: X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQlO9o3iRG7GtPbvxpGAvvxss6G4lxyJLAgZmc9NfzQ7a0NRtA6pLUJjis9XWwwoUNmjkxdR --Apple-Mail-681--955715767 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Agreed... it does seem like a case of 'my wife is prettier'. Maybe I'm oversensitive and it may even be understandable given how much = of my waking time I've devoted to YARN over the last 30 months; but I do = apologize for indulging in the behavior I accused others of. A good = night's sleep does help in clearing mists. IAC, the point I was trying = to quantify is simple - current state of YARN is far better than was = being characterized here. We should get back to discussing 'large-feature development' - thanks = for starting that discussion Steve. Arun On Sep 3, 2012, at 2:30 PM, Eric Baldeschwieler wrote: >=20 > Referring back to Chris M.s thread, this YARN vs HDFS discussion = sounds a lot like an umbrella project issue to me. >=20 > On Sep 2, 2012, at 3:11 PM, Arun Murthy wrote: >=20 >> Eli, >>=20 >> On Sep 2, 2012, at 1:01 PM, Eli Collins wrote: >>=20 >>> On Sat, Sep 1, 2012 at 12:47 PM, Arun C Murthy = wrote: >>>> Todd, >>>>=20 >>>> On Sep 1, 2012, at 1:20 AM, Todd Lipcon wrote: >>>>=20 >>>>> I'd actually contend that YARN was merged too early. I have yet to = see >>>>> anyone running YARN in production, and it's holding up the = "Stable" >>>>> moniker for Hadoop 2.0 -- HDFS-wise we are already quite stable = and >>>>> I'm seeing fewer issues in our customers running Hadoop HDFS 2 >>>>> compared to Hadoop 1-derived code. >>>>=20 >>>> You know I respect you a ton, but I'm very saddened to see you = perpetuate this FUD on our public lists. I expected better, particularly = when everyone is working towards the same goals of advancing Hadoop-2. = This sniping on other members doing work is, um, I'll just stop here = rather than regret later. >>> 2. HDFS is more mature than YARN. Not a surprise given that we all >>> agree YARN is alpha, and a much newer project than HDFS that hasn't >>> yet been deployed in production environments yet (to my knowledge). >>=20 >> Let's focus on the ground reality here. >>=20 >> Please read my (or Rajiv's) message again about YARN's current >> stability and how much it's baked, it's deployment plans to a very >> large cluster in a few *days*. Or, talk to the people developing, >> testing and supporting these customers and clusters. >>=20 >> I'll repeat - YARN has clearly baked much more than HDFS HA given >> the basic bugs (upgrade, edit logs corruption etc.) we've seen after >> being declared *done*; but then we just disagree since clearly I'm >> more conservative. Also, we need to be more conservative wrt HDFS - >> but then what would I know... >>=20 >> I'll admit it's hard to discuss with someone (or a collective) who >> just repeat themselves. Plus, I broke my own rule about email this >> weekend - so, I'll try harder. >>=20 >> Arun >=20 -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/ --Apple-Mail-681--955715767--