You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Guanghao Zhang <zg...@gmail.com> on 2019/01/21 04:25:10 UTC
Release 2.2.0
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
Posted by Jean-Marc Spaggiari <je...@spaggiari.org>.
Wow, that was quick! Thanks a lot. My 2.0.4 doesn't start anymore, so I
will most probably give 2.2.0 a try today! Will comment on the other thread.
Thanks,
JMS
Le jeu. 7 mars 2019 06 h 23, Guanghao Zhang <zg...@gmail.com> a écrit :
> The first release candidates of 2.2.0 is ready and you can take a try for
> it. Thanks.
>
> Jean-Marc Spaggiari <je...@spaggiari.org> 于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) <pa...@gmail.com> 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 <bu...@apache.org> 于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-marc@spaggiari.org>
> > > > wrote:
> > > >
> > > > > Bump ;)
> > > > >
> > > > > Le mar. 5 févr. 2019 à 18:43, Jean-Marc Spaggiari <
> > > > jean-marc@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 <
> zghaobac@gmail.com>
> > a
> > > > > > écrit :
> > > > > >
> > > > > >> Cut a new branch-2.2 at this commit.
> > > > > >>
> > > > > >> commit e736d78362253936492fb3bd16e614d14859281d
> > > > > >> Author: Duo Zhang <zh...@apache.org>
> > > > > >> 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 <st...@apache.org>
> > > > > >>
> > > > > >> Sean Busbey <bu...@apache.org> 于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) <
> > palomino219@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 <bu...@apache.org> 于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) <
> > > > palomino219@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.
> > > > > >> > > > >
> > > > > >> > > > > Guanghao Zhang <zg...@gmail.com> 于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 <bu...@apache.org> 于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 <
> > > > > >> > > zghaobac@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
> > > > > >> > > > > > 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
Posted by Guanghao Zhang <zg...@gmail.com>.
The first release candidates of 2.2.0 is ready and you can take a try for
it. Thanks.
Jean-Marc Spaggiari <je...@spaggiari.org> 于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) <pa...@gmail.com> 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 <bu...@apache.org> 于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-marc@spaggiari.org>
> > > wrote:
> > >
> > > > Bump ;)
> > > >
> > > > Le mar. 5 févr. 2019 à 18:43, Jean-Marc Spaggiari <
> > > jean-marc@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 <zg...@gmail.com>
> a
> > > > > écrit :
> > > > >
> > > > >> Cut a new branch-2.2 at this commit.
> > > > >>
> > > > >> commit e736d78362253936492fb3bd16e614d14859281d
> > > > >> Author: Duo Zhang <zh...@apache.org>
> > > > >> 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 <st...@apache.org>
> > > > >>
> > > > >> Sean Busbey <bu...@apache.org> 于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) <
> palomino219@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 <bu...@apache.org> 于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) <
> > > palomino219@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.
> > > > >> > > > >
> > > > >> > > > > Guanghao Zhang <zg...@gmail.com> 于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 <bu...@apache.org> 于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 <
> > > > >> > > zghaobac@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
> > > > >> > > > > > 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
Posted by Jean-Marc Spaggiari <je...@spaggiari.org>.
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) <pa...@gmail.com> 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 <bu...@apache.org> 于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 <je...@spaggiari.org>
> > wrote:
> >
> > > Bump ;)
> > >
> > > Le mar. 5 févr. 2019 à 18:43, Jean-Marc Spaggiari <
> > jean-marc@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 <zg...@gmail.com> a
> > > > écrit :
> > > >
> > > >> Cut a new branch-2.2 at this commit.
> > > >>
> > > >> commit e736d78362253936492fb3bd16e614d14859281d
> > > >> Author: Duo Zhang <zh...@apache.org>
> > > >> 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 <st...@apache.org>
> > > >>
> > > >> Sean Busbey <bu...@apache.org> 于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) <palomino219@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 <bu...@apache.org> 于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) <
> > palomino219@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.
> > > >> > > > >
> > > >> > > > > Guanghao Zhang <zg...@gmail.com> 于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 <bu...@apache.org> 于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 <
> > > >> > > zghaobac@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
> > > >> > > > > > 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
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
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 <bu...@apache.org> 于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 <je...@spaggiari.org>
> wrote:
>
> > Bump ;)
> >
> > Le mar. 5 févr. 2019 à 18:43, Jean-Marc Spaggiari <
> jean-marc@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 <zg...@gmail.com> a
> > > écrit :
> > >
> > >> Cut a new branch-2.2 at this commit.
> > >>
> > >> commit e736d78362253936492fb3bd16e614d14859281d
> > >> Author: Duo Zhang <zh...@apache.org>
> > >> 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 <st...@apache.org>
> > >>
> > >> Sean Busbey <bu...@apache.org> 于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) <palomino219@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 <bu...@apache.org> 于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) <
> palomino219@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.
> > >> > > > >
> > >> > > > > Guanghao Zhang <zg...@gmail.com> 于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 <bu...@apache.org> 于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 <
> > >> > > zghaobac@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
> > >> > > > > > 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
Posted by Sean Busbey <bu...@apache.org>.
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 <je...@spaggiari.org>
wrote:
> Bump ;)
>
> Le mar. 5 févr. 2019 à 18:43, Jean-Marc Spaggiari <jean-marc@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 <zg...@gmail.com> a
> > écrit :
> >
> >> Cut a new branch-2.2 at this commit.
> >>
> >> commit e736d78362253936492fb3bd16e614d14859281d
> >> Author: Duo Zhang <zh...@apache.org>
> >> 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 <st...@apache.org>
> >>
> >> Sean Busbey <bu...@apache.org> 于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) <palomino219@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 <bu...@apache.org> 于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) <palomino219@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.
> >> > > > >
> >> > > > > Guanghao Zhang <zg...@gmail.com> 于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 <bu...@apache.org> 于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 <
> >> > > zghaobac@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
> >> > > > > > 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
Posted by Jean-Marc Spaggiari <je...@spaggiari.org>.
Bump ;)
Le mar. 5 févr. 2019 à 18:43, Jean-Marc Spaggiari <je...@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 <zg...@gmail.com> a
> écrit :
>
>> Cut a new branch-2.2 at this commit.
>>
>> commit e736d78362253936492fb3bd16e614d14859281d
>> Author: Duo Zhang <zh...@apache.org>
>> 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 <st...@apache.org>
>>
>> Sean Busbey <bu...@apache.org> 于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) <palomino219@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 <bu...@apache.org> 于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) <palomino219@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.
>> > > > >
>> > > > > Guanghao Zhang <zg...@gmail.com> 于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 <bu...@apache.org> 于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 <
>> > > zghaobac@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
>> > > > > > 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
Posted by Jean-Marc Spaggiari <je...@spaggiari.org>.
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 <zg...@gmail.com> a écrit :
> Cut a new branch-2.2 at this commit.
>
> commit e736d78362253936492fb3bd16e614d14859281d
> Author: Duo Zhang <zh...@apache.org>
> 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 <st...@apache.org>
>
> Sean Busbey <bu...@apache.org> 于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) <palomino219@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 <bu...@apache.org> 于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) <palomino219@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.
> > > > >
> > > > > Guanghao Zhang <zg...@gmail.com> 于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 <bu...@apache.org> 于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 <
> > > zghaobac@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
> > > > > > 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
Posted by Guanghao Zhang <zg...@gmail.com>.
Cut a new branch-2.2 at this commit.
commit e736d78362253936492fb3bd16e614d14859281d
Author: Duo Zhang <zh...@apache.org>
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 <st...@apache.org>
Sean Busbey <bu...@apache.org> 于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) <palomino219@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 <bu...@apache.org> 于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) <palomino219@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.
> > > >
> > > > Guanghao Zhang <zg...@gmail.com> 于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 <bu...@apache.org> 于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 <
> > zghaobac@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
> > > > > 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
Posted by Sean Busbey <bu...@apache.org>.
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) <palomino219@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 <bu...@apache.org> 于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) <palomino219@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.
> > >
> > > Guanghao Zhang <zg...@gmail.com> 于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 <bu...@apache.org> 于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 <
> zghaobac@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
> > > > 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
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
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 <bu...@apache.org> 于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) <palomino219@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.
> >
> > Guanghao Zhang <zg...@gmail.com> 于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 <bu...@apache.org> 于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 <zg...@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
> > > 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
Posted by Sean Busbey <bu...@apache.org>.
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) <palomino219@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.
>
> Guanghao Zhang <zg...@gmail.com> 于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 <bu...@apache.org> 于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 <zg...@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
> > 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
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
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 <zg...@gmail.com> 于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 <bu...@apache.org> 于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 <zg...@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
> 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
Posted by Guanghao Zhang <zg...@gmail.com>.
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 <bu...@apache.org> 于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 <zg...@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 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
Posted by Sean Busbey <bu...@apache.org>.
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 <zg...@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 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