Re: [VOTE] The fourth hbase-2.0.0-beta-1 Release Candidate is available for download

[Guanghao Zhang]

+1 (no-binding)

hbase-2.0.0-beta-1-bin.tar.gz (jdk8u144)
- Verified md5sum: ok
- Start HBase in standalone mode: ok
- Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
- Checked master/regionserver/region Web UI: ok

hbase-2.0.0-beta-1-src.tar.gz (jdk8u144)
- Verified md5sum: ok
- Build tarball: ok
- Start HBase in standalone mode: ok
- Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
- Checked master/regionserver/region Web UI: ok


2018-01-13 12:57 GMT+08:00 Stack :

> +1
>
> Checked sig and hash.
> Downloaded locally. Undid and loaded data. Logs look good.
> Put on cluster. Picks up old data fine. Nothing odd in logs (too much
> logging but that is another story).
>
> St.Ack
>
> On Fri, Jan 12, 2018 at 8:48 PM, Stack  wrote:
>
> > The fourth release candidate for HBase 2.0.0-beta-1 is up at:
> >
> >   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-1-RC3/
> >
> > Maven artifacts are available from a staging directory here:
> >
> >   https://repository.apache.org/content/repositories/orgapachehbase-1193
> >
> > All was signed with my key at 8ACC93D2 [1].
> >
> > I tagged the RC as 2.0.0-beta-1-RC1.7 at hash 026f535a7747b89003252ded9
> > 585e827686aa79f
> >
> > This RC has some nice bug fixes over RC0-2 including fixing MOST of the
> > failing and flakey tests (We are still working through them).
> >
> > hbase-2.0.0-beta-1 is our first beta release. It includes all that was in
> > previous alphas (new assignment manager, offheap read/write path,
> in-memory
> > compactions, etc.). The APIs and feature-set are sealed.
> >
> > hbase-2.0.0-beta-1 is a not-for-production preview of hbase-2.0.0. It is
> > meant for devs and downstreamers to test drive and flag us if we messed
> up
> > on anything ahead of our rolling GAs. We are particular interested in
> > hearing from Coprocessor developers.
> >
> > The list of features addressed in 2.0.0 so far can be found here [3].
> > There are thousands. The list of ~2k+ fixes in 2.0.0 exclusively can be
> > found here [4] (My JIRA JQL foo is a bit dodgy -- forgive me if
> mistakes).
> >
> > I've updated our overview doc. on the state of 2.0.0 [6]. We'll do one
> > more beta before we put up our first 2.0.0 Release Candidate by the end
> of
> > January, 2.0.0-beta-2. Its focus will be making it so users can do a
> > rolling upgrade on to hbase-2.x from hbase-1.x (and any bug fixes found
> > running beta-1). Here is the list of what we have targeted so far for
> > beta-2 [5]. Check it out.
> >
> > One known issue is that the User API has not been properly filtered so it
> > shows more than just InterfaceAudience Public content (HBASE-19663, to be
> > fixed by beta-2).
> >
> > Please take this beta for a spin. Please vote on whether it ok to put out
> > this RC as our first beta (Note CHANGES has not yet been updated). Let
> the
> > VOTE be open for 72 hours (Lets say Tuesday morning!)
> >
> > Thanks,
> > Your 2.0.0 Release Manager
> >
> > 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> > 3. https://goo.gl/scYjJr
> > 4. https://goo.gl/dFFT8b
> > 5. https://issues.apache.org/jira/projects/HBASE/versions/12340862
> > 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
> > z9iEu_ktczrlKHK8N4SZzs/
> >
>

Re: [DISCUSS] A Problem When Start HBase Cluster Using Table Based Replication

[Guanghao Zhang]

>From a more general perspective, this may be a general problem as we may
move more and more data from zookeeper to system table. Or we may have more
features to create new system table. But if the RS relays some system table
to start up, we will meet a dead lock...

One solution is let master to serve system table only. So the cluster
startup will have two step. First startup master to serve system table.
Then start region servers. But the problem is master will have
more responsibility and may be a bottleneck.

Another solution is break RS startup progress to two steps. First step is
"serve system table only". Second step is "totally startup and serve any
tables". It means we will import a new state for RS startup. A RS's startup
progress will be STOPPED ==> SYSTEM-TABLE-ONLY ==> STARTED. But this may
need more refactor for our RS code.

Thanks.

2018-03-15 15:57 GMT+08:00 张铎(Duo Zhang) :

> Oh, it should be 'The replication peer related data is small'.
>
> 2018-03-15 15:56 GMT+08:00 张铎(Duo Zhang) :
>
> > I think this is a bit awkward... A region server even does not need the
> > meta table to be online when starting, but it needs another system table
> > when starting...
> >
> > I think unless we can make the regionserver start without replication,
> and
> > initialize it later, otherwise we can not break the tie. Having a special
> > 'region server' seems a bad smell to me. What's the advantage comparing
> to
> > zk?
> >
> > BTW, I believe that we only need the ReplicationPeerStorage to be
> > available when starting a region server, so we can keep this data in zk,
> > and storage the queue related data to hbase:replication table? The
> > replication related data is small so I think this is OK.
> >
> > Thanks.
> >
> > 2018-03-15 14:55 GMT+08:00 OpenInx :
> >
> >> Hi :
> >>
> >> (Paste from https://issues.apache.org/jira/browse/HBASE-20166?
> >> focusedCommentId=16399886&page=com.atlassian.jira.
> >> plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16399886)
> >>
> >> There's a really big problem here if we use table based replication to
> >> start a hbase cluster:
> >>
> >> For HMaster process, it works as following:
> >> 1. Start active master initialization .
> >> 2. Master wait rs report in .
> >> 3. Master assign meta region to one of the region servers .
> >> 4. Master create hbase:replication table if not exist.
> >>
> >> But the RS need to finish initialize the replication source & sink
> before
> >> finish startup( and the initialization of replication source & sink must
> >> finish before opening region, because we need to listen the wal event,
> >> otherwise our replication may lost data), and when initialize the
> source &
> >> sink , we need to read hbase:replication table which hasn't been
> avaiable
> >> because our master is waiting rs to be OK, and the rs is waiting
> >> hbase:replication to be OK ... a dead loop happen again ...
> >>
> >> After discussed with Guanghao Zhang offline, I'm considering that try to
> >> assign all system table to a rs which only accept regions of system
> table
> >> assignment (The rs will skip to initialize the replication source or
> sink
> >> )...
> >>
> >> I've tried to start a mini cluster by setting
> >> hbase.balancer.tablesOnMaster.systemTablesOnly=true
> >> & hbase.balancer.tablesOnMaster=true , it seems not work. because
> >> currently
> >> we initialize the master logic firstly, then region logic for the
> HMaster
> >> process, and it should be ...
> >>
> >>
> >> Any  suggestion  ?
> >>
> >
> >
>

Re: [DISCUSS] A Problem When Start HBase Cluster Using Table Based Replication

[Guanghao Zhang]

>
> We've done the work to make sure hbase:meta
> is up before everything else. It has its own WALs so we can split these
> ahead of user-space WALs, and so on. We've not done the work to for
> hbase:replication or hbase:namespace, hbase:acl... etc.

If we import a new SYSTEM-TABLE-ONLY state for region server startup, then
it is necessary to own WALs for all system tables (not only hbase:meta).
All system tables have their own wal and split these ahead of user-space
WALs. And the WAL of system tables no need replication. So we can start a
region server without replication. After all system table online, region
server can continue start from SYSTEM-TABLE-ONLY to STARTED.

Thanks.

2018-03-16 10:12 GMT+08:00 OpenInx :

> The HBASE-15867 will not be introduced into 2.0.0,   I expect to introduce
> in 2.1.0 release .
>
> Thanks.
>
> On Fri, Mar 16, 2018 at 12:45 AM, Mike Drob  wrote:
>
> > I'm also +1 for splitting RS startup into multiple steps.
> >
> > Looking at the linked JIRA and the parent issue it was not immediately
> > apparent if this is an issue for 2.0 or not - can somebody clarify?
> >
> > On Thu, Mar 15, 2018 at 5:14 AM, 张铎(Duo Zhang) 
> > wrote:
> >
> > > I'm +1 on the second solution.
> > >
> > > 2018-03-15 16:59 GMT+08:00 Guanghao Zhang :
> > >
> > > > From a more general perspective, this may be a general problem as we
> > may
> > > > move more and more data from zookeeper to system table. Or we may
> have
> > > more
> > > > features to create new system table. But if the RS relays some system
> > > table
> > > > to start up, we will meet a dead lock...
> > > >
> > > > One solution is let master to serve system table only. So the cluster
> > > > startup will have two step. First startup master to serve system
> table.
> > > > Then start region servers. But the problem is master will have
> > > > more responsibility and may be a bottleneck.
> > > >
> > > > Another solution is break RS startup progress to two steps. First
> step
> > is
> > > > "serve system table only". Second step is "totally startup and serve
> > any
> > > > tables". It means we will import a new state for RS startup. A RS's
> > > startup
> > > > progress will be STOPPED ==> SYSTEM-TABLE-ONLY ==> STARTED. But this
> > may
> > > > need more refactor for our RS code.
> > > >
> > > > Thanks.
> > > >
> > > > 2018-03-15 15:57 GMT+08:00 张铎(Duo Zhang) :
> > > >
> > > > > Oh, it should be 'The replication peer related data is small'.
> > > > >
> > > > > 2018-03-15 15:56 GMT+08:00 张铎(Duo Zhang) :
> > > > >
> > > > > > I think this is a bit awkward... A region server even does not
> need
> > > the
> > > > > > meta table to be online when starting, but it needs another
> system
> > > > table
> > > > > > when starting...
> > > > > >
> > > > > > I think unless we can make the regionserver start without
> > > replication,
> > > > > and
> > > > > > initialize it later, otherwise we can not break the tie. Having a
> > > > special
> > > > > > 'region server' seems a bad smell to me. What's the advantage
> > > comparing
> > > > > to
> > > > > > zk?
> > > > > >
> > > > > > BTW, I believe that we only need the ReplicationPeerStorage to be
> > > > > > available when starting a region server, so we can keep this data
> > in
> > > > zk,
> > > > > > and storage the queue related data to hbase:replication table?
> The
> > > > > > replication related data is small so I think this is OK.
> > > > > >
> > > > > > Thanks.
> > > > > >
> > > > > > 2018-03-15 14:55 GMT+08:00 OpenInx :
> > > > > >
> > > > > >> Hi :
> > > > > >>
> > > > > >> (Paste from https://issues.apache.org/jira/browse/HBASE-20166?
> > > > > >> focusedCommentId=16399886&page=com.atlassian.jira.
> > > > > >> plugin.system.issuetabpanels%3Acomment-tabpanel#comment-
> 16399886)
> > > > > >>
> > > > > >> There's a really big problem here if we use table based
>

Re: [ANNOUNCE] Please welcome Francis Liu to the HBase PMC

[Guanghao Zhang]

Congratulations!

2018-04-12 5:49 GMT+08:00 Sean Busbey :

> Congrats Francis!
>
> On Wed, Apr 11, 2018 at 3:03 PM, Andrew Purtell 
> wrote:
> > On behalf of the Apache HBase PMC I am pleased to announce that Francis
> > Liu has accepted our invitation to become a PMC member on the Apache
> > HBase project. We appreciate Francis stepping up to take more
> > responsibility in the HBase project. He has been an active contributor to
> > HBase for many years and recently took over responsibilities as branch RM
> > for branch-1.3.
> >
> > Please join me in welcoming Francis to the HBase PMC!
> >
> > --
> > Best regards,
> > Andrew
>

Re: On the 2.1.0 and 3.0.0 release

[Guanghao Zhang]

Why 2.1 doesn't contatin synchronous replication? This can be a experiment
feature in 2.1?

2018-05-07 14:41 GMT+08:00 张铎(Duo Zhang) :

> 2018-05-07 14:38 GMT+08:00 Chia-Ping Tsai :
>
> > > As I volunteered to be the release manager for the 2.1 release line so
> > let
> > > me bring this up.
> > +1 to Duo be RM of 2.1 release.
> >
> > > disabled from 2.0.0 release, for example, serial replication, and in
> > memory compaction
> > IIRC, in memory compaction is enabled in 2.0 and the default policy is
> > BASIC. (please correct me if I misunderstand something.)
> >
> We disabled it by default in the end due to some performance issues...
>
> >
> > > For the 2.1 release line, I would like to define it as the 'real' 2.x
> > Seems the release date between 2.0 and 2.1 will be very close. Is it
> > related to our new release plan? (IIRC, Andrew had suggested some great
> > release plan based time. But I fail to find the thread...)
> >
> > > And for the 3.0.0 release, I think the new features should be decided
> > ASAP.
> > > We need to avoid the same thing happens again, i.e, spending 2 years to
> > > release a major version...
> > agreed!
> >
> > On 2018/05/07 00:52:07, 张铎(Duo Zhang)  wrote:
> > > As I volunteered to be the release manager for the 2.1 release line so
> > let
> > > me bring this up.
> > >
> > > For the 2.1 release line, I would like to define it as the 'real' 2.x
> > > version of HBase. It should include the features which are reverted or
> > > disabled from 2.0.0 release, for example, serial replication, and in
> > memory
> > > compaction. And also, the performance issues. And no more new features.
> > If
> > > no objections, I will start the release work soon.
> > >
> > > And for the 3.0.0 release, I think the new features should be decided
> > ASAP.
> > > We need to avoid the same thing happens again, i.e, spending 2 years to
> > > release a major version...
> > >
> > > For now, the new features
> > > Synchronous replication
> > > CCSMap
> > > Backup
> > > Spark connector(is it still active?)
> > >
> > > And I suggest that we include this:
> > > The read path refactoring(HBASE-20525)
> > >
> > > Suggestions are welcomed.
> > >
> > > Thanks.
> > >
> >
>

Re: [ANNOUNCE] New HBase committer Guangxu Cheng

[Guanghao Zhang]

Congratulations!

2018-06-05 9:29 GMT+08:00 OpenInx :

> Congratulations!
>
> On Mon, Jun 4, 2018 at 6:16 PM, ashish singhi 
> wrote:
>
> > Congrats and Welcome!
> >
> > Regards,
> > Ashish
> > -Original Message-
> > From: 张铎(Duo Zhang) [mailto:palomino...@gmail.com]
> > Sent: Monday, June 04, 2018 12:30 PM
> > To: HBase Dev List ; hbase-user <
> > u...@hbase.apache.org>
> > Subject: [ANNOUNCE] New HBase committer Guangxu Cheng
> >
> > On behalf of the Apache HBase PMC, I am pleased to announce that Guangxu
> > Cheng has accepted the PMC's invitation to become a committer on the
> > project. We appreciate all of Guangxu's generous contributions thus far
> and
> > look forward to his continued involvement.
> >
> > Congratulations and welcome, Guangxu!
> >
>

Re: [VOTE] Merge branch HBASE-19064 back to master

[Guanghao Zhang]

+1

2018-06-21 18:26 GMT+08:00 mengli721014 on 163 dot com :

> 0
>
> 使用AquaMail for Android发送
> http://www.aqua-mail.com
>
>
>
> 在 2018年6月21日 下午4:21:26 "张铎(Duo Zhang)"  写道:
>
> In HBASE-19064 we aim to implement sync replication feature for HBase. You
>> can see the design doc for more details on how it works
>>
>> https://docs.google.com/document/d/193D3aOxD-muPIZuQfI4Zo3_
>> qg6-Nepeu_kraYJVQkiE/edit#
>>
>> And now the feature basically works, we have tested it on real clusters,
>> and also provide the operational documentation in the ref guide. You can
>> see the 'Synchronous Replication' section in the ref guide of branch
>> HBASE-19064.
>>
>> There are known limitations for this feature, and we have
>> created HBASE-20422 to track them.
>>
>> Please vote:
>> [+1] Agree
>> [-1] Disagree
>> [0] Neutral
>>
>> Thanks.
>>
>>
>
>
>

Re: [ANNOUNCE] New HBase committer Reid Chan

[Guanghao Zhang]

Congratulations！

2018-06-26 16:50 GMT+08:00 Yu Li :

> Congratulations and welcome, Reid!
>
> Best Regards,
> Yu
>
> On 26 June 2018 at 15:14, Nihal Jain  wrote:
>
> > Congrats :)
> >
> > On Tue 26 Jun, 2018, 12:22 PM OpenInx,  wrote:
> >
> > > Congratulations and welcome !
> > >
> > > On Tue, Jun 26, 2018 at 2:48 PM, 张铎(Duo Zhang) 
> > > wrote:
> > >
> > > >  Congratulations!
> > > >
> > > > 2018-06-26 14:44 GMT+08:00 Pankaj kr :
> > > >
> > > > > Congratulations Reid Chan..!!
> > > > >
> > > > > Regards,
> > > > > Pankaj Kumar
> > > > > Technical Project Leader
> > > > > Enterprise Intelligence, IT&Cloud BU
> > > > >
> > > > > Huawei Technologies India Pvt. Ltd.
> > > > > Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
> > > > > Bengaluru-560066, Karnataka
> > > > > Tel: + 91-80-49160700 Ext. 71678, Mob: 9535197664,  Email:
> > > > > pankaj...@huawei.com
> > > > >
> > > > > 
> > > > > __
> > > > > This e-mail and its attachments contain confidential information
> from
> > > > > HUAWEI, which
> > > > > is intended only for the person or entity whose address is listed
> > > above.
> > > > > Any use of the
> > > > > information contained herein in any way (including, but not limited
> > to,
> > > > > total or partial
> > > > > disclosure, reproduction, or dissemination) by persons other than
> the
> > > > > intended
> > > > > recipient(s) is prohibited. If you receive this e-mail in error,
> > please
> > > > > notify the sender by
> > > > > phone or email immediately and delete it!
> > > > >
> > > > >
> > > > > -Original Message-
> > > > > From: Chia-Ping Tsai [mailto:chia7...@gmail.com]
> > > > > Sent: Tuesday, June 26, 2018 9:59 AM
> > > > > To: dev@hbase.apache.org; 陳浩駿 
> > > > > Subject: [ANNOUNCE] New HBase committer Reid Chan
> > > > >
> > > > > On behalf of the Apache HBase PMC, I am pleased to announce that
> Reid
> > > > Chan
> > > > > has accepted the PMC's invitation to become a committer on the
> > project.
> > > > We
> > > > > appreciate all of Reid’s generous contributions thus far and look
> > > forward
> > > > > to his continued involvement.
> > > > >
> > > > > Congratulations and welcome, Reid!
> > > > >
> > > > > --
> > > > > Chia-Ping
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] Second release candidate for HBase 2.1.0 (RC1) is available

[Guanghao Zhang]

+1 (binding)

hbase-2.1.0-bin.tar.gz (jdk1.8.0_171)
- Verified sha512: ok
- Start HBase in standalone mode: ok
- Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
- Checked master/regionserver/region Web UI: ok

hbase-2.1.0-src.tar.gz (jdk1.8.0_171)
- Verified sha512: ok
- Build tarball: ok
- Start HBase in standalone mode: ok
- Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
- Checked master/regionserver/region Web UI: ok


2018-07-17 10:47 GMT+08:00 张铎(Duo Zhang) :

> Only one day left. We need more votes here.
>
> Thanks.
>
> 2018-07-14 3:28 GMT+08:00 Josh Elser :
>
> > +1 (binding)
> >
> > * All tests passed locally on the first try (wow)
> > * xsums/sigs are good
> > * KEYS is updated
> > * Compat report looks OK
> >
> >
> > On 7/10/18 9:09 PM, 张铎(Duo Zhang) wrote:
> >
> >> The second release candidate for Apache HBase 2.1.0 is available for
> >> downloading and testing.
> >>
> >> Artifacts and compatibility report are available here:
> >>
> >> https://dist.apache.org/repos/dist/dev/hbase/2.1.0RC1/
> >>
> >> Notice that due to HBASE-19735, now we have a
> >> hbase-2.1.0-client-bin.tar.gz, which contains a reduced set of
> >> dependencies
> >> for client.
> >>
> >> Maven artifacts are available in the staging repository at:
> >>
> >> https://repository.apache.org/content/repositories/orgapachehbase-1225
> >>
> >> All artifacts are signed with my signing key 9AD2AE49, which is also in
> >> the
> >> project KEYS file at
> >>
> >> http://www.apache.org/dist/hbase/KEYS
> >>
> >> These artifacts were tagged 2.1.0RC1 at hash
> >> e1673bb0bbfea21d6e5dba73e013b09b8b49b89b.
> >>
> >> There are 245 issues resolved since 2.0.0. Some new features are:
> >>
> >> 1. Procedure v2 based replication peer modification. The advantage here
> is
> >> that all the replication peer modification will be synchronous, which
> >> means
> >> after the you come back from the call, you can make sure that all the
> >> region servers have loaded the changes. Please see HBASE-19397 for more
> >> details.
> >> 2. Serial Replication. Now in replication we can make sure the order of
> >> pushing logs is same as the order of requests from client. Please see
> >> HBASE-20046 and HBASE-9465 for more details.
> >>
> >> For other important changes:
> >> 1. The minimum hadoop version has been changed to 2.7.1.
> >> 2. We have successfully done a rolling upgrade from 1.4.3 to 2.1.0 which
> >> shows that rolling upgrade from 1.x to 2.x is possible. Notice that this
> >> is
> >> only a experimental feature, as there are likely uncovered corner cases
> in
> >> our limited test. See
> >> http://hbase.apache.org/book.html#upgrade2.0.rolling.upgrades for more
> >> details.
> >>
> >> And HBASE-20862 has fixed the compatibility issues. You can read the
> >> issues
> >> for more details about the compatibility between 2.0.0 and 2.1.0.
> >>
> >> For all the changes, please see the CHANGES.md and RELEASENOTES.md.
> >>
> >> Please take a few minutes to verify the release and vote on releasing
> it:
> >>
> >> [ ] +1 Release this package as Apache HBase 2.1.0
> >> [ ] +0 No opinion
> >> [ ] -1 Do not release this package because...
> >>
> >> The vote will be closed at next Tuesday, 7.17.
> >>
> >> Thanks to the myriad who have helped out with this release,
> >> Your 2.1.0 Release Manager
> >>
> >>
>

Re: Recent trend in JIRA management

[Guanghao Zhang]

So only branch-2.0 need RM's approval. For other release
branchs(1.2/1.3/1.4/2.1), they are same with trunk branch and only need one
+1 from a committer, right?

2018-07-24 7:37 GMT+08:00 Stack :

> On Mon, Jul 23, 2018 at 3:44 PM Josh Elser  wrote:
>
> > I've been operating under the "get approval" for branch-2.0 since it was
> > explicitly asked for.
> >
> >
> Thanks.
>
>
>
> > @Stack you still want to operate in that manner since we're chatting
> > about this?
> >
>
>
> Yeah. Please continue to *synchronize* on me. I want to have final-say on
> all that goes into branch-2.0. I have a hard-won understanding of the
> general state of this branch and want to keep it in a condition whereby it
> continues to pass all nightlies on both hadoop2 and hadoop3. I've been
> running tests on a small cluster and have developed understandings around
> current perf and scale facility. I am also trying to practice an
> important-bug-fixes-only in branch-2.0 policy -- *No Surprises!* -- and
> find that my notion of what is an important bug-fix doesn't always jibe
> with what others think (smile). In a few cases, i want to try the patch
> under load before committing.
>
> I'm working in this manner because I do not have the bandwidth to do random
> spelunking of test/perf or ITBLL failures and so anyone who takes up hbase2
> can be sure there'll be *No Surprises!* on upgrade. I think this tight-hold
> on the reins appropriate early in the life of a new major release where we
> are trying to earn and keep the trust of users who are thinking of making
> the leap from hbase1 to hbase2.
>
> While this is a little out of line w/ Andrew's lockless, approach,
> hopefully I've explained why this approach. Otherwise, +1 on Andrew's ask
> for rolling patches back through all branches and an end to chaotic
> JIRA'ing. It is pain enough already doing branch compares and if
> well-behaved in JIRA, yetus scripts have a chance at automating much of the
> RM drudgery.
>
> S
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> > On 7/23/18 3:47 PM, Andrew Purtell wrote:
> > > Thanks for the great question.
> > >
> > > I can't speak for every RM, but I believe the answer in general is no,
> > you
> > > do not need to get the RM's approval. Personally, I only ask that
> > > committers hold off when trying to make a release, and only if I need
> > time
> > > to stabilize the unit tests on a branch. Normally I do a CTR like
> review
> > > over the commit history in the branch since the last release, and often
> > > only in response to unit test failures or API compatibility check
> errors.
> > >
> > > I would encourage everyone on the project to avoid coordination where
> > > possible. Coordination is expensive. Use lock free design principles
> for
> > > both the software and community practices.
> > >
> > >
> > >
> > > On Mon, Jul 23, 2018 at 12:42 PM Huaxiang Sun
>  > >
> > > wrote:
> > >
> > >> Thanks Andrew for bringing this up. I have one following up question.
> > >> When pushing to 1.2/1.3/1.4, do we need to get RM's approval?
> > >>
> > >> Huaxiang
> > >>
> > >>> On Jul 23, 2018, at 12:24 PM, Andrew Purtell 
> > >> wrote:
> > >>>
> > >>> I forgot to mention if a commit is only made to master, then the RM
> who
> > >>> happens to be looking at history has to take on the task of
> backporting
> > >> the
> > >>> change if it turns out to be a bug fix germane to release branches.
> The
> > >>> worst thing you can do as a committer is take a bug fix change, only
> > >> commit
> > >>> it to trunk, resolve the JIRA, and walk away. The second worst thing
> is
> > >> to
> > >>> commit only to trunk and leave the JIRA open. There is currently one
> > one
> > >>> committer doing these things on a frequent basis. I ask that this
> > >> practice
> > >>> stop. Please view this behavior as poor maintenance practice that
> > should
> > >> be
> > >>> avoided. Frankly, better you not commit the change at all. You are
> not
> > >>> helping the project. It is a net negative.
> > >>>
> > >>> On Mon, Jul 23, 2018 at 12:18 PM Andrew Purtell  >
> > >> wrote:
> > >>>
> >  There is a recent trend in JIRA management where a change being
> > tracked
> > >> by
> >  one JIRA is committed only to master, or maybe master and branch-2,
> > and
> >  then the JIRA is left open. The fix versions may or may not be
> > updated.
> > >> The
> >  biggest offender is Ted Yu but newer committers are also
> occasionally
> > >> doing
> >  it. Ted has no excuse, the rest is understandable.
> > 
> >  Please be advised this makes release management difficult. The RM
> has
> > to
> >  look at every commit in the repository and then make sure JIRA
> > reflects
> > >> the
> >  correct fix version. Otherwise the generated change log for the
> > release
> >  will be incorrect. If more patches are pending for other branches,
> and
> > >> the
> >  fix versions are not set correctly, then the RM may miss the patch
> and
> > >> not
> >  include it into the 

Re: [ANNOUNCE] New Committer: Toshihiro Suzuki

[Guanghao Zhang]

Congratulations!

2018-08-02 6:10 GMT+08:00 张铎(Duo Zhang) :

>  Congratulations!
>
> 2018-08-02 2:40 GMT+08:00 Esteban Gutierrez 
> :
>
> > Congrats, Toshi! and welcome!
> >
> > --
> > Cloudera, Inc.
> >
> >
> > On Wed, Aug 1, 2018 at 12:38 PM, Andrew Purtell 
> > wrote:
> >
> > > Congratulations! And welcome.
> > >
> > > On Wed, Aug 1, 2018 at 7:47 AM Josh Elser  wrote:
> > >
> > > > On behalf of the HBase PMC, I'm pleased to announce that Toshihiro
> > > > Suzuki (aka Toshi, brfn169) has accepted our invitation to become an
> > > > HBase committer. This was extended to Toshi as a result of his
> > > > consistent, high-quality contributions to HBase. Thanks for all of
> your
> > > > hard work, and we look forward to working with you even more!
> > > >
> > > > Please join me in extending a hearty "congrats" to Toshi!
> > > >
> > > > - Josh
> > > >
> > >
> > >
> > > --
> > > Best regards,
> > > Andrew
> > >
> > > Words like orphans lost among the crosstalk, meaning torn from truth's
> > > decrepit hands
> > >- A23, Crosstalk
> > >
> >
>

Re: [VOTE] Second release candidate for hbase-2.0.2 (RC1) is available for download

[Guanghao Zhang]

+1 (binding)

hbase-2.0.2-bin.tar.gz (jdk1.8.0_171)
- Verified sha512: ok
- Start HBase in standalone mode: ok
- Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
- Checked master/regionserver/table/region Web UI: ok

hbase-2.0.2-src.tar.gz (jdk1.8.0_171)
- Verified sha512: ok
- Build tarball: ok
- Start HBase in standalone mode: ok
- Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
- Checked master/regionserver/table/region Web UI: ok

Andrew Purtell  于2018年8月30日周四 上午7:29写道：

> +1
>
> Checked sums and signatures, ok
> Built from source, ok (8u172)
> RAT check passes (8u172)
> Unit test suite passes (8u181)
> Loaded 1M rows with ITBLL, looks fine (8u172)
>
>
> On Tue, Aug 28, 2018 at 9:38 PM Stack  wrote:
>
> > The second release candidate for Apache HBase 2.0.2 (RC1) is available
> > for download and testing. This is a bug fix release with 100+ commits
> [1].
> > Release notes are available here [2]. The compatibility report is at [3].
> >
> > Artifacts are available here:
> >
> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.2RC1/
> >
> > Corresponding convenience artifacts for maven use are in the staging
> > repository:
> >
> >  https://repository.apache.org/content/repositories/orgapachehbase-1231
> >
> > All artifacts are signed with my code signing key, 8ACC93D2, which is
> > also in the project KEYS file:
> >
> > http://www.apache.org/dist/hbase/KEYS
> >
> > These artifacts correspond to commit ref
> >
> >  1cfab033e779df840d5612a85277f42a6a4e8172
> >
> > which has been tagged as 2.0.2RC1.
> >
> > Please take a few minutes to verify the release and vote on releasing it:
> >
> > [ ] +1 Release these artifacts as Apache HBase 2.0.2
> > [ ] -1 Do not release this package because ...
> >
> > This VOTE thread will remain open for at least 72 hours. It will close
> for
> > sure
> > Saturday morning.
> >
> > Thanks,
> > S
> >
> > 1.
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.2RC1/CHANGES.md
> > 2.
> >
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.2RC1/RELEASENOTES.md
> > 3.
> >
> >
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.2RC1/compatibility_report_2.0.1_2.0.2.html
> >
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>- A23, Crosstalk
>

Re: Re: [ANNOUNCE] New HBase committer Jingyun Tian

[Guanghao Zhang]

Congratulations!

Guangxu Cheng  于2018年11月13日周二 下午5:19写道：

> Congratulations and welcome, Jingyun!
>
> Best Regards,
> Guangxu
>
>
>
> Tencent/Guangxu Cheng
>
> From: Nihal Jain
> Date: 2018-11-13 17:30
> To: dev
> Subject: Re: [ANNOUNCE] New HBase committer Jingyun Tian
> Congratulations Jingyun :)
>
> Regards,
> Nihal
>
> On Tue 13 Nov, 2018, 2:19 PM Yu Li 
> > Congratulations and welcome, Jingyun!
> >
> > Best Regards,
> > Yu
> >
> >
> > On Tue, 13 Nov 2018 at 16:46, Srinivas Reddy  >
> > wrote:
> >
> > > Congratulations Jingyun
> > >
> > > -
> > > Srinivas
> > >
> > > - Typed on tiny keys. pls ignore typos.{mobile app}
> > >
> > > On Tue 13 Nov, 2018, 15:54 张铎(Duo Zhang)  > >
> > > > On behalf of the Apache HBase PMC, I am pleased to announce that
> > Jingyun
> > > > Tian has accepted the PMC's invitation to become a committer on the
> > > > project. We appreciate all of Jingyun's generous contributions thus
> far
> > > and
> > > > look forward to his continued involvement.
> > > >
> > > > Congratulations and welcome, Jingyun!
> > > >
> > >
> >
>

Re: [VOTE] First release candidate for HBase 1.2.9 is available

[Guanghao Zhang]

+1 (binding)

hbase-1.2.9-bin.tar.gz (jdk1.8.0_171)
- Verified sha512: ok
- Start HBase in standalone mode: ok
- Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
- Checked master/regionserver/region Web UI: ok

hbase-1.2.9-src.tar.gz (jdk1.8.0_171)
- Verified sha512: ok
- Build tarball: ok
- Start HBase in standalone mode: ok
- Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
- Checked master/regionserver/region Web UI: ok

Ashish Singhi  于2018年11月20日周二 下午8:46写道：

> +1
> - Built tar ball from src
> - Exercised some shell commands
> - Checked process and audit logs for operations
> - mvn test passed
>
> Regards,
> Ashish
>
> On Sun, Nov 18, 2018 at 11:39 AM Sean Busbey  wrote:
>
> > The first release candidate for HBase 1.2.9 is available for download:
> >
> > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.2.9RC0/
> >
> > Maven artifacts are also available in a staging repository at:
> >
> > https://repository.apache.org/content/repositories/orgapachehbase-1236/
> >
> > Artifacts are signed with my key (0D80DB7C) published in our KEYS
> > file at http://www.apache.org/dist/hbase/KEYS
> >
> > The RC corresponds to the signed tag 1.2.9RC0, which currently points
> >  to commit ref
> >
> >  fd0d55b1e5ef54eb9bf60cce1f0a8e4c1da073ef
> >
> >  HBase 1.2.9 is the ninth maintenance release in the HBase 1.2 line,
> >  continuing on the theme of bringing a stable, reliable database to
> >  the Hadoop and NoSQL communities. This release includes about a half
> >  dozen bug fixes done in the month since 1.2.8.
> >
> >  The detailed source and binary compatibility report vs 1.2.8 has been
> >  published for your review, at:
> >
> >  https://s.apache.org/hbase-1.2.9-rc0-compat-report
> >
> >  The report shows no incompatibilities.
> >
> >  Critical fixes include:
> >
> >  * HBASE-21347 Backport HBASE-21200 "Memstore flush doesn't finish
> >because of seekToPreviousRow() in memstore scanner." to
> >branch-1
> >  * HBASE-21357 RS should abort if OOM in Reader thread
> >  * HBASE-20604 ProtobufLogReader#readNext can incorrectly loop to the
> >same position in the stream until the the WAL is rolled
> >
> >  The full list of fixes included in this release is available at:
> >
> >  https://s.apache.org/hbase-1.2.9-jira-release-notes
> >
> >  and in the CHANGES.txt file included in the distribution.
> >
> >  Please try out this candidate and vote +1/-1 on whether we should
> >  release these artifacts as HBase 1.2.9.
> >
> >  The VOTE will remain open for at least 72 hours. Given sufficient votes
> >  I would like to close it on November 26th, 2018.
> >
> >  thanks!
> >
> >  -busbey
> >
> >  as of this email the posted artifacts have the following SHA512:
> >
> >  hbase-1.2.9-src.tar.gz:
> >  49498136 FA865B7C E70C0A81 18F6B221 CA3D0266 C26DDDE2
> >  513C206C 4D28E228 048171C2 DD608DB2 0DA164BD ADBED4BF
> >  80DC40E4 6D93CC11 6C25C617 CA25E5A7
> >
> >  hbase-1.2.9-bin.tar.gz:
> >  4D9E1278 8634E250 841E55CB 8879EAC1 5C9BCF7F 09DE018A
> >  AD0CCB0E 118C2D02 BCA5F4F3 EACB9857 D8236E07 6E3CD0A4
> >  43B90567 3AB5C83C AD642547 037588BA
> >
>

Re: [ANNOUNCE] Allan Yang joins the Apache HBase PMC

[Guanghao Zhang]

Congratulations!

Reid Chan  于2018年11月29日周四 上午10:17写道：

> Congratulations! Allan
>
> --
>
> Best regards,
> R.C
>
>
>
> 
> From: Jingyun Tian 
> Sent: 29 November 2018 09:43
> To: dev@hbase.apache.org
> Subject: Re: [ANNOUNCE] Allan Yang joins the Apache HBase PMC
>
> Congratulations! Allan!
>
> On Thu, Nov 29, 2018 at 9:42 AM OpenInx  wrote:
>
> > Congratulations, Allan!
> >
> > On Thu, Nov 29, 2018 at 6:58 AM Zach York 
> > wrote:
> >
> > > Congratulations and welcome Allan!
> > >
> > >
> > > On Wed, Nov 28, 2018 at 10:21 AM Esteban Gutierrez
> > >  wrote:
> > >
> > > > Congratulations, Allan!
> > > >
> > > > --
> > > > Cloudera, Inc.
> > > >
> > > >
> > > >
> > > > On Wed, Nov 28, 2018 at 10:11 AM Yu Li  wrote:
> > > >
> > > > > On behalf of the Apache HBase PMC I am pleased to announce that
> Allan
> > > > Yang
> > > > > has accepted our invitation to become a PMC member on the Apache
> > HBase
> > > > > project. We appreciate Allan stepping up to take more
> responsibility
> > in
> > > > the
> > > > > HBase project.
> > > > >
> > > > > Please join me in welcoming Allan to the HBase PMC!
> > > > >
> > > > > Best Regards,
> > > > > Yu
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSS] EOL branch-1.3

[Guanghao Zhang]

+1. But branch-1.2 is not EOL now?

张铎(Duo Zhang)  于2018年12月8日周六 上午9:28写道：

> +1.
>
> Andrew Purtell  于2018年12月8日周六 上午5:45写道：
>
> > I'm good with doing one more 1.3 release. It would be my pleasure to
> offer
> > that service to the community. I like RM-ing.
> >
> >
> > On Fri, Dec 7, 2018 at 12:29 PM Stack  wrote:
> >
> > > +1
> > >
> > > (Pity you have to make a release to EOL it).
> > >
> > > S
> > >
> > > On Fri, Dec 7, 2018 at 11:25 AM Andrew Purtell 
> > > wrote:
> > >
> > > > We haven't had a release from branch-1.3 for a long time and do not
> > > appear
> > > > to have an active RM for it. Unless a RM for 1.3 steps forward and
> > > promises
> > > > to make a release in the very near future, I propose we make one more
> > > > release of 1.3, from the head of branch-1.3, and then retire the
> > branch.
> > > If
> > > > this is acceptable I can RM the final 1.3 release.
> > > >
> > > > --
> > > > Best regards,
> > > > Andrew
> > > >
> > > > Words like orphans lost among the crosstalk, meaning torn from
> truth's
> > > > decrepit hands
> > > >- A23, Crosstalk
> > > >
> > >
> >
> >
> > --
> > Best regards,
> > Andrew
> >
> > Words like orphans lost among the crosstalk, meaning torn from truth's
> > decrepit hands
> >- A23, Crosstalk
> >
>

Re: [VOTE] The first HBase 1.3.3 release candidate (RC0) is available

[Guanghao Zhang]

+1 (binding)

hbase-1.3.3-bin.tar.gz (jdk1.8.0_144)
- Verified sha512: ok
- Start HBase in standalone mode: ok
- Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
- Checked master/regionserver/region Web UI: ok

hbase-1.3.3-src.tar.gz (jdk1.8.0_144)
- Verified sha512: ok
- Build tarball: ok
- Start HBase in standalone mode: ok
- Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
- Checked master/regionserver/region Web UI: ok

Peter Somogyi  于2018年12月21日周五 下午5:25写道：

> +1 (non-binding)
>
> Checksum, signature: OK
> Build from source: OK
> Rat check: OK
> Unit tests: OK
> TestReplicationSmallTests and TestRemoveRegionMetrics failed once but I
> was not able to reproduce
> Shell commands: OK
> Web UI: OK
>
> Peter
>
> On Wed, Dec 19, 2018 at 9:42 AM Francis Christopher Liu <
> toffer@gmail.com> wrote:
>
> > +1 (Binding)
> >
> > I checked the following:
> > 1. Checksums and signatures
> > 2. Rat
> > 3. Built From Source and Ran unit tests
> > 4. Some shell commands
> > 5. Web UI
> > 6. LTT with 1M rows
> >
> > Thanks,
> > Francis
> >
> > On Fri, Dec 14, 2018 at 10:43 PM Sakthi 
> > wrote:
> >
> > > (+1 Non-Binding)
> > >
> > >1. Checksums and signatures(both src and bin): OK
> > >2. Rat Check: OK
> > >3. Built from source: OK
> > >4. Unit Tests: OK
> > >5. Basic Shell commands: OK
> > >6. Web UI: OK
> > >7. LTT with 1M rows: OK
> > >
> > > Sakthi
> > >
> > > On Fri, Dec 14, 2018 at 6:18 PM Andrew Purtell 
> > > wrote:
> > >
> > > > The first HBase 1.3.3 release candidate (RC0) is available for
> download
> > > at
> > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.3.3RC0/ and
> Maven
> > > > artifacts are available in the temporary repository
> > > >
> > https://repository.apache.org/content/repositories/orgapachehbase-1244/
> > > >
> > > > The git tag corresponding to the candidate is '1.3.3RC0'
> (a75a458e0c).
> > > >
> > > > A detailed source and binary compatibility report for this release is
> > > > available at
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.3.3RC0/compat-check-report.html
> > > > . I believe there are no reported compatibility issues that are out
> of
> > > > policy, justifiable, or have not been previously discussed, like the
> > > > removal of Base64. Please review and raise any concerns if you have
> > them.
> > > >
> > > > A list of the 174 issues resolved in this release can be found at
> > > > https://s.apache.org/uKCX .
> > > >
> > > > Please try out the candidate and vote +1/0/-1.
> > > >
> > > > The vote will be open for at least 72 hours. Unless objection I will
> > try
> > > to
> > > > close it Friday December 21, 2018 if we have sufficient votes.
> > > >
> > > > Prior to making this announcement I made the following preflight
> > checks:
> > > >
> > > > RAT check passes (7u80)
> > > > Unit test suite passes (8u172)
> > > > Loaded the UI in a browser, poked around (8u181)
> > > > LTT load 100M rows with 100% verification and 20% updates (8u181)
> > > > ITBLL 500M rows with slowDeterministic monkey (8u181)
> > > > ITBLL 500M rows with serverKilling monkey (8u181)
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Andrew
> > > >
> > > > Words like orphans lost among the crosstalk, meaning torn from
> truth's
> > > > decrepit hands
> > > >- A23, Crosstalk
> > > >
> > >
> >
>

Re: [VOTE] Second release candidate for HBase 2.1.2 is available for download

[Guanghao Zhang]

+1 (binding)

hbase-2.1.2-bin.tar.gz (jdk1.8.0_171)
- Verified sha512: ok
- Start HBase in standalone mode: ok
- Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
- Checked master/regionserver/region Web UI: ok

hbase-2.1.2-src.tar.gz (jdk1.8.0_171)
- Verified sha512: ok
- Build tarball: ok
- Start HBase in standalone mode: ok
- Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
- Checked master/regionserver/region Web UI: ok

Allan Yang  于2019年1月8日周二 上午10:18写道：

> +1 (binding)
>
> -- Build from src - OK
>
> -- SHA and Signatures(both src and bin) - OK
>
> -- start in distributed mode - OK
>
> -- Basic shell commands[create/drop/alter/get/put/scan] - OK
>
> -- Check Web UI - OK
>
> -- ITBLL 1B row for 1 run - OK
> Best Regards
> Allan Yang
>
>
> Peter Somogyi  于2019年1月8日周二 上午12:00写道：
>
> > +1 (non-binding)
> >
> > Checksum, signature: OK
> > Build from source: OK
> > Unit tests: OK
> > LTT 1M rows: OK
> > Basic shell commands: OK
> > Apache Rat: OK
> >
> > Thanks,
> > Peter
> >
> > On Mon, Jan 7, 2019 at 9:20 AM Allan Yang  wrote:
> >
> > > OK, there is a 2.1.2 pending, will test the RC and come back soon.
> > > Best Regards
> > > Allan Yang
> > >
> > >
> > > 张铎(Duo Zhang)  于2019年1月7日周一 下午12:12写道：
> > >
> > > > +1(binding)
> > > >
> > > > Built from src: OK
> > > > Checked sums & sigs: All matched
> > > > Run all UTs(jdk8u151): Fine. The same with testing 2.0.4RC1. With
> > > > -PrunAllTests several UTs failed, and then passed when running
> > > sequentially
> > > > Started a 5 nodes cluster: OK, the master UI is fine
> > > > Run basic shell cmds: OK
> > > > Run LTT with 1M rows: Read & Write, both OK, and then major compact
> the
> > > > table, and execute the count command in shell, also 1M rows returned.
> > > >
> > > > Stack  于2019年1月3日周四 上午9:23写道：
> > > >
> > > > > The second release candidate for HBase 2.1.2 is available for
> > download:
> > > > >
> > > > > * https://dist.apache.org/repos/dist/dev/hbase/hbase-2.1.2RC1/
> > > > > *
> > > > >
> > > > > Maven artifacts are also available in a staging repository at:
> > > > >
> > > > >
> > > https://repository.apache.org/content/repositories/orgapachehbase-1247
> > > > >
> > > > > Artifacts are signed with my key (DB9D313DA7874F29) published in
> our
> > > > > KEYS file at http://www.apache.org/dist/hbase/KEYS
> > > > >
> > > > > The RC corresponds to the signed tag 2.1.2RC1, which currently
> points
> > > > > to commit
> > > > >
> > > > >   1dfc418f77801fbfb59a125756891b9100c1fc6d
> > > > >
> > > > > HBase 2.1.2 is the third maintenance release in the HBase 2.0 line,
> > > > > continuing on the theme of bringing a stable, reliable database to
> > > > > the Hadoop and NoSQL communities. It fixes a critical issue found
> > > > > in the recent 2.0.3 and 2.1.1 releases (only), HBASE-21551. 2.1.2
> > > > > includes ~70 bug and improvement fixes done since the 2.1.1,
> > > > > ~ eight weeks ago.
> > > > >
> > > > > The detailed source and binary compatibility report vs 2.1.1 has
> been
> > > > > published for your review, at:
> > > > >
> > > > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.1.2RC1
> > > > > /compatibility_report_2.1.1vs2.1.2.html
> > > > >
> > > > > The report shows no incompatibilities.
> > > > >
> > > > > The full list of fixes included in this release is available in
> > > > > the CHANGES.md that ships as part of the release also available
> > > > > here:
> > > > >
> > > > >
> > > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.1.2RC1/CHANGES.md
> > > > >
> > > > > The RELEASENOTES.md are here:
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.1.2RC1/RELEASENOTES.md
> > > > >
> > > > > Please try out this candidate and vote +1/-1 on whether we should
> > > > > release these artifacts as HBase 2.1.2.
> > > > >
> > > > > The VOTE will remain open for at least 72 hours. Given sufficient
> > votes
> > > > > I would like to close it on Sunday, January 6th, 2018.
> > > > >
> > > > > Thanks,
> > > > > S
> > > > > P.S. Happy New Year!
> > > > >
> > > >
> > >
> >
>

Re: Nice article on one of our own....

[Guanghao Zhang]

Congratulations!

Reid Chan  于2019年1月10日周四 上午10:24写道：

> Thumbs up & clap!
>
>
>
>
> --
>
> Best regards,
> R.C
>
>
>
>
>
> 
> From: Stack 
> Sent: 10 January 2019 02:41
> To: HBase Dev List
> Subject: Nice article on one of our own
>
> See #3 in list of top 5 Apache committers:
> https://www.cbronline.com/feature/apache-top-5
> S
>

Release 2.2.0

[Guanghao Zhang]

Hi, all, there has been six months since we released 2.1.0. And there are
429 issues which fixed version is 2.2.0[1]. Our internal branch which based
branch-2 run ITBLL successfully recently. branch-2 is stable now and it is
time to release 2.2.0. I volunteered to be the release manager for the 2.2
release line. And plan to cut branch-2.2 from branch-2.

For 2.2.0, the biggest change is about AMV2[2]: HBASE-20881 is an
incompatible change and different implemenation with branch-2.0 and
branch-2.1. Need to add more document about how to rolling upgrade from
2.0.* or 2.1.* to 2.2.*. Meanwhile, need document about how rolling upgrade
from 1.* to 2.2.*. Now HBCK2 tool support branch-2's region assignments,
too.

Another features will be included:
1. HBASE-20610 Procedure V2 - Distributed Log Splitting[3]
2. HBASE-21649 Complete Thrift2[4]
3. HBASE-16707 Improve throttling feature for production usage[5]
4. HBASE-20886 [Auth] Support keytab login in hbase client[6]
5. HBASE-20636 Introduce two bloom filter type : ROWPREFIX_FIXED_LENGTH and
ROWPREFIX_DELIMITED[7]

Open a issue HBASE-21747 to release 2.2.0[8]. Suggestions are welcomed.
Thanks.

Best Regards,
Guanghao

[1]
https://issues.apache.org/jira/browse/HBASE-21746?jql=project%20%3D%20HBASE%20AND%20fixVersion%20%3D%202.2.0
[2] https://issues.apache.org/jira/browse/HBASE-20881
[3] https://issues.apache.org/jira/browse/HBASE-20610
[4] https://issues.apache.org/jira/browse/HBASE-21649
[5] https://issues.apache.org/jira/browse/HBASE-16707
[6] https://issues.apache.org/jira/browse/HBASE-20886
[7] https://issues.apache.org/jira/browse/HBASE-20636
[8] https://issues.apache.org/jira/browse/HBASE-21747

Re: [ANNOUNCE] Please welcome Peter Somogyi to the HBase PMC

[Guanghao Zhang]

Congratulations!

Yu Li  于2019年1月22日周二 上午10:48写道：

> Congratulations, Peter!
>
> Best Regards,
> Yu
>
>
> On Tue, 22 Jan 2019 at 10:38, Guangxu Cheng 
> wrote:
>
> > Congratulations Peter!
> >
> > -
> > Best Regards
> > Guangxu Cheng
> >
> > Allan Yang  于2019年1月22日周二 上午10:15写道：
> >
> > > Congratulations Peter!
> > > Best Regards
> > > Allan Yang
> > >
> > >
> > > Pankaj kr  于2019年1月22日周二 上午9:49写道：
> > >
> > > >
> > > > Congratulations Peter...!!!
> > > >
> > > > Regards,
> > > > Pankaj
> > > >
> > > > --
> > > > Pankaj Kumar
> > > > M: +91-9535197664(India Contact Number)
> > > > E: pankaj...@huawei.com
> > > > 2012实验室-班加罗尔研究所IT&Cloud BU分部
> > > > 2012 Laboratories-IT&Cloud BU Branch Dept.HTIPL
> > > > From:Duo Zhang 
> > > > To:HBase Dev List ;hbase-user <
> > > u...@hbase.apache.org
> > > > >
> > > > Date:2019-01-22 07:06:43
> > > > Subject:[ANNOUNCE] Please welcome Peter Somogyi to the HBase PMC
> > > >
> > > > On behalf of the Apache HBase PMC I am pleased to announce that Peter
> > > > Somogyi
> > > > has accepted our invitation to become a PMC member on the Apache
> HBase
> > > > project.
> > > > We appreciate Peter stepping up to take more responsibility in the
> > HBase
> > > > project.
> > > >
> > > > Please join me in welcoming Peter to the HBase PMC!
> > > >
> > >
> >
>

Re: Release 2.2.0

[Guanghao Zhang]

Our new internal branch is based on branch-2. And we already rolling
upgrade our staging cluster from our internal 0.98 branch to it... I will
take a try for 2.0.* to 2.2.0.

Are you saying we need to make sure it can do this? Or are you
> asserting that it already does?
>
It already does.


Sean Busbey  于2019年1月22日周二 下午9:48写道：

> excellent! thanks for volunteering to get the 2.2 release line going
> Guanghao!
>
> > Need to add more document about how to rolling upgrade from
> 2.0.* or 2.1.* to 2.2.*. Meanwhile, need document about how rolling upgrade
> from 1.* to 2.2.*.
>
> Has anyone confirmed that rolling upgrade to 2.2.0 works? I thought it
> couldn't because of the change to assignment handling classes?
>
> > Now HBCK2 tool support branch-2's region assignments,
> too.
>
> Are you saying we need to make sure it can do this? Or are you
> asserting that it already does?
>
> On Sun, Jan 20, 2019 at 10:25 PM Guanghao Zhang 
> wrote:
> >
> > Hi, all, there has been six months since we released 2.1.0. And there are
> > 429 issues which fixed version is 2.2.0[1]. Our internal branch which
> based
> > branch-2 run ITBLL successfully recently. branch-2 is stable now and it
> is
> > time to release 2.2.0. I volunteered to be the release manager for the
> 2.2
> > release line. And plan to cut branch-2.2 from branch-2.
> >
> > For 2.2.0, the biggest change is about AMV2[2]: HBASE-20881 is an
> > incompatible change and different implemenation with branch-2.0 and
> > branch-2.1. Need to add more document about how to rolling upgrade from
> > 2.0.* or 2.1.* to 2.2.*. Meanwhile, need document about how rolling
> upgrade
> > from 1.* to 2.2.*. Now HBCK2 tool support branch-2's region assignments,
> > too.
> >
> > Another features will be included:
> > 1. HBASE-20610 Procedure V2 - Distributed Log Splitting[3]
> > 2. HBASE-21649 Complete Thrift2[4]
> > 3. HBASE-16707 Improve throttling feature for production usage[5]
> > 4. HBASE-20886 [Auth] Support keytab login in hbase client[6]
> > 5. HBASE-20636 Introduce two bloom filter type : ROWPREFIX_FIXED_LENGTH
> and
> > ROWPREFIX_DELIMITED[7]
> >
> > Open a issue HBASE-21747 to release 2.2.0[8]. Suggestions are welcomed.
> > Thanks.
> >
> > Best Regards,
> > Guanghao
> >
> > [1]
> >
> https://issues.apache.org/jira/browse/HBASE-21746?jql=project%20%3D%20HBASE%20AND%20fixVersion%20%3D%202.2.0
> > [2] https://issues.apache.org/jira/browse/HBASE-20881
> > [3] https://issues.apache.org/jira/browse/HBASE-20610
> > [4] https://issues.apache.org/jira/browse/HBASE-21649
> > [5] https://issues.apache.org/jira/browse/HBASE-16707
> > [6] https://issues.apache.org/jira/browse/HBASE-20886
> > [7] https://issues.apache.org/jira/browse/HBASE-20636
> > [8] https://issues.apache.org/jira/browse/HBASE-21747
>

Re: Release 2.2.0

[Guanghao Zhang]

Cut a new branch-2.2 at this commit.

commit e736d78362253936492fb3bd16e614d14859281d
Author: Duo Zhang 
Date: Mon Jan 28 18:21:51 2019 +0800

HBASE-21792 Mark HTableMultiplexer as deprecated and remove it in 3.0.0

Signed-off-by: Michael Stack 

Sean Busbey  于2019年1月24日周四 上午9:45写道：

> Okay it sounds like we definitely need a better doc about this as a
> starting point. I have some additional questions about failure handling;
> should we go through them here or in a jira about improving how upgrade
> from 2.0/2.1 gets handled?
>
> On Wed, Jan 23, 2019, 07:33 张铎(Duo Zhang) 
> > Oh, you misunderstood me. It is just for master, you need make sure that
> > before you killing the old version master, there is no RITs. And once the
> > new master is up, everything is fine., as the new master will detect if
> > there are old style AssignProcedure/UnassignProcedures, if so it will
> quit
> > immediately.
> >
> > Sean Busbey  于2019年1月23日周三 下午9:21写道：
> >
> > > Yes, please. I don't think it's reasonable to expect no region
> > transitions
> > > during a rolling upgrade window; that would imply no servers can crash
> > > during the upgrade.
> > >
> > > On Wed, Jan 23, 2019, 07:04 张铎(Duo Zhang)  wrote:
> > >
> > > > From 1.x it is OK, but from 2.0 or 2.1, we need make sure that there
> > are
> > > no
> > > > RITs ongoing. We could see if we can make the upgrading more
> smoothly.
> > > >
> > > > Guanghao Zhang  于2019年1月23日周三 下午8:56写道：
> > > >
> > > > > Our new internal branch is based on branch-2. And we already
> rolling
> > > > > upgrade our staging cluster from our internal 0.98 branch to it...
> I
> > > will
> > > > > take a try for 2.0.* to 2.2.0.
> > > > >
> > > > > Are you saying we need to make sure it can do this? Or are you
> > > > > > asserting that it already does?
> > > > > >
> > > > > It already does.
> > > > >
> > > > >
> > > > > Sean Busbey  于2019年1月22日周二 下午9:48写道：
> > > > >
> > > > > > excellent! thanks for volunteering to get the 2.2 release line
> > going
> > > > > > Guanghao!
> > > > > >
> > > > > > > Need to add more document about how to rolling upgrade from
> > > > > > 2.0.* or 2.1.* to 2.2.*. Meanwhile, need document about how
> rolling
> > > > > upgrade
> > > > > > from 1.* to 2.2.*.
> > > > > >
> > > > > > Has anyone confirmed that rolling upgrade to 2.2.0 works? I
> thought
> > > it
> > > > > > couldn't because of the change to assignment handling classes?
> > > > > >
> > > > > > > Now HBCK2 tool support branch-2's region assignments,
> > > > > > too.
> > > > > >
> > > > > > Are you saying we need to make sure it can do this? Or are you
> > > > > > asserting that it already does?
> > > > > >
> > > > > > On Sun, Jan 20, 2019 at 10:25 PM Guanghao Zhang <
> > zghao...@gmail.com>
> > > > > > wrote:
> > > > > > >
> > > > > > > Hi, all, there has been six months since we released 2.1.0. And
> > > there
> > > > > are
> > > > > > > 429 issues which fixed version is 2.2.0[1]. Our internal branch
> > > which
> > > > > > based
> > > > > > > branch-2 run ITBLL successfully recently. branch-2 is stable
> now
> > > and
> > > > it
> > > > > > is
> > > > > > > time to release 2.2.0. I volunteered to be the release manager
> > for
> > > > the
> > > > > > 2.2
> > > > > > > release line. And plan to cut branch-2.2 from branch-2.
> > > > > > >
> > > > > > > For 2.2.0, the biggest change is about AMV2[2]: HBASE-20881 is
> an
> > > > > > > incompatible change and different implemenation with branch-2.0
> > and
> > > > > > > branch-2.1. Need to add more document about how to rolling
> > upgrade
> > > > from
> > > > > > > 2.0.* or 2.1.* to 2.2.*. Meanwhile, need document about how
> > rolling
> > > > > > upgrade
> > > > > > > from 1.* to 2.2.*. Now HBCK2 tool support branch-2's region
> >

Re: [ANNOUNCE] New HBase committer Xu Cang

[Guanghao Zhang]

Congratulations!

Esteban Gutierrez  于2019年2月12日周二 上午3:22写道：

> Congrats, Xu!
>
> --
> Cloudera, Inc.
>
>
>
> On Sun, Feb 10, 2019 at 8:54 PM OpenInx  wrote:
>
> > Congratulations!
> >
> > On Fri, Feb 8, 2019 at 7:42 PM 张铎(Duo Zhang) 
> > wrote:
> >
> > > Congratulations!
> > >
> > > Allan Yang  于2019年2月8日周五 下午7:40写道：
> > >
> > > > Congratulations, Xu!
> > > > Best Regards
> > > > Allan Yang
> > > >
> > > >
> > > > Xu Cang  于2019年2月7日周四 上午3:06写道：
> > > >
> > > > > Thank you all! Looking forward to contributing more and making more
> > > > > meaningful impact on our community.
> > > > >
> > > > > Xu
> > > > >
> > > > > On Wed, Feb 6, 2019 at 1:13 AM Yuhao Bi 
> wrote:
> > > > >
> > > > > > Congratulations!
> > > > > >
> > > > > > Pankaj kr  于2019年2月6日周三 下午4:40写道：
> > > > > >
> > > > > > > Congratulations Xu...!!
> > > > > > >
> > > > > > > Regards,
> > > > > > > Pankaj
> > > > > > >
> > > > > > >
> > > > > > > -Original Message-
> > > > > > > From: Andrew Purtell [mailto:apurt...@apache.org]
> > > > > > > Sent: 06 February 2019 04:19
> > > > > > > To: dev ; Hbase-User <
> > u...@hbase.apache.org>
> > > > > > > Subject: [ANNOUNCE] New HBase committer Xu Cang
> > > > > > >
> > > > > > > On behalf of the Apache HBase PMC, I am pleased to announce
> that
> > Xu
> > > > > Cang
> > > > > > > has accepted the PMC's invitation to become a committer on the
> > > > project.
> > > > > > We
> > > > > > > appreciate all of Xu's generous contributions thus far and look
> > > > forward
> > > > > > to
> > > > > > > his continued involvement.
> > > > > > >
> > > > > > > Congratulations and welcome, Xu!
> > > > > > >
> > > > > > > --
> > > > > > > Best regards,
> > > > > > > Andrew
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] Second release candidate for HBase 2.1.3 is available for download

[Guanghao Zhang]

+1 (binding)

hbase-2.1.3-bin.tar.gz (jdk1.8.0_171)
- Verified sha512: ok
- Start HBase in standalone mode: ok
- Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
- Checked master/regionserver/region Web UI: ok
- PE write/read 100K rows: good

hbase-2.1.3-src.tar.gz (jdk1.8.0_171)
- Verified sha512: ok
- Build tarball: ok
- Start HBase in standalone mode: ok
- Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
- Checked master/regionserver/region Web UI: ok
- PE write/read 100K rows: good

张铎(Duo Zhang)  于2019年2月11日周一 下午8:15写道：

> The second release candidate for HBase 2.1.3 is available for download:
>
>   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.1.3RC1
>
> Maven artifacts are also available in a staging repository at:
>
>   https://repository.apache.org/content/repositories/orgapachehbase-1254/
>
> Artifacts are signed with my key (9AD2AE49) published in our KEYS file at
>
>  http://www.apache.org/dist/hbase/KEYS
>
> The RC corresponds to the signed tag 2.1.3RC1, which currently points to
> commit
>
>   da5ec9e4c06c537213883cca8f3cc9a7c19daf67
>
> HBase 2.1.3 is the fourth maintenance release in the HBase 2.1 line,
> continuing on the theme of bringing a stable, reliable database to the
> Hadoop and NoSQL communities. It fixes CVE-2018-1320 by upgrading thrift
> dependency from 0.9.3 to 0.12.0, all hbase users who use thrift are highly
> recommended to upgrade.
>
> 2.1.3 includes ~60 bug and improvement fixes done since the 2.1.2. There is
> an incompatible change, HBASE-21684, where we change the superclass of
> StoppedRpcClientException from HBaseIOException to DoNotRetryIOException,
> should be low risk, and feel free to contact us if this breaks anything for
> you.
>
> The detailed source and binary compatibility report vs 2.1.2 has been
> published for your review, at:
>
>
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.1.3RC1/compatibility_report_2.1.2vs2.1.3RC1.html
>
> The report shows no incompatibilities.
>
> The full list of fixes included in this release is available in the
> CHANGES.md that ships as part of the release also available here:
>
>   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.1.3RC1/CHANGES.md
>
> The RELEASENOTES.md are here:
>
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.1.3RC1/RELEASENOTES.md
>
> Please try out this candidate and vote +1/-1 on whether we should release
> these artifacts as HBase 2.1.3.
>
> The VOTE will remain open for at least 72 hours.
>
> Thanks
>

Re: [VOTE] Merge feature branch HBASE-26233 back to master

[Guanghao Zhang]

+1 from me.

The idea and solution is great!

Thanks.

Duo Zhang  于2021年12月18日周六 16:31写道：

> There is a previous thread[1] to mention that the main development work on
> HBASE-26233[2] is done. And now the testing work has been done too, so I
> send this official vote to merge for HBASE-26233 back into master.
>
> For those who are not familiar with HBASE-26233, it is for re-implementing
> the region replication framework, to decouple with the general replication
> framework. You could see the design doc[3] for more details. I've also
> opened a PR against master[4], PTAL if you have interest.
>
> You can see the final test result on HBASE-26487[5].
> In conclusion, there is no regression on performance when running PE.
> Using the new tool introduced in HBASE-26540[6], the new implementation can
> perform much better than the old implementation. When inserting 1M rows,
> the max lag on secondary replica is 335ms, and the 99.9% lag is 3 only 3ms,
> while the lag of the old implementation highly depends on the
> replication.source.sleepforretries config but you should not set it to a
> very small value as it will waste a lot of resources.
> On IntegrationTestRegionReplicaReplication, both implementations can not
> pass but the problems are not related to the changing part, so should not
> be a blocker. Will file follow on issues to address these problems.
>
> The vote will open for at least 72 hours.
>
> Please vote:
> +1: Merge the changes from HBASE-26233 to master
> -1: Do not merge these changes because ...
>
> Thanks.
>
> 1. https://lists.apache.org/thread/t8w053kpy9pj1vg1x3c0kjjh4ongrxzy
> 2. https://issues.apache.org/jira/browse/HBASE-26233
> 3.
>
> https://docs.google.com/document/d/1WPSBwRqIPgTrPRM2wtzAe-3XUvA9S7auWy3Fy8xuZLc/edit
> 4. https://github.com/apache/hbase/pull/3891
> 5. https://issues.apache.org/jira/browse/HBASE-26487
> 6. https://issues.apache.org/jira/browse/HBASE-26540
>

Re: [ANNOUNCE] Please welcome Xiaolin Ha(哈晓琳) to the HBase PMC

[Guanghao Zhang]

Congratulations!

Tak Lon (Stephen) Wu  于2022年4月12日周二 02:28写道：

> Congratulations Xiaolin!
>
> -Stephen
>
> On Mon, Apr 11, 2022 at 9:45 AM Pankaj Kumar 
> wrote:
> >
> > Congratulations Xiaolin..!!
> >
> > Regards,
> > Pankaj
> >
> > On Sat, Apr 9, 2022, 6:41 PM 张铎(Duo Zhang) 
> wrote:
> >
> > > On behalf of the Apache HBase PMC I am pleased to announce that
> Xiaolin Ha
> > > has accepted our invitation to become a PMC member on the Apache HBase
> > > project. We appreciate Xiaolin Ha stepping up to take more
> responsibility
> > > in
> > > the HBase project.
> > >
> > > Please join me in welcoming Xiaolin Ha to the HBase PMC!
> > >
> > > 我很高兴代表 Apache HBase PMC 宣布哈晓琳已接受我们的邀请，
> > > 成为 Apache HBase 项目的 PMC 成员。感谢哈晓琳愿意在 HBase 项目
> > > 中承担更大的责任。
> > >
> > > 欢迎哈晓琳！
> > >
>

Re: [ANNOUNCE] New HBase committer Bryan Beaudreault

[Guanghao Zhang]

Congratulations!

Tak Lon (Stephen) Wu  于2022年4月12日周二 02:29写道：

> Congrats Bryan!
>
> -Stephen
>
> On Mon, Apr 11, 2022 at 9:44 AM Pankaj Kumar 
> wrote:
> >
> > Congratulations & welcome Bryan..!!
> >
> > Regards,
> > Pankaj
> >
> > On Sat, Apr 9, 2022, 5:15 PM 张铎(Duo Zhang) 
> wrote:
> >
> > > On behalf of the Apache HBase PMC, I am pleased to announce that Bryan
> > > Beaudreault(bbeaudreault) has accepted the PMC's invitation to become a
> > > committer on the project. We appreciate all of Bryan's generous
> > > contributions thus far and look forward to his continued involvement.
> > >
> > > Congratulations and welcome, Bryan Beaudreault!
> > >
> > > 我很高兴代表 Apache HBase PMC 宣布 Bryan Beaudreault 已接受我们的邀请，成为 Apache HBase
> 项目的
> > > Committer。感谢 Bryan Beaudreault 一直以来为 HBase 项目做出的贡献，并期待他在未来继续承担更多的责任。
> > >
> > > 欢迎 Bryan Beaudreault！
> > >
>

Re: [VOTE] First release candidate for hbase-thirdparty 4.1.1 is available for download

[Guanghao Zhang]

+1 (binding)

* Signature: ok
* Checksum : ok
* Rat check (1.8.0_301): ok
 - mvn clean apache-rat:check
* Built from source (1.8.0_301): ok
 - mvn clean install  -DskipTests

张铎(Duo Zhang)  于2022年6月20日周一 23:40写道：

> See https://github.com/apache/hbase/pull/4552
>
> After modifying some code in HBase, mainly because of a behavior change in
> jetty, we can pass all the UTs when depending on hbase-thirdparty-4.1.1.
>
> 张铎(Duo Zhang)  于2022年6月18日周六 23:04写道：
>
> > Please vote on this Apache hbase thirdparty release candidate,
> > hbase-thirdparty-4.1.1RC0
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache hbase thirdparty 4.1.1
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 4.1.1RC0:
> >
> >   https://github.com/apache/hbase-thirdparty/tree/4.1.1RC0
> >
> > This tag currently points to git reference
> >
> >   d674246a75e1d7d1d4c5ee09a2567bbfa1cec022
> >
> > The release files, including signatures, digests, as well as CHANGES.md
> > and RELEASENOTES.md included in this RC can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/hbase/hbase-thirdparty-4.1.1RC0/
> >
> > Maven artifacts are available in a staging repository at:
> >
> >
> https://repository.apache.org/content/repositories/orgapachehbase-1488/
> >
> > Artifacts were signed with the 9AD2AE49 key which can be found in:
> >
> >   https://downloads.apache.org/hbase/KEYS
> >
> > To learn more about Apache hbase thirdparty, please see
> >
> >   http://hbase.apache.org/
> >
> > Thanks,
> > Your HBase Release Manager
> >
>

Re: [VOTE] The first release candidate for HBase 2.5.2 is available

[Guanghao Zhang]

+1 (binding)

* Checksum : ok
* Rat check (1.8.0_301): ok
 - mvn clean apache-rat:check
* Built from source (1.8.0_301): ok
 - mvn clean install -DskipTests
* Unit tests pass (1.8.0_301): ok
 - mvn package -P runSmallTests

Duo Zhang  于2022年11月30日周三 23:37写道：

> Bump.
>
> The phoenix community has tested the hadoop3 artifacts and it works well.
>
> Let's get this release done~
>
> Thanks.
>
> Duo Zhang  于2022年11月24日周四 12:32写道：
> >
> > Please vote on this Apache hbase release candidate,
> > hbase-2.5.2RC0
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache hbase 2.5.2
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 2.5.2RC0:
> >
> >   https://github.com/apache/hbase/tree/2.5.2RC0
> >
> > This tag currently points to git reference
> >
> >   3e28acf0b819f4b4a1ada2b98d59e05b0ef94f96
> >
> > The release files, including signatures, digests, as well as CHANGES.md
> > and RELEASENOTES.md included in this RC can be found at:
> >
> >   https://dist.apache.org/repos/dist/dev/hbase/2.5.2RC0/
> >
> > Maven artifacts are available in a staging repository at:
> >
> >
> https://repository.apache.org/content/repositories/orgapachehbase-1503/
> >
> > Maven artifacts for hadoop3 are available in a staging repository at:
> >
> >
> https://repository.apache.org/content/repositories/orgapachehbase-1504/
> >
> > Artifacts were signed with the 0x9AD2AE49 key which can be found in:
> >
> >   https://downloads.apache.org/hbase/KEYS
> >
> > 2.5.2 includes 28 bug and improvement fixes done since 2.5.1. And
> > starting from 2.5.2, we will publish dist and maven artifacts for both
> > hadoop2 and hadoop3. Feel free to report any issues for the newly
> > published hadoop3 dist and maven artifacts.
> >
> > To learn more about Apache hbase, please see
> >
> >   http://hbase.apache.org/
> >
> > Thanks,
> > Your HBase Release Manager
>

Re: [ANNOUNCE] New HBase Committer Liangjun He

[Guanghao Zhang]

Congratulations!

OpenInx  于2022年12月6日周二 19:03写道：

> Congrats and welcome !
>
> On Tue, Dec 6, 2022 at 2:21 AM Andrew Purtell  wrote:
>
> > Congratulations, and welcome!
> >
> > On Sat, Dec 3, 2022 at 5:51 AM Yu Li  wrote:
> >
> > > Hi All,
> > >
> > > On behalf of the Apache HBase PMC, I am pleased to announce that
> Liangjun
> > > He (heliangjun) has accepted the PMC's invitation to become a committer
> > on
> > > the project. We appreciate all of Liangjun's generous contributions
> thus
> > > far and look forward to his continued involvement.
> > >
> > > Congratulations and welcome, Liangjun!
> > >
> > > 我很高兴代表 Apache HBase PMC 宣布 Liangjun He (何良均) 已接受我们的邀请，成为 Apache HBase
> 项目的
> > > Committer。感谢何良均一直以来为 HBase 项目做出的贡献，并期待他在未来继续承担更多的责任。
> > >
> > > 欢迎良均！
> > >
> > > Best Regards,
> > > Yu
> > > --
> > > Best Regards,
> > > Yu
> > >
> >
> >
> > --
> > Best regards,
> > Andrew
> >
> > Unrest, ignorance distilled, nihilistic imbeciles -
> > It's what we’ve earned
> > Welcome, apocalypse, what’s taken you so long?
> > Bring us the fitting end that we’ve been counting on
> >- A23, Welcome, Apocalypse
> >
>

Re: [DISCUSS] How to deal with the disabling of public sign ups for jira.a.o(enable github issues?)

[Guanghao Zhang]

Did other projects have the same solution for this, sync github issues to
jira issues? Github issues will be useful to get more feedback.

张铎(Duo Zhang)  于2022年12月6日周二 00:13写道：

> The PR for HBASE-27513 is available
>
> https://github.com/apache/hbase/pull/4913
>
> Let's at least tell our users to send email to private@hbase for
> acquiring a jira account.
>
> Thanks.
>
> 张铎(Duo Zhang)  于2022年12月2日周五 12:46写道：
> >
> > Currently all the comment on github PR will be sent to issues@hbase,
> > like this one
> >
> > https://lists.apache.org/thread/jbfm269b4m24xl2r82l8b0t3pmqr44hr
> >
> > But I think this can only be used as an archive, to make sure that all
> > discussions are recorded on asf infrastructure.
> >
> > For github issues, I'm afraid we can only do the same thing. As the
> > format of github comment is different, it will be hard to read if we
> > just sync the message to jira...
> >
> > Thanks.
> >
> > Bryan Beaudreault  于2022年12月1日周四
> 21:30写道：
> > >
> > > Should we have them sent to private@? Just thinking in terms of
> reducing
> > > spam to users who put their email and full name on a public list.
> > >
> > > One thought I had about bug tracking is whether we could use some sort
> of
> > > github -> jira sync. I've seen them used before, where it automatically
> > > syncs issues and comments between the two systems. It's definitely not
> > > ideal, but maybe an option? I'm guessing it would require INFRA help.
> > >
> > > On Thu, Dec 1, 2022 at 5:47 AM 张铎(Duo Zhang) 
> wrote:
> > >
> > > > I've filed HBASE-27513 for changing the readme on github.
> > > >
> > > > At least let's reuse the existing mailing list for acquiring jira
> account.
> > > >
> > > > Thanks.
> > > >
> > > > 张铎(Duo Zhang)  于2022年11月29日周二 22:34写道：
> > > >
> > > > >
> > > > > Bump and also send this to user@hbase.
> > > > >
> > > > > We need to find a way to deal with the current situation where
> > > > > contributors can not create a Jira account on their own...
> > > > >
> > > > > At least, we need to change the readme on github page, web site and
> > > > > also the ref guide to tell users how to acquire a jira account...
> > > > >
> > > > > Thanks.
> > > > >
> > > > > 张铎(Duo Zhang)  于2022年11月27日周日 22:06写道：
> > > > > >
> > > > > > For me, I think most developers already have a github account, so
> > > > > > enabling it could help us get more feedback. For lots of younger
> > > > > > Chinese developers, they rarely use email in their daily life...
> > > > > > No doubt later we need to modify our readme on github. If we
> just let
> > > > > > users go to github issues on the readme, they will soon open an
> issue
> > > > > > there. But if we ask users to first send an email to a mailing
> list,
> > > > > > for acquiring a jira account, and then wait for a PMC member to
> submit
> > > > > > the request, and receive the email response, set up their
> account, and
> > > > > > then they can finally open an issue on jira. I'm afraid lots of
> users
> > > > > > will just give up, it is not very friendly...
> > > > > >
> > > > > > And I do not mean separate issue systems for users and devs.
> Users can
> > > > > > still open jira issues or ask in the mailing list if they want,
> github
> > > > > > issues is just another channel. If a user asks something in the
> > > > > > mailing list and we think it is a bug, we will ask the user to
> file an
> > > > > > issue or we will file an issue for it. It is just the same with
> github
> > > > > > issues.
> > > > > >
> > > > > > Thanks.
> > > > > >
> > > > > > Nick Dimiduk  于2022年11月24日周四 15:44写道：
> > > > > > >
> > > > > > > This new situation around JIRA seems very similar to the
> existing
> > > > situation
> > > > > > > around Slack. A new community member currently must acquire a
> Slack
> > > > invite
> > > > > > > somehow, usually by emailing one of the lists. Mailing lists
> > > > themselves
> > > > > > > involve a signup process, though it may be possible to email
> > > > user/-zh/dev
> > > > > > > without first subscribing to the list.
> > > > > > >
> > > > > > > I have a -0 opinion on using GitHub Issues to manage JIRA
> > > > subscription
> > > > > > > access. It seems like a comical cascade of complexity. I’d
> prefer to
> > > > keep
> > > > > > > GitHub Issues available to us as a future alternative to JIRA
> for
> > > > project
> > > > > > > issue tracking. I agree with you that migrating away from JIRA
> will
> > > > be
> > > > > > > painful.
> > > > > > >
> > > > > > > I’m not a big fan of having separate issue systems for users
> vs.
> > > > devs. It
> > > > > > > emphasizes the idea that users and devs are different groups of
> > > > people with
> > > > > > > unequal voice in the project direction. I suppose it could be
> done
> > > > well,
> > > > > > > but I think it is more likely to be done poorly.
> > > > > > >
> > > > > > > I follow the Infra list, but only casually. It seems there’s a
> plan
> > > > to
> > > > > > > eventually adopt some Atlassian Cloud service, which ha

Re: [VOTE] First release candidate for hbase 3.0.0-alpha-4 is available for download

[Guanghao Zhang]

+1 (binding)

* Checksum : ok
* Rat check (1.8.0_362): ok
 - mvn clean apache-rat:check
* Built from source (1.8.0_362): ok
 - mvn clean install -DskipTests
* Unit tests pass (1.8.0_362): ok
 - mvn clean package -P runSmallTests
 -Dsurefire.rerunFailingTestsCount=3

Shanmukha Haripriya Kota  于2023年6月7日周三 08:17写道：

> +1
>
> [INFO]
> 
> [INFO] BUILD SUCCESS
> [INFO]
> 
> [INFO] Total time:  33:55 min
> [INFO] Finished at: 2023-06-06T19:00:23-05:00
> [INFO]
> 
> ~/Desktop/hbase300/hbase-3.0.0-alpha-4/dev-support
> * Signature: ok
> * Checksum : ok
> * Rat check (11.0.10): ok
>  - mvn clean apache-rat:check
> * Built from source (11.0.10): ok
>  - mvn clean install  -DskipTests
> * Unit tests pass (11.0.10): ok
>  - mvn clean package -P runSmallTests
>  -Dsurefire.rerunFailingTestsCount=3
>
> [1]  + 19163 done   ./hbase-vote.sh -s  -f
> https://dist.apache.org/repos/dist/release/hbase/KEYS
>
> On Tue, Jun 6, 2023 at 10:22 AM Andrew Purtell 
> wrote:
>
> > +1 (binding)
> >
> > * Signature: ok
> > * Checksum : ok
> > * Rat check (11.0.19): ok
> >  - mvn clean apache-rat:check
> > * Built from source (11.0.19): ok
> >  - mvn clean install  -DskipTests
> > * Unit tests pass (11.0.19): failed
> >  - mvn clean package -P runAllTests
> >  -Dsurefire.rerunFailingTestsCount=3
> >
> > TestSpnegoHttpServer and TestProxyUserSpnegoHttpServer in hbase-http
> > consistently failed but it may be environmental, related to local keberos
> > configs.
> >
> > On Sun, May 28, 2023 at 8:13 AM Duo Zhang  wrote:
> >
> > > Please vote on this Apache hbase release candidate,
> > > hbase-3.0.0-alpha-4RC0
> > >
> > > The VOTE will remain open for at least 72 hours.
> > >
> > > [ ] +1 Release this package as Apache hbase 3.0.0-alpha-4
> > > [ ] -1 Do not release this package because ...
> > >
> > > The tag to be voted on is 3.0.0-alpha-4RC0:
> > >
> > >   https://github.com/apache/hbase/tree/3.0.0-alpha-4RC0
> > >
> > > This tag currently points to git reference
> > >
> > >   e44cc02c75ecae7ece845f04722eb16b7528393f
> > >
> > > The release files, including signatures, digests, as well as CHANGES.md
> > > and RELEASENOTES.md included in this RC can be found at:
> > >
> > >   https://dist.apache.org/repos/dist/dev/hbase/3.0.0-alpha-4RC0/
> > >
> > > Maven artifacts are available in a staging repository at:
> > >
> > >
> > https://repository.apache.org/content/repositories/orgapachehbase-1520/
> > >
> > > Maven artifacts for hadoop3 are available in a staging repository at:
> > >
> > >   https://repository.apache.org/content/repositories/not-applicable/
> > >
> > > Artifacts were signed with the 0x9AD2AE49 key which can be found in:
> > >
> > >   https://downloads.apache.org/hbase/KEYS
> > >
> > > 3.0.0-alpha-4 is the fourth alpha release for our 3.0.0 major release
> > line.
> > > HBase 3.0.0 includes the following big feature/changes:
> > >   Synchronous Replication
> > >   OpenTelemetry Tracing
> > >   Distributed MOB Compaction
> > >   Backup and Restore
> > >   Move RSGroup balancer to core
> > >   Reimplement sync client on async client
> > >   CPEPs on shaded protobuf
> > >   Move the logging framework from log4j to log4j2
> > >   Decouple region replication and general replication framework, and
> > >   also make region replication can work when SKIP_WAL is used
> > >   A new file system based replication peer storage
> > >   Used hbase table instead of zookeeper for tracking hbase replication
> > > queue
> > >
> > > Notice that this is not a production ready release. It is used to let
> our
> > > users try and test the new major release, to get feedback before the
> > final
> > > GA release is out.
> > > So please do NOT use it in production. Just try it and report back
> > > everything you find unusual.
> > >
> > > And this time we will not include CHANGES.md and RELEASENOTE.md
> > > in our source code, you can find it on the download site. For getting
> > these
> > > two files for old releases, please go to
> > >
> > >   https://archive.apache.org/dist/hbase/
> > >
> > > To learn more about Apache hbase, please see
> > >
> > >   http://hbase.apache.org/
> > >
> > > Thanks,
> > > Your HBase Release Manager
> > >
> >
> >
> > --
> > Best regards,
> > Andrew
> >
> > Unrest, ignorance distilled, nihilistic imbeciles -
> > It's what we’ve earned
> > Welcome, apocalypse, what’s taken you so long?
> > Bring us the fitting end that we’ve been counting on
> >- A23, Welcome, Apocalypse
> >
>
>
> --
> Regards,
> Shanmukha Kota
>

Re: [ANNOUNCE] Duo Zhang (张铎) joins the Apache HBase PMC

[Guanghao Zhang]

Congratulations!

2016-09-07 12:56 GMT+08:00 ramkrishna vasudevan <
ramkrishna.s.vasude...@gmail.com>:

> Congrats Duo..!!!
>
> On Wed, Sep 7, 2016 at 10:16 AM, liushaohui  wrote:
>
> > Congratulations~
> >
> > -Shaohui Liu
> >
> >
> > On 09/07/2016 12:26 PM, Stack wrote:
> >
> >> On behalf of the Apache HBase PMC I am pleased to announce that 张铎
> >> has accepted our invitation to become a PMC member on the Apache
> >> HBase project. Duo has healthy notions on where the project should be
> >> headed and over the last year and more has been working furiously to
> take
> >> us there.
> >>
> >> Please join me in welcoming Duo to the HBase PMC!
> >>
> >> One of us!
> >> St.Ack
> >>
> >>
> >
>

Re: [ANNOUNCE] New HBase committer Phil Yang

[Guanghao Zhang]

Congratulations!

2016-11-29 17:49 GMT+08:00 Duo Zhang :

> On behalf of the Apache HBase PMC, I am pleased to announce that Phil Yang
> has accepted the PMC's invitation to become a committer on the project. We
> appreciate all of Phil's generous contributions thus far and look forward
> to his continued involvement.
>
> Congratulations and welcome, Phil!
>

Re: [ANNOUNCE] New HBase committer Lijin Bin

[Guanghao Zhang]

Congratulations!

2016-11-29 17:48 GMT+08:00 Duo Zhang :

> On behalf of the Apache HBase PMC, I am pleased to announce that Lijin
> Bin(binlijin) has accepted the PMC's invitation to become a committer on
> the project. We appreciate all of Lijin's generous contributions thus far
> and look forward to his continued involvement.
>
> Congratulations and welcome, Lijin!
>

Re: Question about RPC call timeout

[Guanghao Zhang]

Yes. For idempotent operations, the same rpc call can be executed twice.

2016-12-10 7:17 GMT+08:00 wang shu :

> Hi all,
>
> I have a very stress test on hbase by creating 1000 threads at the client
> side, and each thread will call PUT function, and the client will throw out
> some rpctimeout exception. It seems that the client will continue retrying
> until the result is not NULL. Is that possible the rpc call already reach
> the server rpc calllqueue, but still have timeout exception? If it is true,
> does that mean the same rpc call will be executed twice?
>
> Thanks a lot for your help.
>
> Best,
>
> Shu
>

Re: [ANNOUNCE] New HBase committer Guanghao Zhang

[Guanghao Zhang]

Thanks all. Looking forward to work with you guys and keep contributing for
HBase. Thanks.

2016-12-20 16:48 GMT+08:00 Yu Li :

> Congratulations and welcome Guanghao!
>
> Best Regards,
> Yu
>
> On 20 December 2016 at 12:59, 宾莉金 or binlijin  wrote:
>
> > Congratulations and welcome!
> >
> > 2016-12-20 12:54 GMT+08:00 Nick Dimiduk :
> >
> > > Congratulations Guanghao and thank you for all your contributions!
> > >
> > > On Mon, Dec 19, 2016 at 5:37 PM Duo Zhang  wrote:
> > >
> > > > On behalf of the Apache HBase PMC, I am pleased to announce that
> > Guanghao
> > > >
> > > > Zhang has accepted the PMC's invitation to become a committer on the
> > > >
> > > > project. We appreciate all of Guanghao's generous contributions thus
> > far
> > > >
> > > > and look forward to his continued involvement.
> > > >
> > > >
> > > >
> > > > Congratulations and welcome, Guanghao!
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > *Best Regards,*
> >  lijin bin
> >
>

Re: Moving 2.0 forward

[Guanghao Zhang]

For 6. Significant contirbs in master only, there are some issues about
replication operations routed through master. They are sub-task
of HBASE-10504. And there are other umbrella issue for replication, like
HBase-14379 Replication V2 and HBASE-15867 Moving HBase Replication
tracking from Zookeeper to HBase. So i thought we can add a new section named
hbase-replication to possible 2.0.0s. This will help us to track the state.
Thanks.

Re: Inconsistent behavior of scan with filter and maxVersions?

[Guanghao Zhang]

There is a issue HBASE-17125 about this inconsistent problem but we didn't
have a final solution. You can take a look about the discussion. Thanks.

2017-02-28 9:26 GMT+08:00 Huaxiang Sun :

> Hi HBase Devs,
>
> Nicolae Popa found an inconsistent behavior when doing scan with
> filter, there is maxVersions configured for column family.
> Start with the example.
>
> hbase(main):001:0> create 't1', {NAME => 'f1', VERSIONS => 1}
> hbase(main):002:0> put 't1', 'r1', 'f1:q1', 'a'
> hbase(main):003:0> put 't1', 'r1', 'f1:q1', ‘b'
>
> // There are two versions for r1, f1:q1
>
> hbase(main):004:0> scan 't1'
> ROW  COLUMN+CELL
>  r1  column=f1:q1,
> timestamp=1488244089712, value=b
> 1 row(s)
>
> // Scan with value filter ‘a’, returns the cell for ‘a’, even maxVersions
> is configured to be 1
> hbase(main):006:0> scan 't1', {FILTER => "ValueFilter(=,'binary:a')"}
> ROW  COLUMN+CELL
>  r1  column=f1:q1,
> timestamp=1488244087738, value=a
> 1 row(s)
> hbase(main):007:0> scan 't1', {FILTER => "ValueFilter(=,'binary:b')"}
> ROW  COLUMN+CELL
>  r1  column=f1:q1,
> timestamp=1488244089712, value=b
> 1 row(s)
>
> // After flush and major compaction, the older version is deleted from
> hfile.
> hbase(main):011:0> flush 't1'
> hbase(main):012:0> major_compact 't1'
> hbase(main):013:0> scan 't1', {FILTER => "ValueFilter(=,'binary:b')"}
> ROW  COLUMN+CELL
>  r1  column=f1:q1,
> timestamp=1488244089712, value=b
> 1 row(s)
>
> //Scan with value filter ‘a’, returns nothing now.
> hbase(main):014:0> scan 't1', {FILTER => "ValueFilter(=,'binary:a')"}
> ROW  COLUMN+CELL
> 0 row(s)
> hbase(main):015:0>
>
> In the above example, the scan result for valueFilter ‘a” is inconsistent
> across flush and major compaction. The reason is that when filter returns
> SKIP, the version count is not increased. The older version is treated as
> the latest version.
>
> Is this the expected behavior? when maxVersions is specified in HCD, is
> user supposed to see the latest maxVersions or it could be affected by
> filters? It is not a raw scan in this example.
>
> Thanks,
> Huaxiang Sun

Re: ANNOUNCE: Good news!!!! Two new PMC and a new Committer!

[Guanghao Zhang]

Congratulations!

2017-03-17 14:49 GMT+08:00 ashish singhi :

> Many congratulations, Josh, Jing Chen He and Eshcar !!!
>
> -Original Message-
> From: saint@gmail.com [mailto:saint@gmail.com] On Behalf Of Stack
> Sent: 17 March 2017 11:07
> To: HBase Dev List 
> Subject: ANNOUNCE: Good news Two new PMC and a new Committer!
>
> Josh Elser and Jing Chen (Jerry) have both been added to the HBase PMC.
> These lads have been stellar helping the project along; Jerry for a good
> few years now and Josh, though less time served, has made up for the lack
> with style. It makes sense that they be made PMCers!
>
> Let me take this opportunity while I have your attention to also welcome
> Eshcar Hillel as a Committer on Apache HBase. We are very glad to have her
> on-board. She's a brainbox who has been working on the inmemory compaction
> project among other things and is without fear when it comes to taking a
> deep dive into crud!
>
> Welcome aboard Josh, Jing Chen He, and Eshcar!
>
> St.Ack
>

Re: [ANNOUNCE] New HBase committer Chia-Ping Tsai

[Guanghao Zhang]

Congratulations！

2017-03-20 9:08 GMT+08:00 宾莉金 or binlijin :

> Congratulations and welcome!
>
> 2017-03-19 15:43 GMT+08:00 Phil Yang :
>
> > Congratulations!
> >
> > Thanks,
> > Phil
> >
> >
> > 2017-03-18 20:38 GMT+08:00 Ashish Singhi  >:
> >
> > > Many Congratulations !
> > >
> > > On Sat, Mar 18, 2017 at 4:00 AM, Anoop John 
> > wrote:
> > >
> > > > On behalf of the Apache HBase PMC, I am pleased to announce that
> > > Chia-Ping
> > > > Tsai
> > > > has accepted the PMC's invitation to become a committer on the
> project.
> > > We
> > > > appreciate all of his contributions thus far and look forward
> > > > to his continued involvement.
> > > >
> > > > Congratulation and welcome Chia-Ping Tsai!
> > > >
> > > > -Anoop-
> > > >
> > >
> >
>
>
>
> --
> *Best Regards,*
>  lijin bin
>

Re: ANNOUNCE: Yu Li joins the Apache HBase PMC

[Guanghao Zhang]

Congratulations!

2017-04-16 21:36 GMT+08:00 Yu Li :

> Thanks all! My honor and will do my best.
>
> Best Regards,
> Yu
>
> On 16 April 2017 at 14:20, 张铎(Duo Zhang)  wrote:
>
> > Congratulations!
> >
> > 2017-04-16 11:24 GMT+08:00 Mikhail Antonov :
> >
> >> Congratulations Yu!
> >>
> >> -Mikhail
> >>
> >> On Sat, Apr 15, 2017 at 12:44 PM, Nick Dimiduk 
> >> wrote:
> >>
> >> > Congratulations Yu and thanks a lot! Keep up the good work!
> >> >
> >> > On Fri, Apr 14, 2017 at 7:22 AM Anoop John 
> >> wrote:
> >> >
> >> > > On behalf of the Apache HBase PMC I"m pleased to announce that Yu Li
> >> > > has accepted our invitation to become a PMC member on the Apache
> HBase
> >> > > project. He has been an active contributor to HBase for past many
> >> > > years. Looking forward for
> >> > > many more contributions from him.
> >> > >
> >> > > Welcome to the PMC, Yu Li...
> >> > >
> >> > >
> >> > > -Anoop-
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Thanks,
> >> Michael Antonov
> >>
> >
> >
>

Re: [VOTE] First release candidate for HBase 1.2.6 is available

[Guanghao Zhang]

hbase-1.2.6-bin.tar.gz
- Verified md5sum: ok
- Start HBase in standalone mode: ok
- Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
- Checked master/regionserver/table Web UI and found a problem: Table UI,
split/compact not work with a given key. It was fixed by HBASE-3462. But
the fix was only merged to master branch. I thought this is a bug fix so it
should be merged to branch-1.2, too?

Exception:
java.lang.IllegalArgumentException: Invalid region: 50
at
org.apache.hadoop.hbase.client.HBaseAdmin.splitRegion(HBaseAdmin.java:2668)
at
org.apache.hadoop.hbase.client.HBaseAdmin.splitRegion(HBaseAdmin.java:2605)
at
org.apache.hadoop.hbase.generated.master.table_jsp._jspService(table_jsp.java:127)

Thanks.

2017-05-31 23:38 GMT+08:00 Andrew Purtell :

> +1
>
> ​Checked sums and signatures: ok
> Unpacked tarballs, layout looks good
> Built from source: ok (7u80)
> RAT check passes: ok (7u80)
> Unit test passes: ok (7u80)
> Loaded 1M rows with LTT: ok, all keys verified, latencies in the ballpark,
> no unusual messages or warnings (8u121)​
> API compatibility report looks good
>
>
> On Mon, May 29, 2017 at 9:31 AM, Sean Busbey  wrote:
>
> > The first release candidate for HBase 1.2.6 is available for download at:
> >
> > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.2.6RC0/
> >
> > Maven artifacts are also available in a staging repository at:
> >
> > https://repository.apache.org/content/repositories/orgapachehbase-1168/
> >
> > Artifacts are signed with my key (0D80DB7C) published in our KEYS
> > file at http://www.apache.org/dist/hbase/KEYS
> >
> > The RC corresponds to the signed tag 1.2.6RC0, which currently points
> > to commit ref
> >
> > 2f9b9e17d0522e36063bf52ecc58576243d20b3f
> >
> > The detailed source and binary compatibility report vs 1.2.5 has been
> > published for your review, at:
> >
> > https://s.apache.org/hbase-1.2.6-rc0-compat-report
> >
> > HBase 1.2.6 is the sixth maintenance release in the HBase 1.2 line,
> > continuing on the theme of bringing a stable, reliable database to
> > the Hadoop and NoSQL communities. This release includes over 25
> > bug fixes since 1.2.5.
> >
> > Critical fixes include:
> >
> > * HBASE-17287 - Master becomes a zombie if filesystem object closes
> > * HBASE-16630 - Fragmentation in long running Bucket Cache
> > * HBASE-17717 - Incorrect ZK ACL set for HBase superuser
> > * HBASE-15941 - HBCK repair should not unsplit healthy splitted region
> >
> > The full list of fixes included in this release is available at:
> >
> > https://s.apache.org/hbase-1.2.6-jira-release-notes
> >
> > and in the CHANGES.txt file included in the distribution.
> >
> > Please try out this candidate and vote +1/-1 on whether we should
> > release these artifacts as HBase 1.2.6.
> >
> > The VOTE will remain open for at least 72 hours. Given sufficient votes
> > I would like to close it on June 5th, 2017.
> >
> > thanks!
> >
>
>
>
> --
> Best regards,
>
>- Andy
>
> If you are given a choice, you believe you have acted freely. - Raymond
> Teller (via Peter Watts)
>

Re: [ANNOUNCE] New HBase committer Allan Yang

[Guanghao Zhang]

Congratulations!

2017-06-09 13:41 GMT+08:00 Jingcheng Du :

> Congratulations!
>
> 2017-06-09 13:20 GMT+08:00 Karan Mehta :
>
> > Congratulations, Allan!! :)
> >
> > Thanks,
> > Karan
> > ᐧ
> >
> > On Thu, Jun 8, 2017 at 10:11 PM, Stack  wrote:
> >
> > > Hurray!
> > >
> > > On Thu, Jun 8, 2017 at 8:49 PM, Yu Li  wrote:
> > >
> > > > On behalf of the Apache HBase PMC, I am pleased to announce that
> Allan
> > > Yang
> > > > has accepted the PMC's invitation to become a committer on the
> > > > project. We appreciate all of Allan's generous contributions thus far
> > and
> > > > look forward to his continued involvement.
> > > >
> > > > Congratulations and welcome, Allan!
> > > >
> > >
> >
>

Re: [ANNOUNCE] New Apache HBase committer Ashu Pachauri

[Guanghao Zhang]

Congratulations and welcome!

2017-06-17 7:27 GMT+08:00 Gary Helmling :

> On behalf of the Apache HBase PMC, I am pleased to announce that Ashu
> Pachauri has accepted the PMC's invitation to become a committer on the
> project.  We appreciate all of Ashu's generous contributions thus far and
> look forward to his continued involvement.
>
> Congratulations and welcome, Ashu!
>

Re: default ReplicationEndpoint implementation?

[Guanghao Zhang]

The default ReplicationEndpoint's implementation is
HBaseInterClusterReplicationEndpoint. You can take a look about
https://issues.apache.org/jira/browse/HBASE-11367 to find more details.

2017-06-18 21:51 GMT+08:00 Jan Kunigk :

> Hello, does someone happen to know what the default ReplicationEndpoint
> implementation is?
> hbase shell allows to specify an ENDPOINT_CLASSNAME, but one can also use
> add_peer without specifying it.
> ReplicationPeerConfig also does not seem to subscribe a default
> implementation, so I wonder wether there is a configuration option in one
> of the xml file that I fail to find...
>
> Regards, J
>

Re: Difference between peerData and configuration in ReplicationPeerConfig

[Guanghao Zhang]

We have a ReplicationEndpoint implementation which replicate data to a
streaming system(similar to kafka). And only use the configuration for the
endpoint. I don't know the difference between DATA and CONFIG. I thought
use CONFIG is enough for most cases.

2017-06-18 22:01 GMT+08:00 Jan Kunigk :

> Hi, I am aware this might be pretty much a newbie question but I struggle
> to see any docs on the what peerData and or configuration in
> ReplicationPeerConfig should be used for...
>
>   private final Map peerData;
>   private final Map configuration;
>
> I would like to use them in a way that I feel apt to support a JIRA I am
> working on, but I want to make sure I do not miss the understanding of a
> different designated use. The configuration field seems to be quite clear
> from the context, but what about peerData?
>
> src/main/ruby/shell/commands/add_peer.rb clarifies the syntax but not the
> semantics...
>  hbase> add_peer '9', ENDPOINT_CLASSNAME =>
> 'org.apache.hadoop.hbase.MyReplicationEndpoint',
> DATA => { "key1" => 1 }, CONFIG => { "config1" => "value1", "config2"
> => "value2" },
>
> Again, I hope I am not missing something obvious and would appreciate any
> pointer.
>
>
> Best, J
>

Re: [ANNOUNCE] New HBase committer Huaxiang Sun

[Guanghao Zhang]

Congratulations and welcome, Huaxiang!

2017-06-20 8:15 GMT+08:00 Jimmy Xiang :

> Congrats!
>
> On Mon, Jun 19, 2017 at 5:02 PM, Stephen Jiang 
> wrote:
> > Congrats and welcome to the team!
> >
> > Stephen
> >
> > On Mon, Jun 19, 2017 at 1:43 PM, Mike Drob  wrote:
> >
> >> Great work, Huaxiang!
> >>
> >> On Mon, Jun 19, 2017 at 2:30 PM, Sean Busbey  wrote:
> >>
> >> > On behalf of the Apache HBase PMC, I am pleased to announce that
> >> > Huaxiang Sun has accepted the PMC's invitation to become a committer
> >> > on the project. We appreciate all of Huaxiang's great work thus far
> >> > and look forward to continued involvement.
> >> >
> >> > Please join me in congratulating Huaxiang!
> >> >
> >>
>

Re: Re: [ANNOUNCE] Devaraj Das joins the Apache HBase PMC

[Guanghao Zhang]

Congratulations!

2017-07-06 10:52 GMT+08:00 Yu Li :

> Congratulations Devaraj!
>
> Best Regards,
> Yu
>
> On 6 July 2017 at 10:37, Chunhui Shen  wrote:
>
> > Congratulations!
> >
> >
> > At 2017-07-06 09:52:17, "Allan Yang"  wrote:
> > >Congratulations, Devaraj !
> > >
> > >Best Regards
> > >Allan Yang
> > >
> > >2017-07-06 9:44 GMT+08:00 Pankaj kr :
> > >
> > >> Congratulations Devaraj..!!
> > >>
> > >> Thanks & Regards,
> > >> Pankaj
> > >>
> > >> HUAWEI TECHNOLOGIES CO.LTD.
> > >> Huawei Tecnologies India Pvt. Ltd.
> > >> Near EPIP Industrial Area, Kundalahalli Village
> > >> Whitefield, Bangalore-560066
> > >> www.huawei.com
> > >> 
> > >> -
> > >> This e-mail and its attachments contain confidential information from
> > >> HUAWEI, which
> > >> is intended only for the person or entity whose address is listed
> above.
> > >> Any use of the
> > >> information contained herein in any way (including, but not limited
> to,
> > >> total or partial
> > >> disclosure, reproduction, or dissemination) by persons other than the
> > >> intended
> > >> recipient(s) is prohibited. If you receive this e-mail in error,
> please
> > >> notify the sender by
> > >> phone or email immediately and delete it!
> > >>
> > >>
> > >> -Original Message-
> > >> From: Josh Elser [mailto:els...@apache.org]
> > >> Sent: Thursday, July 06, 2017 12:27 AM
> > >> To: dev@hbase.apache.org; u...@hbase.apache.org
> > >> Subject: [ANNOUNCE] Devaraj Das joins the Apache HBase PMC
> > >>
> > >> I'm pleased to announce yet another PMC addition in the form of
> Devaraj
> > >> Das. One of the "old guard" in the broader Hadoop umbrella, he's also
> a
> > >> long-standing member in our community. We all look forward to the
> > continued
> > >> contributions and project leadership.
> > >>
> > >> Please join me in welcoming Devaraj!
> > >>
> > >> - Josh (on behalf of the PMC)
> > >>
> >
>

One problem about document change

[Guanghao Zhang]

Hi, folks

Now I am working on the asynchronous admin which is part of asynchronous
client. The asynchronous client feature were pushed to branch-2 and master
branch. But one confuse thing is about the document change. The book site
is generated by master branch's code. So the document change should only be
pushed to master branch? Or it should be pushed to branch-2 and master
both, because this feature was merged to branch-2, too? I am not sure about
this, so look forward to you guys' idea. Thanks.

Guanghao Zhang

Re: One problem about document change

[Guanghao Zhang]

Thanks for your explanation. So if we only push it to master branch, we
should only add master tag to the fix versions of the document issue, right?

2017-07-17 22:00 GMT+08:00 Sean Busbey :

> Contributors and committers usually only worry about making documentation
> changes to the master branch.
>
> When it comes time to spin up release candidates for a new version, the
> release manager usually copies the then-current state of documentation in
> the master branch to the branch they'll be working from (in this case
> branch-2). Sometimes that documentation is also tailored further to the
> release line (e.g. to remove irrelevant feature discussion).
>
> On Sun, Jul 16, 2017 at 9:16 AM, Guanghao Zhang 
> wrote:
>
> > Hi, folks
> >
> > Now I am working on the asynchronous admin which is part of asynchronous
> > client. The asynchronous client feature were pushed to branch-2 and
> master
> > branch. But one confuse thing is about the document change. The book site
> > is generated by master branch's code. So the document change should only
> be
> > pushed to master branch? Or it should be pushed to branch-2 and master
> > both, because this feature was merged to branch-2, too? I am not sure
> about
> > this, so look forward to you guys' idea. Thanks.
> >
> > Guanghao Zhang
> >
>

[ANNOUNCE] Asynchronous client is available in HBase 2.0

[Guanghao Zhang]

Dear all,

Asynchronous client aims to provide the ability to access HBase
asynchronously. You can obtain an AsyncConnection from ConnectionFactory,
and then get an asynchronous table instance (for DML operations) or an
asynchronous admin instance (for DDL operations) from it to access HBase.
For the asynchronous table or admin, most methods have the same meaning
with the old Table or Admin interface, expect that the return value is
wrapped with a CompletableFuture (java 8 or higher is required) usually.
You can get more details from the documentation[1][2].

There are two examples about the asynchronous client. AsyncClientExample[3]
is a simple example to show you how to use AsyncTable. HttpProxyExample[4]
is an example for advance user to show you how to use RawAsyncTable to
write a fully asynchronous HTTP proxy server. Welcome to try the
asynchronous client in your project.

We tested the performance of asynchronous client by
the PerformanceEvaluation tool. And it showed that async client has almost
same latency with sync client[5]. Notice: when we did performance test for
asynchronous client. We found some performance issue when use jdk 1.8_111.
And it was fixed when use jdk 1.8_131 [6]. So suggest use a bigger version
than jdk8_131 when you use the asynchronous client.

The major umbrella issues include:
HBASE-16432 Revisit the asynchronous ipc implementation[7]
HBASE-16833 Implement asynchronous hbase client based on HBASE-15921[8]
HBASE-17359 Implement async admin[9]

There is also an issue HBASE-17856 to track the further improvements for
asynchronous hbase client[10].

Finally, thanks Duo Zhang and Zheng Hu who worked with me together to
implement the asynchronous client.

Best Regards,
Guanghao

[1] https://hbase.apache.org/book.html#async.client
[2] https://hbase.apache.org/book.html#async.admin
[3]
https://github.com/apache/hbase/blob/master/hbase-examples/src/main/java/org/apache/hadoop/hbase/client/example/AsyncClientExample.java
[4]
https://github.com/apache/hbase/blob/master/hbase-examples/src/main/java/org/apache/hadoop/hbase/client/example/HttpProxyExample.java
[5] https://www.slideshare.net/HBaseCon/hbase-at-xiaomi
[6]
http://hg.openjdk.java.net/jdk8/jdk8/jdk/file/687fd7c7986d/src/share/classes/java/util/concurrent/CompletableFuture.java
[7] https://issues.apache.org/jira/browse/HBASE-16432
[8] https://issues.apache.org/jira/browse/HBASE-16833
[9] https://issues.apache.org/jira/browse/HBASE-17359
[10] https://issues.apache.org/jira/browse/HBASE-17856

Re: [ANNOUNCE] New HBase committer Mike Drob

[Guanghao Zhang]

Congratulations！

2017-08-04 5:34 GMT+08:00 Ted Yu :

> Congratulations, Mike.
>
> (Just got access to gmail).
>
> On Tue, Aug 1, 2017 at 8:38 AM, Josh Elser  wrote:
>
> > On behalf of the Apache HBase PMC, I'm pleased to announce that Mike Drob
> > has accepted the PMC's invitation to become a committer.
> >
> > Mike has been doing some great things lately in the project and this is a
> > simple way that we can express our thanks. As my boss likes to tell me:
> the
> > reward for a job well-done is more work to do! We're all looking forward
> to
> > your continued involvement :)
> >
> > Please join me in congratulating Mike!
> >
> > - Josh
> >
>

Re: [ANNOUNCE] Asynchronous client is available in HBase 2.0

[Guanghao Zhang]

@stack, sorry for reply late, sir. As HBASE-16388
<https://issues.apache.org/jira/browse/HBASE-16388> said, the client
threads may be blocked by only one slow region server. But a better
solution for this problem is to use async hbase client. And there are many
reasons to make a region server slow, slow read from hdfs, gc stw, etc. So
this should be a advantage of the async client. PS: my colleague Zheng Hu
talked about this problem on today's HBaseCon Asia :-). About the
performance of async client, there are two important metrics: latency and
QPS. Our PE tool can be used to test latency and it will be addressed by
HBASE-17994 <https://issues.apache.org/jira/browse/HBASE-17994>. And YCSB
maybe better to test QPS. I will publish the test result when we get more
test data. Thanks.


2017-07-22 0:35 GMT+08:00 Andrew Purtell :

> This is exciting!
> Thanks so much for this hard work.
>
> On Fri, Jul 21, 2017 at 2:21 AM, Phil Yang  wrote:
>
> > I filed an issue HBASE-18334
> > <https://issues.apache.org/jira/browse/HBASE-18334> to remove the old
> sync
> > implementation. I think we can do it in 3.0 and keep sync logic in
> > branch-2? Of course we can also remove it in 2.1 or higher 2.x branch but
> > if we remove it since 2.0 it may be a little radical  :)
> >
> > Thanks,
> > Phil
> >
> >
> > 2017-07-21 6:15 GMT+08:00 Stack :
> >
> > > Very sweet Guanghao. Thanks for all the hard work (you, Duo and all who
> > > contributed to the async work).
> > >
> > > When you think we should move the sync client to be on top of the async
> > > chassis?
> > >
> > > Thanks,
> > > St.Ack
> > >
> > > P.S. It looks like you updated its status in this doc,
> > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > ktczrlKHK8N4SZzs/edit#,
> > > thanks.
> > >
> > > On Thu, Jul 20, 2017 at 4:51 AM, Guanghao Zhang 
> > > wrote:
> > >
> > > > Dear all,
> > > >
> > > > Asynchronous client aims to provide the ability to access HBase
> > > > asynchronously. You can obtain an AsyncConnection from
> > ConnectionFactory,
> > > > and then get an asynchronous table instance (for DML operations) or
> an
> > > > asynchronous admin instance (for DDL operations) from it to access
> > HBase.
> > > > For the asynchronous table or admin, most methods have the same
> meaning
> > > > with the old Table or Admin interface, expect that the return value
> is
> > > > wrapped with a CompletableFuture (java 8 or higher is required)
> > usually.
> > > > You can get more details from the documentation[1][2].
> > > >
> > > > There are two examples about the asynchronous client.
> > > AsyncClientExample[3]
> > > > is a simple example to show you how to use AsyncTable.
> > > HttpProxyExample[4]
> > > > is an example for advance user to show you how to use RawAsyncTable
> to
> > > > write a fully asynchronous HTTP proxy server. Welcome to try the
> > > > asynchronous client in your project.
> > > >
> > > > We tested the performance of asynchronous client by
> > > > the PerformanceEvaluation tool. And it showed that async client has
> > > almost
> > > > same latency with sync client[5]. Notice: when we did performance
> test
> > > for
> > > > asynchronous client. We found some performance issue when use jdk
> > > 1.8_111.
> > > > And it was fixed when use jdk 1.8_131 [6]. So suggest use a bigger
> > > version
> > > > than jdk8_131 when you use the asynchronous client.
> > > >
> > > > The major umbrella issues include:
> > > > HBASE-16432 Revisit the asynchronous ipc implementation[7]
> > > > HBASE-16833 Implement asynchronous hbase client based on
> HBASE-15921[8]
> > > > HBASE-17359 Implement async admin[9]
> > > >
> > > > There is also an issue HBASE-17856 to track the further improvements
> > for
> > > > asynchronous hbase client[10].
> > > >
> > > > Finally, thanks Duo Zhang and Zheng Hu who worked with me together to
> > > > implement the asynchronous client.
> > > >
> > > > Best Regards,
> > > > Guanghao
> > > >
> > > > [1] https://hbase.apache.org/book.html#async.client
> > > > [2] https://hbase.apache.org/book.html#async.admin
> > > > [3]
> > > > https://github.com/apache/hbase/blob

Re: Moving 2.0 forward

[Guanghao Zhang]

About compatibility, there is one incompatible change about the replication
TableCFs' config. The old config is a string and it concatenate the list of
tables and column families in format "table1:cf1,cf2;table2:cfA,cfB" in
zookeeper for table-cf to replication peer mapping. When parse the config,
it use ":" to split the string. If table name includes namespace, it will
be wrong (See HBASE-11386
). It is a problem since
we support namespace (0.98). So HBASE-11393
 (and HBASE-16653
) changed it to a PB
object. When rolling update cluster, you need rolling master first. And the
master will try to translate the string config to a PB object. But there
are two problems.
1. Permission problem. The replication client can write the zookeeper
directly. So the znode may have different owner. And master may don't have
the write permission for the znode. It maybe failed to translate old
table-cfs string to new PB Object. See HBASE-16938

2. We usually keep compatibility between old client and new server. But the
old replication client may write a string config to znode directly. Then
the new server can't parse them.

PS: HBASE-11386 is a problem since 0.98. But there are not too many users
report this problem. So it maybe not a big incompatible issue..

2017-08-15 1:54 GMT+08:00 Stack :

> Heads-up:
>
> I'm about to put up an hbase-2.0.0-alpha2 Release Candidate. Theme is
> updated dependencies, reliance on relocated popular libs (guava, netty,
> protobuf), purge of checked-in generated src, and master-carries-no-regions
> by default.
>
> alpha3 I hope will follow soon after (end-of-August?). Its theme will be
> settling the APIs and compatibility (At first blush, we are not looking too
> bad; our Sean ran some tests over weekend that have hbase-1 client running
> against an hbase-2 cluster). The Coprocessor Interface revamp should be
> done by alpha3 (i.e. returning Interfaces rather than Implementations, and
> our shutdown of CPs accessing classes in hbase marked InterfaceAudience).
> We'll also have purged thirdparty classes from our API; e.g. guava 0.12
> Service showing through in our replication API and protobufs in Admin
> Interface. On alpha3, we will have to do a bunch of outreach to make sure
> our downstreamers are up on what is coming down the pipe.
>
> Beta1 in mid-September?
>
> I encourage you to check out the items marked for hbase2:
> https://issues.apache.org/jira/projects/HBASE/versions/12327188 Edit as
> you
> see appropriate. Punt if you know the JIRA will not get any attention in
> next month or so.
>
> A bunch of issues marked blocker are unassigned. I'll leave them as is
> another while but I'll boot them soon.
>
> While I have your attention:
>
> + I think we should leave thrift version at 0.9.3. Moving hbase thrift to
> 0.10.0 will break existing clients. The change is easy enough if folks need
> to upgrade their hbase thrift. See HBASE-18591.
> + Upgrade from 0.94 is disallowed. You have to get to 1.0 first (0.98?).
>
> St.Ack
>
>
>
> On Wed, Aug 2, 2017 at 9:43 AM, Stack  wrote:
>
> >
> >
> > On Tue, Aug 1, 2017 at 2:06 PM, Josh Elser  wrote:
> >
> >>
> >>
> >> On 7/31/17 9:00 AM, Stack wrote:
> >>
> >>> On Mon, Jul 24, 2017 at 12:25 PM, Josh Elser
> wrote:
> >>>
> >>> ...
> 
>  I like the idea of this also hitting 2.0 as it would make the feature
> a
>  bit more "real", but am obviously a little nervous (I have no reason
> to
>  be
>  nervous though). I am pretty happy with the feature in terms of how
>  much it
>  is covered via testing.
> 
>  https://issues.apache.org/jira/browse/HBASE-17748
> 
> 
> 
>  Sounds good to me. Whats involved? Backport? If so, +1 Josh.
> >>>
> >>> Last think on space quota says that need doc too. See 'Space Quota' in
> >>> here:
> >>> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
> >>> Eu_ktczrlKHK8N4SZzs/edit#heading=h.wuw3a6jukzo5
> >>> Does this little section need an update Josh?
> >>>
> >>> Thanks,
> >>> S
> >>>
> >>
> >> Yep, just a couple of cherry-picks. Good test coverage and some docs
> >> already included for 17748.  Happy to put that on my plate if you're
> good
> >> with it. I can reasonably assume that no one is against it :)
> >>
> >> I think I had knocked out docs for the "phase 1" stuff before we merged
> >> it in from the original feature branch. I'll double check and update the
> >> gdoc. Perhaps this was just a timing thing.
> >>
> >
> > Thanks Josh,
> > S
> >
>

Re: [VOTE] First hbase-2.0.0-alpha-2 Release Candidate is available

[Guanghao Zhang]

+1(non-binding)

Verified md5sum: ok
Build from source: ok
Start HBase in standalone mode: ok
Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
Checked master/regionserver/table/region Web UI: ok
Stop HBase: ok

2017-08-19 11:31 GMT+08:00 ramkrishna vasudevan <
ramkrishna.s.vasude...@gmail.com>:

> +1
> Untared the tar ball.
>
> Loaded some 100G data with PE .Did full table scan. Then ran randomReads
> with 500 threads with and without block cache.
> All seems to be fine.
>
> Regards
> Ram
>
> On Sat, Aug 19, 2017 at 2:33 AM, Stack  wrote:
>
> > On Fri, Aug 18, 2017 at 1:45 PM, Josh Elser  wrote:
> >
> > > +1 (binding)
> > >
> > > * Saw the same unit test failures as Andrew did (obviously)
> > > * Ran a brief randomWrite PE locally and didn't have any obvious issues
> > >
> > > I took a glance at the contents of the lib/ dir for the bin tarball,
> and
> > > noticed that we seem to be duplicating a few dependencies (e.g.
> > jetty-util,
> > > javax.servlet*, jersey*, aopalliance*). It probably wouldn't be a bad
> > idea
> > > to proactively look at these and compare to a 1.x release (for
> licensing
> > > purposes)
> > >
> > >
> > Thanks for testing. The REST one is a little involved but will be fixed
> by
> > alpha3 (with some sweet help from Samir).
> >
> > Good idea on review of lib-dir: HBASE-18630
> >
> > Thanks Josh,
> > St.Ack
> >
> >
> >
> > > On 8/16/17 4:43 PM, Stack wrote:
> > >
> > >> The first release candidate for HBase 2.0.0-alpha-2 is up at:
> > >>
> > >>https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-
> alpha-2RC0/
> > >>
> > >> Maven artifacts are available from a staging directory here:
> > >>
> > >>https://repository.apache.org/content/repositories/
> > orgapachehbase-1173
> > >>
> > >> All was signed with my key at y 8ACC93D2
> > >> 
> > >>
> > >>
> > >> I tagged the RC as 2.0.0-alpha-2RC0
> > >> (7149f999786b6fd5a3fc1f7aec1214afb738925e)
> > >>
> > >> hbase-2.0.0-alpha-2 includes all that was in alpha-1 (new assignment
> > >> manager, offheap read/write path, in-memory compactions, etc.) plus a
> > >> return to branch-1 deploy mode where master carries no regions
> (branch-2
> > >> and master up to this had master carrying system tables), a purge of
> all
> > >> checked-in generated content, updates to all dependencies including a
> > move
> > >> to rely on new hbase-thirdparty lib for relocated versions of guava,
> > >> netty,
> > >> and protobuf, etc.
> > >>
> > >> This is a rough cut ('alpha'), not-for-production preview of what
> > >> hbase-2.0.0 will look like meant for devs and downstreamers to test
> > drive
> > >> and flag us early if we messed up anything ahead of our rolling GAs.
> > >>
> > >> The list of features addressed in 2.0.0 so far can be found here [4].
> > >> There
> > >> are about 2700+. The list of ~500 fixes in 2.0.0 exclusively can be
> > found
> > >> here [3].
> > >>
> > >> I've updated our overview doc. on the state of 2.0.0 [1] but JIRA
> 2.0.0
> > >> label [2] has undergone extensive weeding and presents a fairly good
> > >> picture on what is yet to do before we 2.0.0. Check it out.
> > >>
> > >> Please take it for a spin and vote on whether it ok to put out as our
> > >> first
> > >> alpha (bar is low for an 'alpha'). Let the VOTE be open for 72 hours
> > >> (Saturday)
> > >>
> > >> Thanks,
> > >> St.Ack
> > >>
> > >> 1.
> > >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
> > >> Eu_ktczrlKHK8N4SZzs/edit#
> > >> 2. https://issues.apache.org/jira/projects/HBASE/versions/12327188
> > >> 3.
> > >> https://issues.apache.org/jira/browse/HBASE-18611?jql=projec
> > >> t%20%3D%20HBASE%20%20and%20(fixVersion%20%3D%202.0.0%20%7C%
> > >> 7C%20fixVersion%20%3D%202.0.0.alpha1%20%7C%7C%20fixVersion%
> > >> 20%3D%202.0.0-alpha-2)%20and%20fixVersion%20not%20in%20(1.
> > >> 0.0%2C%201.0.1%2C%201.0.2%2C%201.0.3%2C%201.0.4%2C%201.0.5%
> > >> 2C%201.0.6%2C%201.1.0%2C%201.1.1%2C%201.1.2%2C%201.1.3%2C%
> > >> 201.1.4%2C%201.1.5%2C%201.1.6%2C%201.1.7%2C%201.1.8%2C%201.
> > >> 1.9%2C%201.1.10%2C%201.2.0%2C%201.2.1%2C%201.2.2%2C%201.2.3%
> > >> 2C%201.2.4%2C%201.2.5%2C%201.2.6%2C%201.3.0%2C%201.3.1%2C%
> > >> 201.4.0)%20and%20%20(status%20%3D%20Open%20or%20status%20%
> > >> 3D%20%22Patch%20Available%22)
> > >> 4.
> > >> https://issues.apache.org/jira/browse/HBASE-18599?jql=projec
> > >> t%20%3D%20HBASE%20%20and%20(%20fixVersion%20%3D%202.0.0%20%7
> > >> C%7C%20fixVersion%20%3D%202.0.0-alpha-1%20%7C%7C%20fixVersio
> > >> n%20%3D%202.0.0-alpha-2)%20and%20(status%20%3D%20Resolved)
> > >>
> > >>
> >
>

Re: Please congratulate our new PMC Chair Misty Stanley-Jones

[Guanghao Zhang]

Congratulations!

2017-09-22 11:20 GMT+08:00 Chia-Ping Tsai :

> congrats Misty!!!
>
> On 2017-09-22 03:08, Andrew Purtell  wrote:
> > At today's meeting of the Board, Special Resolution B changing the HBase
> > project Chair to Misty Stanley-Jones was passed unanimously.
> >
> > Please join me in congratulating Misty on her new role!
> >
> > ​(If you need any help or advice please don't hesitate to ping me, Misty,
> > but I suspect you'll do just fine and won't need it.)​
> >
> >
> > --
> > Best regards,
> > Andrew
> >
>

Re: Welcome Chia-Ping Tsai to the HBase PMC

[Guanghao Zhang]

Congratulations!

2017-09-30 6:38 GMT+08:00 Andrew Purtell :

> Congratulations, Chia-Ping! Welcome to the PMC.
>
> On Fri, Sep 29, 2017 at 3:19 PM, Misty Stanley-Jones 
> wrote:
>
> > The HBase PMC is delighted to announce that Chia-Ping Tsai has agreed to
> > join
> > the HBase PMC, and help to make the project run smoothly. Chia-Ping
> became
> > an
> > HBase committer over 6 months ago, based on long-running participate in
> the
> > HBase project, a consistent record of resolving HBase issues, and
> > contributions
> > to testing and performance.
> >
> > Thank you for stepping up to serve, Chia-Ping!
> >
> > As a reminder, if anyone would like to nominate another person as a
> > committer or PMC member, even if you are not currently a committer or PMC
> > member, you can always drop a note to priv...@hbase.apache.org to let us
> > know!
> >
> > Thanks,
> > Misty (on behalf of the HBase PMC)
> >
>
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>- A23, Crosstalk
>

Re: [DISCUSS] Merge FilterList Improvement - Branch HBASE-18410

[Guanghao Zhang]

HBASE-18368-HBASE-18410.v2.patch got a proper QA
run: PreCommit-HBASE-Build/9157. And the failed ut is not related. So I
committed it to branch HBASE-18410...
HBASE-18368 changed the javadoc of NEXT_ROW. This is a incompatible change
for filter developer?

2017-10-20 9:14 GMT+08:00 Ted Yu :

> Some of recent patches, such as HBASE-18368-HBASE-18410.v2.patch, didn't
> get proper QA run (due to precommit disruption).
>
> We'd better get several good QA runs.
>
> Cheers
>
> On Thu, Oct 19, 2017 at 5:38 PM, 张铎(Duo Zhang) 
> wrote:
>
> > I believe there are several UTs which we want them to be the guard of
> > merging? What is the situation of these UTs?
> >
> > Thanks.
> >
> > 2017-10-20 8:33 GMT+08:00 OpenInx :
> >
> > > Hi All :
> > >
> > >
> > > All subtasks have been resolved except HBASE-18993
> > > , I think it's time
> > to
> > > merge HBASE-18410 
> > > branch
> > > to master now.
> > >
> > > Any concerns ?
> > >
> > > Thanks.
> > >
> >
>

Re: [ANNOUNCE] New HBase committer Zheng Hu

[Guanghao Zhang]

Congratulations!

2017-10-23 18:11 GMT+08:00 Jingcheng Du :

> Congratulations!
>
> 2017-10-23 16:00 GMT+08:00 OpenInx :
>
> > Thanks the HBase Community  &  the HBase Committee.  Will do my best to
> > grow with the community.
> >
> > On Mon, Oct 23, 2017 at 3:10 PM, Ted Yu  wrote:
> >
> > > Congratulations,  Cheng.
> > >  Original message From: libis 
> > > Date: 10/22/17  11:50 PM  (GMT-08:00) To: dev@hbase.apache.org
> Subject:
> > > Re: [ANNOUNCE] New HBase committer Zheng Hu
> > > Congratulations!!!
> > >
> > > 2017-10-23 14:21 GMT+08:00 ramkrishna vasudevan <
> > > ramkrishna.s.vasude...@gmail.com>:
> > >
> > > > Welcome Zheng and congratulations !!!
> > > >
> > > > On Mon, Oct 23, 2017 at 11:48 AM, Duo Zhang 
> > wrote:
> > > >
> > > > > On behalf of the Apache HBase PMC, I am pleased to announce that
> > Zheng
> > > Hu
> > > > > has accepted the PMC's invitation to become a committer on the
> > project.
> > > > We
> > > > > appreciate all of Zheng's generous contributions thus far and look
> > > > forward
> > > > > to his continued involvement.
> > > > >
> > > > > Congratulations and welcome, Zheng!
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > ==
> > Openinx  blog : http://openinx.github.io
> >
> > TO BE A GREAT HACKER !
> > ==
> >
>

Re: [ANNOUNCE] New HBase committer Lars Francke

[Guanghao Zhang]

Congratulations!

2017-10-26 14:25 GMT+08:00 Yu Li :

> Congratulations!
>
> Best Regards,
> Yu
>
> On 26 October 2017 at 13:39, Anoop John  wrote:
>
> > Congrats and welcome Lars F.
> >
> > -Anoop-
> >
> > On Thu, Oct 26, 2017 at 9:58 AM, ramkrishna vasudevan
> >  wrote:
> > > Welcome Lars..
> > >
> > > On Thu, Oct 26, 2017 at 9:54 AM, Misty Stanley-Jones  >
> > > wrote:
> > >
> > >> Welcome Lars!
> > >>
> > >> On Wed, Oct 25, 2017 at 7:24 PM Jingcheng Du 
> > wrote:
> > >>
> > >> > Congratulations!
> > >> >
> > >> > 2017-10-26 9:45 GMT+08:00 OpenInx :
> > >> >
> > >> > > Congratulations.
> > >> > >
> > >> > > On Thu, Oct 26, 2017 at 9:36 AM, 张铎(Duo Zhang) <
> > palomino...@gmail.com>
> > >> > > wrote:
> > >> > >
> > >> > > > Congratulations!
> > >> > > >
> > >> > > > 2017-10-26 4:35 GMT+08:00 Esteban Gutierrez <
> este...@cloudera.com
> > >:
> > >> > > >
> > >> > > > > Congrats Lars F! well deserved!
> > >> > > > >
> > >> > > > > --
> > >> > > > > Cloudera, Inc.
> > >> > > > >
> > >> > > > >
> > >> > > > > On Wed, Oct 25, 2017 at 3:26 PM, Andrew Purtell <
> > >> apurt...@apache.org
> > >> > >
> > >> > > > > wrote:
> > >> > > > >
> > >> > > > > > Congratulations and welcome!
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > On Wed, Oct 25, 2017 at 12:56 PM, Lars George <
> > >> > lars.geo...@gmail.com
> > >> > > >
> > >> > > > > > wrote:
> > >> > > > > >
> > >> > > > > > > On behalf of the Apache HBase PMC, I am pleased to
> announce
> > >> that
> > >> > > Lars
> > >> > > > > > > Francke has accepted the PMC's invitation to become a
> > committer
> > >> > on
> > >> > > > the
> > >> > > > > > > project.
> > >> > > > > > >
> > >> > > > > > > We appreciate all of Lars' great work thus far and look
> > forward
> > >> > to
> > >> > > > > > > continued involvement.
> > >> > > > > > >
> > >> > > > > > > Please join me in congratulating LarsF! (Opting to use
> last
> > >> name
> > >> > > > > > > initials as we now have three Lars' as committers)
> > >> > > > > > >
> > >> > > > > > > --
> > >> > > > > > > Best regards,
> > >> > > > > > > LarsG
> > >> > > > > > >
> > >> > > > > >
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > --
> > >> > > > > > Best regards,
> > >> > > > > > Andrew
> > >> > > > > >
> > >> > > > > > Words like orphans lost among the crosstalk, meaning torn
> from
> > >> > > truth's
> > >> > > > > > decrepit hands
> > >> > > > > >- A23, Crosstalk
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> > >
> > >> > >
> > >> > >
> > >> > > --
> > >> > > ==
> > >> > > Openinx  blog : http://openinx.github.io
> > >> > >
> > >> > > TO BE A GREAT HACKER !
> > >> > > ==
> > >> > >
> > >> >
> > >>
> >
>

Re: Moving 2.0 forward

[Guanghao Zhang]

I saw beta == no new features, no API changes, just fixes. And I am working
on HBASE-18805 to unify Admin and AsyncAdmin methods. The fix version was
2.0-beta-1. But I thought this will introduce API change(deprecate some API
and introduce new one). So should I change the fix versions to 2.0-alpha-4
and finish it before we release 2.0-alpha-4?

Issue HBASE-18978 (Align the methods in Table and AsyncTable) may have same
problem. Thanks.

2017-10-26 9:51 GMT+08:00 张铎(Duo Zhang) :

> OK, skimmed,  we are in trouble! The in memory compaction just use the same
> constructor with normal compaction to construct a StoreScanner, and use it
> to do compaction...
>
> We have to provide several preXXX and postXXX for it, at least we should
> allow user reset TTL and max versions, and also do filtering on the
> scanner.
>
> Thanks.
>
>
>
> 2017-10-26 9:41 GMT+08:00 张铎(Duo Zhang) :
>
> > When adding back the pre(Flush/Compact/Store)ScannerOpen methods in
> > HBASE-19033, I found that there maybe a hole in our CP hools. It is the
> in
> > memory compaction.
> >
> > As Anoop suggested in HBASE-19001, we still need to give user the ability
> > to extend the max versions and TTL config, so I plan to add back the
> hooks
> > above to let CP users can change the max versions and TTL of a ScanInfo
> > object. But I'm not sure whether in memory compaction will also discard
> > expired cells, if so then we are in trouble...
> >
> > Thanks.
> >
> > 2017-10-25 6:03 GMT+08:00 Stack :
> >
> >> Chatting with my coworker Mr. Mike Drob, we were batting back and forth
> >> what remains to be done. Surfacing our thoughts here so you all clued
> >> inOr if you think otherwise, please speak up.
> >>
> >> We have ~13 issues to land:
> >> https://issues.apache.org/jira/projects/HBASE/versions/12341594 About
> two
> >> are meta-issues that are about process which leaves 11.
> >>
> >> Duo and Zheng Hu are to merge the FilterList fixes improvements
> >> (HBASE-19057, HBASE-18410 et al.). These are blocker because some
> changed
> >> API/semantic that we need to get out earlier rather than later.
> >>
> >> Once the above is merged, HBASE-13346, change of Filter method names to
> >> mention Cell instead of KeyValue can land.
> >>
> >> HBASE-199048 needs a review (Anoop will probably do it), removing
> >> IA.Private objects as params to MasterObserver... Hopefully this goes in
> >> soon.
> >>
> >> Duo is hard at work on trackers for flush and compaction for CPs
> >> (HBASE-18905). How is HBASE-19033 looking Duo (facility for Tephra)?
> >>
> >> I think HBASE-18906 (Phoenix Region#waitFor...) will evaporate after Duo
> >> is
> >> done w/ his work above.
> >>
> >> I'm on HBASE-18770 bypass and HBASE-19077 restore some parity after all
> >> the
> >> purges allowing CPs do direct calls against Regions in same Host.
> >>
> >> Anoop is on HBASE-19047 (Fixes) and Ram on cleanup of CellUtil.
> >>
> >> Another day or two?
> >>
> >> St.Ack
> >>
> >>
> >>
> >> On Mon, Oct 23, 2017 at 2:52 PM, Stack  wrote:
> >>
> >> >
> >> > On Mon, Oct 23, 2017 at 11:59 AM, Josh Elser 
> wrote:
> >> >
> >> >> +1
> >> >>
> >> >> I was trying to work on helping out on the outstanding alpha-4 stuff
> >> last
> >> >> week -- will be continuing to try to do the same this week.
> >> >>
> >> >> If you need any help, Stack, or if others need reviews where I
> haven't
> >> >> noticed on my own: feel free to @mention me.
> >> >>
> >> >>
> >> > Thanks for the offer Josh. All items seem assigned and are being
> >> actively
> >> > worked on. If you get a moment, reviews by you (or anyone else) helps
> >> move
> >> > the process along.
> >> >
> >> > We need to merge in HBASE-18410 branch to pick up Filter improvements.
> >> > Then HBASE-13346 can go in.
> >> >
> >> > You are already helping out on HBASE-18906, thanks. Looks like that
> will
> >> > be addressed by other alpha-4s about to land.
> >> >
> >> > St.Ack
> >> > TODOs: https://issues.apache.org/jira/projects/HBASE/versions/
> 12341594
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >> On 10/23/17 12:53 PM, Stack wrote:
> >> >>
> >> >>> (Reviving this thread)
> >> >>>
> >> >>> Lets push out alpha-4 this week. Alpha-4 is the release that has the
> >> >>> refactor of the Coprocessor API shutting down access to internals
> >> marked
> >> >>> InterfaceAudience.Private.
> >> >>>
> >> >>> The outstanding list is here:
> >> >>> https://issues.apache.org/jira/projects/HBASE/versions/12341594
> >> >>>
> >> >>> Please push in anything marked alpha-4 that belongs to you.
> >> >>>
> >> >>> If issue, talk out loud on this thread. If you need a review to land
> >> an
> >> >>> item, shout on the issue and here; we'll help you out.
> >> >>>
> >> >>> As is, items are coming along nicely I'd say. We need to merge the
> >> filter
> >> >>> branch -- HBASE-18410 -- so APIs are finished for hbase2.
> >> >>>
> >> >>> Post alpha-4, we'll have to hunt down our downstreamers and help
> them
> >> >>> test
> >> >>> on top of alpha-4 so

Re: Re: [ANNOUNCE] New HBase Committer Jan Hentschel

[Guanghao Zhang]

Congratulations!

2017-10-27 10:16 GMT+08:00 OpenInx :

> Congratulations and welcome, Jan!
>
> On Fri, Oct 27, 2017 at 10:03 AM, Jesse Yates 
> wrote:
>
> > Congrats and welcome!
> >
> > On Thu, Oct 26, 2017 at 6:57 PM 张铎(Duo Zhang) 
> > wrote:
> >
> > > Congratulations!
> > >
> > > 2017-10-27 9:51 GMT+08:00 Chunhui Shen :
> > >
> > > > Congratulations, Jan !
> > > >
> > > >
> > > > At 2017-10-27 07:45:25, "Andrew Purtell" 
> wrote:
> > > > >Congratulations and welcome, Jan!
> > > > >
> > > > >
> > > > >On Thu, Oct 26, 2017 at 3:39 PM, Stack  wrote:
> > > > >
> > > > >> On behalf of the Apache HBase PMC, I am pleased to announce that
> Jan
> > > > >> Hentschel has accepted the PMC's invitation to become a committer
> on
> > > > >> the project.
> > > > >>
> > > > >> We appreciate all of Jan' great work thus far and look forward to
> > his
> > > > >> continued involvement.
> > > > >>
> > > > >> Please join me in congratulating Jan! (One of us!)
> > > > >>
> > > > >> S
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > >--
> > > > >Best regards,
> > > > >Andrew
> > > > >
> > > > >Words like orphans lost among the crosstalk, meaning torn from
> truth's
> > > > >decrepit hands
> > > > >   - A23, Crosstalk
> > > >
> > >
> >
>
>
>
> --
> ==
> Openinx  blog : http://openinx.github.io
>
> TO BE A GREAT HACKER !
> ==
>

Re: Moving 2.0 forward

[Guanghao Zhang]

>
> For public API we have rules on how to keep compatible so I think it is
> less hurt for users, beta1 is fine.
>
Got it. Thanks for you explanation.

When you think you'd be done w/ the sync of Admin and AsyncAdmin
> Interfaces? Are the changes to Admin or to AsyncAdmin?

There are two issues (HBASE-19009 and HBASE-18950) need more review.  After
resolve these issues, I will upload a new patch for HBASE-18911. Thanks.

2017-10-27 0:14 GMT+08:00 Stack :

> On Thu, Oct 26, 2017 at 2:27 AM, Guanghao Zhang 
> wrote:
>
> > I saw beta == no new features, no API changes, just fixes. And I am
> working
> > on HBASE-18805 to unify Admin and AsyncAdmin methods. The fix version was
> > 2.0-beta-1. But I thought this will introduce API change(deprecate some
> API
> > and introduce new one). So should I change the fix versions to
> 2.0-alpha-4
> > and finish it before we release 2.0-alpha-4?
> >
> > Issue HBASE-18978 (Align the methods in Table and AsyncTable) may have
> same
> > problem. Thanks.
> >
> >
> Yeah, we were supposed to be done w/ public API changes when we shipped
> alpha-3 (smile).
>
> For Admin Interface, semantic versioning applies as per Duo comment. I see
> some polish still being done on the Admin/Table APIs (removal of deprecated
> methods, alignment of Admin and AsyncAdmin APIs). Hard to say no to this
> clean up on our most public facing Interfaces.
>
> When you think you'd be done w/ the sync of Admin and AsyncAdmin
> Interfaces? Are the changes to Admin or to AsyncAdmin?
>
> Thank you Guanghao Zhang,
>
> St.Ack
>
>
> > 2017-10-26 9:51 GMT+08:00 张铎(Duo Zhang) :
> >
> > > OK, skimmed,  we are in trouble! The in memory compaction just use the
> > same
> > > constructor with normal compaction to construct a StoreScanner, and use
> > it
> > > to do compaction...
> > >
> > > We have to provide several preXXX and postXXX for it, at least we
> should
> > > allow user reset TTL and max versions, and also do filtering on the
> > > scanner.
> > >
> > > Thanks.
> > >
> > >
> > >
> > > 2017-10-26 9:41 GMT+08:00 张铎(Duo Zhang) :
> > >
> > > > When adding back the pre(Flush/Compact/Store)ScannerOpen methods in
> > > > HBASE-19033, I found that there maybe a hole in our CP hools. It is
> the
> > > in
> > > > memory compaction.
> > > >
> > > > As Anoop suggested in HBASE-19001, we still need to give user the
> > ability
> > > > to extend the max versions and TTL config, so I plan to add back the
> > > hooks
> > > > above to let CP users can change the max versions and TTL of a
> ScanInfo
> > > > object. But I'm not sure whether in memory compaction will also
> discard
> > > > expired cells, if so then we are in trouble...
> > > >
> > > > Thanks.
> > > >
> > > > 2017-10-25 6:03 GMT+08:00 Stack :
> > > >
> > > >> Chatting with my coworker Mr. Mike Drob, we were batting back and
> > forth
> > > >> what remains to be done. Surfacing our thoughts here so you all
> clued
> > > >> inOr if you think otherwise, please speak up.
> > > >>
> > > >> We have ~13 issues to land:
> > > >> https://issues.apache.org/jira/projects/HBASE/versions/12341594
> About
> > > two
> > > >> are meta-issues that are about process which leaves 11.
> > > >>
> > > >> Duo and Zheng Hu are to merge the FilterList fixes improvements
> > > >> (HBASE-19057, HBASE-18410 et al.). These are blocker because some
> > > changed
> > > >> API/semantic that we need to get out earlier rather than later.
> > > >>
> > > >> Once the above is merged, HBASE-13346, change of Filter method names
> > to
> > > >> mention Cell instead of KeyValue can land.
> > > >>
> > > >> HBASE-199048 needs a review (Anoop will probably do it), removing
> > > >> IA.Private objects as params to MasterObserver... Hopefully this
> goes
> > in
> > > >> soon.
> > > >>
> > > >> Duo is hard at work on trackers for flush and compaction for CPs
> > > >> (HBASE-18905). How is HBASE-19033 looking Duo (facility for Tephra)?
> > > >>
> > > >> I think HBASE-18906 (Phoenix Region#waitFor...) will evaporate after
> > Duo
> > > >> is
> > > >> done w/ his work above.
>

Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available

[Guanghao Zhang]

Download src and build pass.
But when start-hbase.sh, I found the master can't start in standalone mode.

```
running master, logging to
/home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-master-Xiaohao.out
As this is a development environment, we need
/home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/bin/../target/cached_classpath.txt
to be generated from maven (command: mvn install -DskipTests)
: running regionserver, logging to
/home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-regionserver-Xiaohao.out
: As this is a development environment, we need
/home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/bin/../target/cached_classpath.txt
to be generated from maven (command: mvn install -DskipTests)
```

And I try mvn install -DskipTests, and found the cached_classpath.txt
in hbase-build-configuration/target/cached_classpath.txt. The path is wrong
in bin/hbase. So I
update f="${HBASE_HOME}/hbase-build-configuration/target/cached_classpath.txt"
in bin/hbase, then start master success. File a jira for this?

2017-11-02 14:02 GMT+08:00 Stack :

> On Wed, Nov 1, 2017 at 9:41 PM, Josh Elser  wrote:
>
> > +1 (binding)
> >
> > * UT's mostly ok. Exceptions being: TestNamespacesInstanceResource,
> > TestReplicaWithCluster, TestReplicationAdmin, and
> TestRegionServerHostname
> > consistently fail for me locally (commented on HBASE-19147)
> > * xsum+sigs OK
> > * can build from source
> > * src archive contents looks OK (exception below)
> > * Built, deployed locally, ran PE without issue
> >
> >
> Excellent. Thanks Josh.
>
>
>
> > I stumbled across src/main/site/resources/repo/o
> > rg/apache/maven/skins/maven-fluido-skin/1.5-HBASE/maven-
> fluido-skin-1.5-HBASE.jar
> > in the source archive which was introduced via
> > https://issues.apache.org/jira/browse/HBASE-14785. Best as I can tell,
> > this was a hack to work around a fluido-skin bug and we should be able to
> > remove it now. Not sure if we've already discussed the
> > binary-file-in-src-release concerns of this previously or not...
> >
> >
> Sean noted this in an alpha-3 VOTE.
>
> I came across it yesterday.
>
> What you reckon Misty (if you looking at this?) If you remember, what would
> I look for?
>
> Thanks,
> St.Ack
>
>
>
>
>
> > - Josh
> >
> >
> > On 11/1/17 10:17 AM, Stack wrote:
> >
> >> The first release candidate for HBase 2.0.0-alpha4 is up at:
> >>
> >>https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha4RC0/
> >>
> >> Maven artifacts are available from a staging directory here:
> >>
> >>https://repository.apache.org/content/repositories/
> orgapachehbase-1178
> >>
> >> All was signed with my key at 8ACC93D2 [1]
> >>
> >> I tagged the RC as 2.0.0-alpha4RC0
> >> (5c4b985f89c99cc8b0f8515a4097c811a0848835)
> >>
> >> hbase-2.0.0-alpha4 is our fourth alpha release along our march toward
> >> hbase-2.0.0. It includes all that was in previous alphas (new assignment
> >> manager, offheap read/write path, in-memory compactions, etc.), but had
> a
> >> focus on "Coprocessor Fixup": We no longer pass Coprocessors
> >> InterfaceAudience.Private parameters and we cut down on the access and
> >> ability to influence hbase core processing (See [2] on why the radical
> >> changes in Coprocessor Interface). If you are a Coprocessor developer or
> >> have Coprocessors to deploy on hbase-2.0.0, we need to hear about your
> >> experience now before we make an hbase-2.0.0 beta.
> >>
> >> hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production preview
> of
> >> what hbase-2.0.0 will look like. It is meant for devs and downstreamers
> to
> >> test drive and flag us early if we messed up anything ahead of our
> rolling
> >> GAs.
> >>
> >> The list of features addressed in 2.0.0 so far can be found here [3].
> >> There
> >> are thousands. The list of ~2k+ fixes in 2.0.0 exclusively can be found
> >> here [4] (My JIRA JQL foo is a bit dodgy -- forgive me if mistakes).
> >>
> >> I've updated our overview doc. on the state of 2.0.0 [6]. 2.0.0-beta-1
> >> will
> >> be our next release. Its theme is the "Finishing up 2.0.0" release. Here
> >> is
> >> the list of what we have targeted for beta-1 [5]. Check it out. Shout if
> >> there is anything missing. We may do a 2.0.0-beta-2 if a need. We'll
> see.
> >>
> >> Please take this alpha for a spin especially if you are a Coprocessor
> >> developer or have a Coprocessor you want to deploy on hbase-2.0.0.
> Please
> >> vote on whether it ok to put out this RC as our first alpha (bar is low
> >> for
> >> an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE be
> open
> >> for 72 hours (Saturday)
> >>
> >> Thanks,
> >> Your 2.0.0 Release Manager
> >>
> >> 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> >> 2. Why CPs are Incompatible:
> >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
> >> Eu_ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> >> 3. https://goo.gl/scYjJr
> >> 4. https://goo.gl/tMHkYS
> >>

Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available

[Guanghao Zhang]

Updated f="${HBASE_HOME}/target/cached_classpath.txt" to
f="${HBASE_HOME}/hbase-build-configuration/target/cached_classpath.txt".
Then start hbase success. Anything wrong for my environment?

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-11T00:41:47+08:00)
Maven home: /opt/soft/apache-maven-3.3.9
Java version: 1.8.0_131, vendor: Oracle Corporation
Java home: /opt/soft/jdk1.8.0_131/jre
Default locale: zh_CN, platform encoding: UTF-8
OS name: "linux", version: "3.13.0-46-generic", arch: "amd64", family:
"unix"



2017-11-02 15:18 GMT+08:00 Guanghao Zhang :

> Download src and build pass.
> But when start-hbase.sh, I found the master can't start in standalone mode.
>
> ```
> running master, logging to /home/hao/open_source/hbase_
> release/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-master-Xiaohao.out
> As this is a development environment, we need /home/hao/open_source/hbase_
> release/hbase-2.0.0-alpha4/bin/../target/cached_classpath.txt to be
> generated from maven (command: mvn install -DskipTests)
> : running regionserver, logging to /home/hao/open_source/hbase_
> release/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-regionserver-Xiaohao.out
> : As this is a development environment, we need
> /home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/
> bin/../target/cached_classpath.txt to be generated from maven (command:
> mvn install -DskipTests)
> ```
>
> And I try mvn install -DskipTests, and found the cached_classpath.txt
> in hbase-build-configuration/target/cached_classpath.txt. The path is
> wrong in bin/hbase. So I update f="${HBASE_HOME}/hbase-
> build-configuration/target/cached_classpath.txt" in bin/hbase, then start
> master success. File a jira for this?
>
> 2017-11-02 14:02 GMT+08:00 Stack :
>
>> On Wed, Nov 1, 2017 at 9:41 PM, Josh Elser  wrote:
>>
>> > +1 (binding)
>> >
>> > * UT's mostly ok. Exceptions being: TestNamespacesInstanceResource,
>> > TestReplicaWithCluster, TestReplicationAdmin, and
>> TestRegionServerHostname
>> > consistently fail for me locally (commented on HBASE-19147)
>> > * xsum+sigs OK
>> > * can build from source
>> > * src archive contents looks OK (exception below)
>> > * Built, deployed locally, ran PE without issue
>> >
>> >
>> Excellent. Thanks Josh.
>>
>>
>>
>> > I stumbled across src/main/site/resources/repo/o
>> > rg/apache/maven/skins/maven-fluido-skin/1.5-HBASE/maven-flui
>> do-skin-1.5-HBASE.jar
>> > in the source archive which was introduced via
>> > https://issues.apache.org/jira/browse/HBASE-14785. Best as I can tell,
>> > this was a hack to work around a fluido-skin bug and we should be able
>> to
>> > remove it now. Not sure if we've already discussed the
>> > binary-file-in-src-release concerns of this previously or not...
>> >
>> >
>> Sean noted this in an alpha-3 VOTE.
>>
>> I came across it yesterday.
>>
>> What you reckon Misty (if you looking at this?) If you remember, what
>> would
>> I look for?
>>
>> Thanks,
>> St.Ack
>>
>>
>>
>>
>>
>> > - Josh
>> >
>> >
>> > On 11/1/17 10:17 AM, Stack wrote:
>> >
>> >> The first release candidate for HBase 2.0.0-alpha4 is up at:
>> >>
>> >>https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha4RC0/
>> >>
>> >> Maven artifacts are available from a staging directory here:
>> >>
>> >>https://repository.apache.org/content/repositories/orgapache
>> hbase-1178
>> >>
>> >> All was signed with my key at 8ACC93D2 [1]
>> >>
>> >> I tagged the RC as 2.0.0-alpha4RC0
>> >> (5c4b985f89c99cc8b0f8515a4097c811a0848835)
>> >>
>> >> hbase-2.0.0-alpha4 is our fourth alpha release along our march toward
>> >> hbase-2.0.0. It includes all that was in previous alphas (new
>> assignment
>> >> manager, offheap read/write path, in-memory compactions, etc.), but
>> had a
>> >> focus on "Coprocessor Fixup": We no longer pass Coprocessors
>> >> InterfaceAudience.Private parameters and we cut down on the access and
>> >> ability to influence hbase core processing (See [2] on why the radical
>> >> changes in Coprocessor Interface). If you are a Coprocessor developer
>> or
>> >> have Coprocessors to deploy on hbase-2.0.0, we need to hear about your
>> >> experience now before we make an hbase-2.0

Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available

[Guanghao Zhang]

There is already a issue HBASE-18705
<https://issues.apache.org/jira/browse/HBASE-18705> about this problem. But
it was only pushed to master branch.

2017-11-02 15:21 GMT+08:00 Guanghao Zhang :

> Updated f="${HBASE_HOME}/target/cached_classpath.txt" to
> f="${HBASE_HOME}/hbase-build-configuration/target/cached_classpath.txt".
> Then start hbase success. Anything wrong for my environment?
>
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-11T00:41:47+08:00)
> Maven home: /opt/soft/apache-maven-3.3.9
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home: /opt/soft/jdk1.8.0_131/jre
> Default locale: zh_CN, platform encoding: UTF-8
> OS name: "linux", version: "3.13.0-46-generic", arch: "amd64", family:
> "unix"
>
>
>
> 2017-11-02 15:18 GMT+08:00 Guanghao Zhang :
>
>> Download src and build pass.
>> But when start-hbase.sh, I found the master can't start in standalone
>> mode.
>>
>> ```
>> running master, logging to /home/hao/open_source/hbase_re
>> lease/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-master-Xiaohao.out
>> As this is a development environment, we need
>> /home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/bin/../target/cached_classpath.txt
>> to be generated from maven (command: mvn install -DskipTests)
>> : running regionserver, logging to /home/hao/open_source/hbase_re
>> lease/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-regionserver-Xiaohao.out
>> : As this is a development environment, we need
>> /home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/bin/../target/cached_classpath.txt
>> to be generated from maven (command: mvn install -DskipTests)
>> ```
>>
>> And I try mvn install -DskipTests, and found the cached_classpath.txt
>> in hbase-build-configuration/target/cached_classpath.txt. The path is
>> wrong in bin/hbase. So I update f="${HBASE_HOME}/hbase-
>> build-configuration/target/cached_classpath.txt" in bin/hbase, then
>> start master success. File a jira for this?
>>
>> 2017-11-02 14:02 GMT+08:00 Stack :
>>
>>> On Wed, Nov 1, 2017 at 9:41 PM, Josh Elser  wrote:
>>>
>>> > +1 (binding)
>>> >
>>> > * UT's mostly ok. Exceptions being: TestNamespacesInstanceResource,
>>> > TestReplicaWithCluster, TestReplicationAdmin, and
>>> TestRegionServerHostname
>>> > consistently fail for me locally (commented on HBASE-19147)
>>> > * xsum+sigs OK
>>> > * can build from source
>>> > * src archive contents looks OK (exception below)
>>> > * Built, deployed locally, ran PE without issue
>>> >
>>> >
>>> Excellent. Thanks Josh.
>>>
>>>
>>>
>>> > I stumbled across src/main/site/resources/repo/o
>>> > rg/apache/maven/skins/maven-fluido-skin/1.5-HBASE/maven-flui
>>> do-skin-1.5-HBASE.jar
>>> > in the source archive which was introduced via
>>> > https://issues.apache.org/jira/browse/HBASE-14785. Best as I can tell,
>>> > this was a hack to work around a fluido-skin bug and we should be able
>>> to
>>> > remove it now. Not sure if we've already discussed the
>>> > binary-file-in-src-release concerns of this previously or not...
>>> >
>>> >
>>> Sean noted this in an alpha-3 VOTE.
>>>
>>> I came across it yesterday.
>>>
>>> What you reckon Misty (if you looking at this?) If you remember, what
>>> would
>>> I look for?
>>>
>>> Thanks,
>>> St.Ack
>>>
>>>
>>>
>>>
>>>
>>> > - Josh
>>> >
>>> >
>>> > On 11/1/17 10:17 AM, Stack wrote:
>>> >
>>> >> The first release candidate for HBase 2.0.0-alpha4 is up at:
>>> >>
>>> >>https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alp
>>> ha4RC0/
>>> >>
>>> >> Maven artifacts are available from a staging directory here:
>>> >>
>>> >>https://repository.apache.org/content/repositories/orgapache
>>> hbase-1178
>>> >>
>>> >> All was signed with my key at 8ACC93D2 [1]
>>> >>
>>> >> I tagged the RC as 2.0.0-alpha4RC0
>>> >> (5c4b985f89c99cc8b0f8515a4097c811a0848835)
>>> >>
>>> >> hbase-2.0.0-alpha4 is our fourth alpha release along our march toward
>>> >> hbase-2.0.0. It includes all that was in pre

Re: DISCUSSION: Minimum hbase1 version from which you can upgrade to hbase2 (1.2.x?)

[Guanghao Zhang]

Can we rolling from 0.98 and 1.1 to 1.2? If this rolling is ok, user can
rolling to 2.0 by two steps, 0.98 to 1.2, then 1.2 to 2.0.

2017-11-04 11:25 GMT+08:00 Nick Dimiduk :

> 1.2 is good, but are we aware of anything that precludes 1.1? 0.98? On disk
> compatibility (HFile, WAL, AMv2) should be the limiting factor here, right?
> Wire protocols have been compatible all the while...
>
> On Fri, Nov 3, 2017 at 5:56 PM Zach York 
> wrote:
>
> > +1 for having the minimum (supported) hbase1 version be 1.2.x.
> >
> > On Fri, Nov 3, 2017 at 5:30 PM, Stack  wrote:
> >
> > > Over in the adjacent "[DISCUSS] hbase-2.0.0 compatibility expectations"
> > > thread, we chatted some on what would be the minimum hbase-1.x version
> > from
> > > which you can upgrade to hbase-2.
> > >
> > > The last statement made on this topic by Sean was that only upgrades
> from
> > > 1.2.x, our current stable offering, or later should be supported.
> > >
> > > There was no dissent.
> > >
> > > We all good w/ this? Speak up if you disagree else 1.2.x becomes the
> > > 'official' minimum.
> > >
> > > NOTES:
> > >
> > > + We need to agree on a minimum so we know what migrations to test.
> > > + It might be possible to upgrade from versions before 1.2.x but we (or
> > at
> > > least I -- smile) won't have tried it or run verifications to ensure
> all
> > > made it over (let us know if you successfully migrate from a baseline
> > that
> > > precedes 1.2).
> > > + Hopefully we can avoid requiring Users move to the latest on the 1.2
> > > branch. This shouldn't be necessary doing a stop/start upgrade. It
> might
> > be
> > > needed doing a rolling upgrade. Lets see.
> > >
> > > Thanks,
> > > St.Ack
> > >
> >
>

Re: DISCUSSION: Minimum hbase1 version from which you can upgrade to hbase2 (1.2.x?)

[Guanghao Zhang]

Our internal branch is based on 0.98. And we plan rolling to 2.0. So I will
take a try for rolling from 0.98 to 2.0. But we take a lot backport to our
internal branch, like async client, netty rpc client, serial replication,
throttling, some replication improvements and so on. So our rolling
experience may not apply to community totally. I will post our rolling
experience (which can apply to community 0.98 branch) after we rolling to
2.0 :-).

2017-11-05 2:41 GMT+08:00 Stack :

> On Fri, Nov 3, 2017 at 9:01 PM, Guanghao Zhang  wrote:
>
> > Can we rolling from 0.98 and 1.1 to 1.2? If this rolling is ok, user can
> > rolling to 2.0 by two steps, 0.98 to 1.2, then 1.2 to 2.0.
> >
> >
> Yes. They could do that. Would be a pain. Might be able to go from 0.98 to
> 2.0 though... I've not tried it.
> St.Ack
>
>
>
>
> > 2017-11-04 11:25 GMT+08:00 Nick Dimiduk :
> >
> > > 1.2 is good, but are we aware of anything that precludes 1.1? 0.98? On
> > disk
> > > compatibility (HFile, WAL, AMv2) should be the limiting factor here,
> > right?
> > > Wire protocols have been compatible all the while...
> > >
> > > On Fri, Nov 3, 2017 at 5:56 PM Zach York  >
> > > wrote:
> > >
> > > > +1 for having the minimum (supported) hbase1 version be 1.2.x.
> > > >
> > > > On Fri, Nov 3, 2017 at 5:30 PM, Stack  wrote:
> > > >
> > > > > Over in the adjacent "[DISCUSS] hbase-2.0.0 compatibility
> > expectations"
> > > > > thread, we chatted some on what would be the minimum hbase-1.x
> > version
> > > > from
> > > > > which you can upgrade to hbase-2.
> > > > >
> > > > > The last statement made on this topic by Sean was that only
> upgrades
> > > from
> > > > > 1.2.x, our current stable offering, or later should be supported.
> > > > >
> > > > > There was no dissent.
> > > > >
> > > > > We all good w/ this? Speak up if you disagree else 1.2.x becomes
> the
> > > > > 'official' minimum.
> > > > >
> > > > > NOTES:
> > > > >
> > > > > + We need to agree on a minimum so we know what migrations to test.
> > > > > + It might be possible to upgrade from versions before 1.2.x but we
> > (or
> > > > at
> > > > > least I -- smile) won't have tried it or run verifications to
> ensure
> > > all
> > > > > made it over (let us know if you successfully migrate from a
> baseline
> > > > that
> > > > > precedes 1.2).
> > > > > + Hopefully we can avoid requiring Users move to the latest on the
> > 1.2
> > > > > branch. This shouldn't be necessary doing a stop/start upgrade. It
> > > might
> > > > be
> > > > > needed doing a rolling upgrade. Lets see.
> > > > >
> > > > > Thanks,
> > > > > St.Ack
> > > > >
> > > >
> > >
> >
>

Re: Release 1.4.0 update

[Guanghao Zhang]

Andrew, HBASE-18626 is a document fix for the incompatible change about the
replication TableCFs' config. Can we include it for 1.4? Thanks.

2017-12-01 9:19 GMT+08:00 Stack :

> I pushed HBASE-18233. Thanks for finding the issue and patience waiting on
> fix Andrew.
> St.Ack
>
> On Thu, Nov 30, 2017 at 5:04 PM, Andrew Purtell 
> wrote:
>
> > No problem, committing it now
> >
> > On Thu, Nov 30, 2017 at 4:54 PM, Sergey Soldatov <
> sergeysolda...@gmail.com
> > >
> > wrote:
> >
> > > Andrew,
> > >
> > > Can we include HBASE-19393 as well? Quite annoying issue and very
> simple
> > > fix.
> > >
> > > Thanks,
> > > Sergey
> > >
> > > On Thu, Nov 30, 2017 at 3:47 PM, Andrew Purtell 
> > > wrote:
> > >
> > > > Not too late, no
> > > >
> > > > On Thu, Nov 30, 2017 at 3:31 PM, Stack  wrote:
> > > >
> > > > > Fix is up if it is not too late Andrew.
> > > > > St.Ack
> > > > >
> > > > > On Thu, Nov 30, 2017 at 1:58 PM, Stack  wrote:
> > > > >
> > > > > > Andrew, your testing has turned up an issue in HBASE-18233. It is
> > > > present
> > > > > > in the 1.4 candidate patch and in 1.3. The failure is
> > intermittent. I
> > > > am
> > > > > > working on a fix but want to make sure I have it right. So, I
> > > withdraw
> > > > my
> > > > > > request that 1.4 include it.
> > > > > >
> > > > > > Thanks,
> > > > > > S
> > > > > >
> > > > > > On Wed, Nov 29, 2017 at 5:14 PM, Andrew Purtell <
> > apurt...@apache.org
> > > >
> > > > > > wrote:
> > > > > >
> > > > > >> TestGlobalThrottler is a problem stemming from the revert of
> > > > HBASE-9465
> > > > > >> ​ on branch-1.4. The test came in on HBASE-17314 so I'll also
> > revert
> > > > > that
> > > > > >> from branch-1.4. For more on this see HBASE-19381
> > > > > >> ​
> > > > > >>
> > > > > >> On Wed, Nov 29, 2017 at 5:00 PM, Andrew Purtell <
> > > apurt...@apache.org>
> > > > > >> wrote:
> > > > > >>
> > > > > >> > The TestEndToEndSplitTransaction failure will be fixed by
> > > > HBASE-19379.
> > > > > >> >
> > > > > >> > The TestGlobalThrottler issue is a hang, which is probably why
> > it
> > > > > >> slipped
> > > > > >> > through the cracks. I went back 32 commits from head and it
> was
> > > > still
> > > > > >> > stuck. 64 commits back it's good. Somewhere in between. Will
> get
> > > to
> > > > > the
> > > > > >> > offending commit shortly.
> > > > > >> >
> > > > > >> >
> > > > > >> > On Wed, Nov 29, 2017 at 3:56 PM, Andrew Purtell <
> > > > apurt...@apache.org>
> > > > > >> > wrote:
> > > > > >> >
> > > > > >> >> Thanks. I'll take a look. They were passing for me before I
> > went
> > > > out
> > > > > on
> > > > > >> >> vacation.
> > > > > >> >>
> > > > > >> >>
> > > > > >> >> On Wed, Nov 29, 2017 at 3:52 PM, Stack 
> > wrote:
> > > > > >> >>
> > > > > >> >>> Thanks.
> > > > > >> >>>
> > > > > >> >>> BTW, I noticed this morning that TestGlobalThrottler and
> > > > > >> >>> TestEndToEndSplitTransaction
> > > > > >> >>> fail locally for me and up on jenkins as part of hadoopqa
> runs
> > > and
> > > > > on
> > > > > >> >>> recent 1.4 runs.
> > > > > >> >>>
> > > > > >> >>> I tried to poke at why. They seem fine in 1.2, 1.3, and 2.0.
> > Got
> > > > > >> >>> distracted
> > > > > >> >>> and got no further than this
> > > > > >> >>>
> > > > > >> >>> S
> > > > > >> >>>
> > > > > >> >>> On Wed, Nov 29, 2017 at 3:00 PM, Andrew Purtell <
> > > > > apurt...@apache.org>
> > > > > >> >>> wrote:
> > > > > >> >>>
> > > > > >> >>> > Ok, no problem.
> > > > > >> >>> >
> > > > > >> >>> > On Wed, Nov 29, 2017 at 2:59 PM, Stack 
> > > > wrote:
> > > > > >> >>> >
> > > > > >> >>> > > May I get HBASE-18233 into 1.4.0 Andrew? It is in 1.2
> and
> > > 1.3.
> > > > > >> >>> Waiting on
> > > > > >> >>> > > hadoopqa run. Would be good to have it all up and down
> > > > branch-1.
> > > > > >> >>> > > Thanks Sir,
> > > > > >> >>> > > St.Ack
> > > > > >> >>> > >
> > > > > >> >>> > > On Wed, Nov 29, 2017 at 12:38 PM, Peter Somogyi <
> > > > > >> >>> psomo...@cloudera.com>
> > > > > >> >>> > > wrote:
> > > > > >> >>> > >
> > > > > >> >>> > > > HBASE-19188 was just resolved. :)
> > > > > >> >>> > > >
> > > > > >> >>> > > > On Wed, Nov 29, 2017 at 8:12 PM, Andrew Purtell <
> > > > > >> >>> apurt...@apache.org>
> > > > > >> >>> > > > wrote:
> > > > > >> >>> > > >
> > > > > >> >>> > > > > I come back to find HBASE-19188 is a blocker. :-/
> > > > > >> >>> > > > > Need to resolve it
> > > > > >> >>> > > > >
> > > > > >> >>> > > > > On Sat, Nov 18, 2017 at 10:30 AM, Sean Busbey <
> > > > > >> bus...@apache.org
> > > > > >> >>> >
> > > > > >> >>> > > wrote:
> > > > > >> >>> > > > >
> > > > > >> >>> > > > > > thanks for all the work as RM on this Andrew!
> > > > > >> >>> > > > > >
> > > > > >> >>> > > > > > On Sat, Nov 18, 2017 at 12:19 PM, Andrew Purtell
> > > > > >> >>> > > > > >  wrote:
> > > > > >> >>> > > > > > > Everything is in and ready to go. I'm out next
> > week
> > > > for
> > > > > >> the
> > > > > >> >>> > > > > Thanksgiving
> > > > > >> >>> > > > > > > holiday, but will be back fi

Re: [VOTE] The second HBase 1.4.0 release candidate (RC1) is available

[Guanghao Zhang]

+1 (non-binding)

hbase-1.4.0-bin.tar.gz (jdk8u144)
- Verified md5sum: ok
- Start HBase in standalone mode: ok
- Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
- Checked master/regionserver/region Web UI: ok

hbase-1.4.0-src.tar.gz (jdk8u144)
- Verified md5sum: ok
- Build tarball: ok
- Start HBase in standalone mode: ok
- Verified with shell, create/disable/enable/drop/get/put/scan/delete: ok
- Checked master/regionserver/region Web UI: ok

One trivial bug for Table ui: the compaction state will show a exception
message when the table is disabled. Will fill a issue for this.

Thanks.

2017-12-09 9:50 GMT+08:00 Andrew Purtell :

> The second HBase 1.4.0​ release candidate (RC1) is available for download
> at https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.0RC1/ and Maven
> artifacts are available in the temporary repository
> https://repository.apache.org/content/repositories/orgapachehbase-1186/ .
>
> The git tag corresponding to the candidate is '1.4.0RC1' (10b9b9fae6).
>
> A detailed source and binary compatibility report for this release is
> available for your review at
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.0RC1/
> hbase-1.3.1-1.4.0RC1_compatibility_report.html
> ​. All reported compatibility issues should comply with policy but please
> review them carefully.
>
> A list of the 660 issues resolved in this release can be found at
> https://s.apache.org/OErT .
>
> The changes since RC0 are:
>
> * [HBASE-19180] - Remove unused imports from AlwaysPasses
> * [HBASE-19373] - Fix Checkstyle error in hbase-annotations
> * [HBASE-19435] - Reopen Files for ClosedChannelException in
> BucketCache
> * [HBASE-19465] - Required httpcore and httpclient jars not included in
> binary distribution
> * [HBASE-19467] - rsgroups shell commands don't properly display
> elapsed time
>
> Please try out the candidate and vote +1/0/-1.
>
> This vote will be open for at least 72 hours. Unless objection I will try
> to close it ​Monday December 18, 2017 if we have sufficient votes.
>
> Prior to making this announcement I made the following preflight checks to
> 1.4.0RC0 (3d571827cb):
>
> RAT check passes (7u80)
> Unit test suite passes (8u131)
> LTT load 1M rows with 100% verification and 20% updates (8u131)
> PE randomWrite, randomRead, scanRange100 (8u131)
> 100M rows ITBLL (8u131)
>
> and the following preflight checks to 1.4.0RC1 (10b9b9fae6):
>
> RAT check passes (7u80)
> Unit test suite passes (8u131)
>
> Between now and when I want to close the vote I'll write up human readable
> release notes for the release announcement as promised.
>
> I also have agreed to run a scale ITBLL test, a performance comparison with
> 1.2 using YCSB, a  performance comparison with 1.2 using PE, and an
> analysis of code and allocation hot spot changes from 1.2, all of which I
> will publish when available and factor in to my vote.
>
> --
> Best regards,
> Andrew
>

Re: [ANNOUNCE] Please welcome new HBase committer YI Liang

[Guanghao Zhang]

Congratulations!

2017-12-21 10:58 GMT+08:00 张铎(Duo Zhang) :

> Congratulations!
>
> 2017-12-21 10:52 GMT+08:00 Jingcheng Du :
>
> > Congratulations, Yi!
> >
> > 2017-12-21 9:31 GMT+08:00 OpenInx :
> >
> > > Congratulations , and welcome !
> > >
> > > On Thu, Dec 21, 2017 at 8:08 AM, Ted Yu  wrote:
> > >
> > > > Congratulations, Yi !
> > > >
> > > > On Wed, Dec 20, 2017 at 4:06 PM, Jerry He 
> wrote:
> > > >
> > > > > On behalf of the Apache HBase PMC, I am pleased to announce that
> > > > > Yi Liang has accepted the PMC's invitation to become a committer
> > > > > on the project.
> > > > >
> > > > > We appreciate all of Yi's great work thus far and look forward to
> > > > > his continued involvement.
> > > > >
> > > > > Please join me in congratulating Yi!
> > > > >
> > > > > --
> > > > > Thanks,
> > > > > Jerry
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > ==
> > > Openinx  blog : http://openinx.github.io
> > >
> > > TO BE A GREAT HACKER !
> > > ==
> > >
> >
>

[VOTE] First release candidate for HBASE 2.2.0 is available

[Guanghao Zhang]

Please vote on this release candidate (RC) for Apache HBase 2.2.0.
This is the first release of the branch-2.2 line.

The VOTE will remain open for at least 72 hours.

[ ] +1 Release this package as Apache HBase 2.2.0
[ ] -1 Do not release this package because ...

The tag to be voted on is 2.2.0-RC0 (commit
4ab2dc20f15e9b59477de4bd971c367f3ce342cb):

 https://github.com/apache/hbase/tree/2.2.0-RC0

The release files, including signatures, digests, etc. can be found at:

https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC0/

Maven artifacts are available in a staging repository at:

https://repository.apache.org/content/repositories/orgapachehbase-1286

Signatures used for HBase RCs can be found in this file:

https://dist.apache.org/repos/dist/release/hbase/KEYS

The list of bug fixes going into 2.2.0 can be found in included
CHANGES.md and RELEASENOTES.md available here:

https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC0/CHANGES.md
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC0/RELEASENOTES.md

To learn more about Apache HBase, please see http://hbase.apache.org/

Thanks,
Guanghao Zhang

Re: Release 2.2.0

[Guanghao Zhang]

The first release candidates of 2.2.0 is ready and you can take a try for
it. Thanks.

Jean-Marc Spaggiari  于2019年3月7日周四 上午3:24写道：

> thanks for the update. I just built 2.2.0-SNAPSHOT locally. Built well. I
> will see if I can deploy it and test it. Else I will wait for Guanghao's
> communication.
>
> Le mar. 5 mars 2019 à 20:59, 张铎(Duo Zhang)  a
> écrit :
>
> > Yes, Guanghao is still working on it. It usually spends more time for a
> > minor release than a patch release, as we need to align the git commits
> and
> > the jira issues. And usually there will be a lot of differences...
> >
> > Sean Busbey  于2019年3月6日周三 上午9:40写道：
> >
> > > I believe work on the RC is being tracked in
> > >
> > > https://issues.apache.org/jira/browse/HBASE-21747
> > >
> > > Looks like an RC is imminent.
> > >
> > > On Tue, Mar 5, 2019, 14:39 Jean-Marc Spaggiari <
> jean-m...@spaggiari.org>
> > > wrote:
> > >
> > > > Bump ;)
> > > >
> > > > Le mar. 5 févr. 2019 à 18:43, Jean-Marc Spaggiari <
> > > jean-m...@spaggiari.org
> > > > >
> > > > a écrit :
> > > >
> > > > > Hi all,
> > > > >
> > > > > When we will have a 2.2.0 RC I will give a try of the upgrade path
> > from
> > > > > 2.0.x... do we have any idea when this will be out?
> > > > >
> > > > > JMS
> > > > >
> > > > > Le mar. 29 janv. 2019 02 h 09, Guanghao Zhang 
> a
> > > > > écrit :
> > > > >
> > > > >> Cut a new branch-2.2 at this commit.
> > > > >>
> > > > >> commit e736d78362253936492fb3bd16e614d14859281d
> > > > >> Author: Duo Zhang 
> > > > >> Date: Mon Jan 28 18:21:51 2019 +0800
> > > > >>
> > > > >> HBASE-21792 Mark HTableMultiplexer as deprecated and remove it in
> > > 3.0.0
> > > > >>
> > > > >> Signed-off-by: Michael Stack 
> > > > >>
> > > > >> Sean Busbey  于2019年1月24日周四 上午9:45写道：
> > > > >>
> > > > >> > Okay it sounds like we definitely need a better doc about this
> as
> > a
> > > > >> > starting point. I have some additional questions about failure
> > > > handling;
> > > > >> > should we go through them here or in a jira about improving how
> > > > upgrade
> > > > >> > from 2.0/2.1 gets handled?
> > > > >> >
> > > > >> > On Wed, Jan 23, 2019, 07:33 张铎(Duo Zhang) <
> palomino...@gmail.com
> > > > wrote:
> > > > >> >
> > > > >> > > Oh, you misunderstood me. It is just for master, you need make
> > > sure
> > > > >> that
> > > > >> > > before you killing the old version master, there is no RITs.
> And
> > > > once
> > > > >> the
> > > > >> > > new master is up, everything is fine., as the new master will
> > > detect
> > > > >> if
> > > > >> > > there are old style AssignProcedure/UnassignProcedures, if so
> it
> > > > will
> > > > >> > quit
> > > > >> > > immediately.
> > > > >> > >
> > > > >> > > Sean Busbey  于2019年1月23日周三 下午9:21写道：
> > > > >> > >
> > > > >> > > > Yes, please. I don't think it's reasonable to expect no
> region
> > > > >> > > transitions
> > > > >> > > > during a rolling upgrade window; that would imply no servers
> > can
> > > > >> crash
> > > > >> > > > during the upgrade.
> > > > >> > > >
> > > > >> > > > On Wed, Jan 23, 2019, 07:04 张铎(Duo Zhang) <
> > > palomino...@gmail.com
> > > > >> > wrote:
> > > > >> > > >
> > > > >> > > > > From 1.x it is OK, but from 2.0 or 2.1, we need make sure
> > that
> > > > >> there
> > > > >> > > are
> > > > >> > > > no
> > > > >> > > > > RITs ongoing. We could see if we can make the upgrading
> more
> > > > >> > smoothly.
> > > > >> &

Re: [VOTE] First release candidate for HBASE 2.2.0 is available

[Guanghao Zhang]

Ok. But we need to update the ref guide about how to release. It has too
many mistakes now...

Re: [VOTE] First release candidate for HBASE 2.2.0 is available

[Guanghao Zhang]

sha512 added. And removed md5. Can be found at
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC0/

Guanghao Zhang  于2019年3月8日周五 下午4:09写道：

> Ok. But we need to update the ref guide about how to release. It has too
> many mistakes now...
>

Re: [VOTE] First release candidate for HBASE 2.2.0 is available

[Guanghao Zhang]

Upload  compatibility report to
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC0/compat-check-report.html

Guanghao Zhang  于2019年3月9日周六 下午12:23写道：

> sha512 added. And removed md5. Can be found at
> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC0/
>
> Guanghao Zhang  于2019年3月8日周五 下午4:09写道：
>
>> Ok. But we need to update the ref guide about how to release. It has too
>> many mistakes now...
>>
>

Re: [VOTE] First release candidate for HBASE 2.2.0 is available

[Guanghao Zhang]

Let me start a new RC1. HBASE-21970 should be included and need a release
note.

Sean Busbey  于2019年3月12日周二 上午8:35写道：

> I'm -1 on RC0 as it is.
>
> The current release notes don't include any call out about the upgrade
> steps needed. Since we don't usually have minor-version specific
> upgrade steps and especially since there are things folks need to do
> before installing 2.2.0, it's important that they be front and center.
> Possibly that should mean a link to the ref guide section from the RC
> instructions and eventual announcement.
>
> I think either HBASE-21075 needs to have 2.2.0 included in its fix
> version or the release note from that issue needs to be copied over to
> HBASE-21970 and it needs to have 2.2.0 included in its fix version(s).
> In either case the release notes should link to the ref guide section.
>
> On Thu, Mar 7, 2019 at 3:44 AM Guanghao Zhang  wrote:
> >
> > Please vote on this release candidate (RC) for Apache HBase 2.2.0.
> > This is the first release of the branch-2.2 line.
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache HBase 2.2.0
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 2.2.0-RC0 (commit
> > 4ab2dc20f15e9b59477de4bd971c367f3ce342cb):
> >
> >  https://github.com/apache/hbase/tree/2.2.0-RC0
> >
> > The release files, including signatures, digests, etc. can be found at:
> >
> > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC0/
> >
> > Maven artifacts are available in a staging repository at:
> >
> > https://repository.apache.org/content/repositories/orgapachehbase-1286
> >
> > Signatures used for HBase RCs can be found in this file:
> >
> > https://dist.apache.org/repos/dist/release/hbase/KEYS
> >
> > The list of bug fixes going into 2.2.0 can be found in included
> > CHANGES.md and RELEASENOTES.md available here:
> >
> > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC0/CHANGES.md
> > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC0/RELEASENOTES.md
> >
> > To learn more about Apache HBase, please see http://hbase.apache.org/
> >
> > Thanks,
> > Guanghao Zhang
>

[DISCUSS] HBASE-14850 C++ client implementation

[Guanghao Zhang]

Hi, all, we plan to pick hbase-native-client feature up. And my colleague
Junhong Xu is working on this. Now it can build rightly. And create
table/get/put/scan/delete works right. We plan to continue development on
feature branch HBASE-14850. But we found it didn't has a precommit check
for this. We are trying to add a precommit check in HBASE-22046.

As we have hbase-connectors project now and Sean Busbey suggested to move
the native client to hbase-connector project. Or we can create a new
project hbase-native-client for this. But the problem is the compatibility
may be break when there are some changes in HBase project. Looking forward
to your suggestions. Thanks.

Re: [DISCUSS] HBASE-14850 C++ client implementation

[Guanghao Zhang]

I am +1 to push the hbase-native-client to a new git repo. One more
question, how to create a new repo in gitbox? Do we have some ref guide for
this? Thanks.

Sean Busbey  于2019年3月14日周四 下午9:58写道：

> I'd also like to see the native client in its own repo. Dealing with a
> new build system for C++ will be some overhead, but I suspect less
> overhead than if we have to stitch that build to work with maven in
> the same repo.
>
> Also I think the hbase-connectors repo is overdue for a release and
> I'd rather avoid either rushing the C++ client, blocking to wait for
> it, or doing the work to pull it aside when doing a release.
>
> On Thu, Mar 14, 2019 at 8:28 AM 张铎(Duo Zhang) 
> wrote:
> >
> > For hbase-connectors, it is still a maven project, but the native client
> is
> > a C++ project, so maybe we could just give it a separated repo...
> >
> > Stack  于2019年3月14日周四 下午1:54写道：
> >
> > > On Wed, Mar 13, 2019 at 12:54 AM Guanghao Zhang 
> > > wrote:
> > > ...
> > >
> > > > As we have hbase-connectors project now and Sean Busbey suggested to
> move
> > > > the native client to hbase-connector project. Or we can create a new
> > > > project hbase-native-client for this. But the problem is the
> > > compatibility
> > > > may be break when there are some changes in HBase project. Looking
> > > forward
> > > > to your suggestions.
> > > >
> > >
> > > Would hbase-native-client be in hbase-connectors? I'd imagine this
> would
> > > make the development easier.
> > >
> > > Once you'd made a release of the new client, could we a step to the
> nightly
> > > build that pulls the new client and runs it through paces complaining
> if it
> > > fails?
> > >
> > > (sounds great)
> > > S
> > >
>

Re: [DISCUSS] HBASE-14850 C++ client implementation

[Guanghao Zhang]

https://gitbox.apache.org/repos/asf?p=hbase-native-client.git
The new hbase-native-client repo created and push the commit from
HBASE-14850 to it.

Peter Somogyi  于2019年3月20日周三 下午8:08写道：

> +1 for hbase-native-client repo.
> You can create a new gitbox repository on https://gitbox.apache.org/ by
> filling out a simple form.
>
> On Wed, Mar 20, 2019 at 8:48 AM Guanghao Zhang  wrote:
>
> > I am +1 to push the hbase-native-client to a new git repo. One more
> > question, how to create a new repo in gitbox? Do we have some ref guide
> for
> > this? Thanks.
> >
> > Sean Busbey  于2019年3月14日周四 下午9:58写道：
> >
> > > I'd also like to see the native client in its own repo. Dealing with a
> > > new build system for C++ will be some overhead, but I suspect less
> > > overhead than if we have to stitch that build to work with maven in
> > > the same repo.
> > >
> > > Also I think the hbase-connectors repo is overdue for a release and
> > > I'd rather avoid either rushing the C++ client, blocking to wait for
> > > it, or doing the work to pull it aside when doing a release.
> > >
> > > On Thu, Mar 14, 2019 at 8:28 AM 张铎(Duo Zhang) 
> > > wrote:
> > > >
> > > > For hbase-connectors, it is still a maven project, but the native
> > client
> > > is
> > > > a C++ project, so maybe we could just give it a separated repo...
> > > >
> > > > Stack  于2019年3月14日周四 下午1:54写道：
> > > >
> > > > > On Wed, Mar 13, 2019 at 12:54 AM Guanghao Zhang <
> zghao...@gmail.com>
> > > > > wrote:
> > > > > ...
> > > > >
> > > > > > As we have hbase-connectors project now and Sean Busbey suggested
> > to
> > > move
> > > > > > the native client to hbase-connector project. Or we can create a
> > new
> > > > > > project hbase-native-client for this. But the problem is the
> > > > > compatibility
> > > > > > may be break when there are some changes in HBase project.
> Looking
> > > > > forward
> > > > > > to your suggestions.
> > > > > >
> > > > >
> > > > > Would hbase-native-client be in hbase-connectors? I'd imagine this
> > > would
> > > > > make the development easier.
> > > > >
> > > > > Once you'd made a release of the new client, could we a step to the
> > > nightly
> > > > > build that pulls the new client and runs it through paces
> complaining
> > > if it
> > > > > fails?
> > > > >
> > > > > (sounds great)
> > > > > S
> > > > >
> > >
> >
>

Re: [DISCUSS] HBASE-14850 C++ client implementation

[Guanghao Zhang]

The new github repo is https://github.com/apache/hbase-native-client.

Sean Busbey  于2019年4月11日周四 上午12:55写道：

> also please
>
> * delete the feature branch for HBASE-14850
> * update HBASE-14850 jira with a pointer
>
> Could you include a summary on the jira for status of nightly/precommit
> tests?
>
> On Wed, Apr 10, 2019 at 11:22 AM Stack  wrote:
> >
> > Point this to the new repo
> > https://github.com/apache/hbase/tree/master/hbase-native-client ?
> > Thanks,
> > S
> >
> > On Wed, Apr 10, 2019 at 7:07 AM Guanghao Zhang 
> wrote:
> >
> > > https://gitbox.apache.org/repos/asf?p=hbase-native-client.git
> > > The new hbase-native-client repo created and push the commit from
> > > HBASE-14850 to it.
> > >
> > > Peter Somogyi  于2019年3月20日周三 下午8:08写道：
> > >
> > > > +1 for hbase-native-client repo.
> > > > You can create a new gitbox repository on https://gitbox.apache.org/
> by
> > > > filling out a simple form.
> > > >
> > > > On Wed, Mar 20, 2019 at 8:48 AM Guanghao Zhang 
> > > wrote:
> > > >
> > > > > I am +1 to push the hbase-native-client to a new git repo. One more
> > > > > question, how to create a new repo in gitbox? Do we have some ref
> guide
> > > > for
> > > > > this? Thanks.
> > > > >
> > > > > Sean Busbey  于2019年3月14日周四 下午9:58写道：
> > > > >
> > > > > > I'd also like to see the native client in its own repo. Dealing
> with
> > > a
> > > > > > new build system for C++ will be some overhead, but I suspect
> less
> > > > > > overhead than if we have to stitch that build to work with maven
> in
> > > > > > the same repo.
> > > > > >
> > > > > > Also I think the hbase-connectors repo is overdue for a release
> and
> > > > > > I'd rather avoid either rushing the C++ client, blocking to wait
> for
> > > > > > it, or doing the work to pull it aside when doing a release.
> > > > > >
> > > > > > On Thu, Mar 14, 2019 at 8:28 AM 张铎(Duo Zhang) <
> palomino...@gmail.com
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > For hbase-connectors, it is still a maven project, but the
> native
> > > > > client
> > > > > > is
> > > > > > > a C++ project, so maybe we could just give it a separated
> repo...
> > > > > > >
> > > > > > > Stack  于2019年3月14日周四 下午1:54写道：
> > > > > > >
> > > > > > > > On Wed, Mar 13, 2019 at 12:54 AM Guanghao Zhang <
> > > > zghao...@gmail.com>
> > > > > > > > wrote:
> > > > > > > > ...
> > > > > > > >
> > > > > > > > > As we have hbase-connectors project now and Sean Busbey
> > > suggested
> > > > > to
> > > > > > move
> > > > > > > > > the native client to hbase-connector project. Or we can
> create
> > > a
> > > > > new
> > > > > > > > > project hbase-native-client for this. But the problem is
> the
> > > > > > > > compatibility
> > > > > > > > > may be break when there are some changes in HBase project.
> > > > Looking
> > > > > > > > forward
> > > > > > > > > to your suggestions.
> > > > > > > > >
> > > > > > > >
> > > > > > > > Would hbase-native-client be in hbase-connectors? I'd imagine
> > > this
> > > > > > would
> > > > > > > > make the development easier.
> > > > > > > >
> > > > > > > > Once you'd made a release of the new client, could we a step
> to
> > > the
> > > > > > nightly
> > > > > > > > build that pulls the new client and runs it through paces
> > > > complaining
> > > > > > if it
> > > > > > > > fails?
> > > > > > > >
> > > > > > > > (sounds great)
> > > > > > > > S
> > > > > > > >
> > > > > >
> > > > >
> > > >
> > >
>

Re: Contributor Permission Request

[Guanghao Zhang]

Done. Add to HBase jira CONTRIBUTORS. Thanks.

fei wen  于2019年4月11日周四 下午7:26写道：

> Hi,
>   I want to contribute to Apache HBase.
> Would you please give me the contributor permission?
> My JIRA ID is wen.feiyi.
>

Re: Contributor Permission Request

[Guanghao Zhang]

Done. Add to  HBase jira CONTRIBUTORS, too.

Manjeet Singh  于2019年4月12日周五 上午12:56写道：

> Hi
>
> Request you to please add me as well for contribute to Apache HBase.
> My id is manjeet.chand...@gmail.com
>
> Thanks
> Manjeet singh
>
> On Thu, 11 Apr 2019, 19:52 Guanghao Zhang,  wrote:
>
> > Done. Add to HBase jira CONTRIBUTORS. Thanks.
> >
> > fei wen  于2019年4月11日周四 下午7:26写道：
> >
> > > Hi,
> > >   I want to contribute to Apache HBase.
> > > Would you please give me the contributor permission?
> > > My JIRA ID is wen.feiyi.
> > >
> >
>

Re: [VOTE] First release candidate for HBASE 2.2.0 is available

[Guanghao Zhang]

Sorry for late... I am  testing the ITBLL for 2.2.0 and it passed
yesterday. See  https://issues.apache.org/jira/browse/HBASE-21886. I will
generate RC1 later. Thanks.

Jean-Marc Spaggiari  于2019年4月11日周四 下午10:52写道：

> Hi all,
>
> Any chance to get an updated RC soon?
>
> JM
>
> Le mar. 12 mars 2019 à 12:23, Sean Busbey  a écrit :
>
> > quick follow-up here. the full version info is in fact missing the
> > revision:
> >
> > hbase-2.2.0 busbey$ ./bin/hbase version
> > HBase 2.2.0
> > Source code repository
> > git://hao-OptiPlex-7050/home/hao/open_source/hbase revision=
> > Compiled by hao on 2019年 03月 07日 星期四 14:05:34 CST
> > From source with checksum 783fee467bb1b28666f0d904437862c4
> >
> > I think this is the issue stack ran into on HBASE-21935/HBASE-21999
> > where HBASE-20764 introduced a git cli option that issn't supported on
> > older versions of git.
> >
> > Guanghao for the next RC would it be possible to update your local git
> > version?
> >
> > On Tue, Mar 12, 2019 at 9:37 AM Sean Busbey  wrote:
> > >
> > > locale of the build is up to the RM (this is why, for example, the 2.1
> > > release line javadocs have chinese for the boilerplate text[1])
> > >
> > > however, it does look like that shell output might be missing the
> > > build revision information from git or we might not be properly
> > > parsing the output from git when a non-english locale is used.
> > >
> > > [1]: http://hbase.apache.org/2.1/apidocs/index.html
> > >
> > >
> > > On Tue, Mar 12, 2019 at 8:54 AM Jean-Marc Spaggiari
> > >  wrote:
> > > >
> > > > Also, in the shell,it displays Asian texte:
> > > >
> > > > "Version 2.2.0, r, 2019年 03月 07日 星期四 14:05:34 CST"
> > > >
> > > > Not sure if that's we want.
> > > >
> > > > JMS
> > > >
> > > > Le lun. 11 mars 2019 à 21:53, Guanghao Zhang  a
> > écrit :
> > > >
> > > > > Let me start a new RC1. HBASE-21970 should be included and need a
> > release
> > > > > note.
> > > > >
> > > > > Sean Busbey  于2019年3月12日周二 上午8:35写道：
> > > > >
> > > > > > I'm -1 on RC0 as it is.
> > > > > >
> > > > > > The current release notes don't include any call out about the
> > upgrade
> > > > > > steps needed. Since we don't usually have minor-version specific
> > > > > > upgrade steps and especially since there are things folks need to
> > do
> > > > > > before installing 2.2.0, it's important that they be front and
> > center.
> > > > > > Possibly that should mean a link to the ref guide section from
> the
> > RC
> > > > > > instructions and eventual announcement.
> > > > > >
> > > > > > I think either HBASE-21075 needs to have 2.2.0 included in its
> fix
> > > > > > version or the release note from that issue needs to be copied
> > over to
> > > > > > HBASE-21970 and it needs to have 2.2.0 included in its fix
> > version(s).
> > > > > > In either case the release notes should link to the ref guide
> > section.
> > > > > >
> > > > > > On Thu, Mar 7, 2019 at 3:44 AM Guanghao Zhang <
> zghao...@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > > Please vote on this release candidate (RC) for Apache HBase
> > 2.2.0.
> > > > > > > This is the first release of the branch-2.2 line.
> > > > > > >
> > > > > > > The VOTE will remain open for at least 72 hours.
> > > > > > >
> > > > > > > [ ] +1 Release this package as Apache HBase 2.2.0
> > > > > > > [ ] -1 Do not release this package because ...
> > > > > > >
> > > > > > > The tag to be voted on is 2.2.0-RC0 (commit
> > > > > > > 4ab2dc20f15e9b59477de4bd971c367f3ce342cb):
> > > > > > >
> > > > > > >  https://github.com/apache/hbase/tree/2.2.0-RC0
> > > > > > >
> > > > > > > The release files, including signatures, digests, etc. can be
> > found at:
> > > > > > >
> > > > > > > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC0/
> > > > > > >
> > > > > > > Maven artifacts are available in a staging repository at:
> > > > > > >
> > > > > > >
> > https://repository.apache.org/content/repositories/orgapachehbase-1286
> > > > > > >
> > > > > > > Signatures used for HBase RCs can be found in this file:
> > > > > > >
> > > > > > > https://dist.apache.org/repos/dist/release/hbase/KEYS
> > > > > > >
> > > > > > > The list of bug fixes going into 2.2.0 can be found in included
> > > > > > > CHANGES.md and RELEASENOTES.md available here:
> > > > > > >
> > > > > > >
> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC0/CHANGES.md
> > > > > > >
> > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC0/RELEASENOTES.md
> > > > > > >
> > > > > > > To learn more about Apache HBase, please see
> > http://hbase.apache.org/
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Guanghao Zhang
> > > > > >
> > > > >
> >
>

Re: [VOTE] HBase Thirdparty 2.2.1 RC1

[Guanghao Zhang]

I download the src code and install it locally. Then release branch-2.2.1
with it and meet a error. The mvn cmd is: mvn clean install -DskipTests
-Prelease.

[WARNING] Rule 0: org.apache.maven.plugins.enforcer.EvaluateBeanshell
failed with message:
License errors detected, for more detail find ERROR in
/home/hao/open_source/hbase/hbase-shaded/hbase-shaded-client/target/maven-shared-archive-resources/META-INF/LICENSE

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M2:enforce
(check-aggregate-license) on project hbase-shaded-client: Some Enforcer
rules have failed. Look above for specific messages explaining why the rule
failed. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M2:enforce
(check-aggregate-license) on project hbase-shaded-client: Some Enforcer
rules have failed. Look above for specific messages explaining why the rule
failed.

Stack  于2019年4月17日周三 上午12:12写道：

> Please consider the following as the 2.2.1 release of Apache HBase
> Thirdparty. It is the first release candidate for your consideration. It
> has one fix over hbase-thirdparty-2.2.0 to cure an 'interesting'
> dependency issue found in 2.2.0 (HBASE-22233).
>
> Source artifact, signatures, checksums, and changes are available at:
>
>  https://dist.apache.org/repos/dist/dev/hbase/hbase-thirdparty/2.2.1RC0/
>
> The release was made against tag 2.2.1RC0. It was signed with my key
> 'st...@duboce.net' which can be found here:
>
>  https://dist.apache.org/repos/dist/release/hbase/KEYS
>
> Maven staging repository is available at:
>
>  https://repository.apache.org/content/repositories/orgapachehbase-1304
>
> This vote will remain open for at least 72 hours.
>
> Yours,
> Your HBase Release Manager
>

Re: [VOTE] HBase Thirdparty 2.2.1 RC1

[Guanghao Zhang]

After applying HBASE-2, mvn assembly:single failed...
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:3.0.0:single (default-cli)
on project hbase-assembly: Failed to create assembly: Error adding file
'org.apache.hbase:hbase-common:test-jar:tests:2.2.1-SNAPSHOT' to archive:
/home/hao/open_source/hbase/hbase-common/target/test-classes isn't a file.
-> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-assembly-plugin:3.0.0:single
(default-cli) on project hbase-assembly: Failed to create assembly: Error
adding file 'org.apache.hbase:hbase-common:test-jar:tests:2.2.1-SNAPSHOT'
to archive: /home/hao/open_source/hbase/hbase-common/target/test-classes
isn't a file.

张铎(Duo Zhang)  于2019年4月17日周三 下午12:05写道：

> +1(binding)
>
> Checked sigs and sums: matched
> Built from src: OK
> Built hbase site with 2.2.1RC0 after applying the patch in HBASE-2: OK
>
>
>
> 张铎(Duo Zhang)  于2019年4月17日周三 上午9:42写道：
>
> > You need to apply the patch in HBASE-2 first.
> >
> > Guanghao Zhang  于2019年4月17日周三 上午9:28写道：
> >
> >> I download the src code and install it locally. Then release
> branch-2.2.1
> >> with it and meet a error. The mvn cmd is: mvn clean install -DskipTests
> >> -Prelease.
> >>
> >> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.EvaluateBeanshell
> >> failed with message:
> >> License errors detected, for more detail find ERROR in
> >>
> >>
> /home/hao/open_source/hbase/hbase-shaded/hbase-shaded-client/target/maven-shared-archive-resources/META-INF/LICENSE
> >>
> >> [ERROR] Failed to execute goal
> >> org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M2:enforce
> >> (check-aggregate-license) on project hbase-shaded-client: Some Enforcer
> >> rules have failed. Look above for specific messages explaining why the
> >> rule
> >> failed. -> [Help 1]
> >> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute
> >> goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M2:enforce
> >> (check-aggregate-license) on project hbase-shaded-client: Some Enforcer
> >> rules have failed. Look above for specific messages explaining why the
> >> rule
> >> failed.
> >>
> >> Stack  于2019年4月17日周三 上午12:12写道：
> >>
> >> > Please consider the following as the 2.2.1 release of Apache HBase
> >> > Thirdparty. It is the first release candidate for your consideration.
> It
> >> > has one fix over hbase-thirdparty-2.2.0 to cure an 'interesting'
> >> > dependency issue found in 2.2.0 (HBASE-22233).
> >> >
> >> > Source artifact, signatures, checksums, and changes are available at:
> >> >
> >> >
> >> https://dist.apache.org/repos/dist/dev/hbase/hbase-thirdparty/2.2.1RC0/
> >> >
> >> > The release was made against tag 2.2.1RC0. It was signed with my key
> >> > 'st...@duboce.net' which can be found here:
> >> >
> >> >  https://dist.apache.org/repos/dist/release/hbase/KEYS
> >> >
> >> > Maven staging repository is available at:
> >> >
> >> >
> https://repository.apache.org/content/repositories/orgapachehbase-1304
> >> >
> >> > This vote will remain open for at least 72 hours.
> >> >
> >> > Yours,
> >> > Your HBase Release Manager
> >> >
> >>
> >
>

Re: [VOTE] HBase Thirdparty 2.2.1 RC1

[Guanghao Zhang]

Yes. I am building hbase with the new thirdparty 2.2.1...

Peter Somogyi  于2019年4月17日周三 下午8:10写道：

> +1 (with note)
>
> Checked signature, checksum
> Built from source on 2.2.1RC0 tag
> Built HBase master branch with HBASE-2 patch applied.
>
> NOTE:
> The CHANGES.md file marks 2.2.0 as unreleased.
> "Release thirdparty-2.2.0 - Unreleased (as of 2019-03-30)"
>
> Thanks,
> Peter
>
> On Tue, Apr 16, 2019 at 6:12 PM Stack  wrote:
>
> > Please consider the following as the 2.2.1 release of Apache HBase
> > Thirdparty. It is the first release candidate for your consideration. It
> > has one fix over hbase-thirdparty-2.2.0 to cure an 'interesting'
> > dependency issue found in 2.2.0 (HBASE-22233).
> >
> > Source artifact, signatures, checksums, and changes are available at:
> >
> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-thirdparty/2.2.1RC0/
> >
> > The release was made against tag 2.2.1RC0. It was signed with my key
> > 'st...@duboce.net' which can be found here:
> >
> >  https://dist.apache.org/repos/dist/release/hbase/KEYS
> >
> > Maven staging repository is available at:
> >
> >  https://repository.apache.org/content/repositories/orgapachehbase-1304
> >
> > This vote will remain open for at least 72 hours.
> >
> > Yours,
> > Your HBase Release Manager
> >
>

Re: [VOTE] HBase Thirdparty 2.2.1 RC1

[Guanghao Zhang]

+1 (binding). It passed when build site and assembly separated.

Build from src and mvn install: OK
Built HBase branch-2.2 with HBASE-2 patch applied, build site and
assembly separated: OK

Thanks.

Stack  于2019年4月18日周四 上午5:34写道：

> +1 From me.
> S
>
> On Tue, Apr 16, 2019 at 5:11 PM Stack  wrote:
>
> > Please consider the following as the 2.2.1 release of Apache HBase
> > Thirdparty. It is the first release candidate for your consideration. It
> > has one fix over hbase-thirdparty-2.2.0 to cure an 'interesting'
> > dependency issue found in 2.2.0 (HBASE-22233).
> >
> > Source artifact, signatures, checksums, and changes are available at:
> >
> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-thirdparty/2.2.1RC0/
> >
> > The release was made against tag 2.2.1RC0. It was signed with my key
> > 'st...@duboce.net' which can be found here:
> >
> >  https://dist.apache.org/repos/dist/release/hbase/KEYS
> >
> > Maven staging repository is available at:
> >
> >  https://repository.apache.org/content/repositories/orgapachehbase-1304
> >
> > This vote will remain open for at least 72 hours.
> >
> > Yours,
> > Your HBase Release Manager
> >
>

[VOTE] The second HBase 2.2.0 release candidate (RC2) is available

[Guanghao Zhang]

Please vote on this release candidate (RC) for Apache HBase 2.2.0.
This is the first release of the branch-2.2 line.

The VOTE will remain open for at least 72 hours.

[ ] +1 Release this package as Apache HBase 2.2.0
[ ] -1 Do not release this package because ...

The tag to be voted on is 2.2.0-RC2. The release files, including
signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC2/

Maven artifacts are available in a staging repository at:
<https://repository.apache.org/content/repositories/orgapachehbase-1286>
https://repository.apache.org/content/repositories/orgapachehbase-1306/

Signatures used for HBase RCs can be found in this file:
https://dist.apache.org/repos/dist/release/hbase/KEYS

The list of bug fixes going into 2.2.0 can be found in included
CHANGES.md and RELEASENOTES.md available here:
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC2/CHANGES.md
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC2/RELEASENOTES.md

A detailed source and binary compatibility report for this release is
available at
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC2/api_compare_2.2.0RC2_to_2.1.4.html

To learn more about Apache HBase, please see http://hbase.apache.org/

Thanks,
Guanghao Zhang

The second HBase 2.2.0 release candidate (RC2) is available

[Guanghao Zhang]

Please vote on this release candidate (RC) for Apache HBase 2.2.0.
This is the first release of the branch-2.2 line.

The VOTE will remain open for at least 72 hours.

[ ] +1 Release this package as Apache HBase 2.2.0
[ ] -1 Do not release this package because ...

The tag to be voted on is 2.2.0-RC2. The release files, including
signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC2/

Maven artifacts are available in a staging repository at:
<https://repository.apache.org/content/repositories/orgapachehbase-1286>
https://repository.apache.org/content/repositories/orgapachehbase-1306/

Signatures used for HBase RCs can be found in this file:
https://dist.apache.org/repos/dist/release/hbase/KEYS

The list of bug fixes going into 2.2.0 can be found in included
CHANGES.md and RELEASENOTES.md available here:
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC2/CHANGES.md
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC2/RELEASENOTES.md

A detailed source and binary compatibility report for this release is
available at
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC2/api_compare_2.2.0RC2_to_2.1.4.html

To learn more about Apache HBase, please see http://hbase.apache.org/

Thanks,
Guanghao Zhang

Re: [VOTE] The second HBase 2.2.0 release candidate (RC2) is available

[Guanghao Zhang]

Let me start a new RC3.. And it will include HBASE-22298.

张铎(Duo Zhang)  于2019年4月26日周五 下午9:19写道：

> Where do you tag the release? I saw a 2.2.0RC2 tag on gitbox, but I haven't
> found the tag on branch-2.2...
>
> Guanghao Zhang  于2019年4月24日周三 下午6:07写道：
>
> > Please vote on this release candidate (RC) for Apache HBase 2.2.0.
> > This is the first release of the branch-2.2 line.
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache HBase 2.2.0
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 2.2.0-RC2. The release files, including
> > signatures, digests, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC2/
> >
> > Maven artifacts are available in a staging repository at:
> > <https://repository.apache.org/content/repositories/orgapachehbase-1286>
> > https://repository.apache.org/content/repositories/orgapachehbase-1306/
> >
> > Signatures used for HBase RCs can be found in this file:
> > https://dist.apache.org/repos/dist/release/hbase/KEYS
> >
> > The list of bug fixes going into 2.2.0 can be found in included
> > CHANGES.md and RELEASENOTES.md available here:
> > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC2/CHANGES.md
> > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC2/RELEASENOTES.md
> >
> > A detailed source and binary compatibility report for this release is
> > available at
> >
> >
> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC2/api_compare_2.2.0RC2_to_2.1.4.html
> >
> > To learn more about Apache HBase, please see http://hbase.apache.org/
> >
> > Thanks,
> > Guanghao Zhang
> >
>

[VOTE] The third HBase 2.2.0 release candidate (RC3) is available

[Guanghao Zhang]

Please vote on this release candidate (RC) for Apache HBase 2.2.0.
This is the first release of the branch-2.2 line.

The VOTE will remain open for at least 72 hours.

[ ] +1 Release this package as Apache HBase 2.2.0
[ ] -1 Do not release this package because ...

The tag to be voted on is 2.2.0RC3. The release files, including
signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/

Maven artifacts are available in a staging repository at:
https://repository.apache.org/content/repositories/orgapachehbase-1308

Signatures used for HBase RCs can be found in this file:
https://dist.apache.org/repos/dist/release/hbase/KEYS

The list of bug fixes going into 2.2.0 can be found in included
CHANGES.md and RELEASENOTES.md available here:
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/CHANGES.md
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/RELEASENOTES.md

A detailed source and binary compatibility report for this release is
available at
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/api_compare_2.2.0RC3_to_2.1.4.html

To learn more about Apache HBase, please see http://hbase.apache.org/

Thanks,
Guanghao Zhang

Re: [VOTE] The third HBase 2.2.0 release candidate (RC3) is available

[Guanghao Zhang]

Added hbase-2.2.0-client-bin.tar.gz to
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/.

张铎(Duo Zhang)  于2019年4月30日周二 上午10:32写道：

> Oh we do not build the client bin for 2.2.x? IIRC we have this for 2.1.x...
>
> Norbert Kalmar  于2019年4月29日周一 下午11:30写道：
>
> > +1 (non-binding)
> >
> > - signature, checksum OK
> > - built from source (openjdk 1.8.0_163), unit tests pass.
> >
> >
> > On Sun, Apr 28, 2019 at 11:15 AM Guanghao Zhang 
> > wrote:
> >
> > > Please vote on this release candidate (RC) for Apache HBase 2.2.0.
> > > This is the first release of the branch-2.2 line.
> > >
> > > The VOTE will remain open for at least 72 hours.
> > >
> > > [ ] +1 Release this package as Apache HBase 2.2.0
> > > [ ] -1 Do not release this package because ...
> > >
> > > The tag to be voted on is 2.2.0RC3. The release files, including
> > > signatures, digests, etc. can be found at:
> > > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/
> > >
> > > Maven artifacts are available in a staging repository at:
> > > https://repository.apache.org/content/repositories/orgapachehbase-1308
> > >
> > > Signatures used for HBase RCs can be found in this file:
> > > https://dist.apache.org/repos/dist/release/hbase/KEYS
> > >
> > > The list of bug fixes going into 2.2.0 can be found in included
> > > CHANGES.md and RELEASENOTES.md available here:
> > > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/CHANGES.md
> > > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/RELEASENOTES.md
> > >
> > > A detailed source and binary compatibility report for this release is
> > > available at
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/api_compare_2.2.0RC3_to_2.1.4.html
> > >
> > > To learn more about Apache HBase, please see http://hbase.apache.org/
> > >
> > > Thanks,
> > > Guanghao Zhang
> > >
> >
>

Re: [VOTE] The third HBase 2.2.0 release candidate (RC3) is available

[Guanghao Zhang]

Got it... Let me roll a new RC.

张铎(Duo Zhang)  于2019年5月4日周六 下午1:19写道：

> HBASE-22190 has been resolved, let's roll a RC4...
>
> 张铎(Duo Zhang)  于2019年4月30日周二 下午11:08写道：
>
> > See HBASE-22190? Our SnapshotFileCleaner is broken, which may cause data
> > loss. I think this is a very serious bug, worth to sink an RC...
> >
> > Guanghao Zhang  于2019年4月30日周二 上午11:51写道：
> >
> >> Added hbase-2.2.0-client-bin.tar.gz to
> >> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/.
> >>
> >> 张铎(Duo Zhang)  于2019年4月30日周二 上午10:32写道：
> >>
> >> > Oh we do not build the client bin for 2.2.x? IIRC we have this for
> >> 2.1.x...
> >> >
> >> > Norbert Kalmar  于2019年4月29日周一
> 下午11:30写道：
> >> >
> >> > > +1 (non-binding)
> >> > >
> >> > > - signature, checksum OK
> >> > > - built from source (openjdk 1.8.0_163), unit tests pass.
> >> > >
> >> > >
> >> > > On Sun, Apr 28, 2019 at 11:15 AM Guanghao Zhang  >
> >> > > wrote:
> >> > >
> >> > > > Please vote on this release candidate (RC) for Apache HBase 2.2.0.
> >> > > > This is the first release of the branch-2.2 line.
> >> > > >
> >> > > > The VOTE will remain open for at least 72 hours.
> >> > > >
> >> > > > [ ] +1 Release this package as Apache HBase 2.2.0
> >> > > > [ ] -1 Do not release this package because ...
> >> > > >
> >> > > > The tag to be voted on is 2.2.0RC3. The release files, including
> >> > > > signatures, digests, etc. can be found at:
> >> > > > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/
> >> > > >
> >> > > > Maven artifacts are available in a staging repository at:
> >> > > >
> >> https://repository.apache.org/content/repositories/orgapachehbase-1308
> >> > > >
> >> > > > Signatures used for HBase RCs can be found in this file:
> >> > > > https://dist.apache.org/repos/dist/release/hbase/KEYS
> >> > > >
> >> > > > The list of bug fixes going into 2.2.0 can be found in included
> >> > > > CHANGES.md and RELEASENOTES.md available here:
> >> > > > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/CHANGES.md
> >> > > >
> >> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/RELEASENOTES.md
> >> > > >
> >> > > > A detailed source and binary compatibility report for this release
> >> is
> >> > > > available at
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/api_compare_2.2.0RC3_to_2.1.4.html
> >> > > >
> >> > > > To learn more about Apache HBase, please see
> >> http://hbase.apache.org/
> >> > > >
> >> > > > Thanks,
> >> > > > Guanghao Zhang
> >> > > >
> >> > >
> >> >
> >>
> >
>

Re: [ANNOUNCE] Please welcome Jan Hentschel to the Apache HBase PMC

[Guanghao Zhang]

Congratulations

Jan Hentschel  于2019年5月13日周一 上午3:19写道：

> Thanks everybody. It’s an honor and I’ll try to do my best to help the
> project and the community.
>
> From: Balazs Meszaros 
> Reply-To: "dev@hbase.apache.org" 
> Date: Thursday, May 9, 2019 at 1:19 PM
> To: "dev@hbase.apache.org" 
> Cc: "u...@hbase.apache.org" 
> Subject: Re: [ANNOUNCE] Please welcome Jan Hentschel to the Apache HBase
> PMC
>
> Congratulations Jan!
>
> On Thu, May 9, 2019 at 12:07 PM Lars Francke  > wrote:
>
> Congratulations Jan and especially thank you for your work on the
> deprecations
>
> On Wed, May 8, 2019 at 11:37 PM Sean Busbey  bus...@apache.org>> wrote:
>
> > On behalf of the Apache HBase PMC I am pleased to announce that Jan
> > Hentschel has accepted our invitation to become a PMC member on the
> > HBase project. We appreciate Jan stepping up to take more
> > responsibility in the HBase project.
> >
> > Please join me in welcoming Jan to the HBase PMC!
> >
> >
> >
> > As a reminder, if anyone would like to nominate another person as a
> > committer or PMC member, even if you are not currently a committer or
> > PMC member, you can always drop a note to priv...@hbase.apache.org
>  to
> > let us know.
> >
> > -busbey
> >
>
>
>

Re: [VOTE] The third HBase 2.2.0 release candidate (RC3) is available

[Guanghao Zhang]

Found a new problem when run ITBLL for out internal branch which based on
2.2.0, it make a TRSP stuck forever. Will open a new jira to fix it...


Guanghao Zhang  于2019年5月5日周日 上午11:56写道：

> Got it... Let me roll a new RC.
>
> 张铎(Duo Zhang)  于2019年5月4日周六 下午1:19写道：
>
>> HBASE-22190 has been resolved, let's roll a RC4...
>>
>> 张铎(Duo Zhang)  于2019年4月30日周二 下午11:08写道：
>>
>> > See HBASE-22190? Our SnapshotFileCleaner is broken, which may cause data
>> > loss. I think this is a very serious bug, worth to sink an RC...
>> >
>> > Guanghao Zhang  于2019年4月30日周二 上午11:51写道：
>> >
>> >> Added hbase-2.2.0-client-bin.tar.gz to
>> >> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/.
>> >>
>> >> 张铎(Duo Zhang)  于2019年4月30日周二 上午10:32写道：
>> >>
>> >> > Oh we do not build the client bin for 2.2.x? IIRC we have this for
>> >> 2.1.x...
>> >> >
>> >> > Norbert Kalmar  于2019年4月29日周一
>> 下午11:30写道：
>> >> >
>> >> > > +1 (non-binding)
>> >> > >
>> >> > > - signature, checksum OK
>> >> > > - built from source (openjdk 1.8.0_163), unit tests pass.
>> >> > >
>> >> > >
>> >> > > On Sun, Apr 28, 2019 at 11:15 AM Guanghao Zhang <
>> zghao...@gmail.com>
>> >> > > wrote:
>> >> > >
>> >> > > > Please vote on this release candidate (RC) for Apache HBase
>> 2.2.0.
>> >> > > > This is the first release of the branch-2.2 line.
>> >> > > >
>> >> > > > The VOTE will remain open for at least 72 hours.
>> >> > > >
>> >> > > > [ ] +1 Release this package as Apache HBase 2.2.0
>> >> > > > [ ] -1 Do not release this package because ...
>> >> > > >
>> >> > > > The tag to be voted on is 2.2.0RC3. The release files, including
>> >> > > > signatures, digests, etc. can be found at:
>> >> > > > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/
>> >> > > >
>> >> > > > Maven artifacts are available in a staging repository at:
>> >> > > >
>> >> https://repository.apache.org/content/repositories/orgapachehbase-1308
>> >> > > >
>> >> > > > Signatures used for HBase RCs can be found in this file:
>> >> > > > https://dist.apache.org/repos/dist/release/hbase/KEYS
>> >> > > >
>> >> > > > The list of bug fixes going into 2.2.0 can be found in included
>> >> > > > CHANGES.md and RELEASENOTES.md available here:
>> >> > > > https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/CHANGES.md
>> >> > > >
>> >> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/RELEASENOTES.md
>> >> > > >
>> >> > > > A detailed source and binary compatibility report for this
>> release
>> >> is
>> >> > > > available at
>> >> > > >
>> >> > > >
>> >> > >
>> >> >
>> >>
>> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC3/api_compare_2.2.0RC3_to_2.1.4.html
>> >> > > >
>> >> > > > To learn more about Apache HBase, please see
>> >> http://hbase.apache.org/
>> >> > > >
>> >> > > > Thanks,
>> >> > > > Guanghao Zhang
>> >> > > >
>> >> > >
>> >> >
>> >>
>> >
>>
>

[VOTE] The forth HBase 2.2.0 release candidate (RC4) is available

[Guanghao Zhang]

Please vote on this release candidate (RC) for Apache HBase 2.2.0.
This is the first release of the branch-2.2 line.

The VOTE will remain open for at least 72 hours.
[] +1
[] +0/-0 Because ...
[] -1 Do not release this package because ...

The tag to be voted on is 2.2.0RC4. The release files, including
signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC4/

Maven artifacts are available in a staging repository at:
https://repository.apache.org/content/repositories/orgapachehbase-1312

Signatures used for HBase RCs can be found in this file:
https://dist.apache.org/repos/dist/release/hbase/KEYS

The list of bug fixes going into 2.2.0 can be found in included
CHANGES.md and RELEASENOTES.md available here:
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC4/CHANGES.md
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC4/RELEASENOTES.md

A detailed source and binary compatibility report for this release is
available at
https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC4/api_compare_2.2.0RC4_to_2.1.4.html

To learn more about Apache HBase, please see http://hbase.apache.org/

Thanks,
Guanghao Zhang

Re: [VOTE] The forth HBase 2.2.0 release candidate (RC4) is available

[Guanghao Zhang]

Fix typo: [VOTE] The fourth HBase 2.2.0 release candidate (RC4) is
available...

Guanghao Zhang  于2019年5月18日周六 下午2:12写道：

> Please vote on this release candidate (RC) for Apache HBase 2.2.0.
> This is the first release of the branch-2.2 line.
>
> The VOTE will remain open for at least 72 hours.
> [] +1
> [] +0/-0 Because ...
> [] -1 Do not release this package because ...
>
> The tag to be voted on is 2.2.0RC4. The release files, including
> signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC4/
>
> Maven artifacts are available in a staging repository at:
> https://repository.apache.org/content/repositories/orgapachehbase-1312
>
> Signatures used for HBase RCs can be found in this file:
> https://dist.apache.org/repos/dist/release/hbase/KEYS
>
> The list of bug fixes going into 2.2.0 can be found in included
> CHANGES.md and RELEASENOTES.md available here:
> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC4/CHANGES.md
> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC4/RELEASENOTES.md
>
> A detailed source and binary compatibility report for this release is
> available at
> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC4/api_compare_2.2.0RC4_to_2.1.4.html
>
> To learn more about Apache HBase, please see http://hbase.apache.org/
>
> Thanks,
> Guanghao Zhang
>