che.org>; Uma gangumalla
<umamah...@apache.org>; Vinayakumar B <vinayakumar...@huawei.com>;
"hdfs-...@hadoop.apache.org" <hdfs-...@hadoop.apache.org>;
"user@hadoop.apache.org" <user@hadoop.apache.org>; "u...@bookkeeper.apache.org"
<u...@b
: d...@bookkeeper.apache.org; Uma gangumalla; Vinayakumar B;
hdfs-...@hadoop.apache.org; user@hadoop.apache.org; u...@bookkeeper.apache.org
Subject: Re: [DISCUSS] Retire BKJM from trunk?
For Huawei, Vinay/Brahma should know about their usage. I think after QJM
stabilized and ready they also
If I remember correctly, Huawei also adopted QJM component. I hope @Vinay
might have discussed 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,
+ Rakesh and Uma
Rakesh and Uma might have a better idea on this. I think Huawei was using
it when Rakesh and Uma worked there.
- Sijie
On Wed, Jul 27, 2016 at 12:06 PM, Chris Nauroth
wrote:
> I recommend including the BookKeeper community in this discussion. I’ve
>
I recommend including the BookKeeper community in this discussion. I’ve added
their user@ and dev@ lists to this thread.
I do not see BKJM being used in practice. Removing it from trunk would be
attractive in terms of less code for Hadoop to maintain and build, but if we
find existing users
Hi All,
BKJM was Active and made much stable when the NameNode HA was implemented
and there was no QJM implemented.
Now QJM is present and is much stable which is adopted by many production
environment.
I wonder whether it would be a good time to retire BKJM from trunk?
Are there