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 AFDF01092B for ; Mon, 12 Aug 2013 18:38:29 +0000 (UTC) Received: (qmail 29137 invoked by uid 500); 12 Aug 2013 18:38:22 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 28983 invoked by uid 500); 12 Aug 2013 18:38:20 -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 28891 invoked by uid 99); 12 Aug 2013 18:38:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Aug 2013 18:38:19 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tucu@cloudera.com designates 209.85.216.175 as permitted sender) Received: from [209.85.216.175] (HELO mail-qc0-f175.google.com) (209.85.216.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Aug 2013 18:38:13 +0000 Received: by mail-qc0-f175.google.com with SMTP id s11so3558063qcv.6 for ; Mon, 12 Aug 2013 11:37:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=s0bkJxSNs/lSGkPoNiP2SvIBmxWajTsNrFp9Ml1PhUo=; b=CKRhZbrMVu7tMc+IEnVeEgPmiBxsZ84uMaRObwYusyS7hpW5W0dt8J+WyzHl5XSA5K b6hwjgXURT+jul5mMX/JhtM/xh6W5+/X17nb0qQ/tCKmgFnHkFogIg0NL0hoNvuKyQAU EMBwPXaK+jwLto20YU99zTWIfwQwSNnctUeappOEy+UslqblLQpYOZ5JYOaEUxhUPGTo A9hF7gobAceMk0iRXJEnPbsJWC6ojV3o6DzeD9SNlifI4zpqVMbR/Yf4jVHHEzJFQRst rc/S508NrW3+4VXvDrH0FlZwaX4xotbeZ7xmBH8RpyXfxl1Um2YOfmjKSe82Gux62W+S z6KA== X-Gm-Message-State: ALoCoQnrbO0p7tY9SG+nQ+Pk23vnSHgSQsUvZyj7bUMfy3OB1OFoh/TNK+W9UwYue9GlV3cufKoq X-Received: by 10.49.41.74 with SMTP id d10mr462017qel.81.1376332672642; Mon, 12 Aug 2013 11:37:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.49.105.72 with HTTP; Mon, 12 Aug 2013 11:37:21 -0700 (PDT) In-Reply-To: References: <1375975131.91655.YahooMailNeo@web126005.mail.ne1.yahoo.com> <3038D364-C4EC-4047-B96C-48991DB1654E@cloudera.com> From: Alejandro Abdelnur Date: Mon, 12 Aug 2013 11:37:21 -0700 Message-ID: Subject: Re: Upgrade to protobuf 2.5.0 for the 2.1.0 release, HADOOP-9845 To: "common-dev@hadoop.apache.org" Cc: "mapreduce-dev@hadoop.apache.org" , "hdfs-dev@hadoop.apache.org" , Kihwal Lee , "yarn-dev@hadoop.apache.org" Content-Type: multipart/alternative; boundary=047d7bdc7f060bc45704e3c46c87 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bdc7f060bc45704e3c46c87 Content-Type: text/plain; charset=ISO-8859-1 Giri, first of all, thanks for installing protoc 2.5.0. I didn't know we were installing them as the only version and not driven by env/path settings. Now we have a bit of a problem, precommit builds are broken because of mismatch of protoc (2.5.0) and protobuf JAR( 2.4.1). We have to options: 1* commit HADOOP-9845 that will bring protobuf to 2.5.0 and iron out any follow up issues. 2* reinstall protoc 2.4.1 in the jenkins machines and have 2.4.1 and 2.5.0 coexisting My take would be to commit HADOOP-9845 in trunk, iron out any issues an then merge it to the other branches. We need to sort this out quickly as precommits are not working. I'll wait till 3PM today for objections to option #1, if none I'll commit it to trunk. Thanks. Alejandro On Mon, Aug 12, 2013 at 11:30 AM, Giridharan Kesavan < gkesavan@hortonworks.com> wrote: > Like I said protoc is upgraded from 2.4 to 2.5. 2.5 is in the default path. > If we still need 2.4 I may have to install it. Let me know > > -Giri > > > On Sat, Aug 10, 2013 at 7:01 AM, Alejandro Abdelnur >wrote: > > > thanks giri, how do we set 2.4 or 2.5., what is the path to both so we > can > > use and env to set it in the jobs? > > > > thx > > > > Alejandro > > (phone typing) > > > > On Aug 9, 2013, at 23:10, Giridharan Kesavan > > wrote: > > > > > build slaves hadoop1-hadoop9 now has libprotoc 2.5.0 > > > > > > > > > > > > -Giri > > > > > > > > > On Fri, Aug 9, 2013 at 10:56 PM, Giridharan Kesavan < > > > gkesavan@hortonworks.com> wrote: > > > > > >> Alejandro, > > >> > > >> I'm upgrading protobuf on slaves hadoop1-hadoop9. > > >> > > >> -Giri > > >> > > >> > > >> On Fri, Aug 9, 2013 at 1:15 PM, Alejandro Abdelnur > >wrote: > > >> > > >>> pinging again, I need help from somebody with sudo access to the > hadoop > > >>> jenkins boxes to do this or to get sudo access for a couple of hours > to > > >>> set > > >>> up myself. > > >>> > > >>> Please!!! > > >>> > > >>> thx > > >>> > > >>> > > >>> On Thu, Aug 8, 2013 at 2:29 PM, Alejandro Abdelnur < > tucu@cloudera.com > > >>>> wrote: > > >>> > > >>>> To move forward with this we need protoc 2.5.0 in the apache hadoop > > >>>> jenkins boxes. > > >>>> > > >>>> Who can help with this? I assume somebody at Y!, right? > > >>>> > > >>>> Thx > > >>>> > > >>>> > > >>>> On Thu, Aug 8, 2013 at 2:24 PM, Elliott Clark > > >>> wrote: > > >>>> > > >>>>> In HBase land we've pretty well discovered that we'll need to have > > the > > >>>>> same version of protobuf that the HDFS/Yarn/MR servers are running. > > >>>>> That is to say there are issues with ever having 2.4.x and 2.5.x on > > >>>>> the same class path. > > >>>>> > > >>>>> Upgrading to 2.5.x would be great, as it brings some new classes we > > >>>>> could use. With that said HBase is getting pretty close to a > rather > > >>>>> large release (0.96.0 aka The Singularity) so getting this in > sooner > > >>>>> rather than later would be great. If we could get this into 2.1.0 > it > > >>>>> would be great as that would allow us to have a pretty easy story > to > > >>>>> users with regards to protobuf version. > > >>>>> > > >>>>> On Thu, Aug 8, 2013 at 8:18 AM, Kihwal Lee > > >>> wrote: > > >>>>>> Sorry to hijack the thread but, I also wanted to mention Avro. See > > >>>>> HADOOP-9672. > > >>>>>> The version we are using has memory leak and inefficiency issues. > > >>> We've > > >>>>> seen users running into it. > > >>>>>> > > >>>>>> Kihwal > > >>>>>> > > >>>>>> > > >>>>>> ________________________________ > > >>>>>> From: Tsuyoshi OZAWA > > >>>>>> To: "common-dev@hadoop.apache.org" > > >>>>>> Cc: "hdfs-dev@hadoop.apache.org" ; " > > >>>>> yarn-dev@hadoop.apache.org" ; " > > >>>>> mapreduce-dev@hadoop.apache.org" > > >>>>>> Sent: Thursday, August 8, 2013 1:59 AM > > >>>>>> Subject: Re: Upgrade to protobuf 2.5.0 for the 2.1.0 release, > > >>>>> HADOOP-9845 > > >>>>>> > > >>>>>> > > >>>>>> Hi, > > >>>>>> > > >>>>>> About Hadoop, Harsh is dealing with this problem in HADOOP-9346. > > >>>>>> For more detail, please see the JIRA ticket: > > >>>>>> https://issues.apache.org/jira/browse/HADOOP-9346 > > >>>>>> > > >>>>>> - Tsuyoshi > > >>>>>> > > >>>>>> On Thu, Aug 8, 2013 at 1:49 AM, Alejandro Abdelnur < > > >>> tucu@cloudera.com> > > >>>>> wrote: > > >>>>>>> I' like to upgrade to protobuf 2.5.0 for the 2.1.0 release. > > >>>>>>> > > >>>>>>> As mentioned in HADOOP-9845, Protobuf 2.5 has significant > benefits > > >>> to > > >>>>>>> justify the upgrade. > > >>>>>>> > > >>>>>>> Doing the upgrade now, with the first beta, will make things > easier > > >>> for > > >>>>>>> downstream projects (like HBase) using protobuf and adopting > Hadoop > > >>> 2. > > >>>>> If > > >>>>>>> we do the upgrade later, downstream projects will have to > support 2 > > >>>>>>> different versions and they my get in nasty waters due to > classpath > > >>>>> issues. > > >>>>>>> > > >>>>>>> I've locally tested the patch in a pseudo deployment of > 2.1.0-beta > > >>>>> branch > > >>>>>>> and it works fine (something is broken in trunk in the RPC layer > > >>>>> YARN-885). > > >>>>>>> > > >>>>>>> Now, to do this it will require a few things: > > >>>>>>> > > >>>>>>> * Make sure protobuf 2.5.0 is available in the jenkins box > > >>>>>>> * A follow up email to dev@ aliases indicating developers should > > >>>>> install > > >>>>>>> locally protobuf 2.5.0 > > >>>>>>> > > >>>>>>> Thanks. > > >>>>>>> > > >>>>>>> -- > > >>>>>>> Alejandro > > >>>> > > >>>> > > >>>> > > >>>> -- > > >>>> Alejandro > > >>> > > >>> > > >>> > > >>> -- > > >>> Alejandro > > >> > > >> > > > -- Alejandro --047d7bdc7f060bc45704e3c46c87--