Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-07 Thread Stack
Thanks Mike. I'll remove the .md5 when I post the release.

I'm +1.

Ran 1B ITBLL and it passed (10B did not. Work to do).

St.Ack


On Tue, Mar 6, 2018 at 8:50 PM, Mike Drob  wrote:

> +0, I didn't have enough time on this RC to run a more complete suite of
> tests like I was hoping for.
>
> sign/sums ok
> SHOULD NOT supply a MD5 checksum file (because MD5 is too broken). [1]
>
> compile src 8u151 ok
> compile src 8u151 w/ error-prone NOT OK - HBASE-19987
>
> [1]: http://www.apache.org/dev/release-distribution#sigs-and-sums
>
>
>
> On Fri, Mar 2, 2018 at 5:40 PM, Stack  wrote:
>
> > The first release candidate for HBase 2.0.0-beta-2 is up at
> >
> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-2.RC0/
> >
> > Maven artifacts are available from a staging directory here:
> >
> >   https://repository.apache.org/content/repositories/orgapachehbase-1199
> >
> > All was signed with my key at 8ACC93D2 [1]
> >
> > I tagged the RC as 2.0.0-beta-2RC0.2 at
> > 9e9b347d667e1fc6165c9f8ae5ae7052147e8895
> >
> > hbase-2.0.0-beta-2 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
> > actual 2.0.0 release candidates ("GAs").
> >
> > hbase-2.0.0-beta-2 is our second beta release. More than 200 fixes have
> > gone in since
> > beta-1. Unit tests generallly pass when run against hadoop2 and
> hadoop3[5].
> > It includes
> > all that was in previous alphas and beta (new assignment manager, offheap
> > read/write
> > path, in-memory compactions, etc).The list of features addressed in 2.0.0
> > so far can be
> > found here [3]. There are thousands. The list of ~3k+ fixes in 2.0.0
> > exclusively can be
> > found here [4]. Our overview doc. on the state of 2.0.0 is at [6].
> >
> > This beta was supposed to have as its focus rolling upgrade from
> hbase-1.x
> > versions but
> > this is work not complete (At this late stage, it is looking like it will
> > be a post-2.0.0 project).
> >
> > This is our last hbase-2.0.0 beta release. Next up, we'll be rolling an
> > actual 2.0.0 release
> > candidate. Look for this in a week or two after beta-2 goes out, after
> > we've done more
> > testing and documentation (and we fix issues raised by you all against
> this
> > beta).
> >
> > One known issue, still unaddressed, 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 release).
> >
> > Please take this beta for a spin. Please vote on whether it ok to put out
> > this RC as our second
> > beta (Note CHANGES has not yet been updated). Let the VOTE be open for at
> > least 72 hours
> > (Lets say Wednesday morning, March 7th).
> >
> > Thanks,
> > Your 2.0.0 Release Manager
> >
> > 1. http://pgp.mit.edu/pks/lookup?op=get=0x9816C7FC8ACC93D2
> > 3. https://goo.gl/scYjJr
> > 4. https://goo.gl/dFFT8b
> > 5. https://builds.apache.org/job/HBase%20Nightly/job/branch-2/
> > 
> > 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
> > z9iEu_ktczrlKHK8N4SZzs/
> >
>


Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-06 Thread Mike Drob
+0, I didn't have enough time on this RC to run a more complete suite of
tests like I was hoping for.

sign/sums ok
SHOULD NOT supply a MD5 checksum file (because MD5 is too broken). [1]

compile src 8u151 ok
compile src 8u151 w/ error-prone NOT OK - HBASE-19987

[1]: http://www.apache.org/dev/release-distribution#sigs-and-sums



On Fri, Mar 2, 2018 at 5:40 PM, Stack  wrote:

> The first release candidate for HBase 2.0.0-beta-2 is up at
>
>  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-2.RC0/
>
> Maven artifacts are available from a staging directory here:
>
>   https://repository.apache.org/content/repositories/orgapachehbase-1199
>
> All was signed with my key at 8ACC93D2 [1]
>
> I tagged the RC as 2.0.0-beta-2RC0.2 at
> 9e9b347d667e1fc6165c9f8ae5ae7052147e8895
>
> hbase-2.0.0-beta-2 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
> actual 2.0.0 release candidates ("GAs").
>
> hbase-2.0.0-beta-2 is our second beta release. More than 200 fixes have
> gone in since
> beta-1. Unit tests generallly pass when run against hadoop2 and hadoop3[5].
> It includes
> all that was in previous alphas and beta (new assignment manager, offheap
> read/write
> path, in-memory compactions, etc).The list of features addressed in 2.0.0
> so far can be
> found here [3]. There are thousands. The list of ~3k+ fixes in 2.0.0
> exclusively can be
> found here [4]. Our overview doc. on the state of 2.0.0 is at [6].
>
> This beta was supposed to have as its focus rolling upgrade from hbase-1.x
> versions but
> this is work not complete (At this late stage, it is looking like it will
> be a post-2.0.0 project).
>
> This is our last hbase-2.0.0 beta release. Next up, we'll be rolling an
> actual 2.0.0 release
> candidate. Look for this in a week or two after beta-2 goes out, after
> we've done more
> testing and documentation (and we fix issues raised by you all against this
> beta).
>
> One known issue, still unaddressed, 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 release).
>
> Please take this beta for a spin. Please vote on whether it ok to put out
> this RC as our second
> beta (Note CHANGES has not yet been updated). Let the VOTE be open for at
> least 72 hours
> (Lets say Wednesday morning, March 7th).
>
> Thanks,
> Your 2.0.0 Release Manager
>
> 1. http://pgp.mit.edu/pks/lookup?op=get=0x9816C7FC8ACC93D2
> 3. https://goo.gl/scYjJr
> 4. https://goo.gl/dFFT8b
> 5. https://builds.apache.org/job/HBase%20Nightly/job/branch-2/
> 
> 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
> z9iEu_ktczrlKHK8N4SZzs/
>


Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-06 Thread Jean-Marc Spaggiari
I deployed it on 8 nodes, running many different things including MR,
RowCounts, compactions, etc. Nothing new. So far so good...

2018-03-06 17:29 GMT-05:00 Stack :

> On Tue, Mar 6, 2018 at 12:52 PM, Peter Somogyi 
> wrote:
>
> > +1 (non-binding)
> >
> > - Signature, checksum OK
> > - Test suite using 1.8.0_161 OK
> > - Build and run from source OK
> > - Run from bin tarball OK
> > - PE 1M rows OK
> > - LTT 1M rows OK
> > - Basic operations from shell and Java client OK
> >
> > One thing I noticed: CHANGES.txt isn't updated, latest information is
> about
> > 0.93.0 - Unreleased. The 1.4.2 release contains up-to-date CHANGES.txt.
> > Will the CHANGES.txt be updated only for the final 2.0.0 release?
> >
> > Thanks Peter for trying the RC. Yeah, CHANGES.txt needs to be up-to-date
> by RC (I tried to note that this had not been done in the head of this
> thread 'Note CHANGES has not yet been updated').
>
> S
>
>
>
> >
> > On Tue, Mar 6, 2018 at 10:58 AM, Artem Ervits 
> > wrote:
> >
> > > +1 (non-binding)
> > >
> > > Hadoop Pseudo-distrbibuted: 2.7.5
> > > $M2_HOME from scratch
> > > Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
> > > 2017-10-18T07:58:13Z)
> > > Maven home: /opt/maven/apache-maven-3.5.2
> > > Java version: 1.8.0_161, vendor: Oracle Corporation
> > > Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.
> > > x86_64/jre
> > > Default locale: en_US, platform encoding: UTF-8
> > > OS name: "linux", version: "3.10.0-693.11.6.el7.x86_64", arch: "amd64",
> > > family: "unix"
> > >
> > > Binary Release:
> > > Java 1M rows: OK
> > > LTT 1M rows: OK
> > > PE 1M rows: OK
> > > MD5: OK
> > >
> > > hbase shell: OK
> > > create, list, scan, count, truncate, disable, drop
> > > snapshot, restore_snapshot
> > > UI:
> > >   split: OK
> > >   merge: OK
> > >
> > > Source Release:
> > > Build with: mvn clean -DskipTests -Dhadoop-two.version=2.7.5
> > > install && mvn clean -DskipTests -Dhadoop-two.version=2.7.5 package
> > > assembly:single   OK
> > > MD5: OK
> > > installed and ran from src: OK
> > >
> > > mvn test -P runSmallTests: NOK (this can be my own environment and I've
> > > surfaced this in votes for 1.4.1 and 1.4.2 but failing class is the
> same
> > > but failure is different.
> > >
> > >   [ESC[1;34mINFOESC[m] Results:
> > > [ESC[1;34mINFOESC[m]
> > > [ESC[1;31mERRORESC[m] ESC[1;31mFailures: ESC[m
> > > [ESC[1;31mERRORESC[m] ESC[1;31m
> > > TestSpnegoHttpServer.testAllowedClient:243->Assert.
> > > assertEquals:631->Assert.assertEquals:645->Assert.
> > > failNotEquals:834->Assert.fail:88
> > > expected:<200> but was:<401>ESC[m
> > > [ESC[1;34mINFOESC[m]
> > >
> > > On Tue, Mar 6, 2018 at 10:57 AM, Josh Elser  wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > * src release OK
> > > > * xsums/sigs OK
> > > > * Can build and run from src OK
> > > > * Loaded some data locally
> > > >
> > > >
> > > > On 3/2/18 6:40 PM, Stack wrote:
> > > >
> > > >> The first release candidate for HBase 2.0.0-beta-2 is up at
> > > >>
> > > >>   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-
> > beta-2.RC0/
> > > >>
> > > >> Maven artifacts are available from a staging directory here:
> > > >>
> > > >>https://repository.apache.org/content/repositories/
> > > orgapachehbase-1199
> > > >>
> > > >> All was signed with my key at 8ACC93D2 [1]
> > > >>
> > > >> I tagged the RC as 2.0.0-beta-2RC0.2 at
> > > >> 9e9b347d667e1fc6165c9f8ae5ae7052147e8895
> > > >>
> > > >> hbase-2.0.0-beta-2 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
> > > >> actual 2.0.0 release candidates ("GAs").
> > > >>
> > > >> hbase-2.0.0-beta-2 is our second beta release. More than 200 fixes
> > have
> > > >> gone in since
> > > >> beta-1. Unit tests generallly pass when run against hadoop2 and
> > > >> hadoop3[5].
> > > >> It includes
> > > >> all that was in previous alphas and beta (new assignment manager,
> > > offheap
> > > >> read/write
> > > >> path, in-memory compactions, etc).The list of features addressed in
> > > 2.0.0
> > > >> so far can be
> > > >> found here [3]. There are thousands. The list of ~3k+ fixes in 2.0.0
> > > >> exclusively can be
> > > >> found here [4]. Our overview doc. on the state of 2.0.0 is at [6].
> > > >>
> > > >> This beta was supposed to have as its focus rolling upgrade from
> > > hbase-1.x
> > > >> versions but
> > > >> this is work not complete (At this late stage, it is looking like it
> > > will
> > > >> be a post-2.0.0 project).
> > > >>
> > > >> This is our last hbase-2.0.0 beta release. Next up, we'll be rolling
> > an
> > > >> actual 2.0.0 release
> > > >> candidate. Look for this in a week or two after beta-2 goes out,
> after
> > > >> we've done more
> > > >> testing and documentation (and we fix issues raised by you all
> against

Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-06 Thread Stack
On Tue, Mar 6, 2018 at 12:52 PM, Peter Somogyi  wrote:

> +1 (non-binding)
>
> - Signature, checksum OK
> - Test suite using 1.8.0_161 OK
> - Build and run from source OK
> - Run from bin tarball OK
> - PE 1M rows OK
> - LTT 1M rows OK
> - Basic operations from shell and Java client OK
>
> One thing I noticed: CHANGES.txt isn't updated, latest information is about
> 0.93.0 - Unreleased. The 1.4.2 release contains up-to-date CHANGES.txt.
> Will the CHANGES.txt be updated only for the final 2.0.0 release?
>
> Thanks Peter for trying the RC. Yeah, CHANGES.txt needs to be up-to-date
by RC (I tried to note that this had not been done in the head of this
thread 'Note CHANGES has not yet been updated').

S



>
> On Tue, Mar 6, 2018 at 10:58 AM, Artem Ervits 
> wrote:
>
> > +1 (non-binding)
> >
> > Hadoop Pseudo-distrbibuted: 2.7.5
> > $M2_HOME from scratch
> > Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
> > 2017-10-18T07:58:13Z)
> > Maven home: /opt/maven/apache-maven-3.5.2
> > Java version: 1.8.0_161, vendor: Oracle Corporation
> > Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.
> > x86_64/jre
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "linux", version: "3.10.0-693.11.6.el7.x86_64", arch: "amd64",
> > family: "unix"
> >
> > Binary Release:
> > Java 1M rows: OK
> > LTT 1M rows: OK
> > PE 1M rows: OK
> > MD5: OK
> >
> > hbase shell: OK
> > create, list, scan, count, truncate, disable, drop
> > snapshot, restore_snapshot
> > UI:
> >   split: OK
> >   merge: OK
> >
> > Source Release:
> > Build with: mvn clean -DskipTests -Dhadoop-two.version=2.7.5
> > install && mvn clean -DskipTests -Dhadoop-two.version=2.7.5 package
> > assembly:single   OK
> > MD5: OK
> > installed and ran from src: OK
> >
> > mvn test -P runSmallTests: NOK (this can be my own environment and I've
> > surfaced this in votes for 1.4.1 and 1.4.2 but failing class is the same
> > but failure is different.
> >
> >   [ESC[1;34mINFOESC[m] Results:
> > [ESC[1;34mINFOESC[m]
> > [ESC[1;31mERRORESC[m] ESC[1;31mFailures: ESC[m
> > [ESC[1;31mERRORESC[m] ESC[1;31m
> > TestSpnegoHttpServer.testAllowedClient:243->Assert.
> > assertEquals:631->Assert.assertEquals:645->Assert.
> > failNotEquals:834->Assert.fail:88
> > expected:<200> but was:<401>ESC[m
> > [ESC[1;34mINFOESC[m]
> >
> > On Tue, Mar 6, 2018 at 10:57 AM, Josh Elser  wrote:
> >
> > > +1 (binding)
> > >
> > > * src release OK
> > > * xsums/sigs OK
> > > * Can build and run from src OK
> > > * Loaded some data locally
> > >
> > >
> > > On 3/2/18 6:40 PM, Stack wrote:
> > >
> > >> The first release candidate for HBase 2.0.0-beta-2 is up at
> > >>
> > >>   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-
> beta-2.RC0/
> > >>
> > >> Maven artifacts are available from a staging directory here:
> > >>
> > >>https://repository.apache.org/content/repositories/
> > orgapachehbase-1199
> > >>
> > >> All was signed with my key at 8ACC93D2 [1]
> > >>
> > >> I tagged the RC as 2.0.0-beta-2RC0.2 at
> > >> 9e9b347d667e1fc6165c9f8ae5ae7052147e8895
> > >>
> > >> hbase-2.0.0-beta-2 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
> > >> actual 2.0.0 release candidates ("GAs").
> > >>
> > >> hbase-2.0.0-beta-2 is our second beta release. More than 200 fixes
> have
> > >> gone in since
> > >> beta-1. Unit tests generallly pass when run against hadoop2 and
> > >> hadoop3[5].
> > >> It includes
> > >> all that was in previous alphas and beta (new assignment manager,
> > offheap
> > >> read/write
> > >> path, in-memory compactions, etc).The list of features addressed in
> > 2.0.0
> > >> so far can be
> > >> found here [3]. There are thousands. The list of ~3k+ fixes in 2.0.0
> > >> exclusively can be
> > >> found here [4]. Our overview doc. on the state of 2.0.0 is at [6].
> > >>
> > >> This beta was supposed to have as its focus rolling upgrade from
> > hbase-1.x
> > >> versions but
> > >> this is work not complete (At this late stage, it is looking like it
> > will
> > >> be a post-2.0.0 project).
> > >>
> > >> This is our last hbase-2.0.0 beta release. Next up, we'll be rolling
> an
> > >> actual 2.0.0 release
> > >> candidate. Look for this in a week or two after beta-2 goes out, after
> > >> we've done more
> > >> testing and documentation (and we fix issues raised by you all against
> > >> this
> > >> beta).
> > >>
> > >> One known issue, still unaddressed, 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 release).
> > >>
> > >> Please take this beta for a spin. Please vote on whether it ok to put
> > out
> > >> this RC as our second
> > >> beta (Note CHANGES has not yet been updated). Let the VOTE be open for
> > at
> > >> 

Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-06 Thread Peter Somogyi
+1 (non-binding)

- Signature, checksum OK
- Test suite using 1.8.0_161 OK
- Build and run from source OK
- Run from bin tarball OK
- PE 1M rows OK
- LTT 1M rows OK
- Basic operations from shell and Java client OK

One thing I noticed: CHANGES.txt isn't updated, latest information is about
0.93.0 - Unreleased. The 1.4.2 release contains up-to-date CHANGES.txt.
Will the CHANGES.txt be updated only for the final 2.0.0 release?


On Tue, Mar 6, 2018 at 10:58 AM, Artem Ervits  wrote:

> +1 (non-binding)
>
> Hadoop Pseudo-distrbibuted: 2.7.5
> $M2_HOME from scratch
> Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
> 2017-10-18T07:58:13Z)
> Maven home: /opt/maven/apache-maven-3.5.2
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.
> x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-693.11.6.el7.x86_64", arch: "amd64",
> family: "unix"
>
> Binary Release:
> Java 1M rows: OK
> LTT 1M rows: OK
> PE 1M rows: OK
> MD5: OK
>
> hbase shell: OK
> create, list, scan, count, truncate, disable, drop
> snapshot, restore_snapshot
> UI:
>   split: OK
>   merge: OK
>
> Source Release:
> Build with: mvn clean -DskipTests -Dhadoop-two.version=2.7.5
> install && mvn clean -DskipTests -Dhadoop-two.version=2.7.5 package
> assembly:single   OK
> MD5: OK
> installed and ran from src: OK
>
> mvn test -P runSmallTests: NOK (this can be my own environment and I've
> surfaced this in votes for 1.4.1 and 1.4.2 but failing class is the same
> but failure is different.
>
>   [ESC[1;34mINFOESC[m] Results:
> [ESC[1;34mINFOESC[m]
> [ESC[1;31mERRORESC[m] ESC[1;31mFailures: ESC[m
> [ESC[1;31mERRORESC[m] ESC[1;31m
> TestSpnegoHttpServer.testAllowedClient:243->Assert.
> assertEquals:631->Assert.assertEquals:645->Assert.
> failNotEquals:834->Assert.fail:88
> expected:<200> but was:<401>ESC[m
> [ESC[1;34mINFOESC[m]
>
> On Tue, Mar 6, 2018 at 10:57 AM, Josh Elser  wrote:
>
> > +1 (binding)
> >
> > * src release OK
> > * xsums/sigs OK
> > * Can build and run from src OK
> > * Loaded some data locally
> >
> >
> > On 3/2/18 6:40 PM, Stack wrote:
> >
> >> The first release candidate for HBase 2.0.0-beta-2 is up at
> >>
> >>   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-2.RC0/
> >>
> >> Maven artifacts are available from a staging directory here:
> >>
> >>https://repository.apache.org/content/repositories/
> orgapachehbase-1199
> >>
> >> All was signed with my key at 8ACC93D2 [1]
> >>
> >> I tagged the RC as 2.0.0-beta-2RC0.2 at
> >> 9e9b347d667e1fc6165c9f8ae5ae7052147e8895
> >>
> >> hbase-2.0.0-beta-2 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
> >> actual 2.0.0 release candidates ("GAs").
> >>
> >> hbase-2.0.0-beta-2 is our second beta release. More than 200 fixes have
> >> gone in since
> >> beta-1. Unit tests generallly pass when run against hadoop2 and
> >> hadoop3[5].
> >> It includes
> >> all that was in previous alphas and beta (new assignment manager,
> offheap
> >> read/write
> >> path, in-memory compactions, etc).The list of features addressed in
> 2.0.0
> >> so far can be
> >> found here [3]. There are thousands. The list of ~3k+ fixes in 2.0.0
> >> exclusively can be
> >> found here [4]. Our overview doc. on the state of 2.0.0 is at [6].
> >>
> >> This beta was supposed to have as its focus rolling upgrade from
> hbase-1.x
> >> versions but
> >> this is work not complete (At this late stage, it is looking like it
> will
> >> be a post-2.0.0 project).
> >>
> >> This is our last hbase-2.0.0 beta release. Next up, we'll be rolling an
> >> actual 2.0.0 release
> >> candidate. Look for this in a week or two after beta-2 goes out, after
> >> we've done more
> >> testing and documentation (and we fix issues raised by you all against
> >> this
> >> beta).
> >>
> >> One known issue, still unaddressed, 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 release).
> >>
> >> Please take this beta for a spin. Please vote on whether it ok to put
> out
> >> this RC as our second
> >> beta (Note CHANGES has not yet been updated). Let the VOTE be open for
> at
> >> least 72 hours
> >> (Lets say Wednesday morning, March 7th).
> >>
> >> Thanks,
> >> Your 2.0.0 Release Manager
> >>
> >> 1. http://pgp.mit.edu/pks/lookup?op=get=0x9816C7FC8ACC93D2
> >> 3. https://goo.gl/scYjJr
> >> 4. https://goo.gl/dFFT8b
> >> 5. https://builds.apache.org/job/HBase%20Nightly/job/branch-2/
> >> 
> >> 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
> >> z9iEu_ktczrlKHK8N4SZzs/
> >>
> >>
>


Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-06 Thread Artem Ervits
+1 (non-binding)

Hadoop Pseudo-distrbibuted: 2.7.5
$M2_HOME from scratch
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T07:58:13Z)
Maven home: /opt/maven/apache-maven-3.5.2
Java version: 1.8.0_161, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-693.11.6.el7.x86_64", arch: "amd64",
family: "unix"

Binary Release:
Java 1M rows: OK
LTT 1M rows: OK
PE 1M rows: OK
MD5: OK

hbase shell: OK
create, list, scan, count, truncate, disable, drop
snapshot, restore_snapshot
UI:
  split: OK
  merge: OK

Source Release:
Build with: mvn clean -DskipTests -Dhadoop-two.version=2.7.5
install && mvn clean -DskipTests -Dhadoop-two.version=2.7.5 package
assembly:single   OK
MD5: OK
installed and ran from src: OK

mvn test -P runSmallTests: NOK (this can be my own environment and I've
surfaced this in votes for 1.4.1 and 1.4.2 but failing class is the same
but failure is different.

  [ESC[1;34mINFOESC[m] Results:
[ESC[1;34mINFOESC[m]
[ESC[1;31mERRORESC[m] ESC[1;31mFailures: ESC[m
[ESC[1;31mERRORESC[m] ESC[1;31m
TestSpnegoHttpServer.testAllowedClient:243->Assert.assertEquals:631->Assert.assertEquals:645->Assert.failNotEquals:834->Assert.fail:88
expected:<200> but was:<401>ESC[m
[ESC[1;34mINFOESC[m]

On Tue, Mar 6, 2018 at 10:57 AM, Josh Elser  wrote:

> +1 (binding)
>
> * src release OK
> * xsums/sigs OK
> * Can build and run from src OK
> * Loaded some data locally
>
>
> On 3/2/18 6:40 PM, Stack wrote:
>
>> The first release candidate for HBase 2.0.0-beta-2 is up at
>>
>>   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-2.RC0/
>>
>> Maven artifacts are available from a staging directory here:
>>
>>https://repository.apache.org/content/repositories/orgapachehbase-1199
>>
>> All was signed with my key at 8ACC93D2 [1]
>>
>> I tagged the RC as 2.0.0-beta-2RC0.2 at
>> 9e9b347d667e1fc6165c9f8ae5ae7052147e8895
>>
>> hbase-2.0.0-beta-2 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
>> actual 2.0.0 release candidates ("GAs").
>>
>> hbase-2.0.0-beta-2 is our second beta release. More than 200 fixes have
>> gone in since
>> beta-1. Unit tests generallly pass when run against hadoop2 and
>> hadoop3[5].
>> It includes
>> all that was in previous alphas and beta (new assignment manager, offheap
>> read/write
>> path, in-memory compactions, etc).The list of features addressed in 2.0.0
>> so far can be
>> found here [3]. There are thousands. The list of ~3k+ fixes in 2.0.0
>> exclusively can be
>> found here [4]. Our overview doc. on the state of 2.0.0 is at [6].
>>
>> This beta was supposed to have as its focus rolling upgrade from hbase-1.x
>> versions but
>> this is work not complete (At this late stage, it is looking like it will
>> be a post-2.0.0 project).
>>
>> This is our last hbase-2.0.0 beta release. Next up, we'll be rolling an
>> actual 2.0.0 release
>> candidate. Look for this in a week or two after beta-2 goes out, after
>> we've done more
>> testing and documentation (and we fix issues raised by you all against
>> this
>> beta).
>>
>> One known issue, still unaddressed, 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 release).
>>
>> Please take this beta for a spin. Please vote on whether it ok to put out
>> this RC as our second
>> beta (Note CHANGES has not yet been updated). Let the VOTE be open for at
>> least 72 hours
>> (Lets say Wednesday morning, March 7th).
>>
>> Thanks,
>> Your 2.0.0 Release Manager
>>
>> 1. http://pgp.mit.edu/pks/lookup?op=get=0x9816C7FC8ACC93D2
>> 3. https://goo.gl/scYjJr
>> 4. https://goo.gl/dFFT8b
>> 5. https://builds.apache.org/job/HBase%20Nightly/job/branch-2/
>> 
>> 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
>> z9iEu_ktczrlKHK8N4SZzs/
>>
>>


Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-06 Thread Josh Elser

+1 (binding)

* src release OK
* xsums/sigs OK
* Can build and run from src OK
* Loaded some data locally

On 3/2/18 6:40 PM, Stack wrote:

The first release candidate for HBase 2.0.0-beta-2 is up at

  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-2.RC0/

Maven artifacts are available from a staging directory here:

   https://repository.apache.org/content/repositories/orgapachehbase-1199

All was signed with my key at 8ACC93D2 [1]

I tagged the RC as 2.0.0-beta-2RC0.2 at
9e9b347d667e1fc6165c9f8ae5ae7052147e8895

hbase-2.0.0-beta-2 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
actual 2.0.0 release candidates ("GAs").

hbase-2.0.0-beta-2 is our second beta release. More than 200 fixes have
gone in since
beta-1. Unit tests generallly pass when run against hadoop2 and hadoop3[5].
It includes
all that was in previous alphas and beta (new assignment manager, offheap
read/write
path, in-memory compactions, etc).The list of features addressed in 2.0.0
so far can be
found here [3]. There are thousands. The list of ~3k+ fixes in 2.0.0
exclusively can be
found here [4]. Our overview doc. on the state of 2.0.0 is at [6].

This beta was supposed to have as its focus rolling upgrade from hbase-1.x
versions but
this is work not complete (At this late stage, it is looking like it will
be a post-2.0.0 project).

This is our last hbase-2.0.0 beta release. Next up, we'll be rolling an
actual 2.0.0 release
candidate. Look for this in a week or two after beta-2 goes out, after
we've done more
testing and documentation (and we fix issues raised by you all against this
beta).

One known issue, still unaddressed, 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 release).

Please take this beta for a spin. Please vote on whether it ok to put out
this RC as our second
beta (Note CHANGES has not yet been updated). Let the VOTE be open for at
least 72 hours
(Lets say Wednesday morning, March 7th).

Thanks,
Your 2.0.0 Release Manager

1. http://pgp.mit.edu/pks/lookup?op=get=0x9816C7FC8ACC93D2
3. https://goo.gl/scYjJr
4. https://goo.gl/dFFT8b
5. https://builds.apache.org/job/HBase%20Nightly/job/branch-2/

6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
z9iEu_ktczrlKHK8N4SZzs/



Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-06 Thread Josh Elser

On 3/5/18 2:40 PM, Stack wrote:

On Mon, Mar 5, 2018 at 6:56 AM, Chia-Ping Tsai  wrote:


+1 (binding) with some questions
unit test (oracle jdk-8u161) - all pass
deploy binary (3 nodes) - ok
browse master/regionserver web - LGTM
put/delete/get/scan 500W rows - ok
create/disable/drop/put/scan/count by shell - ok

Q1:
the 2.0 binary get fatter than 1.4. (384 MB -> 887MB). Seems we package
the test docs and source code to binary tar. Are all of them necessary?



No. Let me review.


Holy moly. We ship 7x more javadocs than JAR files (in terms of size on 
disk).


IMO, remove all but apidocs with gusto. Looking at what's contained in 
apidocs, I think we should also reduce that much farther (e.g. 
RegionServer javadoc is included?), but maybe that's another discussion.


Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-05 Thread ramkrishna vasudevan
Ya looking at the logs it seems not critical. Also the RawbytesComparator
is no longer serialized and we don use any comparator for the
RawBytesComparator like the RowBloom etc.

Regards
Ram

On Tue, Mar 6, 2018 at 8:52 AM, Chia-Ping Tsai  wrote:

> > We have it as an explicit dependency in our top-level pom. Doing
> > dependency:tree, hadoop minicluster needs it? Its need to run tests? You
> > think we should not include in our binary sir?
> IIRC, those test jars are not in binary.tag before. HBASE-19089 add
> hbase-testing-util module to the assembly so the test jars are packaged to
> binary.tar. I'm fine with them.
>
> On 2018/03/05 19:40:30, Stack  wrote:
> > On Mon, Mar 5, 2018 at 6:56 AM, Chia-Ping Tsai 
> wrote:
> >
> > > +1 (binding) with some questions
> > > unit test (oracle jdk-8u161) - all pass
> > > deploy binary (3 nodes) - ok
> > > browse master/regionserver web - LGTM
> > > put/delete/get/scan 500W rows - ok
> > > create/disable/drop/put/scan/count by shell - ok
> > >
> > > Q1:
> > > the 2.0 binary get fatter than 1.4. (384 MB -> 887MB). Seems we package
> > > the test docs and source code to binary tar. Are all of them necessary?
> > >
> > >
> > No. Let me review.
> >
> >
> >
> > > Q2:
> > > Why some test jars of hadoop are included to hbase/lib? such as
> > > hadoop-common-2.7.4-tests and hadoop-hdfs-2.7.4-tests
> > >
> > >
> > We have it as an explicit dependency in our top-level pom. Doing
> > dependency:tree, hadoop minicluster needs it? Its need to run tests? You
> > think we should not include in our binary sir?
> >
> > [INFO] +- org.apache.hadoop:hadoop-minicluster:jar:2.7.4:test
> > [INFO] |  +- org.apache.hadoop:hadoop-common:test-jar:tests:2.7.4:test
> >
> >
> > Thanks for trying the RC Chia-Ping,
> > S
> >
> >
> >
> >
> >
> >
> >
> > >
> > > On 2018/03/02 23:40:53, Stack  wrote:
> > > > The first release candidate for HBase 2.0.0-beta-2 is up at
> > > >
> > > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-
> beta-2.RC0/
> > > >
> > > > Maven artifacts are available from a staging directory here:
> > > >
> > > >   https://repository.apache.org/content/repositories/
> orgapachehbase-1199
> > > >
> > > > All was signed with my key at 8ACC93D2 [1]
> > > >
> > > > I tagged the RC as 2.0.0-beta-2RC0.2 at
> > > > 9e9b347d667e1fc6165c9f8ae5ae7052147e8895
> > > >
> > > > hbase-2.0.0-beta-2 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
> > > > actual 2.0.0 release candidates ("GAs").
> > > >
> > > > hbase-2.0.0-beta-2 is our second beta release. More than 200 fixes
> have
> > > > gone in since
> > > > beta-1. Unit tests generallly pass when run against hadoop2 and
> > > hadoop3[5].
> > > > It includes
> > > > all that was in previous alphas and beta (new assignment manager,
> offheap
> > > > read/write
> > > > path, in-memory compactions, etc).The list of features addressed in
> 2.0.0
> > > > so far can be
> > > > found here [3]. There are thousands. The list of ~3k+ fixes in 2.0.0
> > > > exclusively can be
> > > > found here [4]. Our overview doc. on the state of 2.0.0 is at [6].
> > > >
> > > > This beta was supposed to have as its focus rolling upgrade from
> > > hbase-1.x
> > > > versions but
> > > > this is work not complete (At this late stage, it is looking like it
> will
> > > > be a post-2.0.0 project).
> > > >
> > > > This is our last hbase-2.0.0 beta release. Next up, we'll be rolling
> an
> > > > actual 2.0.0 release
> > > > candidate. Look for this in a week or two after beta-2 goes out,
> after
> > > > we've done more
> > > > testing and documentation (and we fix issues raised by you all
> against
> > > this
> > > > beta).
> > > >
> > > > One known issue, still unaddressed, 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 release).
> > > >
> > > > Please take this beta for a spin. Please vote on whether it ok to
> put out
> > > > this RC as our second
> > > > beta (Note CHANGES has not yet been updated). Let the VOTE be open
> for at
> > > > least 72 hours
> > > > (Lets say Wednesday morning, March 7th).
> > > >
> > > > Thanks,
> > > > Your 2.0.0 Release Manager
> > > >
> > > > 1. http://pgp.mit.edu/pks/lookup?op=get=0x9816C7FC8ACC93D2
> > > > 3. https://goo.gl/scYjJr
> > > > 4. https://goo.gl/dFFT8b
> > > > 5. https://builds.apache.org/job/HBase%20Nightly/job/branch-2/
> > > > 
> > > > 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
> > > > z9iEu_ktczrlKHK8N4SZzs/
> > > >
> > >
> >
>


Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-05 Thread Chia-Ping Tsai
> We have it as an explicit dependency in our top-level pom. Doing
> dependency:tree, hadoop minicluster needs it? Its need to run tests? You
> think we should not include in our binary sir?
IIRC, those test jars are not in binary.tag before. HBASE-19089 add 
hbase-testing-util module to the assembly so the test jars are packaged to 
binary.tar. I'm fine with them.

On 2018/03/05 19:40:30, Stack  wrote: 
> On Mon, Mar 5, 2018 at 6:56 AM, Chia-Ping Tsai  wrote:
> 
> > +1 (binding) with some questions
> > unit test (oracle jdk-8u161) - all pass
> > deploy binary (3 nodes) - ok
> > browse master/regionserver web - LGTM
> > put/delete/get/scan 500W rows - ok
> > create/disable/drop/put/scan/count by shell - ok
> >
> > Q1:
> > the 2.0 binary get fatter than 1.4. (384 MB -> 887MB). Seems we package
> > the test docs and source code to binary tar. Are all of them necessary?
> >
> >
> No. Let me review.
> 
> 
> 
> > Q2:
> > Why some test jars of hadoop are included to hbase/lib? such as
> > hadoop-common-2.7.4-tests and hadoop-hdfs-2.7.4-tests
> >
> >
> We have it as an explicit dependency in our top-level pom. Doing
> dependency:tree, hadoop minicluster needs it? Its need to run tests? You
> think we should not include in our binary sir?
> 
> [INFO] +- org.apache.hadoop:hadoop-minicluster:jar:2.7.4:test
> [INFO] |  +- org.apache.hadoop:hadoop-common:test-jar:tests:2.7.4:test
> 
> 
> Thanks for trying the RC Chia-Ping,
> S
> 
> 
> 
> 
> 
> 
> 
> >
> > On 2018/03/02 23:40:53, Stack  wrote:
> > > The first release candidate for HBase 2.0.0-beta-2 is up at
> > >
> > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-2.RC0/
> > >
> > > Maven artifacts are available from a staging directory here:
> > >
> > >   https://repository.apache.org/content/repositories/orgapachehbase-1199
> > >
> > > All was signed with my key at 8ACC93D2 [1]
> > >
> > > I tagged the RC as 2.0.0-beta-2RC0.2 at
> > > 9e9b347d667e1fc6165c9f8ae5ae7052147e8895
> > >
> > > hbase-2.0.0-beta-2 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
> > > actual 2.0.0 release candidates ("GAs").
> > >
> > > hbase-2.0.0-beta-2 is our second beta release. More than 200 fixes have
> > > gone in since
> > > beta-1. Unit tests generallly pass when run against hadoop2 and
> > hadoop3[5].
> > > It includes
> > > all that was in previous alphas and beta (new assignment manager, offheap
> > > read/write
> > > path, in-memory compactions, etc).The list of features addressed in 2.0.0
> > > so far can be
> > > found here [3]. There are thousands. The list of ~3k+ fixes in 2.0.0
> > > exclusively can be
> > > found here [4]. Our overview doc. on the state of 2.0.0 is at [6].
> > >
> > > This beta was supposed to have as its focus rolling upgrade from
> > hbase-1.x
> > > versions but
> > > this is work not complete (At this late stage, it is looking like it will
> > > be a post-2.0.0 project).
> > >
> > > This is our last hbase-2.0.0 beta release. Next up, we'll be rolling an
> > > actual 2.0.0 release
> > > candidate. Look for this in a week or two after beta-2 goes out, after
> > > we've done more
> > > testing and documentation (and we fix issues raised by you all against
> > this
> > > beta).
> > >
> > > One known issue, still unaddressed, 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 release).
> > >
> > > Please take this beta for a spin. Please vote on whether it ok to put out
> > > this RC as our second
> > > beta (Note CHANGES has not yet been updated). Let the VOTE be open for at
> > > least 72 hours
> > > (Lets say Wednesday morning, March 7th).
> > >
> > > Thanks,
> > > Your 2.0.0 Release Manager
> > >
> > > 1. http://pgp.mit.edu/pks/lookup?op=get=0x9816C7FC8ACC93D2
> > > 3. https://goo.gl/scYjJr
> > > 4. https://goo.gl/dFFT8b
> > > 5. https://builds.apache.org/job/HBase%20Nightly/job/branch-2/
> > > 
> > > 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
> > > z9iEu_ktczrlKHK8N4SZzs/
> > >
> >
> 


Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-05 Thread Jean-Marc Spaggiari
Wierd. I recompiled with the new JARs and all, it now it works. Sorry for
the spam. Running some tests.

JMS

2018-03-05 20:48 GMT-05:00 Jean-Marc Spaggiari :

> Just curious, has something changed in the LoadBalancer?
>
> My own personal balancer was working fine with 2.0.0-b1 but doesn't seems
> to work anymore with 2.0.0-b2:
> 2018-03-05 20:33:55,073 ERROR [master/node2:6] master.HMaster: Failed
> to become active master
> java.lang.NoSuchFieldError: clusterStatus
> at c.c.s.hbase.LoadBasedBalancer.initialize(LoadBasedBalancer.java:42)
> at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitializati
> on(HMaster.java:869)
> at org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(
> HMaster.java:2020)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:553)
> at java.lang.Thread.run(Thread.java:748)
>
> Has the visibility of the clusterStatus field from StochasticLoadBalancer
> changed between the 2 versions? I'm not good enough at GIT to be able to
> compare them :(
>
> JMS
>
>
> 2018-03-05 16:15 GMT-05:00 Umesh Agashe :
>
>> Thanks Stack! Created HBASE-20135.
>>
>> On Mon, Mar 5, 2018 at 11:31 AM, Stack  wrote:
>>
>> > Thanks  Umesh. File an issue though? Stuff Anoops comment in it. While
>> > 'harmless', it will scare users; we should fix it.
>> > Thanks for trying the RC,
>> > S
>> >
>> > On Sun, Mar 4, 2018 at 8:18 PM, Umesh Agashe 
>> wrote:
>> >
>> > > Yes, I started hbase2 over hbase1 when I got the exception. I also
>> tried
>> > > running TestReplicationAdmin a couple of times and can not reliably
>> > > reproduce the problem.
>> > >
>> > > I am changing my vote to +1.
>> > >
>> > > Thanks,
>> > > Umesh
>> > >
>> > >
>> > > On Sun, Mar 4, 2018 at 2:43 PM, Stack  wrote:
>> > >
>> > > > Thank Umesh for giving it a run.
>> > > >
>> > > > Did you start the hbase2 over an hbase1 dataset. I've seen the
>> > exception
>> > > > you note when I've done this. The startup keeps going over this
>> > > exception,
>> > > > right? (IIRC, its a complaint reading a file written w/ hbase1... We
>> > fail
>> > > > to read in the bloom filter which is not the end-of-the-world).
>> > > >
>> > > > On the replication failures, you can reproduce reliably?
>> > > >
>> > > > Thanks,
>> > > > St.Ack
>> > > >
>> > > >
>> > > >
>> > > > On Sun, Mar 4, 2018 at 9:04 AM, Umesh Agashe 
>> > > wrote:
>> > > >
>> > > > > -1 non-binding (concerns noted below)
>> > > > >
>> > > > > download src & bin tar ball   - OK
>> > > > > signatures & sums
>> - OK
>> > > > > build from source (openjdk version "1.8.0_151")  - OK
>> > > > > rat check
>> > >  -
>> > > > > OK
>> > > > > unit tests
>> > > >  -
>> > > > > NOT OK
>> > > > > start local instance from bin & CRUD from shell  - OK
>> > > > > LTT write, read1 million rows, 2 cols/row  - OK
>> > > > > Upgrade from 1.4.2
>>  - OK
>> > > > > check logs
>> > >  -
>> > > > > NOT OK
>> > > > >
>> > > > > NOTE:
>> > > > > * Error message in the log is concerning.
>> > > > >
>> > > > > Found following exception logged multiple times (~11) in the log:
>> > > > > ERROR [StoreFileOpenerThread-test_cf-1]
>> > regionserver.StoreFileReader:
>> > > > > Error
>> > > > > reading bloom filter meta for GENERAL_BLOOM_META -- proceeding
>> > without
>> > > > > java.io.IOException: Comparator class
>> > > > > org.apache.hadoop.hbase.KeyValue$RawBytesComparator
>> > > > > is not instantiable
>> > > > > at org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.
>> > > createComp
>> > > > > arator(FixedFileTrailer.java:628)
>> > > > > at org.apache.hadoop.hbase.io.hfile.CompoundBloomFilter.<
>> > > init>(
>> > > > > CompoundBloomFilter.java:79)
>> > > > > at org.apache.hadoop.hbase.util.BloomFilterFactory.
>> > > createFromMe
>> > > > > ta(BloomFilterFactory.java:104)
>> > > > > at org.apache.hadoop.hbase.regionserver.StoreFileReader.
>> > > loadBlo
>> > > > > omfilter(StoreFileReader.java:479)
>> > > > > at org.apache.hadoop.hbase.regionserver.HStoreFile.open(
>> > > HStoreF
>> > > > > ile.java:425)
>> > > > > at org.apache.hadoop.hbase.regionserver.HStoreFile.
>> > > initReader(H
>> > > > > StoreFile.java:460)
>> > > > > at org.apache.hadoop.hbase.regionserver.HStore.
>> > > createStoreFileA
>> > > > > ndReader(HStore.java:671)
>> > > > > at org.apache.hadoop.hbase.regionserver.HStore.lambda$
>> > > openStore
>> > > > > Files$0(HStore.java:537)
>> > > > > at java.util.concurrent.FutureTas
>> k.run(FutureTask.java:266)
>> > > > > at java.util.concurrent.Executors$RunnableAdapter.
>> > > call(Executor
>> > > > > s.java:511)
>> > > > > at java.util.concurrent.FutureTas
>> k.run(FutureTask.java:266)
>> > > > > at java.util.concurrent.ThreadPoolExecutor.runWorker(
>> > > ThreadPool
>> > > > > Executor.java:1149)
>> > > > >  

Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-05 Thread Jean-Marc Spaggiari
Just curious, has something changed in the LoadBalancer?

My own personal balancer was working fine with 2.0.0-b1 but doesn't seems
to work anymore with 2.0.0-b2:
2018-03-05 20:33:55,073 ERROR [master/node2:6] master.HMaster: Failed
to become active master
java.lang.NoSuchFieldError: clusterStatus
at c.c.s.hbase.LoadBasedBalancer.initialize(LoadBasedBalancer.java:42)
at
org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:869)
at
org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2020)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:553)
at java.lang.Thread.run(Thread.java:748)

Has the visibility of the clusterStatus field from StochasticLoadBalancer
changed between the 2 versions? I'm not good enough at GIT to be able to
compare them :(

JMS


2018-03-05 16:15 GMT-05:00 Umesh Agashe :

> Thanks Stack! Created HBASE-20135.
>
> On Mon, Mar 5, 2018 at 11:31 AM, Stack  wrote:
>
> > Thanks  Umesh. File an issue though? Stuff Anoops comment in it. While
> > 'harmless', it will scare users; we should fix it.
> > Thanks for trying the RC,
> > S
> >
> > On Sun, Mar 4, 2018 at 8:18 PM, Umesh Agashe 
> wrote:
> >
> > > Yes, I started hbase2 over hbase1 when I got the exception. I also
> tried
> > > running TestReplicationAdmin a couple of times and can not reliably
> > > reproduce the problem.
> > >
> > > I am changing my vote to +1.
> > >
> > > Thanks,
> > > Umesh
> > >
> > >
> > > On Sun, Mar 4, 2018 at 2:43 PM, Stack  wrote:
> > >
> > > > Thank Umesh for giving it a run.
> > > >
> > > > Did you start the hbase2 over an hbase1 dataset. I've seen the
> > exception
> > > > you note when I've done this. The startup keeps going over this
> > > exception,
> > > > right? (IIRC, its a complaint reading a file written w/ hbase1... We
> > fail
> > > > to read in the bloom filter which is not the end-of-the-world).
> > > >
> > > > On the replication failures, you can reproduce reliably?
> > > >
> > > > Thanks,
> > > > St.Ack
> > > >
> > > >
> > > >
> > > > On Sun, Mar 4, 2018 at 9:04 AM, Umesh Agashe 
> > > wrote:
> > > >
> > > > > -1 non-binding (concerns noted below)
> > > > >
> > > > > download src & bin tar ball   - OK
> > > > > signatures & sums-
> OK
> > > > > build from source (openjdk version "1.8.0_151")  - OK
> > > > > rat check
> > >  -
> > > > > OK
> > > > > unit tests
> > > >  -
> > > > > NOT OK
> > > > > start local instance from bin & CRUD from shell  - OK
> > > > > LTT write, read1 million rows, 2 cols/row  - OK
> > > > > Upgrade from 1.4.2   -
> OK
> > > > > check logs
> > >  -
> > > > > NOT OK
> > > > >
> > > > > NOTE:
> > > > > * Error message in the log is concerning.
> > > > >
> > > > > Found following exception logged multiple times (~11) in the log:
> > > > > ERROR [StoreFileOpenerThread-test_cf-1]
> > regionserver.StoreFileReader:
> > > > > Error
> > > > > reading bloom filter meta for GENERAL_BLOOM_META -- proceeding
> > without
> > > > > java.io.IOException: Comparator class
> > > > > org.apache.hadoop.hbase.KeyValue$RawBytesComparator
> > > > > is not instantiable
> > > > > at org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.
> > > createComp
> > > > > arator(FixedFileTrailer.java:628)
> > > > > at org.apache.hadoop.hbase.io.hfile.CompoundBloomFilter.<
> > > init>(
> > > > > CompoundBloomFilter.java:79)
> > > > > at org.apache.hadoop.hbase.util.BloomFilterFactory.
> > > createFromMe
> > > > > ta(BloomFilterFactory.java:104)
> > > > > at org.apache.hadoop.hbase.regionserver.StoreFileReader.
> > > loadBlo
> > > > > omfilter(StoreFileReader.java:479)
> > > > > at org.apache.hadoop.hbase.regionserver.HStoreFile.open(
> > > HStoreF
> > > > > ile.java:425)
> > > > > at org.apache.hadoop.hbase.regionserver.HStoreFile.
> > > initReader(H
> > > > > StoreFile.java:460)
> > > > > at org.apache.hadoop.hbase.regionserver.HStore.
> > > createStoreFileA
> > > > > ndReader(HStore.java:671)
> > > > > at org.apache.hadoop.hbase.regionserver.HStore.lambda$
> > > openStore
> > > > > Files$0(HStore.java:537)
> > > > > at java.util.concurrent.FutureTask.run(FutureTask.
> java:266)
> > > > > at java.util.concurrent.Executors$RunnableAdapter.
> > > call(Executor
> > > > > s.java:511)
> > > > > at java.util.concurrent.FutureTask.run(FutureTask.
> java:266)
> > > > > at java.util.concurrent.ThreadPoolExecutor.runWorker(
> > > ThreadPool
> > > > > Executor.java:1149)
> > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> > > ThreadPoo
> > > > > lExecutor.java:624)
> > > > > at java.lang.Thread.run(Thread.java:748)
> > > > > Caused by: java.lang.NullPointerException
> > > > >
> > > > >
> > > > > 

Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-05 Thread Umesh Agashe
Thanks Stack! Created HBASE-20135.

On Mon, Mar 5, 2018 at 11:31 AM, Stack  wrote:

> Thanks  Umesh. File an issue though? Stuff Anoops comment in it. While
> 'harmless', it will scare users; we should fix it.
> Thanks for trying the RC,
> S
>
> On Sun, Mar 4, 2018 at 8:18 PM, Umesh Agashe  wrote:
>
> > Yes, I started hbase2 over hbase1 when I got the exception. I also tried
> > running TestReplicationAdmin a couple of times and can not reliably
> > reproduce the problem.
> >
> > I am changing my vote to +1.
> >
> > Thanks,
> > Umesh
> >
> >
> > On Sun, Mar 4, 2018 at 2:43 PM, Stack  wrote:
> >
> > > Thank Umesh for giving it a run.
> > >
> > > Did you start the hbase2 over an hbase1 dataset. I've seen the
> exception
> > > you note when I've done this. The startup keeps going over this
> > exception,
> > > right? (IIRC, its a complaint reading a file written w/ hbase1... We
> fail
> > > to read in the bloom filter which is not the end-of-the-world).
> > >
> > > On the replication failures, you can reproduce reliably?
> > >
> > > Thanks,
> > > St.Ack
> > >
> > >
> > >
> > > On Sun, Mar 4, 2018 at 9:04 AM, Umesh Agashe 
> > wrote:
> > >
> > > > -1 non-binding (concerns noted below)
> > > >
> > > > download src & bin tar ball   - OK
> > > > signatures & sums- OK
> > > > build from source (openjdk version "1.8.0_151")  - OK
> > > > rat check
> >  -
> > > > OK
> > > > unit tests
> > >  -
> > > > NOT OK
> > > > start local instance from bin & CRUD from shell  - OK
> > > > LTT write, read1 million rows, 2 cols/row  - OK
> > > > Upgrade from 1.4.2   - OK
> > > > check logs
> >  -
> > > > NOT OK
> > > >
> > > > NOTE:
> > > > * Error message in the log is concerning.
> > > >
> > > > Found following exception logged multiple times (~11) in the log:
> > > > ERROR [StoreFileOpenerThread-test_cf-1]
> regionserver.StoreFileReader:
> > > > Error
> > > > reading bloom filter meta for GENERAL_BLOOM_META -- proceeding
> without
> > > > java.io.IOException: Comparator class
> > > > org.apache.hadoop.hbase.KeyValue$RawBytesComparator
> > > > is not instantiable
> > > > at org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.
> > createComp
> > > > arator(FixedFileTrailer.java:628)
> > > > at org.apache.hadoop.hbase.io.hfile.CompoundBloomFilter.<
> > init>(
> > > > CompoundBloomFilter.java:79)
> > > > at org.apache.hadoop.hbase.util.BloomFilterFactory.
> > createFromMe
> > > > ta(BloomFilterFactory.java:104)
> > > > at org.apache.hadoop.hbase.regionserver.StoreFileReader.
> > loadBlo
> > > > omfilter(StoreFileReader.java:479)
> > > > at org.apache.hadoop.hbase.regionserver.HStoreFile.open(
> > HStoreF
> > > > ile.java:425)
> > > > at org.apache.hadoop.hbase.regionserver.HStoreFile.
> > initReader(H
> > > > StoreFile.java:460)
> > > > at org.apache.hadoop.hbase.regionserver.HStore.
> > createStoreFileA
> > > > ndReader(HStore.java:671)
> > > > at org.apache.hadoop.hbase.regionserver.HStore.lambda$
> > openStore
> > > > Files$0(HStore.java:537)
> > > > at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> > > > at java.util.concurrent.Executors$RunnableAdapter.
> > call(Executor
> > > > s.java:511)
> > > > at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> > > > at java.util.concurrent.ThreadPoolExecutor.runWorker(
> > ThreadPool
> > > > Executor.java:1149)
> > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> > ThreadPoo
> > > > lExecutor.java:624)
> > > > at java.lang.Thread.run(Thread.java:748)
> > > > Caused by: java.lang.NullPointerException
> > > >
> > > >
> > > > * Some of the replication UTs failed with message "peer doesn't
> exist"
> > in
> > > > the log
> > > >
> > > > [ERROR] Errors:
> > > > [ERROR]   TestReplicationAdmin.testAddPeerWithState:171 »
> > > RetriesExhausted
> > > > Failed after ...
> > > > [ERROR]   TestReplicationAdmin.testAppendPeerTableCFs:273 »
> > > > RetriesExhausted Failed afte...
> > > > [ERROR]   TestReplicationAdmin.testEnableDisable:247 »
> > RetriesExhausted
> > > > Failed after att...
> > > > [ERROR]   TestReplicationAdmin.testPeerBandwidth:763 »
> > RetriesExhausted
> > > > Failed after att...
> > > > [ERROR]   TestReplicationAdmin.testPeerClusterKey:779 »
> > RetriesExhausted
> > > > Failed after at...
> > > > [ERROR]   TestReplicationAdmin.testPeerConfig:192 » RetriesExhausted
> > > > Failed
> > > > after attemp...
> > > > [ERROR]   TestReplicationAdmin.testPeerConfigConflict:656 »
> > > > RetriesExhausted Failed afte...
> > > > [ERROR]   TestReplicationAdmin.testPeerExcludeNamespaces:515 »
> > > > RetriesExhausted Failed a...
> > > > [ERROR]   TestReplicationAdmin.testPeerReplicationEndpointImpl:795 »
> > > > RetriesExhausted Fa...
> > > 

Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-05 Thread Stack
On Mon, Mar 5, 2018 at 6:56 AM, Chia-Ping Tsai  wrote:

> +1 (binding) with some questions
> unit test (oracle jdk-8u161) - all pass
> deploy binary (3 nodes) - ok
> browse master/regionserver web - LGTM
> put/delete/get/scan 500W rows - ok
> create/disable/drop/put/scan/count by shell - ok
>
> Q1:
> the 2.0 binary get fatter than 1.4. (384 MB -> 887MB). Seems we package
> the test docs and source code to binary tar. Are all of them necessary?
>
>
No. Let me review.



> Q2:
> Why some test jars of hadoop are included to hbase/lib? such as
> hadoop-common-2.7.4-tests and hadoop-hdfs-2.7.4-tests
>
>
We have it as an explicit dependency in our top-level pom. Doing
dependency:tree, hadoop minicluster needs it? Its need to run tests? You
think we should not include in our binary sir?

[INFO] +- org.apache.hadoop:hadoop-minicluster:jar:2.7.4:test
[INFO] |  +- org.apache.hadoop:hadoop-common:test-jar:tests:2.7.4:test


Thanks for trying the RC Chia-Ping,
S







>
> On 2018/03/02 23:40:53, Stack  wrote:
> > The first release candidate for HBase 2.0.0-beta-2 is up at
> >
> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-2.RC0/
> >
> > Maven artifacts are available from a staging directory here:
> >
> >   https://repository.apache.org/content/repositories/orgapachehbase-1199
> >
> > All was signed with my key at 8ACC93D2 [1]
> >
> > I tagged the RC as 2.0.0-beta-2RC0.2 at
> > 9e9b347d667e1fc6165c9f8ae5ae7052147e8895
> >
> > hbase-2.0.0-beta-2 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
> > actual 2.0.0 release candidates ("GAs").
> >
> > hbase-2.0.0-beta-2 is our second beta release. More than 200 fixes have
> > gone in since
> > beta-1. Unit tests generallly pass when run against hadoop2 and
> hadoop3[5].
> > It includes
> > all that was in previous alphas and beta (new assignment manager, offheap
> > read/write
> > path, in-memory compactions, etc).The list of features addressed in 2.0.0
> > so far can be
> > found here [3]. There are thousands. The list of ~3k+ fixes in 2.0.0
> > exclusively can be
> > found here [4]. Our overview doc. on the state of 2.0.0 is at [6].
> >
> > This beta was supposed to have as its focus rolling upgrade from
> hbase-1.x
> > versions but
> > this is work not complete (At this late stage, it is looking like it will
> > be a post-2.0.0 project).
> >
> > This is our last hbase-2.0.0 beta release. Next up, we'll be rolling an
> > actual 2.0.0 release
> > candidate. Look for this in a week or two after beta-2 goes out, after
> > we've done more
> > testing and documentation (and we fix issues raised by you all against
> this
> > beta).
> >
> > One known issue, still unaddressed, 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 release).
> >
> > Please take this beta for a spin. Please vote on whether it ok to put out
> > this RC as our second
> > beta (Note CHANGES has not yet been updated). Let the VOTE be open for at
> > least 72 hours
> > (Lets say Wednesday morning, March 7th).
> >
> > Thanks,
> > Your 2.0.0 Release Manager
> >
> > 1. http://pgp.mit.edu/pks/lookup?op=get=0x9816C7FC8ACC93D2
> > 3. https://goo.gl/scYjJr
> > 4. https://goo.gl/dFFT8b
> > 5. https://builds.apache.org/job/HBase%20Nightly/job/branch-2/
> > 
> > 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
> > z9iEu_ktczrlKHK8N4SZzs/
> >
>


Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-05 Thread Stack
Thanks  Umesh. File an issue though? Stuff Anoops comment in it. While
'harmless', it will scare users; we should fix it.
Thanks for trying the RC,
S

On Sun, Mar 4, 2018 at 8:18 PM, Umesh Agashe  wrote:

> Yes, I started hbase2 over hbase1 when I got the exception. I also tried
> running TestReplicationAdmin a couple of times and can not reliably
> reproduce the problem.
>
> I am changing my vote to +1.
>
> Thanks,
> Umesh
>
>
> On Sun, Mar 4, 2018 at 2:43 PM, Stack  wrote:
>
> > Thank Umesh for giving it a run.
> >
> > Did you start the hbase2 over an hbase1 dataset. I've seen the exception
> > you note when I've done this. The startup keeps going over this
> exception,
> > right? (IIRC, its a complaint reading a file written w/ hbase1... We fail
> > to read in the bloom filter which is not the end-of-the-world).
> >
> > On the replication failures, you can reproduce reliably?
> >
> > Thanks,
> > St.Ack
> >
> >
> >
> > On Sun, Mar 4, 2018 at 9:04 AM, Umesh Agashe 
> wrote:
> >
> > > -1 non-binding (concerns noted below)
> > >
> > > download src & bin tar ball   - OK
> > > signatures & sums- OK
> > > build from source (openjdk version "1.8.0_151")  - OK
> > > rat check
>  -
> > > OK
> > > unit tests
> >  -
> > > NOT OK
> > > start local instance from bin & CRUD from shell  - OK
> > > LTT write, read1 million rows, 2 cols/row  - OK
> > > Upgrade from 1.4.2   - OK
> > > check logs
>  -
> > > NOT OK
> > >
> > > NOTE:
> > > * Error message in the log is concerning.
> > >
> > > Found following exception logged multiple times (~11) in the log:
> > > ERROR [StoreFileOpenerThread-test_cf-1] regionserver.StoreFileReader:
> > > Error
> > > reading bloom filter meta for GENERAL_BLOOM_META -- proceeding without
> > > java.io.IOException: Comparator class
> > > org.apache.hadoop.hbase.KeyValue$RawBytesComparator
> > > is not instantiable
> > > at org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.
> createComp
> > > arator(FixedFileTrailer.java:628)
> > > at org.apache.hadoop.hbase.io.hfile.CompoundBloomFilter.<
> init>(
> > > CompoundBloomFilter.java:79)
> > > at org.apache.hadoop.hbase.util.BloomFilterFactory.
> createFromMe
> > > ta(BloomFilterFactory.java:104)
> > > at org.apache.hadoop.hbase.regionserver.StoreFileReader.
> loadBlo
> > > omfilter(StoreFileReader.java:479)
> > > at org.apache.hadoop.hbase.regionserver.HStoreFile.open(
> HStoreF
> > > ile.java:425)
> > > at org.apache.hadoop.hbase.regionserver.HStoreFile.
> initReader(H
> > > StoreFile.java:460)
> > > at org.apache.hadoop.hbase.regionserver.HStore.
> createStoreFileA
> > > ndReader(HStore.java:671)
> > > at org.apache.hadoop.hbase.regionserver.HStore.lambda$
> openStore
> > > Files$0(HStore.java:537)
> > > at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> > > at java.util.concurrent.Executors$RunnableAdapter.
> call(Executor
> > > s.java:511)
> > > at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> > > at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPool
> > > Executor.java:1149)
> > > at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoo
> > > lExecutor.java:624)
> > > at java.lang.Thread.run(Thread.java:748)
> > > Caused by: java.lang.NullPointerException
> > >
> > >
> > > * Some of the replication UTs failed with message "peer doesn't exist"
> in
> > > the log
> > >
> > > [ERROR] Errors:
> > > [ERROR]   TestReplicationAdmin.testAddPeerWithState:171 »
> > RetriesExhausted
> > > Failed after ...
> > > [ERROR]   TestReplicationAdmin.testAppendPeerTableCFs:273 »
> > > RetriesExhausted Failed afte...
> > > [ERROR]   TestReplicationAdmin.testEnableDisable:247 »
> RetriesExhausted
> > > Failed after att...
> > > [ERROR]   TestReplicationAdmin.testPeerBandwidth:763 »
> RetriesExhausted
> > > Failed after att...
> > > [ERROR]   TestReplicationAdmin.testPeerClusterKey:779 »
> RetriesExhausted
> > > Failed after at...
> > > [ERROR]   TestReplicationAdmin.testPeerConfig:192 » RetriesExhausted
> > > Failed
> > > after attemp...
> > > [ERROR]   TestReplicationAdmin.testPeerConfigConflict:656 »
> > > RetriesExhausted Failed afte...
> > > [ERROR]   TestReplicationAdmin.testPeerExcludeNamespaces:515 »
> > > RetriesExhausted Failed a...
> > > [ERROR]   TestReplicationAdmin.testPeerReplicationEndpointImpl:795 »
> > > RetriesExhausted Fa...
> > > [ERROR]   TestReplicationAdmin.testSetPeerNamespaces:457 »
> > > RetriesExhausted
> > > Failed after...
> > > [ERROR]   TestReplicationAdmin.testSetReplicateAllUserTables:490 »
> > > RetriesExhausted Fail...
> > > [INFO]
> > > [ERROR] Tests run: 1906, Failures: 0, Errors: 11, Skipped: 21
> > >
> > >
> > > On Fri, Mar 2, 2018 at 3:40 PM, Stack  wrote:
> 

Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-05 Thread Anoop John
>Did you start the hbase2 over an hbase1 dataset. I've seen the exception
you note when I've done this. The startup keeps going over this exception,
right? (IIRC, its a complaint reading a file written w/ hbase1... We fail
to read in the bloom filter which is not the end-of-the-world).

Checking the related code.  There seems no issue..  We are not going
to even fail reading the bloom.  In 2.0 code base we expect the
comparator class name to be null.  But in 1.x we write old KV based
Raw Bytes comparator class name.  So reading that back, we will return
class name as null and we get NPE it looks like.

 else if 
(comparatorClassName.equals("org.apache.hadoop.hbase.KeyValue$RawBytesComparator")
|| 
comparatorClassName.equals("org.apache.hadoop.hbase.util.Bytes$ByteArrayComparator"))
{
  // When the comparator to be used is Bytes.BYTES_RAWCOMPARATOR,
we just return null from here
  // Bytes.BYTES_RAWCOMPARATOR is not a CellComparator
  comparatorKlass = null;
}

We can better do a null check before trying the comparator class
instantiation so that we can avoid this scary error logs :-)   But
very minor..   So absolutely no issues here.

-Anoop-

On Mon, Mar 5, 2018 at 8:26 PM, Chia-Ping Tsai  wrote:
> +1 (binding) with some questions
> unit test (oracle jdk-8u161) - all pass
> deploy binary (3 nodes) - ok
> browse master/regionserver web - LGTM
> put/delete/get/scan 500W rows - ok
> create/disable/drop/put/scan/count by shell - ok
>
> Q1:
> the 2.0 binary get fatter than 1.4. (384 MB -> 887MB). Seems we package the 
> test docs and source code to binary tar. Are all of them necessary?
>
> Q2:
> Why some test jars of hadoop are included to hbase/lib? such as 
> hadoop-common-2.7.4-tests and hadoop-hdfs-2.7.4-tests
>
>
> On 2018/03/02 23:40:53, Stack  wrote:
>> The first release candidate for HBase 2.0.0-beta-2 is up at
>>
>>  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-2.RC0/
>>
>> Maven artifacts are available from a staging directory here:
>>
>>   https://repository.apache.org/content/repositories/orgapachehbase-1199
>>
>> All was signed with my key at 8ACC93D2 [1]
>>
>> I tagged the RC as 2.0.0-beta-2RC0.2 at
>> 9e9b347d667e1fc6165c9f8ae5ae7052147e8895
>>
>> hbase-2.0.0-beta-2 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
>> actual 2.0.0 release candidates ("GAs").
>>
>> hbase-2.0.0-beta-2 is our second beta release. More than 200 fixes have
>> gone in since
>> beta-1. Unit tests generallly pass when run against hadoop2 and hadoop3[5].
>> It includes
>> all that was in previous alphas and beta (new assignment manager, offheap
>> read/write
>> path, in-memory compactions, etc).The list of features addressed in 2.0.0
>> so far can be
>> found here [3]. There are thousands. The list of ~3k+ fixes in 2.0.0
>> exclusively can be
>> found here [4]. Our overview doc. on the state of 2.0.0 is at [6].
>>
>> This beta was supposed to have as its focus rolling upgrade from hbase-1.x
>> versions but
>> this is work not complete (At this late stage, it is looking like it will
>> be a post-2.0.0 project).
>>
>> This is our last hbase-2.0.0 beta release. Next up, we'll be rolling an
>> actual 2.0.0 release
>> candidate. Look for this in a week or two after beta-2 goes out, after
>> we've done more
>> testing and documentation (and we fix issues raised by you all against this
>> beta).
>>
>> One known issue, still unaddressed, 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 release).
>>
>> Please take this beta for a spin. Please vote on whether it ok to put out
>> this RC as our second
>> beta (Note CHANGES has not yet been updated). Let the VOTE be open for at
>> least 72 hours
>> (Lets say Wednesday morning, March 7th).
>>
>> Thanks,
>> Your 2.0.0 Release Manager
>>
>> 1. http://pgp.mit.edu/pks/lookup?op=get=0x9816C7FC8ACC93D2
>> 3. https://goo.gl/scYjJr
>> 4. https://goo.gl/dFFT8b
>> 5. https://builds.apache.org/job/HBase%20Nightly/job/branch-2/
>> 
>> 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
>> z9iEu_ktczrlKHK8N4SZzs/
>>


Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-05 Thread Chia-Ping Tsai
+1 (binding) with some questions
unit test (oracle jdk-8u161) - all pass
deploy binary (3 nodes) - ok
browse master/regionserver web - LGTM
put/delete/get/scan 500W rows - ok
create/disable/drop/put/scan/count by shell - ok

Q1:
the 2.0 binary get fatter than 1.4. (384 MB -> 887MB). Seems we package the 
test docs and source code to binary tar. Are all of them necessary?

Q2:
Why some test jars of hadoop are included to hbase/lib? such as 
hadoop-common-2.7.4-tests and hadoop-hdfs-2.7.4-tests


On 2018/03/02 23:40:53, Stack  wrote: 
> The first release candidate for HBase 2.0.0-beta-2 is up at
> 
>  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-2.RC0/
> 
> Maven artifacts are available from a staging directory here:
> 
>   https://repository.apache.org/content/repositories/orgapachehbase-1199
> 
> All was signed with my key at 8ACC93D2 [1]
> 
> I tagged the RC as 2.0.0-beta-2RC0.2 at
> 9e9b347d667e1fc6165c9f8ae5ae7052147e8895
> 
> hbase-2.0.0-beta-2 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
> actual 2.0.0 release candidates ("GAs").
> 
> hbase-2.0.0-beta-2 is our second beta release. More than 200 fixes have
> gone in since
> beta-1. Unit tests generallly pass when run against hadoop2 and hadoop3[5].
> It includes
> all that was in previous alphas and beta (new assignment manager, offheap
> read/write
> path, in-memory compactions, etc).The list of features addressed in 2.0.0
> so far can be
> found here [3]. There are thousands. The list of ~3k+ fixes in 2.0.0
> exclusively can be
> found here [4]. Our overview doc. on the state of 2.0.0 is at [6].
> 
> This beta was supposed to have as its focus rolling upgrade from hbase-1.x
> versions but
> this is work not complete (At this late stage, it is looking like it will
> be a post-2.0.0 project).
> 
> This is our last hbase-2.0.0 beta release. Next up, we'll be rolling an
> actual 2.0.0 release
> candidate. Look for this in a week or two after beta-2 goes out, after
> we've done more
> testing and documentation (and we fix issues raised by you all against this
> beta).
> 
> One known issue, still unaddressed, 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 release).
> 
> Please take this beta for a spin. Please vote on whether it ok to put out
> this RC as our second
> beta (Note CHANGES has not yet been updated). Let the VOTE be open for at
> least 72 hours
> (Lets say Wednesday morning, March 7th).
> 
> Thanks,
> Your 2.0.0 Release Manager
> 
> 1. http://pgp.mit.edu/pks/lookup?op=get=0x9816C7FC8ACC93D2
> 3. https://goo.gl/scYjJr
> 4. https://goo.gl/dFFT8b
> 5. https://builds.apache.org/job/HBase%20Nightly/job/branch-2/
> 
> 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
> z9iEu_ktczrlKHK8N4SZzs/
> 


Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-04 Thread Umesh Agashe
Yes, I started hbase2 over hbase1 when I got the exception. I also tried
running TestReplicationAdmin a couple of times and can not reliably
reproduce the problem.

I am changing my vote to +1.

Thanks,
Umesh


On Sun, Mar 4, 2018 at 2:43 PM, Stack  wrote:

> Thank Umesh for giving it a run.
>
> Did you start the hbase2 over an hbase1 dataset. I've seen the exception
> you note when I've done this. The startup keeps going over this exception,
> right? (IIRC, its a complaint reading a file written w/ hbase1... We fail
> to read in the bloom filter which is not the end-of-the-world).
>
> On the replication failures, you can reproduce reliably?
>
> Thanks,
> St.Ack
>
>
>
> On Sun, Mar 4, 2018 at 9:04 AM, Umesh Agashe  wrote:
>
> > -1 non-binding (concerns noted below)
> >
> > download src & bin tar ball   - OK
> > signatures & sums- OK
> > build from source (openjdk version "1.8.0_151")  - OK
> > rat check   -
> > OK
> > unit tests
>  -
> > NOT OK
> > start local instance from bin & CRUD from shell  - OK
> > LTT write, read1 million rows, 2 cols/row  - OK
> > Upgrade from 1.4.2   - OK
> > check logs -
> > NOT OK
> >
> > NOTE:
> > * Error message in the log is concerning.
> >
> > Found following exception logged multiple times (~11) in the log:
> > ERROR [StoreFileOpenerThread-test_cf-1] regionserver.StoreFileReader:
> > Error
> > reading bloom filter meta for GENERAL_BLOOM_META -- proceeding without
> > java.io.IOException: Comparator class
> > org.apache.hadoop.hbase.KeyValue$RawBytesComparator
> > is not instantiable
> > at org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.createComp
> > arator(FixedFileTrailer.java:628)
> > at org.apache.hadoop.hbase.io.hfile.CompoundBloomFilter.(
> > CompoundBloomFilter.java:79)
> > at org.apache.hadoop.hbase.util.BloomFilterFactory.createFromMe
> > ta(BloomFilterFactory.java:104)
> > at org.apache.hadoop.hbase.regionserver.StoreFileReader.loadBlo
> > omfilter(StoreFileReader.java:479)
> > at org.apache.hadoop.hbase.regionserver.HStoreFile.open(HStoreF
> > ile.java:425)
> > at org.apache.hadoop.hbase.regionserver.HStoreFile.initReader(H
> > StoreFile.java:460)
> > at org.apache.hadoop.hbase.regionserver.HStore.createStoreFileA
> > ndReader(HStore.java:671)
> > at org.apache.hadoop.hbase.regionserver.HStore.lambda$openStore
> > Files$0(HStore.java:537)
> > at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> > at java.util.concurrent.Executors$RunnableAdapter.call(Executor
> > s.java:511)
> > at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
> > Executor.java:1149)
> > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> > lExecutor.java:624)
> > at java.lang.Thread.run(Thread.java:748)
> > Caused by: java.lang.NullPointerException
> >
> >
> > * Some of the replication UTs failed with message "peer doesn't exist" in
> > the log
> >
> > [ERROR] Errors:
> > [ERROR]   TestReplicationAdmin.testAddPeerWithState:171 »
> RetriesExhausted
> > Failed after ...
> > [ERROR]   TestReplicationAdmin.testAppendPeerTableCFs:273 »
> > RetriesExhausted Failed afte...
> > [ERROR]   TestReplicationAdmin.testEnableDisable:247 » RetriesExhausted
> > Failed after att...
> > [ERROR]   TestReplicationAdmin.testPeerBandwidth:763 » RetriesExhausted
> > Failed after att...
> > [ERROR]   TestReplicationAdmin.testPeerClusterKey:779 » RetriesExhausted
> > Failed after at...
> > [ERROR]   TestReplicationAdmin.testPeerConfig:192 » RetriesExhausted
> > Failed
> > after attemp...
> > [ERROR]   TestReplicationAdmin.testPeerConfigConflict:656 »
> > RetriesExhausted Failed afte...
> > [ERROR]   TestReplicationAdmin.testPeerExcludeNamespaces:515 »
> > RetriesExhausted Failed a...
> > [ERROR]   TestReplicationAdmin.testPeerReplicationEndpointImpl:795 »
> > RetriesExhausted Fa...
> > [ERROR]   TestReplicationAdmin.testSetPeerNamespaces:457 »
> > RetriesExhausted
> > Failed after...
> > [ERROR]   TestReplicationAdmin.testSetReplicateAllUserTables:490 »
> > RetriesExhausted Fail...
> > [INFO]
> > [ERROR] Tests run: 1906, Failures: 0, Errors: 11, Skipped: 21
> >
> >
> > On Fri, Mar 2, 2018 at 3:40 PM, Stack  wrote:
> >
> > > The first release candidate for HBase 2.0.0-beta-2 is up at
> > >
> > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-2.RC0/
> > >
> > > Maven artifacts are available from a staging directory here:
> > >
> > >   https://repository.apache.org/content/repositories/
> orgapachehbase-1199
> > >
> > > All was signed with my key at 8ACC93D2 [1]
> > >
> > > I tagged 

Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-04 Thread Stack
Thank Umesh for giving it a run.

Did you start the hbase2 over an hbase1 dataset. I've seen the exception
you note when I've done this. The startup keeps going over this exception,
right? (IIRC, its a complaint reading a file written w/ hbase1... We fail
to read in the bloom filter which is not the end-of-the-world).

On the replication failures, you can reproduce reliably?

Thanks,
St.Ack



On Sun, Mar 4, 2018 at 9:04 AM, Umesh Agashe  wrote:

> -1 non-binding (concerns noted below)
>
> download src & bin tar ball   - OK
> signatures & sums- OK
> build from source (openjdk version "1.8.0_151")  - OK
> rat check   -
> OK
> unit tests   -
> NOT OK
> start local instance from bin & CRUD from shell  - OK
> LTT write, read1 million rows, 2 cols/row  - OK
> Upgrade from 1.4.2   - OK
> check logs -
> NOT OK
>
> NOTE:
> * Error message in the log is concerning.
>
> Found following exception logged multiple times (~11) in the log:
> ERROR [StoreFileOpenerThread-test_cf-1] regionserver.StoreFileReader:
> Error
> reading bloom filter meta for GENERAL_BLOOM_META -- proceeding without
> java.io.IOException: Comparator class
> org.apache.hadoop.hbase.KeyValue$RawBytesComparator
> is not instantiable
> at org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.createComp
> arator(FixedFileTrailer.java:628)
> at org.apache.hadoop.hbase.io.hfile.CompoundBloomFilter.(
> CompoundBloomFilter.java:79)
> at org.apache.hadoop.hbase.util.BloomFilterFactory.createFromMe
> ta(BloomFilterFactory.java:104)
> at org.apache.hadoop.hbase.regionserver.StoreFileReader.loadBlo
> omfilter(StoreFileReader.java:479)
> at org.apache.hadoop.hbase.regionserver.HStoreFile.open(HStoreF
> ile.java:425)
> at org.apache.hadoop.hbase.regionserver.HStoreFile.initReader(H
> StoreFile.java:460)
> at org.apache.hadoop.hbase.regionserver.HStore.createStoreFileA
> ndReader(HStore.java:671)
> at org.apache.hadoop.hbase.regionserver.HStore.lambda$openStore
> Files$0(HStore.java:537)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executor
> s.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
> Executor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> lExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
>
>
> * Some of the replication UTs failed with message "peer doesn't exist" in
> the log
>
> [ERROR] Errors:
> [ERROR]   TestReplicationAdmin.testAddPeerWithState:171 » RetriesExhausted
> Failed after ...
> [ERROR]   TestReplicationAdmin.testAppendPeerTableCFs:273 »
> RetriesExhausted Failed afte...
> [ERROR]   TestReplicationAdmin.testEnableDisable:247 » RetriesExhausted
> Failed after att...
> [ERROR]   TestReplicationAdmin.testPeerBandwidth:763 » RetriesExhausted
> Failed after att...
> [ERROR]   TestReplicationAdmin.testPeerClusterKey:779 » RetriesExhausted
> Failed after at...
> [ERROR]   TestReplicationAdmin.testPeerConfig:192 » RetriesExhausted
> Failed
> after attemp...
> [ERROR]   TestReplicationAdmin.testPeerConfigConflict:656 »
> RetriesExhausted Failed afte...
> [ERROR]   TestReplicationAdmin.testPeerExcludeNamespaces:515 »
> RetriesExhausted Failed a...
> [ERROR]   TestReplicationAdmin.testPeerReplicationEndpointImpl:795 »
> RetriesExhausted Fa...
> [ERROR]   TestReplicationAdmin.testSetPeerNamespaces:457 »
> RetriesExhausted
> Failed after...
> [ERROR]   TestReplicationAdmin.testSetReplicateAllUserTables:490 »
> RetriesExhausted Fail...
> [INFO]
> [ERROR] Tests run: 1906, Failures: 0, Errors: 11, Skipped: 21
>
>
> On Fri, Mar 2, 2018 at 3:40 PM, Stack  wrote:
>
> > The first release candidate for HBase 2.0.0-beta-2 is up at
> >
> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-2.RC0/
> >
> > Maven artifacts are available from a staging directory here:
> >
> >   https://repository.apache.org/content/repositories/orgapachehbase-1199
> >
> > All was signed with my key at 8ACC93D2 [1]
> >
> > I tagged the RC as 2.0.0-beta-2RC0.2 at
> > 9e9b347d667e1fc6165c9f8ae5ae7052147e8895
> >
> > hbase-2.0.0-beta-2 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
> > actual 2.0.0 release candidates ("GAs").
> >
> > hbase-2.0.0-beta-2 is our second beta release. More than 200 fixes have
> > gone in since
> > beta-1. Unit tests 

Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-04 Thread Umesh Agashe
-1 non-binding (concerns noted below)

download src & bin tar ball   - OK
signatures & sums- OK
build from source (openjdk version "1.8.0_151")  - OK
rat check   - OK
unit tests   -
NOT OK
start local instance from bin & CRUD from shell  - OK
LTT write, read1 million rows, 2 cols/row  - OK
Upgrade from 1.4.2   - OK
check logs -
NOT OK

NOTE:
* Error message in the log is concerning.

Found following exception logged multiple times (~11) in the log:
ERROR [StoreFileOpenerThread-test_cf-1] regionserver.StoreFileReader: Error
reading bloom filter meta for GENERAL_BLOOM_META -- proceeding without
java.io.IOException: Comparator class
org.apache.hadoop.hbase.KeyValue$RawBytesComparator
is not instantiable
at org.apache.hadoop.hbase.io.hfile.FixedFileTrailer.createComp
arator(FixedFileTrailer.java:628)
at org.apache.hadoop.hbase.io.hfile.CompoundBloomFilter.(
CompoundBloomFilter.java:79)
at org.apache.hadoop.hbase.util.BloomFilterFactory.createFromMe
ta(BloomFilterFactory.java:104)
at org.apache.hadoop.hbase.regionserver.StoreFileReader.loadBlo
omfilter(StoreFileReader.java:479)
at org.apache.hadoop.hbase.regionserver.HStoreFile.open(HStoreF
ile.java:425)
at org.apache.hadoop.hbase.regionserver.HStoreFile.initReader(H
StoreFile.java:460)
at org.apache.hadoop.hbase.regionserver.HStore.createStoreFileA
ndReader(HStore.java:671)
at org.apache.hadoop.hbase.regionserver.HStore.lambda$openStore
Files$0(HStore.java:537)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.Executors$RunnableAdapter.call(Executor
s.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
Executor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
lExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException


* Some of the replication UTs failed with message "peer doesn't exist" in
the log

[ERROR] Errors:
[ERROR]   TestReplicationAdmin.testAddPeerWithState:171 » RetriesExhausted
Failed after ...
[ERROR]   TestReplicationAdmin.testAppendPeerTableCFs:273 »
RetriesExhausted Failed afte...
[ERROR]   TestReplicationAdmin.testEnableDisable:247 » RetriesExhausted
Failed after att...
[ERROR]   TestReplicationAdmin.testPeerBandwidth:763 » RetriesExhausted
Failed after att...
[ERROR]   TestReplicationAdmin.testPeerClusterKey:779 » RetriesExhausted
Failed after at...
[ERROR]   TestReplicationAdmin.testPeerConfig:192 » RetriesExhausted Failed
after attemp...
[ERROR]   TestReplicationAdmin.testPeerConfigConflict:656 »
RetriesExhausted Failed afte...
[ERROR]   TestReplicationAdmin.testPeerExcludeNamespaces:515 »
RetriesExhausted Failed a...
[ERROR]   TestReplicationAdmin.testPeerReplicationEndpointImpl:795 »
RetriesExhausted Fa...
[ERROR]   TestReplicationAdmin.testSetPeerNamespaces:457 » RetriesExhausted
Failed after...
[ERROR]   TestReplicationAdmin.testSetReplicateAllUserTables:490 »
RetriesExhausted Fail...
[INFO]
[ERROR] Tests run: 1906, Failures: 0, Errors: 11, Skipped: 21


On Fri, Mar 2, 2018 at 3:40 PM, Stack  wrote:

> The first release candidate for HBase 2.0.0-beta-2 is up at
>
>  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-2.RC0/
>
> Maven artifacts are available from a staging directory here:
>
>   https://repository.apache.org/content/repositories/orgapachehbase-1199
>
> All was signed with my key at 8ACC93D2 [1]
>
> I tagged the RC as 2.0.0-beta-2RC0.2 at
> 9e9b347d667e1fc6165c9f8ae5ae7052147e8895
>
> hbase-2.0.0-beta-2 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
> actual 2.0.0 release candidates ("GAs").
>
> hbase-2.0.0-beta-2 is our second beta release. More than 200 fixes have
> gone in since
> beta-1. Unit tests generallly pass when run against hadoop2 and hadoop3[5].
> It includes
> all that was in previous alphas and beta (new assignment manager, offheap
> read/write
> path, in-memory compactions, etc).The list of features addressed in 2.0.0
> so far can be
> found here [3]. There are thousands. The list of ~3k+ fixes in 2.0.0
> exclusively can be
> found here [4]. Our overview doc. on the state of 2.0.0 is at [6].
>
> This beta was supposed to have as its focus rolling upgrade from hbase-1.x
> versions but
> this is work not complete (At this late stage, it is looking like it will
> be a post-2.0.0 project).
>
> This is our last hbase-2.0.0 beta release. Next up, we'll be rolling an

Re: [VOTE] The first hbase-2.0.0-beta-2 Release Candidate is available for download

2018-03-02 Thread Ted Yu
+1

Checked signature
Ran test suite against hadoop3 - passed
Ran load test tool using the following commands - passed:

hbase ltt -tn ltt -write 20:2000 -data_block_encoding ROW_INDEX_V1
-num_keys 50
hbase ltt -tn ltt -read 100 -max_read_errors 2 -num_keys 50

On Fri, Mar 2, 2018 at 3:40 PM, Stack  wrote:

> The first release candidate for HBase 2.0.0-beta-2 is up at
>
>  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-2.RC0/
>
> Maven artifacts are available from a staging directory here:
>
>   https://repository.apache.org/content/repositories/orgapachehbase-1199
>
> All was signed with my key at 8ACC93D2 [1]
>
> I tagged the RC as 2.0.0-beta-2RC0.2 at
> 9e9b347d667e1fc6165c9f8ae5ae7052147e8895
>
> hbase-2.0.0-beta-2 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
> actual 2.0.0 release candidates ("GAs").
>
> hbase-2.0.0-beta-2 is our second beta release. More than 200 fixes have
> gone in since
> beta-1. Unit tests generallly pass when run against hadoop2 and hadoop3[5].
> It includes
> all that was in previous alphas and beta (new assignment manager, offheap
> read/write
> path, in-memory compactions, etc).The list of features addressed in 2.0.0
> so far can be
> found here [3]. There are thousands. The list of ~3k+ fixes in 2.0.0
> exclusively can be
> found here [4]. Our overview doc. on the state of 2.0.0 is at [6].
>
> This beta was supposed to have as its focus rolling upgrade from hbase-1.x
> versions but
> this is work not complete (At this late stage, it is looking like it will
> be a post-2.0.0 project).
>
> This is our last hbase-2.0.0 beta release. Next up, we'll be rolling an
> actual 2.0.0 release
> candidate. Look for this in a week or two after beta-2 goes out, after
> we've done more
> testing and documentation (and we fix issues raised by you all against this
> beta).
>
> One known issue, still unaddressed, 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 release).
>
> Please take this beta for a spin. Please vote on whether it ok to put out
> this RC as our second
> beta (Note CHANGES has not yet been updated). Let the VOTE be open for at
> least 72 hours
> (Lets say Wednesday morning, March 7th).
>
> Thanks,
> Your 2.0.0 Release Manager
>
> 1. http://pgp.mit.edu/pks/lookup?op=get=0x9816C7FC8ACC93D2
> 3. https://goo.gl/scYjJr
> 4. https://goo.gl/dFFT8b
> 5. https://builds.apache.org/job/HBase%20Nightly/job/branch-2/
> 
> 6. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4
> z9iEu_ktczrlKHK8N4SZzs/
>