Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1D587200B54 for ; Thu, 28 Jul 2016 19:38:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 1BD7C160A85; Thu, 28 Jul 2016 17:38:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 141B1160A56 for ; Thu, 28 Jul 2016 19:38:07 +0200 (CEST) Received: (qmail 75463 invoked by uid 500); 28 Jul 2016 17:38:07 -0000 Mailing-List: contact user-help@bookkeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@bookkeeper.apache.org Delivered-To: mailing list user@bookkeeper.apache.org Received: (qmail 75448 invoked by uid 99); 28 Jul 2016 17:38:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jul 2016 17:38:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 8BAF1C79B0 for ; Thu, 28 Jul 2016 17:38:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -13.801 X-Spam-Level: X-Spam-Status: No, score=-13.801 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_DEF_WHITELIST=-15] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=yahoo-inc.com header.b=kOINinXr; dkim=pass (1024-bit key) header.d=yahoo-inc.com header.b=iajLY8wd Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id dKw0n-IbRU8g for ; Thu, 28 Jul 2016 17:38:04 +0000 (UTC) Received: from mrout5.yahoo.com (mrout5.yahoo.com [216.145.54.154]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id DB8405F476 for ; Thu, 28 Jul 2016 17:38:03 +0000 (UTC) Received: from omp1038.mail.ne1.yahoo.com (omp1038.mail.ne1.yahoo.com [98.138.88.238]) by mrout5.yahoo.com (8.15.2/8.15.2/y.out) with ESMTPS id u6SHbZrg004793 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 28 Jul 2016 10:37:36 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1469727456; bh=rqkLmuTkWb63UUYPIop/QMmnbnGKN3gB85XJwCzHiOQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject; b=kOINinXr9Z1Bgw5YTQOCtUSDBbbANPyNNSo+8KBbedQVRZeqUH2wIqx417UsGLw9C s0lI5ka/dOX7cVo6bgPEyIT/janH9LaFA/RGMPbrKFPg2nV9nC+AeWB9kbqdTfZHw/ PyigIc5+eQGebjeuepp9KWCHz20HTjkOGEdUe30Q= Received: (qmail 88998 invoked by uid 1000); 28 Jul 2016 17:37:35 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo-inc.com; s=ginc1024; t=1469727455; bh=TIeR9TqHca324uE7jCbEfRgmyB/L0eYDBs3cw8R4S00=; h=Date:From:Reply-To:To:Cc:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type; b=iajLY8wdDGTFFTkE3J0ju6La2wQd+0pN60HGUQKdIKtSS993Mi1swRaWQx/A5PfeWAwn+f4aDhZUzHdzNtZaDR15jyrBtSrbL6uMPRkeJDcxhdKCgKKBQyrGCx1/8YzALiBA9Inh9/hol6F4iXb5goqxmjbYLLwWg1V4qo1ypIE= X-YMail-OSG: tphw6hUVM1lkoOEFsnpc_pYqVfM2yfxFoT1VNKJwQwLNE5DerSN3mwKPqzVSCkM mILBnu_WlYigmVRLiFD.A0vMnPjicIZ3RVTkjEMEMwWSHOM6vJwAViQGkPzqIkKQrG2rMYYK8fXA XWK6idM1WOqKLKbymqfJH9zens17xkqKrCy5m6TVy5S9O9WNc2j4LrCmO8.MNAVMC0C2oxezBniE C_32uC_1q9ZZ5jilg6UbVDOQswgT9wF4eHYSu.xOn6WyBUlVP_cIdLpn_j1vjeeVf Received: from jws100240.mail.ne1.yahoo.com by sendmailws110.mail.ne1.yahoo.com; Thu, 28 Jul 2016 17:37:34 +0000; 1469727454.989 Date: Thu, 28 Jul 2016 17:37:32 +0000 (UTC) From: Kihwal Lee Reply-To: Kihwal Lee To: Brahma Reddy Battula , "Gangumalla, Uma" , Rakesh Radhakrishnan , Sijie Guo Cc: "dev@bookkeeper.apache.org" , Uma gangumalla , Vinayakumar B , "hdfs-dev@hadoop.apache.org" , "user@hadoop.apache.org" , "user@bookkeeper.apache.org" Message-ID: <1288296033.5942327.1469727453010.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: <8AD4EE147886274A8B495D6AF407DF698F114475@blreml502-mbx> References: <516863ED4DFA3149A9F907F1395E725201CD6854@blreml501-mbs> <2552173B-EF95-49B1-9CED-AC4F9E945F86@hortonworks.com> <8AD4EE147886274A8B495D6AF407DF698F114475@blreml502-mbx> Subject: Re: [DISCUSS] Retire BKJM from trunk? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_5942324_361163871.1469727453005" archived-at: Thu, 28 Jul 2016 17:38:09 -0000 ------=_Part_5942324_361163871.1469727453005 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable +1 From: Brahma Reddy Battula To: "Gangumalla, Uma" ; Rakesh Radhakrishnan ; Sijie Guo =20 Cc: "dev@bookkeeper.apache.org" ; Uma gangumalla= ; Vinayakumar B ; "hdfs-d= ev@hadoop.apache.org" ; "user@hadoop.apache.org= " ; "user@bookkeeper.apache.org" Sent: Thursday, July 28, 2016 4:21 AM Subject: RE: [DISCUSS] Retire BKJM from trunk? =20 Yes, We can remove from trunk and=C2=A0 can be deprecated in branch-2. We c= onfirmed with all the existing customers on this.. --Brahma Reddy Battula -----Original Message----- From: Gangumalla, Uma [mailto:uma.gangumalla@intel.com]=20 Sent: 28 July 2016 13:22 To: Rakesh Radhakrishnan; Sijie Guo Cc: dev@bookkeeper.apache.org; Uma gangumalla; Vinayakumar B; hdfs-dev@hado= op.apache.org; user@hadoop.apache.org; user@bookkeeper.apache.org Subject: Re: [DISCUSS] Retire BKJM from trunk? For Huawei, Vinay/Brahma should know about their usage. I think after QJM s= tabilized and ready they also adopted to QJM is what I know, but they shoul= d know more than me as I left that employer while ago. If no one is using it, It is ok to remove. Regards, Uma On 7/27/16, 9:49 PM, "Rakesh Radhakrishnan" wrote: >If I remember correctly, Huawei also adopted QJM component. I hope=20 >@Vinay might have discussed internally in Huawei before starting this=20 >e-mail discussion thread. I'm +1, for removing the bkjm contrib from=20 >the trunk code. > >Also, there are quite few open sub-tasks under HDFS-3399 umbrella jira,=20 >which was used for the BKJM implementation time. How about closing=20 >these jira by marking as "Won't Fix"? > >Thanks, >Rakesh >Intel > >On Thu, Jul 28, 2016 at 1:53 AM, Sijie Guo wrote: > >> + Rakesh and Uma >> >> Rakesh and Uma might have a better idea on this. I think Huawei was=20 >>using=C2=A0 it when Rakesh and Uma worked there. >> >> - Sijie >> >> On Wed, Jul 27, 2016 at 12:06 PM, Chris Nauroth=20 >> >> wrote: >> >> > I recommend including the BookKeeper community in this discussion. >>I=C2=B9ve >> > added their user@ and dev@ lists to this thread. >> > >> > I do not see BKJM being used in practice.=C2=A0 Removing it from trunk >>would >> be >> > attractive in terms of less code for Hadoop to maintain and build, >>but if >> > we find existing users that want to keep it, I wouldn=C2=B9t object. >> > >> > --Chris Nauroth >> > >> > On 7/26/16, 11:14 PM, "Vinayakumar B" >>wrote: >> > >> >=C2=A0 =C2=A0 Hi All, >> > >> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 BKJM was Active and made much stable when t= he NameNode HA=20 >> > was implemented and there was no QJM implemented. >> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 Now QJM is present and is much stable which= is adopted by=20 >> > many production environment. >> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 I wonder whether it would be a good time to= retire BKJM from >> trunk? >> > >> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 Are there any users of BKJM exists? >> > >> >=C2=A0 =C2=A0 -Vinay >> > >> > >> > >> --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org ------=_Part_5942324_361163871.1469727453005 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
+1
=


From: Brahma Re= ddy Battula <brahmareddy.battula@huawei.com>
To: "Gangumalla, Uma" <uma.gangumalla@intel= .com>; Rakesh Radhakrishnan <rakeshr@apache.org>; Sijie Guo <si= jie@apache.org>
Cc:= "dev@bookkeeper.apache.org" <dev@bookkeeper.apache.org>; Uma ganguma= lla <umamahesh@apache.org>; Vinayakumar B <vinayakumar.ba@huawei.c= om>; "hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>; "u= ser@hadoop.apache.org" <user@hadoop.apache.org>; "user@bookkeeper.apa= che.org" <user@bookkeeper.apache.org>
Sent: Thursday, July 28, 2016 4:21 AM
Subject: RE: [DISCUSS] Retire BKJM fr= om trunk?


Yes, We can remove fro= m trunk and  can be deprecated in branch-2. We confirmed with all the = existing customers on this..


--Brahma Reddy Battula



-----Original Message-----
From: Gangumalla, Uma [mailto:uma.gangumalla= @intel.com]
Sent: 28 July 2016 13:22
To: Rakesh Radhakrishnan; Sijie Guo
Cc: dev@bookkeeper= .apache.org; Uma gangumalla; Vinayakumar B; hdfs-dev@hadoop.apache.org; user@hadoop.= apache.org; user@bookkeeper.apache.org<= /a>
Subject: Re: [DISCUSS] Retire BKJM from trunk?

For Huawei, Vinay/Brahma should know about t= heir usage. I think after QJM stabilized and ready they also adopted to QJM= is what I know, but they should know more than me as I left that employer = while ago.

If no one is using it, It i= s ok to remove.

Regards,
Uma

On 7/27/16, 9:49 PM, "Rakesh = Radhakrishnan" <rakeshr@apache.org> wrote:

>If I remember correctly, Huawei also ado= pted QJM component. I hope
>@Vinay might have discuss= ed internally in Huawei before starting this
>e-mail = discussion thread. I'm +1, for removing the bkjm contrib from
>the trunk code.
>
>Also= , there are quite few open sub-tasks under HDFS-3399 umbrella jira,
>which was used for the BKJM implementation time. How about = closing
>these jira by marking as "Won't Fix"?
>
>Thanks,
>Rakesh=
>Intel
>
>O= n Thu, Jul 28, 2016 at 1:53 AM, Sijie Guo <sijie@apache.org<= /a>> wrote:
>
>> + Rakesh a= nd Uma
>>
>> Rakesh and Uma= might have a better idea on this. I think Huawei was
&g= t;>using  it when Rakesh and Uma worked there.
&g= t;>
>> - Sijie
>>
>> On Wed, Jul 27, 2016 at 12:06 PM, Chris Nauroth
>><cnauroth@hortonworks.c= om>
>> wrote:
>>
>> > I recommend including the BookKeeper community= in this discussion.
>>I=C2=B9ve
= >> > added their user@ and dev@ lists to this thread.
>> >
>> > I do not see BKJM being= used in practice.  Removing it from trunk
>>w= ould
>> be
>> > attracti= ve in terms of less code for Hadoop to maintain and build,
>>but if
>> > we find existing users tha= t want to keep it, I wouldn=C2=B9t object.
>> ><= br clear=3D"none">>> > --Chris Nauroth
>> = >
>> > On 7/26/16, 11:14 PM, "Vinayakumar B" = <vinayakumar.ba@huawei.com>
>>wrote:
>> >
>> >    Hi All,
>> >
>> >        BKJM was Active and ma= de much stable when the NameNode HA
>> > was im= plemented and there was no QJM implemented.
>> >=         Now QJM is present and is much stable which is = adopted by
>> > many production environment.>> >        I wonder whether i= t would be a good time to retire BKJM from
>> trunk= ?
>> >
>> >  &nb= sp;     Are there any users of BKJM exists?
>= ;> >
>> >    -Vinay
>> >
>> >
>= > >
>>

<= br clear=3D"none">---------------------------------------------------------= ------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org<= /a>
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org



----------------------------------------------------------------= -----
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.orgFor additional commands, e-mail: hdfs-dev-help@hadoop.apache.org


------=_Part_5942324_361163871.1469727453005--