You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by Stack <st...@duboce.net> on 2018/01/04 03:26:06 UTC

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

+1 from me.
S

On Fri, Dec 29, 2017 at 12:15 PM, Stack <st...@duboce.net> wrote:

> The first release candidate for HBase 2.0.0-beta-1 is up at:
>
>  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-1-RC0/
>
> Maven artifacts are available from a staging directory here:
>
>  https://repository.apache.org/content/repositories/orgapachehbase-1188
>
> All was signed with my key at 8ACC93D2 [1]
>
> I tagged the RC as 2.0.0-beta-1-RC0 (0907563eb72697b394b8b960fe5488
> 7d6ff304fd)
>
> hbase-2.0.0-beta-1 is our first beta release. It includes all that was in
> previous alphas (new assignment manager, offheap read/write path, in-memory
> compactions, etc.). The APIs and feature-set are sealed.
>
> hbase-2.0.0-beta-1 is a not-for-production preview of hbase-2.0.0. It is
> meant for devs and downstreamers to test drive and flag us if we messed up
> on anything ahead of our rolling GAs. We are particular interested in
> hearing from Coprocessor developers.
>
> The list of features addressed in 2.0.0 so far can be found here [3].
> There are thousands. The list of ~2k+ fixes in 2.0.0 exclusively can be
> found here [4] (My JIRA JQL foo is a bit dodgy -- forgive me if mistakes).
>
> I've updated our overview doc. on the state of 2.0.0 [6]. We'll do one
> more beta before we put up our first 2.0.0 Release Candidate by the end of
> January, 2.0.0-beta-2. Its focus will be making it so users can do a
> rolling upgrade on to hbase-2.x from hbase-1.x (and any bug fixes found
> running beta-1). Here is the list of what we have targeted so far for
> beta-2 [5]. Check it out.
>
> One knownissue is that the User API has not been properly filtered so it
> shows more than just InterfaceAudience Public content (HBASE-19663, to be
> fixed by beta-2).
>
> Please take this beta for a spin. Please vote on whether it ok to put out
> this RC as our first beta (Note CHANGES has not yet been updated). Let the
> VOTE be open for 72 hours (Monday)
>
> Thanks,
> Your 2.0.0 Release Manager
>
> 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> 3. https://goo.gl/scYjJr
> 4. https://goo.gl/dFFT8b
> 5. https://issues.apache.org/jira/projects/HBASE/versions/12340862
> 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
> z9iEu_ktczrlKHK8N4SZzs/
>

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

Posted by Stack <st...@duboce.net>.
On Thu, Jan 4, 2018 at 12:39 PM, Jean-Marc Spaggiari <
jean-marc@spaggiari.org> wrote:

> If I re-run from the original cluster, now that I have snappy enabled, it
> works. But if it helps I can easily remove snappy libs, transfer from
> source, re-run and capture all the logs. It's an easy step. Just confirm
> and I will do it.
>
> Apart from that, everything else seems to run correctly. I ran some
> RowCounters, merged regions, compactions, splits, alters, etc. Have not
> found anything else. Still +1 ;)
>
>
Sounds like disabled SNAPPY damaged the cluster. It shouldn't. Let me try
it myself. If I can't repro the damage I'll come looking for you.
Thanks JMS,
S



> JMS
>
> 2018-01-03 22:26 GMT-05:00 Stack <st...@duboce.net>:
>
> > +1 from me.
> > S
> >
> > On Fri, Dec 29, 2017 at 12:15 PM, Stack <st...@duboce.net> wrote:
> >
> > > The first release candidate for HBase 2.0.0-beta-1 is up at:
> > >
> > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-1-RC0/
> > >
> > > Maven artifacts are available from a staging directory here:
> > >
> > >  https://repository.apache.org/content/repositories/
> orgapachehbase-1188
> > >
> > > All was signed with my key at 8ACC93D2 [1]
> > >
> > > I tagged the RC as 2.0.0-beta-1-RC0 (0907563eb72697b394b8b960fe5488
> > > 7d6ff304fd)
> > >
> > > hbase-2.0.0-beta-1 is our first beta release. It includes all that was
> in
> > > previous alphas (new assignment manager, offheap read/write path,
> > in-memory
> > > compactions, etc.). The APIs and feature-set are sealed.
> > >
> > > hbase-2.0.0-beta-1 is a not-for-production preview of hbase-2.0.0. It
> is
> > > meant for devs and downstreamers to test drive and flag us if we messed
> > up
> > > on anything ahead of our rolling GAs. We are particular interested in
> > > hearing from Coprocessor developers.
> > >
> > > The list of features addressed in 2.0.0 so far can be found here [3].
> > > There are thousands. The list of ~2k+ fixes in 2.0.0 exclusively can be
> > > found here [4] (My JIRA JQL foo is a bit dodgy -- forgive me if
> > mistakes).
> > >
> > > I've updated our overview doc. on the state of 2.0.0 [6]. We'll do one
> > > more beta before we put up our first 2.0.0 Release Candidate by the end
> > of
> > > January, 2.0.0-beta-2. Its focus will be making it so users can do a
> > > rolling upgrade on to hbase-2.x from hbase-1.x (and any bug fixes found
> > > running beta-1). Here is the list of what we have targeted so far for
> > > beta-2 [5]. Check it out.
> > >
> > > One knownissue is that the User API has not been properly filtered so
> it
> > > shows more than just InterfaceAudience Public content (HBASE-19663, to
> be
> > > fixed by beta-2).
> > >
> > > Please take this beta for a spin. Please vote on whether it ok to put
> out
> > > this RC as our first beta (Note CHANGES has not yet been updated). Let
> > the
> > > VOTE be open for 72 hours (Monday)
> > >
> > > Thanks,
> > > Your 2.0.0 Release Manager
> > >
> > > 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> > > 3. https://goo.gl/scYjJr
> > > 4. https://goo.gl/dFFT8b
> > > 5. https://issues.apache.org/jira/projects/HBASE/versions/12340862
> > > 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
> > > z9iEu_ktczrlKHK8N4SZzs/
> > >
> >
>

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

Posted by Stack <st...@duboce.net>.
On Thu, Jan 4, 2018 at 12:39 PM, Jean-Marc Spaggiari <
jean-marc@spaggiari.org> wrote:

> If I re-run from the original cluster, now that I have snappy enabled, it
> works. But if it helps I can easily remove snappy libs, transfer from
> source, re-run and capture all the logs. It's an easy step. Just confirm
> and I will do it.
>
> Apart from that, everything else seems to run correctly. I ran some
> RowCounters, merged regions, compactions, splits, alters, etc. Have not
> found anything else. Still +1 ;)
>
>
Sounds like disabled SNAPPY damaged the cluster. It shouldn't. Let me try
it myself. If I can't repro the damage I'll come looking for you.
Thanks JMS,
S



> JMS
>
> 2018-01-03 22:26 GMT-05:00 Stack <st...@duboce.net>:
>
> > +1 from me.
> > S
> >
> > On Fri, Dec 29, 2017 at 12:15 PM, Stack <st...@duboce.net> wrote:
> >
> > > The first release candidate for HBase 2.0.0-beta-1 is up at:
> > >
> > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-1-RC0/
> > >
> > > Maven artifacts are available from a staging directory here:
> > >
> > >  https://repository.apache.org/content/repositories/
> orgapachehbase-1188
> > >
> > > All was signed with my key at 8ACC93D2 [1]
> > >
> > > I tagged the RC as 2.0.0-beta-1-RC0 (0907563eb72697b394b8b960fe5488
> > > 7d6ff304fd)
> > >
> > > hbase-2.0.0-beta-1 is our first beta release. It includes all that was
> in
> > > previous alphas (new assignment manager, offheap read/write path,
> > in-memory
> > > compactions, etc.). The APIs and feature-set are sealed.
> > >
> > > hbase-2.0.0-beta-1 is a not-for-production preview of hbase-2.0.0. It
> is
> > > meant for devs and downstreamers to test drive and flag us if we messed
> > up
> > > on anything ahead of our rolling GAs. We are particular interested in
> > > hearing from Coprocessor developers.
> > >
> > > The list of features addressed in 2.0.0 so far can be found here [3].
> > > There are thousands. The list of ~2k+ fixes in 2.0.0 exclusively can be
> > > found here [4] (My JIRA JQL foo is a bit dodgy -- forgive me if
> > mistakes).
> > >
> > > I've updated our overview doc. on the state of 2.0.0 [6]. We'll do one
> > > more beta before we put up our first 2.0.0 Release Candidate by the end
> > of
> > > January, 2.0.0-beta-2. Its focus will be making it so users can do a
> > > rolling upgrade on to hbase-2.x from hbase-1.x (and any bug fixes found
> > > running beta-1). Here is the list of what we have targeted so far for
> > > beta-2 [5]. Check it out.
> > >
> > > One knownissue is that the User API has not been properly filtered so
> it
> > > shows more than just InterfaceAudience Public content (HBASE-19663, to
> be
> > > fixed by beta-2).
> > >
> > > Please take this beta for a spin. Please vote on whether it ok to put
> out
> > > this RC as our first beta (Note CHANGES has not yet been updated). Let
> > the
> > > VOTE be open for 72 hours (Monday)
> > >
> > > Thanks,
> > > Your 2.0.0 Release Manager
> > >
> > > 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> > > 3. https://goo.gl/scYjJr
> > > 4. https://goo.gl/dFFT8b
> > > 5. https://issues.apache.org/jira/projects/HBASE/versions/12340862
> > > 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
> > > z9iEu_ktczrlKHK8N4SZzs/
> > >
> >
>

Re: [VOTE] The first hbase-2.0.0-beta-1 Release Candidate is available

Posted by Jean-Marc Spaggiari <je...@spaggiari.org>.
If I re-run from the original cluster, now that I have snappy enabled, it
works. But if it helps I can easily remove snappy libs, transfer from
source, re-run and capture all the logs. It's an easy step. Just confirm
and I will do it.

Apart from that, everything else seems to run correctly. I ran some
RowCounters, merged regions, compactions, splits, alters, etc. Have not
found anything else. Still +1 ;)

JMS

2018-01-03 22:26 GMT-05:00 Stack <st...@duboce.net>:

> +1 from me.
> S
>
> On Fri, Dec 29, 2017 at 12:15 PM, Stack <st...@duboce.net> wrote:
>
> > The first release candidate for HBase 2.0.0-beta-1 is up at:
> >
> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-1-RC0/
> >
> > Maven artifacts are available from a staging directory here:
> >
> >  https://repository.apache.org/content/repositories/orgapachehbase-1188
> >
> > All was signed with my key at 8ACC93D2 [1]
> >
> > I tagged the RC as 2.0.0-beta-1-RC0 (0907563eb72697b394b8b960fe5488
> > 7d6ff304fd)
> >
> > hbase-2.0.0-beta-1 is our first beta release. It includes all that was in
> > previous alphas (new assignment manager, offheap read/write path,
> in-memory
> > compactions, etc.). The APIs and feature-set are sealed.
> >
> > hbase-2.0.0-beta-1 is a not-for-production preview of hbase-2.0.0. It is
> > meant for devs and downstreamers to test drive and flag us if we messed
> up
> > on anything ahead of our rolling GAs. We are particular interested in
> > hearing from Coprocessor developers.
> >
> > The list of features addressed in 2.0.0 so far can be found here [3].
> > There are thousands. The list of ~2k+ fixes in 2.0.0 exclusively can be
> > found here [4] (My JIRA JQL foo is a bit dodgy -- forgive me if
> mistakes).
> >
> > I've updated our overview doc. on the state of 2.0.0 [6]. We'll do one
> > more beta before we put up our first 2.0.0 Release Candidate by the end
> of
> > January, 2.0.0-beta-2. Its focus will be making it so users can do a
> > rolling upgrade on to hbase-2.x from hbase-1.x (and any bug fixes found
> > running beta-1). Here is the list of what we have targeted so far for
> > beta-2 [5]. Check it out.
> >
> > One knownissue is that the User API has not been properly filtered so it
> > shows more than just InterfaceAudience Public content (HBASE-19663, to be
> > fixed by beta-2).
> >
> > Please take this beta for a spin. Please vote on whether it ok to put out
> > this RC as our first beta (Note CHANGES has not yet been updated). Let
> the
> > VOTE be open for 72 hours (Monday)
> >
> > Thanks,
> > Your 2.0.0 Release Manager
> >
> > 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> > 3. https://goo.gl/scYjJr
> > 4. https://goo.gl/dFFT8b
> > 5. https://issues.apache.org/jira/projects/HBASE/versions/12340862
> > 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
> > z9iEu_ktczrlKHK8N4SZzs/
> >
>