hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Busbey <bus...@apache.org>
Subject Re: Release 2.2.0
Date Wed, 23 Jan 2019 13:21:22 GMT
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 <zghaobac@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 <busbey@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
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message