[DISCUSS] Cut branch-2.3 and EOL branch-2.1

[Duo Zhang <zh...@apache.org>]

After "HBASE-23326 Implement a ProcedureStore which stores procedures in a
HRegion" and related issues are resolved, I think the last flaky part of
the proc-v2 framework has been resolved.

Notice that this does not mean there is no bug. The problem for the old
procedure store is that, no one in the community can even touch the code.
So even if we know there are bugs, no one can fix them. As now it is rely
on a region, I'm sure that most people in the community, even not a
committer, can modify the code easily.

So the plan here is to cut branch-2.3, and start to stablize it. And once
2.3.0 is out, I will do a final 2.1.x release and mark branch-2.1 as EOL.

Suggestions are welcomed. Oh, we need a release manager for branch-2.3. Any
volunteers?

Thanks.

Re: [DISCUSS] Cut branch-2.3 and EOL branch-2.1

[Stack <st...@duboce.net>]

On Fri, Jan 3, 2020 at 7:47 AM Nick Dimiduk <nd...@apache.org> wrote:

> On Fri, Jan 3, 2020 at 00:42 Duo Zhang <zh...@apache.org> wrote:
> ...
> I volunteer to RM 2.3; I don’t mind taking another tour in the role.
> Someone else speak up though if you feel you have a stronger claim.
>
>
I'd volunteer to be your RM lieutenant (can help around release scripts and
testing).
S

Re: [DISCUSS] Cut branch-2.3 and EOL branch-2.1

[OpenInx <op...@gmail.com>]

One of the most important issue for branch-2.3 is HBASE-21879,  which means
reading block offheap
from fs to save GC.   There's one remaining  open issue which need to
upgrade the Hadoop version to
make the offheap reading really work, I will finish that issue in the next
few days.

BTW, I was planing to be the branch-2.3 release manager but seems not
enough time now,
please ping me if anything I can help.  Thanks for your volunteer, Nick.

On Tue, Jan 7, 2020 at 1:04 AM Nick Dimiduk <nd...@gmail.com> wrote:

> Filed https://issues.apache.org/jira/browse/HBASE-23652 .
>
> On Sat, Jan 4, 2020 at 7:00 AM 张铎(Duo Zhang) <pa...@gmail.com>
> wrote:
>
> > Nick Dimiduk <nd...@apache.org> 于2020年1月3日周五 下午11:47写道：
> >
> > > On Fri, Jan 3, 2020 at 00:42 Duo Zhang <zh...@apache.org> wrote:
> > >
> > > > After "HBASE-23326 Implement a ProcedureStore which stores procedures
> > in
> > > a
> > > > HRegion" and related issues are resolved, I think the last flaky part
> > of
> > > > the proc-v2 framework has been resolved.
> > >
> > >
> > > 23326 is quite a present for the new year!
> > >
> > > So the plan here is to cut branch-2.3, and start to stablize it. And
> once
> > > > 2.3.0 is out, I will do a final 2.1.x release and mark branch-2.1 as
> > EOL.
> > >
> > >
> > > +1
> > >
> > > Suggestions are welcomed.
> > >
> > >
> > > My primary suggestion is we need to make sure the rolling upgrade from
> > 2.1
> > > to 2.3 is as “turnkey” as possible. We already have the change to
> > > persistent procedures from 2.2, which adds a hiccup. Let’s try to make
> > this
> > > more smooth for the under-staffed operations houses out there.
> > >
> > Oh, thanks for your reminding. We do have a problem for upgrading, we
> > should check whether there are unsupported procedures before migrating
> the
> > procedure data on 2.3, as we want user to restart the 2.1 master first to
> > finish the procedures, but as we have already migrated the procedure
> data,
> > there is no way for the user to downgrade...
> >
> > Let file an issue for this...
> >
> > >
> > > Oh, we need a release manager for branch-2.3. Any
> > > > volunteers?
> > >
> > >
> > > I volunteer to RM 2.3; I don’t mind taking another tour in the role.
> > > Someone else speak up though if you feel you have a stronger claim.
> > >
> > > Thanks,
> > > Nick
> > >
> > > >
> > >
> >
>

Re: [DISCUSS] Cut branch-2.3 and EOL branch-2.1

[Nick Dimiduk <nd...@gmail.com>]

Filed https://issues.apache.org/jira/browse/HBASE-23652 .

On Sat, Jan 4, 2020 at 7:00 AM 张铎(Duo Zhang) <pa...@gmail.com> wrote:

> Nick Dimiduk <nd...@apache.org> 于2020年1月3日周五 下午11:47写道：
>
> > On Fri, Jan 3, 2020 at 00:42 Duo Zhang <zh...@apache.org> wrote:
> >
> > > After "HBASE-23326 Implement a ProcedureStore which stores procedures
> in
> > a
> > > HRegion" and related issues are resolved, I think the last flaky part
> of
> > > the proc-v2 framework has been resolved.
> >
> >
> > 23326 is quite a present for the new year!
> >
> > So the plan here is to cut branch-2.3, and start to stablize it. And once
> > > 2.3.0 is out, I will do a final 2.1.x release and mark branch-2.1 as
> EOL.
> >
> >
> > +1
> >
> > Suggestions are welcomed.
> >
> >
> > My primary suggestion is we need to make sure the rolling upgrade from
> 2.1
> > to 2.3 is as “turnkey” as possible. We already have the change to
> > persistent procedures from 2.2, which adds a hiccup. Let’s try to make
> this
> > more smooth for the under-staffed operations houses out there.
> >
> Oh, thanks for your reminding. We do have a problem for upgrading, we
> should check whether there are unsupported procedures before migrating the
> procedure data on 2.3, as we want user to restart the 2.1 master first to
> finish the procedures, but as we have already migrated the procedure data,
> there is no way for the user to downgrade...
>
> Let file an issue for this...
>
> >
> > Oh, we need a release manager for branch-2.3. Any
> > > volunteers?
> >
> >
> > I volunteer to RM 2.3; I don’t mind taking another tour in the role.
> > Someone else speak up though if you feel you have a stronger claim.
> >
> > Thanks,
> > Nick
> >
> > >
> >
>

Re: [DISCUSS] Cut branch-2.3 and EOL branch-2.1

["张铎 (Duo Zhang)" <pa...@gmail.com>]

Nick Dimiduk <nd...@apache.org> 于2020年1月3日周五 下午11:47写道：

> On Fri, Jan 3, 2020 at 00:42 Duo Zhang <zh...@apache.org> wrote:
>
> > After "HBASE-23326 Implement a ProcedureStore which stores procedures in
> a
> > HRegion" and related issues are resolved, I think the last flaky part of
> > the proc-v2 framework has been resolved.
>
>
> 23326 is quite a present for the new year!
>
> So the plan here is to cut branch-2.3, and start to stablize it. And once
> > 2.3.0 is out, I will do a final 2.1.x release and mark branch-2.1 as EOL.
>
>
> +1
>
> Suggestions are welcomed.
>
>
> My primary suggestion is we need to make sure the rolling upgrade from 2.1
> to 2.3 is as “turnkey” as possible. We already have the change to
> persistent procedures from 2.2, which adds a hiccup. Let’s try to make this
> more smooth for the under-staffed operations houses out there.
>
Oh, thanks for your reminding. We do have a problem for upgrading, we
should check whether there are unsupported procedures before migrating the
procedure data on 2.3, as we want user to restart the 2.1 master first to
finish the procedures, but as we have already migrated the procedure data,
there is no way for the user to downgrade...

Let file an issue for this...

>
> Oh, we need a release manager for branch-2.3. Any
> > volunteers?
>
>
> I volunteer to RM 2.3; I don’t mind taking another tour in the role.
> Someone else speak up though if you feel you have a stronger claim.
>
> Thanks,
> Nick
>
> >
>

Re: [DISCUSS] Cut branch-2.3 and EOL branch-2.1

[Nick Dimiduk <nd...@apache.org>]

On Fri, Jan 3, 2020 at 00:42 Duo Zhang <zh...@apache.org> wrote:

> After "HBASE-23326 Implement a ProcedureStore which stores procedures in a
> HRegion" and related issues are resolved, I think the last flaky part of
> the proc-v2 framework has been resolved.


23326 is quite a present for the new year!

So the plan here is to cut branch-2.3, and start to stablize it. And once
> 2.3.0 is out, I will do a final 2.1.x release and mark branch-2.1 as EOL.


+1

Suggestions are welcomed.


My primary suggestion is we need to make sure the rolling upgrade from 2.1
to 2.3 is as “turnkey” as possible. We already have the change to
persistent procedures from 2.2, which adds a hiccup. Let’s try to make this
more smooth for the under-staffed operations houses out there.

Oh, we need a release manager for branch-2.3. Any
> volunteers?


I volunteer to RM 2.3; I don’t mind taking another tour in the role.
Someone else speak up though if you feel you have a stronger claim.

Thanks,
Nick

>