Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: <CAMUu0w-bsWa9m2HWCiXPEHBsDSWjh9r1TX5h1BE1H=5u_WW0HA@mail.gmail.com>
References: <64DC0B0F-E4F4-4057-B6D4-99F1AB870D19@gmail.com>
 <10AF22C1-E962-41C4-9AC4-CDD48732B675@gmail.com> <90291ea3-935e-b0bd-4053-a4e2494b733c@apache.org>
 <CADcMMgFFUs_KMkemYG7Zudfd+jWqZ5KQbZaTLbvxoE5N-=GExA@mail.gmail.com>
 <CAB8hLampTH6FSBKP=bLe4qZ61Ndsq1VgNjroqQAxbJTX+4=bHw@mail.gmail.com>
 <CADcMMgHcAiBP9e1aMDXuRvSo8bcKpSV2E5_yAk38J4TDjVV81w@mail.gmail.com>
 <1708072065.5042071.1484705475111@mail.yahoo.com> <CADcMMgH=P3w37PkDyq83nALhn6VtTm2M7njxKZ6wxZmEVh4WcA@mail.gmail.com>
 <358199494.84630.1484778398192@mail.yahoo.com> <CADcMMgGuO5htdKfVAuOeMPts_imx+Qa7uX=nOi9SP-o4Se7pdA@mail.gmail.com>
 <74F23C0E-AB0B-468E-81C9-92B3058A2753@gmail.com> <CAAT7MkrC_9YF3WV6X2HxwtiH4nZKN3AT0zbW6j-8HWPmCZhUoA@mail.gmail.com>
 <CADcMMgGhQC74y=EE+QcPqV7zDA6JEHDGoDxsz_WcZNvBVShEkw@mail.gmail.com>
 <CADcMMgES7tUZJ7knk4PkwEx3=+-Jrj=1xWbMBqDdHLFrf6CfWw@mail.gmail.com>
 <58BF2B62.203@apache.org> <CADcMMgESSh2Ka74T0-7Y-F8+SWte61ekkNG3=N5Gq6EVoPSamw@mail.gmail.com>
 <58C4A522.4080502@apache.org> <CADcMMgEV0FFCAvx9WhwBbd2V3HzP4C52BrfmV+wcFasAebCqEw@mail.gmail.com>
 <CAMUu0w-bsWa9m2HWCiXPEHBsDSWjh9r1TX5h1BE1H=5u_WW0HA@mail.gmail.com>
From: Yu Li <carp84@gmail.com>
Date: Fri, 31 Mar 2017 15:35:08 +0800
Message-ID: <CAM7-19+dHJW6yu4fM9bWZEdXrMnB5F3+CBk=c-zYk2we4o3Erg@mail.gmail.com>
Subject: Re: Moving 2.0 forward
To: dev@hbase.apache.org
Content-Type: multipart/alternative; boundary=001a113b02945adaee054c01d9f1
archived-at: Fri, 31 Mar 2017 07:35:14 -0000

--001a113b02945adaee054c01d9f1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

+1 on early branch, and count me in for the coming stability/perf projects
(smile).

Best Regards,
Yu

On 31 March 2017 at 09:22, Enis S=C3=B6ztutar <enis@apache.org> wrote:

> Thanks Stack for the update. +1 on branching as soon as possible. For
> getting aforementioned stability, we need to start rejecting patches/
> features from 2.0.0. Branching early gives us the option of gradually
> working towards that, but also does not block new development to happen o=
n
> master. I think the most important job for the RM is to say NO to
> improvement jiras going into 2.0, if they have nothing to do with the
> agreed upon goals of the release.
>
> Enis
>
> On Thu, Mar 30, 2017 at 5:07 PM, Stack <stack@duboce.net> wrote:
>
> > Some notes on progress toward hbase2.
> >
> > Given that stability and performance are NOT emergent behaviors but
> rather
> > projects unto themselves, my thought is that we commit all that we've
> > agreed as core for hbase2 (see [1]), branch, and then work on stabilizi=
ng
> > and perf rather than do stabilize, commit, and then branch. What this
> means
> > in practice is that for features like Inmemory Compaction, we commit it
> > defaulted 'on' ("BASIC" mode) which is what we want in hbase2. Should i=
t
> > prove problematic under test, we disable it before release.
> >
> > Are folks good w/ this mode? I ask because, in a few issues there are
> > requests for proof that a master feature is 'stable' before commit. Thi=
s
> is
> > normally a healthy request only in master's case, it is hard to
> demonstrate
> > stability given its current state.
> >
> > Other outstanding issues such as decisions about whether master hosts
> > system tables only (by default), I'm thinking, we can work out post
> branch
> > in alpha/betas before release.
> >
> > The awkward item is the long-pole Assignment Manager. This is an
> > all-or-nothing affair. Here we are switching in a new Master core. Whil=
e
> I
> > think it fine that AMv2 is incomplete come branch time, those of us
> working
> > on the new AM still need to demonstrate to you all that it basically
> > viable.
> >
> > The point-of-no-return is commit of the patch in HBASE-14614. HBASE-146=
14
> > (AMv2) is coming close to passing all unit tests. We'll spend some time
> > running it on a cluster to make sure it fundamentally sound and will
> report
> > back on our experience. There has been an ask for some dev doc and
> > low-levels on how it works (in progress). Let satisfaction of these
> > requests be blockers on commit. We'll put the HBASE-14614 commit up for=
 a
> > vote on dev list given its import.
> >
> > Branch will happen after HBASE-14614 goes in (or its rejection) with ou=
r
> > first alpha soon after. Its looking like a week or two at least given h=
ow
> > things have been going up to this.
> >
> > I intend to start in on hbase2 stability/perf projects after we branch.
> >
> > Interested in any thoughts you all might have on the above (Would also
> > appreciate updates on state in [1] if you are a feature owner).
> >
> > Thanks,
> > St.Ack
> >
> > 1. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
> > z9iEu_ktczrlKHK8N4SZzs/edit#
> >
> >
> >
> > On Sat, Mar 11, 2017 at 5:32 PM, Josh Elser <elserj@apache.org> wrote:
> >
> > >
> > > Stack wrote:
> > >
> > >> On Tue, Mar 7, 2017 at 1:51 PM, Josh Elser<elserj@apache.org>  wrote=
:
> > >>
> > >> Thanks for pulling in the FS Quotas work, Stack. I'm trying to cross
> the
> > >>> last T's and dot the last I's.
> > >>>
> > >>> The biggest thing I know I need to do still is to write a new chapt=
er
> > to
> > >>> the book. After that, I'd start entertaining larger
> reviews/discussions
> > >>> to
> > >>> merge the feature into master. Anyone with free time (giggles) is
> more
> > >>> than
> > >>> welcome to start perusing :)
> > >>>
> > >>>
> > >>> Out of interest, this could come in after 2.0 Josh? Any 2.0 specifi=
c
> > >> needs
> > >> to make this work?
> > >>
> > >> Meantime, updated the 2.0 doc 1.
> > >>
> > >> Thanks Josh,
> > >> St.Ack
> > >>
> > >> 1.
> > >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
> > >> Eu_ktczrlKHK8N4SZzs/edit#
> > >>
> > >>
> > > Nope, no need to block 2.0 on this one (given the other, related
> > chatter).
> > > Would be nice to get it in, but I completely understand if it slips :=
)
> > >
> > > Thanks for updating the doc for me!
> > >
> >
>

--001a113b02945adaee054c01d9f1--