You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Stack <st...@duboce.net> on 2017/11/01 14:17:11 UTC
[VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
The first release candidate for HBase 2.0.0-alpha4 is up at:
https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha4RC0/
Maven artifacts are available from a staging directory here:
https://repository.apache.org/content/repositories/orgapachehbase-1178
All was signed with my key at 8ACC93D2 [1]
I tagged the RC as 2.0.0-alpha4RC0
(5c4b985f89c99cc8b0f8515a4097c811a0848835)
hbase-2.0.0-alpha4 is our fourth alpha release along our march toward
hbase-2.0.0. It includes all that was in previous alphas (new assignment
manager, offheap read/write path, in-memory compactions, etc.), but had a
focus on "Coprocessor Fixup": We no longer pass Coprocessors
InterfaceAudience.Private parameters and we cut down on the access and
ability to influence hbase core processing (See [2] on why the radical
changes in Coprocessor Interface). If you are a Coprocessor developer or
have Coprocessors to deploy on hbase-2.0.0, we need to hear about your
experience now before we make an hbase-2.0.0 beta.
hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production preview of
what hbase-2.0.0 will look like. It is meant for devs and downstreamers to
test drive and flag us early if we messed up anything ahead of our rolling
GAs.
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]. 2.0.0-beta-1 will
be our next release. Its theme is the "Finishing up 2.0.0" release. Here is
the list of what we have targeted for beta-1 [5]. Check it out. Shout if
there is anything missing. We may do a 2.0.0-beta-2 if a need. We'll see.
Please take this alpha for a spin especially if you are a Coprocessor
developer or have a Coprocessor you want to deploy on hbase-2.0.0. Please
vote on whether it ok to put out this RC as our first alpha (bar is low for
an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE be open
for 72 hours (Saturday)
Thanks,
Your 2.0.0 Release Manager
1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
2. Why CPs are Incompatible:
https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
3. https://goo.gl/scYjJr
4. https://goo.gl/tMHkYS
5. https://issues.apache.org/jira/projects/HBASE/versions/12340861
6.
https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_ktczrlKHK8N4SZzs/
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Peter Somogyi <ps...@cloudera.com>.
+1 (non-binding), found 1 issue.
Checked signatures, sums - OK
Built from source tar and git tag (Oracle JDK 1.8.0_151, Maven 3.5.2) - OK
Rat check - OK
Starting standalone server from bin tar - OK
LTT with 1M rows - OK
LICENSE, NOTICE - OK
Problem:
Starting standalone server after building from src tar fails: same problem
that Guanghao Zhang had. HBASE-18705
On Wed, Nov 1, 2017 at 3:17 PM, Stack <st...@duboce.net> wrote:
> The first release candidate for HBase 2.0.0-alpha4 is up at:
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha4RC0/
>
> Maven artifacts are available from a staging directory here:
>
> https://repository.apache.org/content/repositories/orgapachehbase-1178
>
> All was signed with my key at 8ACC93D2 [1]
>
> I tagged the RC as 2.0.0-alpha4RC0
> (5c4b985f89c99cc8b0f8515a4097c811a0848835)
>
> hbase-2.0.0-alpha4 is our fourth alpha release along our march toward
> hbase-2.0.0. It includes all that was in previous alphas (new assignment
> manager, offheap read/write path, in-memory compactions, etc.), but had a
> focus on "Coprocessor Fixup": We no longer pass Coprocessors
> InterfaceAudience.Private parameters and we cut down on the access and
> ability to influence hbase core processing (See [2] on why the radical
> changes in Coprocessor Interface). If you are a Coprocessor developer or
> have Coprocessors to deploy on hbase-2.0.0, we need to hear about your
> experience now before we make an hbase-2.0.0 beta.
>
> hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production preview of
> what hbase-2.0.0 will look like. It is meant for devs and downstreamers to
> test drive and flag us early if we messed up anything ahead of our rolling
> GAs.
>
> 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]. 2.0.0-beta-1 will
> be our next release. Its theme is the "Finishing up 2.0.0" release. Here is
> the list of what we have targeted for beta-1 [5]. Check it out. Shout if
> there is anything missing. We may do a 2.0.0-beta-2 if a need. We'll see.
>
> Please take this alpha for a spin especially if you are a Coprocessor
> developer or have a Coprocessor you want to deploy on hbase-2.0.0. Please
> vote on whether it ok to put out this RC as our first alpha (bar is low for
> an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE be open
> for 72 hours (Saturday)
>
> Thanks,
> Your 2.0.0 Release Manager
>
> 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> 2. Why CPs are Incompatible:
> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> 3. https://goo.gl/scYjJr
> 4. https://goo.gl/tMHkYS
> 5. https://issues.apache.org/jira/projects/HBASE/versions/12340861
> 6.
> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> ktczrlKHK8N4SZzs/
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Umesh Agashe <ua...@cloudera.com>.
+1
Questions/ concerns:
* Staging directory naming convention changed between alpha-3 and alpha-4:
hbase-2.0.0-alpha-3RC0/
hbase-2.0.0-alpha4RC0/
* .gitignore be included in source bundle, can it be dropped?
Verifications:
* Download the src tarball: good.
* Verify the checksums and signature: good.
* Extract and build from source. openjdk version "1.8.0_131": good.
* Rat check: good.
* Download the bin tarball: good.
* Verify the checksums and signature: good.
* Extract it and verify layout visually: good.
* Start a local instance. Run the 'hbase shell' with some basic table commands:
good.
* Run ltt with 10 million rows and 2 columns/ row: good.
* Inspect logs: good.
On Wed, Nov 1, 2017 at 7:17 AM, Stack <st...@duboce.net> wrote:
> The first release candidate for HBase 2.0.0-alpha4 is up at:
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha4RC0/
>
> Maven artifacts are available from a staging directory here:
>
> https://repository.apache.org/content/repositories/orgapachehbase-1178
>
> All was signed with my key at 8ACC93D2 [1]
>
> I tagged the RC as 2.0.0-alpha4RC0
> (5c4b985f89c99cc8b0f8515a4097c811a0848835)
>
> hbase-2.0.0-alpha4 is our fourth alpha release along our march toward
> hbase-2.0.0. It includes all that was in previous alphas (new assignment
> manager, offheap read/write path, in-memory compactions, etc.), but had a
> focus on "Coprocessor Fixup": We no longer pass Coprocessors
> InterfaceAudience.Private parameters and we cut down on the access and
> ability to influence hbase core processing (See [2] on why the radical
> changes in Coprocessor Interface). If you are a Coprocessor developer or
> have Coprocessors to deploy on hbase-2.0.0, we need to hear about your
> experience now before we make an hbase-2.0.0 beta.
>
> hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production preview of
> what hbase-2.0.0 will look like. It is meant for devs and downstreamers to
> test drive and flag us early if we messed up anything ahead of our rolling
> GAs.
>
> 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]. 2.0.0-beta-1 will
> be our next release. Its theme is the "Finishing up 2.0.0" release. Here is
> the list of what we have targeted for beta-1 [5]. Check it out. Shout if
> there is anything missing. We may do a 2.0.0-beta-2 if a need. We'll see.
>
> Please take this alpha for a spin especially if you are a Coprocessor
> developer or have a Coprocessor you want to deploy on hbase-2.0.0. Please
> vote on whether it ok to put out this RC as our first alpha (bar is low for
> an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE be open
> for 72 hours (Saturday)
>
> Thanks,
> Your 2.0.0 Release Manager
>
> 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> 2. Why CPs are Incompatible:
> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> 3. https://goo.gl/scYjJr
> 4. https://goo.gl/tMHkYS
> 5. https://issues.apache.org/jira/projects/HBASE/versions/12340861
> 6.
> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> ktczrlKHK8N4SZzs/
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Andrew Purtell <ap...@apache.org>.
+1
Sums and signatures: ok
Spot check LICENSE and NOTICE: ok
RAT check: ok
Built from source: ok (8u133)
LTT, 1M rows: ok (8u133)
On Wed, Nov 1, 2017 at 7:17 AM, Stack <st...@duboce.net> wrote:
> The first release candidate for HBase 2.0.0-alpha4 is up at:
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha4RC0/
>
> Maven artifacts are available from a staging directory here:
>
> https://repository.apache.org/content/repositories/orgapachehbase-1178
>
> All was signed with my key at 8ACC93D2 [1]
>
> I tagged the RC as 2.0.0-alpha4RC0
> (5c4b985f89c99cc8b0f8515a4097c811a0848835)
>
> hbase-2.0.0-alpha4 is our fourth alpha release along our march toward
> hbase-2.0.0. It includes all that was in previous alphas (new assignment
> manager, offheap read/write path, in-memory compactions, etc.), but had a
> focus on "Coprocessor Fixup": We no longer pass Coprocessors
> InterfaceAudience.Private parameters and we cut down on the access and
> ability to influence hbase core processing (See [2] on why the radical
> changes in Coprocessor Interface). If you are a Coprocessor developer or
> have Coprocessors to deploy on hbase-2.0.0, we need to hear about your
> experience now before we make an hbase-2.0.0 beta.
>
> hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production preview of
> what hbase-2.0.0 will look like. It is meant for devs and downstreamers to
> test drive and flag us early if we messed up anything ahead of our rolling
> GAs.
>
> 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]. 2.0.0-beta-1 will
> be our next release. Its theme is the "Finishing up 2.0.0" release. Here is
> the list of what we have targeted for beta-1 [5]. Check it out. Shout if
> there is anything missing. We may do a 2.0.0-beta-2 if a need. We'll see.
>
> Please take this alpha for a spin especially if you are a Coprocessor
> developer or have a Coprocessor you want to deploy on hbase-2.0.0. Please
> vote on whether it ok to put out this RC as our first alpha (bar is low for
> an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE be open
> for 72 hours (Saturday)
>
> Thanks,
> Your 2.0.0 Release Manager
>
> 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> 2. Why CPs are Incompatible:
> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> 3. https://goo.gl/scYjJr
> 4. https://goo.gl/tMHkYS
> 5. https://issues.apache.org/jira/projects/HBASE/versions/12340861
> 6.
> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> ktczrlKHK8N4SZzs/
>
--
Best regards,
Andrew
Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
- A23, Crosstalk
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Peter Somogyi <ps...@cloudera.com>.
+1 (non-binding), found 1 issue.
Checked signatures, sums - OK
Built from source tar and git tag (Oracle JDK 1.8.0_151, Maven 3.5.2) - OK
Rat check - OK
Starting standalone server from bin tar - OK
LTT with 1M rows - OK
LICENSE, NOTICE - OK
Problem:
Starting standalone server after building from src tar fails: same problem
that Guanghao Zhang had. HBASE-18705
On Wed, Nov 1, 2017 at 3:17 PM, Stack <st...@duboce.net> wrote:
> The first release candidate for HBase 2.0.0-alpha4 is up at:
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha4RC0/
>
> Maven artifacts are available from a staging directory here:
>
> https://repository.apache.org/content/repositories/orgapachehbase-1178
>
> All was signed with my key at 8ACC93D2 [1]
>
> I tagged the RC as 2.0.0-alpha4RC0
> (5c4b985f89c99cc8b0f8515a4097c811a0848835)
>
> hbase-2.0.0-alpha4 is our fourth alpha release along our march toward
> hbase-2.0.0. It includes all that was in previous alphas (new assignment
> manager, offheap read/write path, in-memory compactions, etc.), but had a
> focus on "Coprocessor Fixup": We no longer pass Coprocessors
> InterfaceAudience.Private parameters and we cut down on the access and
> ability to influence hbase core processing (See [2] on why the radical
> changes in Coprocessor Interface). If you are a Coprocessor developer or
> have Coprocessors to deploy on hbase-2.0.0, we need to hear about your
> experience now before we make an hbase-2.0.0 beta.
>
> hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production preview of
> what hbase-2.0.0 will look like. It is meant for devs and downstreamers to
> test drive and flag us early if we messed up anything ahead of our rolling
> GAs.
>
> 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]. 2.0.0-beta-1 will
> be our next release. Its theme is the "Finishing up 2.0.0" release. Here is
> the list of what we have targeted for beta-1 [5]. Check it out. Shout if
> there is anything missing. We may do a 2.0.0-beta-2 if a need. We'll see.
>
> Please take this alpha for a spin especially if you are a Coprocessor
> developer or have a Coprocessor you want to deploy on hbase-2.0.0. Please
> vote on whether it ok to put out this RC as our first alpha (bar is low for
> an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE be open
> for 72 hours (Saturday)
>
> Thanks,
> Your 2.0.0 Release Manager
>
> 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> 2. Why CPs are Incompatible:
> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> 3. https://goo.gl/scYjJr
> 4. https://goo.gl/tMHkYS
> 5. https://issues.apache.org/jira/projects/HBASE/versions/12340861
> 6.
> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> ktczrlKHK8N4SZzs/
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by ramkrishna vasudevan <ra...@gmail.com>.
Downloaded src tar and bin tar.
After building the src code tried to start from the src/bin folder. But it
had the cached_classpath issue. I can see that already the issue has been
backported.
Then started master and region server with bin tar. Ran PE tool. All looks
fine.
Infact ran PE tool with AsyncWAL also to verify its performance. Seems it
is faster than the normal WAL. (but we are not looking for this now).
Overall +1.
Regards
Ram
On Thu, Nov 2, 2017 at 10:39 PM, Stack <st...@duboce.net> wrote:
> I backported HBASE-18705.
> St.Ack
>
> On Thu, Nov 2, 2017 at 10:05 AM, Stack <st...@duboce.net> wrote:
>
> > Thank you Guanghao. Let me see about getting the issue backported. Are
> you
> > a +/- 1 sir? Thanks for the digging.
> > S
> >
> > On Thu, Nov 2, 2017 at 1:31 AM, Guanghao Zhang <zg...@gmail.com>
> wrote:
> >
> >> There is already a issue HBASE-18705
> >> <https://issues.apache.org/jira/browse/HBASE-18705> about this problem.
> >> But
> >> it was only pushed to master branch.
> >>
> >> 2017-11-02 15:21 GMT+08:00 Guanghao Zhang <zg...@gmail.com>:
> >>
> >> > Updated f="${HBASE_HOME}/target/cached_classpath.txt" to
> >> > f="${HBASE_HOME}/hbase-build-configuration/target/cached_cla
> >> sspath.txt".
> >> > Then start hbase success. Anything wrong for my environment?
> >> >
> >> > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> >> > 2015-11-11T00:41:47+08:00)
> >> > Maven home: /opt/soft/apache-maven-3.3.9
> >> > Java version: 1.8.0_131, vendor: Oracle Corporation
> >> > Java home: /opt/soft/jdk1.8.0_131/jre
> >> > Default locale: zh_CN, platform encoding: UTF-8
> >> > OS name: "linux", version: "3.13.0-46-generic", arch: "amd64", family:
> >> > "unix"
> >> >
> >> >
> >> >
> >> > 2017-11-02 15:18 GMT+08:00 Guanghao Zhang <zg...@gmail.com>:
> >> >
> >> >> Download src and build pass.
> >> >> But when start-hbase.sh, I found the master can't start in standalone
> >> >> mode.
> >> >>
> >> >> ```
> >> >> running master, logging to /home/hao/open_source/hbase_re
> >> >> lease/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-master-Xiaohao.out
> >> >> As this is a development environment, we need
> >> >> /home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/bin/.
> >> ./target/cached_classpath.txt
> >> >> to be generated from maven (command: mvn install -DskipTests)
> >> >> : running regionserver, logging to /home/hao/open_source/hbase_re
> >> >> lease/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-regionserver-
> >> Xiaohao.out
> >> >> : As this is a development environment, we need
> >> >> /home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/bin/.
> >> ./target/cached_classpath.txt
> >> >> to be generated from maven (command: mvn install -DskipTests)
> >> >> ```
> >> >>
> >> >> And I try mvn install -DskipTests, and found the cached_classpath.txt
> >> >> in hbase-build-configuration/target/cached_classpath.txt. The path
> is
> >> >> wrong in bin/hbase. So I update f="${HBASE_HOME}/hbase-
> >> >> build-configuration/target/cached_classpath.txt" in bin/hbase, then
> >> >> start master success. File a jira for this?
> >> >>
> >> >> 2017-11-02 14:02 GMT+08:00 Stack <st...@duboce.net>:
> >> >>
> >> >>> On Wed, Nov 1, 2017 at 9:41 PM, Josh Elser <el...@apache.org>
> wrote:
> >> >>>
> >> >>> > +1 (binding)
> >> >>> >
> >> >>> > * UT's mostly ok. Exceptions being: TestNamespacesInstanceResource
> ,
> >> >>> > TestReplicaWithCluster, TestReplicationAdmin, and
> >> >>> TestRegionServerHostname
> >> >>> > consistently fail for me locally (commented on HBASE-19147)
> >> >>> > * xsum+sigs OK
> >> >>> > * can build from source
> >> >>> > * src archive contents looks OK (exception below)
> >> >>> > * Built, deployed locally, ran PE without issue
> >> >>> >
> >> >>> >
> >> >>> Excellent. Thanks Josh.
> >> >>>
> >> >>>
> >> >>>
> >> >>> > I stumbled across src/main/site/resources/repo/o
> >> >>> > rg/apache/maven/skins/maven-fluido-skin/1.5-HBASE/maven-flui
> >> >>> do-skin-1.5-HBASE.jar
> >> >>> > in the source archive which was introduced via
> >> >>> > https://issues.apache.org/jira/browse/HBASE-14785. Best as I can
> >> tell,
> >> >>> > this was a hack to work around a fluido-skin bug and we should be
> >> able
> >> >>> to
> >> >>> > remove it now. Not sure if we've already discussed the
> >> >>> > binary-file-in-src-release concerns of this previously or not...
> >> >>> >
> >> >>> >
> >> >>> Sean noted this in an alpha-3 VOTE.
> >> >>>
> >> >>> I came across it yesterday.
> >> >>>
> >> >>> What you reckon Misty (if you looking at this?) If you remember,
> what
> >> >>> would
> >> >>> I look for?
> >> >>>
> >> >>> Thanks,
> >> >>> St.Ack
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>> > - Josh
> >> >>> >
> >> >>> >
> >> >>> > On 11/1/17 10:17 AM, Stack wrote:
> >> >>> >
> >> >>> >> The first release candidate for HBase 2.0.0-alpha4 is up at:
> >> >>> >>
> >> >>> >> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alp
> >> >>> ha4RC0/
> >> >>> >>
> >> >>> >> Maven artifacts are available from a staging directory here:
> >> >>> >>
> >> >>> >> https://repository.apache.org/content/repositories/orgapache
> >> >>> hbase-1178
> >> >>> >>
> >> >>> >> All was signed with my key at 8ACC93D2 [1]
> >> >>> >>
> >> >>> >> I tagged the RC as 2.0.0-alpha4RC0
> >> >>> >> (5c4b985f89c99cc8b0f8515a4097c811a0848835)
> >> >>> >>
> >> >>> >> hbase-2.0.0-alpha4 is our fourth alpha release along our march
> >> toward
> >> >>> >> hbase-2.0.0. It includes all that was in previous alphas (new
> >> >>> assignment
> >> >>> >> manager, offheap read/write path, in-memory compactions, etc.),
> but
> >> >>> had a
> >> >>> >> focus on "Coprocessor Fixup": We no longer pass Coprocessors
> >> >>> >> InterfaceAudience.Private parameters and we cut down on the
> access
> >> and
> >> >>> >> ability to influence hbase core processing (See [2] on why the
> >> radical
> >> >>> >> changes in Coprocessor Interface). If you are a Coprocessor
> >> developer
> >> >>> or
> >> >>> >> have Coprocessors to deploy on hbase-2.0.0, we need to hear about
> >> your
> >> >>> >> experience now before we make an hbase-2.0.0 beta.
> >> >>> >>
> >> >>> >> hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production
> >> >>> preview of
> >> >>> >> what hbase-2.0.0 will look like. It is meant for devs and
> >> >>> downstreamers to
> >> >>> >> test drive and flag us early if we messed up anything ahead of
> our
> >> >>> rolling
> >> >>> >> GAs.
> >> >>> >>
> >> >>> >> 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].
> >> 2.0.0-beta-1
> >> >>> >> will
> >> >>> >> be our next release. Its theme is the "Finishing up 2.0.0"
> release.
> >> >>> Here
> >> >>> >> is
> >> >>> >> the list of what we have targeted for beta-1 [5]. Check it out.
> >> Shout
> >> >>> if
> >> >>> >> there is anything missing. We may do a 2.0.0-beta-2 if a need.
> >> We'll
> >> >>> see.
> >> >>> >>
> >> >>> >> Please take this alpha for a spin especially if you are a
> >> Coprocessor
> >> >>> >> developer or have a Coprocessor you want to deploy on
> hbase-2.0.0.
> >> >>> Please
> >> >>> >> vote on whether it ok to put out this RC as our first alpha (bar
> is
> >> >>> low
> >> >>> >> for
> >> >>> >> an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the
> VOTE
> >> be
> >> >>> open
> >> >>> >> for 72 hours (Saturday)
> >> >>> >>
> >> >>> >> Thanks,
> >> >>> >> Your 2.0.0 Release Manager
> >> >>> >>
> >> >>> >> 1. http://pgp.mit.edu/pks/lookup?op=get&search=
> 0x9816C7FC8ACC93D2
> >> >>> >> 2. Why CPs are Incompatible:
> >> >>> >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
> >> >>> >> Eu_ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> >> >>> >> 3. https://goo.gl/scYjJr
> >> >>> >> 4. https://goo.gl/tMHkYS
> >> >>> >> 5. https://issues.apache.org/jira/projects/HBASE/versions/
> 12340861
> >> >>> >> 6.
> >> >>> >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
> >> >>> >> Eu_ktczrlKHK8N4SZzs/
> >> >>> >>
> >> >>> >>
> >> >>>
> >> >>
> >> >>
> >> >
> >>
> >
> >
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Stack <st...@duboce.net>.
I backported HBASE-18705.
St.Ack
On Thu, Nov 2, 2017 at 10:05 AM, Stack <st...@duboce.net> wrote:
> Thank you Guanghao. Let me see about getting the issue backported. Are you
> a +/- 1 sir? Thanks for the digging.
> S
>
> On Thu, Nov 2, 2017 at 1:31 AM, Guanghao Zhang <zg...@gmail.com> wrote:
>
>> There is already a issue HBASE-18705
>> <https://issues.apache.org/jira/browse/HBASE-18705> about this problem.
>> But
>> it was only pushed to master branch.
>>
>> 2017-11-02 15:21 GMT+08:00 Guanghao Zhang <zg...@gmail.com>:
>>
>> > Updated f="${HBASE_HOME}/target/cached_classpath.txt" to
>> > f="${HBASE_HOME}/hbase-build-configuration/target/cached_cla
>> sspath.txt".
>> > Then start hbase success. Anything wrong for my environment?
>> >
>> > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
>> > 2015-11-11T00:41:47+08:00)
>> > Maven home: /opt/soft/apache-maven-3.3.9
>> > Java version: 1.8.0_131, vendor: Oracle Corporation
>> > Java home: /opt/soft/jdk1.8.0_131/jre
>> > Default locale: zh_CN, platform encoding: UTF-8
>> > OS name: "linux", version: "3.13.0-46-generic", arch: "amd64", family:
>> > "unix"
>> >
>> >
>> >
>> > 2017-11-02 15:18 GMT+08:00 Guanghao Zhang <zg...@gmail.com>:
>> >
>> >> Download src and build pass.
>> >> But when start-hbase.sh, I found the master can't start in standalone
>> >> mode.
>> >>
>> >> ```
>> >> running master, logging to /home/hao/open_source/hbase_re
>> >> lease/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-master-Xiaohao.out
>> >> As this is a development environment, we need
>> >> /home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/bin/.
>> ./target/cached_classpath.txt
>> >> to be generated from maven (command: mvn install -DskipTests)
>> >> : running regionserver, logging to /home/hao/open_source/hbase_re
>> >> lease/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-regionserver-
>> Xiaohao.out
>> >> : As this is a development environment, we need
>> >> /home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/bin/.
>> ./target/cached_classpath.txt
>> >> to be generated from maven (command: mvn install -DskipTests)
>> >> ```
>> >>
>> >> And I try mvn install -DskipTests, and found the cached_classpath.txt
>> >> in hbase-build-configuration/target/cached_classpath.txt. The path is
>> >> wrong in bin/hbase. So I update f="${HBASE_HOME}/hbase-
>> >> build-configuration/target/cached_classpath.txt" in bin/hbase, then
>> >> start master success. File a jira for this?
>> >>
>> >> 2017-11-02 14:02 GMT+08:00 Stack <st...@duboce.net>:
>> >>
>> >>> On Wed, Nov 1, 2017 at 9:41 PM, Josh Elser <el...@apache.org> wrote:
>> >>>
>> >>> > +1 (binding)
>> >>> >
>> >>> > * UT's mostly ok. Exceptions being: TestNamespacesInstanceResource,
>> >>> > TestReplicaWithCluster, TestReplicationAdmin, and
>> >>> TestRegionServerHostname
>> >>> > consistently fail for me locally (commented on HBASE-19147)
>> >>> > * xsum+sigs OK
>> >>> > * can build from source
>> >>> > * src archive contents looks OK (exception below)
>> >>> > * Built, deployed locally, ran PE without issue
>> >>> >
>> >>> >
>> >>> Excellent. Thanks Josh.
>> >>>
>> >>>
>> >>>
>> >>> > I stumbled across src/main/site/resources/repo/o
>> >>> > rg/apache/maven/skins/maven-fluido-skin/1.5-HBASE/maven-flui
>> >>> do-skin-1.5-HBASE.jar
>> >>> > in the source archive which was introduced via
>> >>> > https://issues.apache.org/jira/browse/HBASE-14785. Best as I can
>> tell,
>> >>> > this was a hack to work around a fluido-skin bug and we should be
>> able
>> >>> to
>> >>> > remove it now. Not sure if we've already discussed the
>> >>> > binary-file-in-src-release concerns of this previously or not...
>> >>> >
>> >>> >
>> >>> Sean noted this in an alpha-3 VOTE.
>> >>>
>> >>> I came across it yesterday.
>> >>>
>> >>> What you reckon Misty (if you looking at this?) If you remember, what
>> >>> would
>> >>> I look for?
>> >>>
>> >>> Thanks,
>> >>> St.Ack
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> > - Josh
>> >>> >
>> >>> >
>> >>> > On 11/1/17 10:17 AM, Stack wrote:
>> >>> >
>> >>> >> The first release candidate for HBase 2.0.0-alpha4 is up at:
>> >>> >>
>> >>> >> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alp
>> >>> ha4RC0/
>> >>> >>
>> >>> >> Maven artifacts are available from a staging directory here:
>> >>> >>
>> >>> >> https://repository.apache.org/content/repositories/orgapache
>> >>> hbase-1178
>> >>> >>
>> >>> >> All was signed with my key at 8ACC93D2 [1]
>> >>> >>
>> >>> >> I tagged the RC as 2.0.0-alpha4RC0
>> >>> >> (5c4b985f89c99cc8b0f8515a4097c811a0848835)
>> >>> >>
>> >>> >> hbase-2.0.0-alpha4 is our fourth alpha release along our march
>> toward
>> >>> >> hbase-2.0.0. It includes all that was in previous alphas (new
>> >>> assignment
>> >>> >> manager, offheap read/write path, in-memory compactions, etc.), but
>> >>> had a
>> >>> >> focus on "Coprocessor Fixup": We no longer pass Coprocessors
>> >>> >> InterfaceAudience.Private parameters and we cut down on the access
>> and
>> >>> >> ability to influence hbase core processing (See [2] on why the
>> radical
>> >>> >> changes in Coprocessor Interface). If you are a Coprocessor
>> developer
>> >>> or
>> >>> >> have Coprocessors to deploy on hbase-2.0.0, we need to hear about
>> your
>> >>> >> experience now before we make an hbase-2.0.0 beta.
>> >>> >>
>> >>> >> hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production
>> >>> preview of
>> >>> >> what hbase-2.0.0 will look like. It is meant for devs and
>> >>> downstreamers to
>> >>> >> test drive and flag us early if we messed up anything ahead of our
>> >>> rolling
>> >>> >> GAs.
>> >>> >>
>> >>> >> 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].
>> 2.0.0-beta-1
>> >>> >> will
>> >>> >> be our next release. Its theme is the "Finishing up 2.0.0" release.
>> >>> Here
>> >>> >> is
>> >>> >> the list of what we have targeted for beta-1 [5]. Check it out.
>> Shout
>> >>> if
>> >>> >> there is anything missing. We may do a 2.0.0-beta-2 if a need.
>> We'll
>> >>> see.
>> >>> >>
>> >>> >> Please take this alpha for a spin especially if you are a
>> Coprocessor
>> >>> >> developer or have a Coprocessor you want to deploy on hbase-2.0.0.
>> >>> Please
>> >>> >> vote on whether it ok to put out this RC as our first alpha (bar is
>> >>> low
>> >>> >> for
>> >>> >> an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE
>> be
>> >>> open
>> >>> >> for 72 hours (Saturday)
>> >>> >>
>> >>> >> Thanks,
>> >>> >> Your 2.0.0 Release Manager
>> >>> >>
>> >>> >> 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
>> >>> >> 2. Why CPs are Incompatible:
>> >>> >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
>> >>> >> Eu_ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
>> >>> >> 3. https://goo.gl/scYjJr
>> >>> >> 4. https://goo.gl/tMHkYS
>> >>> >> 5. https://issues.apache.org/jira/projects/HBASE/versions/12340861
>> >>> >> 6.
>> >>> >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
>> >>> >> Eu_ktczrlKHK8N4SZzs/
>> >>> >>
>> >>> >>
>> >>>
>> >>
>> >>
>> >
>>
>
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Stack <st...@duboce.net>.
Thank you Guanghao. Let me see about getting the issue backported. Are you
a +/- 1 sir? Thanks for the digging.
S
On Thu, Nov 2, 2017 at 1:31 AM, Guanghao Zhang <zg...@gmail.com> wrote:
> There is already a issue HBASE-18705
> <https://issues.apache.org/jira/browse/HBASE-18705> about this problem.
> But
> it was only pushed to master branch.
>
> 2017-11-02 15:21 GMT+08:00 Guanghao Zhang <zg...@gmail.com>:
>
> > Updated f="${HBASE_HOME}/target/cached_classpath.txt" to
> > f="${HBASE_HOME}/hbase-build-configuration/target/cached_classpath.txt".
> > Then start hbase success. Anything wrong for my environment?
> >
> > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> > 2015-11-11T00:41:47+08:00)
> > Maven home: /opt/soft/apache-maven-3.3.9
> > Java version: 1.8.0_131, vendor: Oracle Corporation
> > Java home: /opt/soft/jdk1.8.0_131/jre
> > Default locale: zh_CN, platform encoding: UTF-8
> > OS name: "linux", version: "3.13.0-46-generic", arch: "amd64", family:
> > "unix"
> >
> >
> >
> > 2017-11-02 15:18 GMT+08:00 Guanghao Zhang <zg...@gmail.com>:
> >
> >> Download src and build pass.
> >> But when start-hbase.sh, I found the master can't start in standalone
> >> mode.
> >>
> >> ```
> >> running master, logging to /home/hao/open_source/hbase_re
> >> lease/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-master-Xiaohao.out
> >> As this is a development environment, we need
> >> /home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/
> bin/../target/cached_classpath.txt
> >> to be generated from maven (command: mvn install -DskipTests)
> >> : running regionserver, logging to /home/hao/open_source/hbase_re
> >> lease/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-regionserver-Xiaohao.out
> >> : As this is a development environment, we need
> >> /home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/
> bin/../target/cached_classpath.txt
> >> to be generated from maven (command: mvn install -DskipTests)
> >> ```
> >>
> >> And I try mvn install -DskipTests, and found the cached_classpath.txt
> >> in hbase-build-configuration/target/cached_classpath.txt. The path is
> >> wrong in bin/hbase. So I update f="${HBASE_HOME}/hbase-
> >> build-configuration/target/cached_classpath.txt" in bin/hbase, then
> >> start master success. File a jira for this?
> >>
> >> 2017-11-02 14:02 GMT+08:00 Stack <st...@duboce.net>:
> >>
> >>> On Wed, Nov 1, 2017 at 9:41 PM, Josh Elser <el...@apache.org> wrote:
> >>>
> >>> > +1 (binding)
> >>> >
> >>> > * UT's mostly ok. Exceptions being: TestNamespacesInstanceResource,
> >>> > TestReplicaWithCluster, TestReplicationAdmin, and
> >>> TestRegionServerHostname
> >>> > consistently fail for me locally (commented on HBASE-19147)
> >>> > * xsum+sigs OK
> >>> > * can build from source
> >>> > * src archive contents looks OK (exception below)
> >>> > * Built, deployed locally, ran PE without issue
> >>> >
> >>> >
> >>> Excellent. Thanks Josh.
> >>>
> >>>
> >>>
> >>> > I stumbled across src/main/site/resources/repo/o
> >>> > rg/apache/maven/skins/maven-fluido-skin/1.5-HBASE/maven-flui
> >>> do-skin-1.5-HBASE.jar
> >>> > in the source archive which was introduced via
> >>> > https://issues.apache.org/jira/browse/HBASE-14785. Best as I can
> tell,
> >>> > this was a hack to work around a fluido-skin bug and we should be
> able
> >>> to
> >>> > remove it now. Not sure if we've already discussed the
> >>> > binary-file-in-src-release concerns of this previously or not...
> >>> >
> >>> >
> >>> Sean noted this in an alpha-3 VOTE.
> >>>
> >>> I came across it yesterday.
> >>>
> >>> What you reckon Misty (if you looking at this?) If you remember, what
> >>> would
> >>> I look for?
> >>>
> >>> Thanks,
> >>> St.Ack
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> > - Josh
> >>> >
> >>> >
> >>> > On 11/1/17 10:17 AM, Stack wrote:
> >>> >
> >>> >> The first release candidate for HBase 2.0.0-alpha4 is up at:
> >>> >>
> >>> >> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alp
> >>> ha4RC0/
> >>> >>
> >>> >> Maven artifacts are available from a staging directory here:
> >>> >>
> >>> >> https://repository.apache.org/content/repositories/orgapache
> >>> hbase-1178
> >>> >>
> >>> >> All was signed with my key at 8ACC93D2 [1]
> >>> >>
> >>> >> I tagged the RC as 2.0.0-alpha4RC0
> >>> >> (5c4b985f89c99cc8b0f8515a4097c811a0848835)
> >>> >>
> >>> >> hbase-2.0.0-alpha4 is our fourth alpha release along our march
> toward
> >>> >> hbase-2.0.0. It includes all that was in previous alphas (new
> >>> assignment
> >>> >> manager, offheap read/write path, in-memory compactions, etc.), but
> >>> had a
> >>> >> focus on "Coprocessor Fixup": We no longer pass Coprocessors
> >>> >> InterfaceAudience.Private parameters and we cut down on the access
> and
> >>> >> ability to influence hbase core processing (See [2] on why the
> radical
> >>> >> changes in Coprocessor Interface). If you are a Coprocessor
> developer
> >>> or
> >>> >> have Coprocessors to deploy on hbase-2.0.0, we need to hear about
> your
> >>> >> experience now before we make an hbase-2.0.0 beta.
> >>> >>
> >>> >> hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production
> >>> preview of
> >>> >> what hbase-2.0.0 will look like. It is meant for devs and
> >>> downstreamers to
> >>> >> test drive and flag us early if we messed up anything ahead of our
> >>> rolling
> >>> >> GAs.
> >>> >>
> >>> >> 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].
> 2.0.0-beta-1
> >>> >> will
> >>> >> be our next release. Its theme is the "Finishing up 2.0.0" release.
> >>> Here
> >>> >> is
> >>> >> the list of what we have targeted for beta-1 [5]. Check it out.
> Shout
> >>> if
> >>> >> there is anything missing. We may do a 2.0.0-beta-2 if a need. We'll
> >>> see.
> >>> >>
> >>> >> Please take this alpha for a spin especially if you are a
> Coprocessor
> >>> >> developer or have a Coprocessor you want to deploy on hbase-2.0.0.
> >>> Please
> >>> >> vote on whether it ok to put out this RC as our first alpha (bar is
> >>> low
> >>> >> for
> >>> >> an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE
> be
> >>> open
> >>> >> for 72 hours (Saturday)
> >>> >>
> >>> >> Thanks,
> >>> >> Your 2.0.0 Release Manager
> >>> >>
> >>> >> 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> >>> >> 2. Why CPs are Incompatible:
> >>> >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
> >>> >> Eu_ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> >>> >> 3. https://goo.gl/scYjJr
> >>> >> 4. https://goo.gl/tMHkYS
> >>> >> 5. https://issues.apache.org/jira/projects/HBASE/versions/12340861
> >>> >> 6.
> >>> >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
> >>> >> Eu_ktczrlKHK8N4SZzs/
> >>> >>
> >>> >>
> >>>
> >>
> >>
> >
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Guanghao Zhang <zg...@gmail.com>.
There is already a issue HBASE-18705
<https://issues.apache.org/jira/browse/HBASE-18705> about this problem. But
it was only pushed to master branch.
2017-11-02 15:21 GMT+08:00 Guanghao Zhang <zg...@gmail.com>:
> Updated f="${HBASE_HOME}/target/cached_classpath.txt" to
> f="${HBASE_HOME}/hbase-build-configuration/target/cached_classpath.txt".
> Then start hbase success. Anything wrong for my environment?
>
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-11T00:41:47+08:00)
> Maven home: /opt/soft/apache-maven-3.3.9
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home: /opt/soft/jdk1.8.0_131/jre
> Default locale: zh_CN, platform encoding: UTF-8
> OS name: "linux", version: "3.13.0-46-generic", arch: "amd64", family:
> "unix"
>
>
>
> 2017-11-02 15:18 GMT+08:00 Guanghao Zhang <zg...@gmail.com>:
>
>> Download src and build pass.
>> But when start-hbase.sh, I found the master can't start in standalone
>> mode.
>>
>> ```
>> running master, logging to /home/hao/open_source/hbase_re
>> lease/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-master-Xiaohao.out
>> As this is a development environment, we need
>> /home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/bin/../target/cached_classpath.txt
>> to be generated from maven (command: mvn install -DskipTests)
>> : running regionserver, logging to /home/hao/open_source/hbase_re
>> lease/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-regionserver-Xiaohao.out
>> : As this is a development environment, we need
>> /home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/bin/../target/cached_classpath.txt
>> to be generated from maven (command: mvn install -DskipTests)
>> ```
>>
>> And I try mvn install -DskipTests, and found the cached_classpath.txt
>> in hbase-build-configuration/target/cached_classpath.txt. The path is
>> wrong in bin/hbase. So I update f="${HBASE_HOME}/hbase-
>> build-configuration/target/cached_classpath.txt" in bin/hbase, then
>> start master success. File a jira for this?
>>
>> 2017-11-02 14:02 GMT+08:00 Stack <st...@duboce.net>:
>>
>>> On Wed, Nov 1, 2017 at 9:41 PM, Josh Elser <el...@apache.org> wrote:
>>>
>>> > +1 (binding)
>>> >
>>> > * UT's mostly ok. Exceptions being: TestNamespacesInstanceResource,
>>> > TestReplicaWithCluster, TestReplicationAdmin, and
>>> TestRegionServerHostname
>>> > consistently fail for me locally (commented on HBASE-19147)
>>> > * xsum+sigs OK
>>> > * can build from source
>>> > * src archive contents looks OK (exception below)
>>> > * Built, deployed locally, ran PE without issue
>>> >
>>> >
>>> Excellent. Thanks Josh.
>>>
>>>
>>>
>>> > I stumbled across src/main/site/resources/repo/o
>>> > rg/apache/maven/skins/maven-fluido-skin/1.5-HBASE/maven-flui
>>> do-skin-1.5-HBASE.jar
>>> > in the source archive which was introduced via
>>> > https://issues.apache.org/jira/browse/HBASE-14785. Best as I can tell,
>>> > this was a hack to work around a fluido-skin bug and we should be able
>>> to
>>> > remove it now. Not sure if we've already discussed the
>>> > binary-file-in-src-release concerns of this previously or not...
>>> >
>>> >
>>> Sean noted this in an alpha-3 VOTE.
>>>
>>> I came across it yesterday.
>>>
>>> What you reckon Misty (if you looking at this?) If you remember, what
>>> would
>>> I look for?
>>>
>>> Thanks,
>>> St.Ack
>>>
>>>
>>>
>>>
>>>
>>> > - Josh
>>> >
>>> >
>>> > On 11/1/17 10:17 AM, Stack wrote:
>>> >
>>> >> The first release candidate for HBase 2.0.0-alpha4 is up at:
>>> >>
>>> >> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alp
>>> ha4RC0/
>>> >>
>>> >> Maven artifacts are available from a staging directory here:
>>> >>
>>> >> https://repository.apache.org/content/repositories/orgapache
>>> hbase-1178
>>> >>
>>> >> All was signed with my key at 8ACC93D2 [1]
>>> >>
>>> >> I tagged the RC as 2.0.0-alpha4RC0
>>> >> (5c4b985f89c99cc8b0f8515a4097c811a0848835)
>>> >>
>>> >> hbase-2.0.0-alpha4 is our fourth alpha release along our march toward
>>> >> hbase-2.0.0. It includes all that was in previous alphas (new
>>> assignment
>>> >> manager, offheap read/write path, in-memory compactions, etc.), but
>>> had a
>>> >> focus on "Coprocessor Fixup": We no longer pass Coprocessors
>>> >> InterfaceAudience.Private parameters and we cut down on the access and
>>> >> ability to influence hbase core processing (See [2] on why the radical
>>> >> changes in Coprocessor Interface). If you are a Coprocessor developer
>>> or
>>> >> have Coprocessors to deploy on hbase-2.0.0, we need to hear about your
>>> >> experience now before we make an hbase-2.0.0 beta.
>>> >>
>>> >> hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production
>>> preview of
>>> >> what hbase-2.0.0 will look like. It is meant for devs and
>>> downstreamers to
>>> >> test drive and flag us early if we messed up anything ahead of our
>>> rolling
>>> >> GAs.
>>> >>
>>> >> 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]. 2.0.0-beta-1
>>> >> will
>>> >> be our next release. Its theme is the "Finishing up 2.0.0" release.
>>> Here
>>> >> is
>>> >> the list of what we have targeted for beta-1 [5]. Check it out. Shout
>>> if
>>> >> there is anything missing. We may do a 2.0.0-beta-2 if a need. We'll
>>> see.
>>> >>
>>> >> Please take this alpha for a spin especially if you are a Coprocessor
>>> >> developer or have a Coprocessor you want to deploy on hbase-2.0.0.
>>> Please
>>> >> vote on whether it ok to put out this RC as our first alpha (bar is
>>> low
>>> >> for
>>> >> an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE be
>>> open
>>> >> for 72 hours (Saturday)
>>> >>
>>> >> Thanks,
>>> >> Your 2.0.0 Release Manager
>>> >>
>>> >> 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
>>> >> 2. Why CPs are Incompatible:
>>> >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
>>> >> Eu_ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
>>> >> 3. https://goo.gl/scYjJr
>>> >> 4. https://goo.gl/tMHkYS
>>> >> 5. https://issues.apache.org/jira/projects/HBASE/versions/12340861
>>> >> 6.
>>> >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
>>> >> Eu_ktczrlKHK8N4SZzs/
>>> >>
>>> >>
>>>
>>
>>
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Guanghao Zhang <zg...@gmail.com>.
Updated f="${HBASE_HOME}/target/cached_classpath.txt" to
f="${HBASE_HOME}/hbase-build-configuration/target/cached_classpath.txt".
Then start hbase success. Anything wrong for my environment?
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-11T00:41:47+08:00)
Maven home: /opt/soft/apache-maven-3.3.9
Java version: 1.8.0_131, vendor: Oracle Corporation
Java home: /opt/soft/jdk1.8.0_131/jre
Default locale: zh_CN, platform encoding: UTF-8
OS name: "linux", version: "3.13.0-46-generic", arch: "amd64", family:
"unix"
2017-11-02 15:18 GMT+08:00 Guanghao Zhang <zg...@gmail.com>:
> Download src and build pass.
> But when start-hbase.sh, I found the master can't start in standalone mode.
>
> ```
> running master, logging to /home/hao/open_source/hbase_
> release/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-master-Xiaohao.out
> As this is a development environment, we need /home/hao/open_source/hbase_
> release/hbase-2.0.0-alpha4/bin/../target/cached_classpath.txt to be
> generated from maven (command: mvn install -DskipTests)
> : running regionserver, logging to /home/hao/open_source/hbase_
> release/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-regionserver-Xiaohao.out
> : As this is a development environment, we need
> /home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/
> bin/../target/cached_classpath.txt to be generated from maven (command:
> mvn install -DskipTests)
> ```
>
> And I try mvn install -DskipTests, and found the cached_classpath.txt
> in hbase-build-configuration/target/cached_classpath.txt. The path is
> wrong in bin/hbase. So I update f="${HBASE_HOME}/hbase-
> build-configuration/target/cached_classpath.txt" in bin/hbase, then start
> master success. File a jira for this?
>
> 2017-11-02 14:02 GMT+08:00 Stack <st...@duboce.net>:
>
>> On Wed, Nov 1, 2017 at 9:41 PM, Josh Elser <el...@apache.org> wrote:
>>
>> > +1 (binding)
>> >
>> > * UT's mostly ok. Exceptions being: TestNamespacesInstanceResource,
>> > TestReplicaWithCluster, TestReplicationAdmin, and
>> TestRegionServerHostname
>> > consistently fail for me locally (commented on HBASE-19147)
>> > * xsum+sigs OK
>> > * can build from source
>> > * src archive contents looks OK (exception below)
>> > * Built, deployed locally, ran PE without issue
>> >
>> >
>> Excellent. Thanks Josh.
>>
>>
>>
>> > I stumbled across src/main/site/resources/repo/o
>> > rg/apache/maven/skins/maven-fluido-skin/1.5-HBASE/maven-flui
>> do-skin-1.5-HBASE.jar
>> > in the source archive which was introduced via
>> > https://issues.apache.org/jira/browse/HBASE-14785. Best as I can tell,
>> > this was a hack to work around a fluido-skin bug and we should be able
>> to
>> > remove it now. Not sure if we've already discussed the
>> > binary-file-in-src-release concerns of this previously or not...
>> >
>> >
>> Sean noted this in an alpha-3 VOTE.
>>
>> I came across it yesterday.
>>
>> What you reckon Misty (if you looking at this?) If you remember, what
>> would
>> I look for?
>>
>> Thanks,
>> St.Ack
>>
>>
>>
>>
>>
>> > - Josh
>> >
>> >
>> > On 11/1/17 10:17 AM, Stack wrote:
>> >
>> >> The first release candidate for HBase 2.0.0-alpha4 is up at:
>> >>
>> >> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha4RC0/
>> >>
>> >> Maven artifacts are available from a staging directory here:
>> >>
>> >> https://repository.apache.org/content/repositories/orgapache
>> hbase-1178
>> >>
>> >> All was signed with my key at 8ACC93D2 [1]
>> >>
>> >> I tagged the RC as 2.0.0-alpha4RC0
>> >> (5c4b985f89c99cc8b0f8515a4097c811a0848835)
>> >>
>> >> hbase-2.0.0-alpha4 is our fourth alpha release along our march toward
>> >> hbase-2.0.0. It includes all that was in previous alphas (new
>> assignment
>> >> manager, offheap read/write path, in-memory compactions, etc.), but
>> had a
>> >> focus on "Coprocessor Fixup": We no longer pass Coprocessors
>> >> InterfaceAudience.Private parameters and we cut down on the access and
>> >> ability to influence hbase core processing (See [2] on why the radical
>> >> changes in Coprocessor Interface). If you are a Coprocessor developer
>> or
>> >> have Coprocessors to deploy on hbase-2.0.0, we need to hear about your
>> >> experience now before we make an hbase-2.0.0 beta.
>> >>
>> >> hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production
>> preview of
>> >> what hbase-2.0.0 will look like. It is meant for devs and
>> downstreamers to
>> >> test drive and flag us early if we messed up anything ahead of our
>> rolling
>> >> GAs.
>> >>
>> >> 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]. 2.0.0-beta-1
>> >> will
>> >> be our next release. Its theme is the "Finishing up 2.0.0" release.
>> Here
>> >> is
>> >> the list of what we have targeted for beta-1 [5]. Check it out. Shout
>> if
>> >> there is anything missing. We may do a 2.0.0-beta-2 if a need. We'll
>> see.
>> >>
>> >> Please take this alpha for a spin especially if you are a Coprocessor
>> >> developer or have a Coprocessor you want to deploy on hbase-2.0.0.
>> Please
>> >> vote on whether it ok to put out this RC as our first alpha (bar is low
>> >> for
>> >> an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE be
>> open
>> >> for 72 hours (Saturday)
>> >>
>> >> Thanks,
>> >> Your 2.0.0 Release Manager
>> >>
>> >> 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
>> >> 2. Why CPs are Incompatible:
>> >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
>> >> Eu_ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
>> >> 3. https://goo.gl/scYjJr
>> >> 4. https://goo.gl/tMHkYS
>> >> 5. https://issues.apache.org/jira/projects/HBASE/versions/12340861
>> >> 6.
>> >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
>> >> Eu_ktczrlKHK8N4SZzs/
>> >>
>> >>
>>
>
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Guanghao Zhang <zg...@gmail.com>.
Download src and build pass.
But when start-hbase.sh, I found the master can't start in standalone mode.
```
running master, logging to
/home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-master-Xiaohao.out
As this is a development environment, we need
/home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/bin/../target/cached_classpath.txt
to be generated from maven (command: mvn install -DskipTests)
: running regionserver, logging to
/home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/bin/../logs/hbase-hao-regionserver-Xiaohao.out
: As this is a development environment, we need
/home/hao/open_source/hbase_release/hbase-2.0.0-alpha4/bin/../target/cached_classpath.txt
to be generated from maven (command: mvn install -DskipTests)
```
And I try mvn install -DskipTests, and found the cached_classpath.txt
in hbase-build-configuration/target/cached_classpath.txt. The path is wrong
in bin/hbase. So I
update f="${HBASE_HOME}/hbase-build-configuration/target/cached_classpath.txt"
in bin/hbase, then start master success. File a jira for this?
2017-11-02 14:02 GMT+08:00 Stack <st...@duboce.net>:
> On Wed, Nov 1, 2017 at 9:41 PM, Josh Elser <el...@apache.org> wrote:
>
> > +1 (binding)
> >
> > * UT's mostly ok. Exceptions being: TestNamespacesInstanceResource,
> > TestReplicaWithCluster, TestReplicationAdmin, and
> TestRegionServerHostname
> > consistently fail for me locally (commented on HBASE-19147)
> > * xsum+sigs OK
> > * can build from source
> > * src archive contents looks OK (exception below)
> > * Built, deployed locally, ran PE without issue
> >
> >
> Excellent. Thanks Josh.
>
>
>
> > I stumbled across src/main/site/resources/repo/o
> > rg/apache/maven/skins/maven-fluido-skin/1.5-HBASE/maven-
> fluido-skin-1.5-HBASE.jar
> > in the source archive which was introduced via
> > https://issues.apache.org/jira/browse/HBASE-14785. Best as I can tell,
> > this was a hack to work around a fluido-skin bug and we should be able to
> > remove it now. Not sure if we've already discussed the
> > binary-file-in-src-release concerns of this previously or not...
> >
> >
> Sean noted this in an alpha-3 VOTE.
>
> I came across it yesterday.
>
> What you reckon Misty (if you looking at this?) If you remember, what would
> I look for?
>
> Thanks,
> St.Ack
>
>
>
>
>
> > - Josh
> >
> >
> > On 11/1/17 10:17 AM, Stack wrote:
> >
> >> The first release candidate for HBase 2.0.0-alpha4 is up at:
> >>
> >> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha4RC0/
> >>
> >> Maven artifacts are available from a staging directory here:
> >>
> >> https://repository.apache.org/content/repositories/
> orgapachehbase-1178
> >>
> >> All was signed with my key at 8ACC93D2 [1]
> >>
> >> I tagged the RC as 2.0.0-alpha4RC0
> >> (5c4b985f89c99cc8b0f8515a4097c811a0848835)
> >>
> >> hbase-2.0.0-alpha4 is our fourth alpha release along our march toward
> >> hbase-2.0.0. It includes all that was in previous alphas (new assignment
> >> manager, offheap read/write path, in-memory compactions, etc.), but had
> a
> >> focus on "Coprocessor Fixup": We no longer pass Coprocessors
> >> InterfaceAudience.Private parameters and we cut down on the access and
> >> ability to influence hbase core processing (See [2] on why the radical
> >> changes in Coprocessor Interface). If you are a Coprocessor developer or
> >> have Coprocessors to deploy on hbase-2.0.0, we need to hear about your
> >> experience now before we make an hbase-2.0.0 beta.
> >>
> >> hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production preview
> of
> >> what hbase-2.0.0 will look like. It is meant for devs and downstreamers
> to
> >> test drive and flag us early if we messed up anything ahead of our
> rolling
> >> GAs.
> >>
> >> 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]. 2.0.0-beta-1
> >> will
> >> be our next release. Its theme is the "Finishing up 2.0.0" release. Here
> >> is
> >> the list of what we have targeted for beta-1 [5]. Check it out. Shout if
> >> there is anything missing. We may do a 2.0.0-beta-2 if a need. We'll
> see.
> >>
> >> Please take this alpha for a spin especially if you are a Coprocessor
> >> developer or have a Coprocessor you want to deploy on hbase-2.0.0.
> Please
> >> vote on whether it ok to put out this RC as our first alpha (bar is low
> >> for
> >> an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE be
> open
> >> for 72 hours (Saturday)
> >>
> >> Thanks,
> >> Your 2.0.0 Release Manager
> >>
> >> 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> >> 2. Why CPs are Incompatible:
> >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
> >> Eu_ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> >> 3. https://goo.gl/scYjJr
> >> 4. https://goo.gl/tMHkYS
> >> 5. https://issues.apache.org/jira/projects/HBASE/versions/12340861
> >> 6.
> >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
> >> Eu_ktczrlKHK8N4SZzs/
> >>
> >>
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Stack <st...@duboce.net>.
On Wed, Nov 1, 2017 at 9:41 PM, Josh Elser <el...@apache.org> wrote:
> +1 (binding)
>
> * UT's mostly ok. Exceptions being: TestNamespacesInstanceResource,
> TestReplicaWithCluster, TestReplicationAdmin, and TestRegionServerHostname
> consistently fail for me locally (commented on HBASE-19147)
> * xsum+sigs OK
> * can build from source
> * src archive contents looks OK (exception below)
> * Built, deployed locally, ran PE without issue
>
>
Excellent. Thanks Josh.
> I stumbled across src/main/site/resources/repo/o
> rg/apache/maven/skins/maven-fluido-skin/1.5-HBASE/maven-fluido-skin-1.5-HBASE.jar
> in the source archive which was introduced via
> https://issues.apache.org/jira/browse/HBASE-14785. Best as I can tell,
> this was a hack to work around a fluido-skin bug and we should be able to
> remove it now. Not sure if we've already discussed the
> binary-file-in-src-release concerns of this previously or not...
>
>
Sean noted this in an alpha-3 VOTE.
I came across it yesterday.
What you reckon Misty (if you looking at this?) If you remember, what would
I look for?
Thanks,
St.Ack
> - Josh
>
>
> On 11/1/17 10:17 AM, Stack wrote:
>
>> The first release candidate for HBase 2.0.0-alpha4 is up at:
>>
>> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha4RC0/
>>
>> Maven artifacts are available from a staging directory here:
>>
>> https://repository.apache.org/content/repositories/orgapachehbase-1178
>>
>> All was signed with my key at 8ACC93D2 [1]
>>
>> I tagged the RC as 2.0.0-alpha4RC0
>> (5c4b985f89c99cc8b0f8515a4097c811a0848835)
>>
>> hbase-2.0.0-alpha4 is our fourth alpha release along our march toward
>> hbase-2.0.0. It includes all that was in previous alphas (new assignment
>> manager, offheap read/write path, in-memory compactions, etc.), but had a
>> focus on "Coprocessor Fixup": We no longer pass Coprocessors
>> InterfaceAudience.Private parameters and we cut down on the access and
>> ability to influence hbase core processing (See [2] on why the radical
>> changes in Coprocessor Interface). If you are a Coprocessor developer or
>> have Coprocessors to deploy on hbase-2.0.0, we need to hear about your
>> experience now before we make an hbase-2.0.0 beta.
>>
>> hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production preview of
>> what hbase-2.0.0 will look like. It is meant for devs and downstreamers to
>> test drive and flag us early if we messed up anything ahead of our rolling
>> GAs.
>>
>> 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]. 2.0.0-beta-1
>> will
>> be our next release. Its theme is the "Finishing up 2.0.0" release. Here
>> is
>> the list of what we have targeted for beta-1 [5]. Check it out. Shout if
>> there is anything missing. We may do a 2.0.0-beta-2 if a need. We'll see.
>>
>> Please take this alpha for a spin especially if you are a Coprocessor
>> developer or have a Coprocessor you want to deploy on hbase-2.0.0. Please
>> vote on whether it ok to put out this RC as our first alpha (bar is low
>> for
>> an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE be open
>> for 72 hours (Saturday)
>>
>> Thanks,
>> Your 2.0.0 Release Manager
>>
>> 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
>> 2. Why CPs are Incompatible:
>> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
>> Eu_ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
>> 3. https://goo.gl/scYjJr
>> 4. https://goo.gl/tMHkYS
>> 5. https://issues.apache.org/jira/projects/HBASE/versions/12340861
>> 6.
>> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9i
>> Eu_ktczrlKHK8N4SZzs/
>>
>>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Josh Elser <el...@apache.org>.
+1 (binding)
* UT's mostly ok. Exceptions being: TestNamespacesInstanceResource,
TestReplicaWithCluster, TestReplicationAdmin, and
TestRegionServerHostname consistently fail for me locally (commented on
HBASE-19147)
* xsum+sigs OK
* can build from source
* src archive contents looks OK (exception below)
* Built, deployed locally, ran PE without issue
I stumbled across
src/main/site/resources/repo/org/apache/maven/skins/maven-fluido-skin/1.5-HBASE/maven-fluido-skin-1.5-HBASE.jar
in the source archive which was introduced via
https://issues.apache.org/jira/browse/HBASE-14785. Best as I can tell,
this was a hack to work around a fluido-skin bug and we should be able
to remove it now. Not sure if we've already discussed the
binary-file-in-src-release concerns of this previously or not...
- Josh
On 11/1/17 10:17 AM, Stack wrote:
> The first release candidate for HBase 2.0.0-alpha4 is up at:
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha4RC0/
>
> Maven artifacts are available from a staging directory here:
>
> https://repository.apache.org/content/repositories/orgapachehbase-1178
>
> All was signed with my key at 8ACC93D2 [1]
>
> I tagged the RC as 2.0.0-alpha4RC0
> (5c4b985f89c99cc8b0f8515a4097c811a0848835)
>
> hbase-2.0.0-alpha4 is our fourth alpha release along our march toward
> hbase-2.0.0. It includes all that was in previous alphas (new assignment
> manager, offheap read/write path, in-memory compactions, etc.), but had a
> focus on "Coprocessor Fixup": We no longer pass Coprocessors
> InterfaceAudience.Private parameters and we cut down on the access and
> ability to influence hbase core processing (See [2] on why the radical
> changes in Coprocessor Interface). If you are a Coprocessor developer or
> have Coprocessors to deploy on hbase-2.0.0, we need to hear about your
> experience now before we make an hbase-2.0.0 beta.
>
> hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production preview of
> what hbase-2.0.0 will look like. It is meant for devs and downstreamers to
> test drive and flag us early if we messed up anything ahead of our rolling
> GAs.
>
> 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]. 2.0.0-beta-1 will
> be our next release. Its theme is the "Finishing up 2.0.0" release. Here is
> the list of what we have targeted for beta-1 [5]. Check it out. Shout if
> there is anything missing. We may do a 2.0.0-beta-2 if a need. We'll see.
>
> Please take this alpha for a spin especially if you are a Coprocessor
> developer or have a Coprocessor you want to deploy on hbase-2.0.0. Please
> vote on whether it ok to put out this RC as our first alpha (bar is low for
> an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE be open
> for 72 hours (Saturday)
>
> Thanks,
> Your 2.0.0 Release Manager
>
> 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> 2. Why CPs are Incompatible:
> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> 3. https://goo.gl/scYjJr
> 4. https://goo.gl/tMHkYS
> 5. https://issues.apache.org/jira/projects/HBASE/versions/12340861
> 6.
> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_ktczrlKHK8N4SZzs/
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Umesh Agashe <ua...@cloudera.com>.
+1
Questions/ concerns:
* Staging directory naming convention changed between alpha-3 and alpha-4:
hbase-2.0.0-alpha-3RC0/
hbase-2.0.0-alpha4RC0/
* .gitignore be included in source bundle, can it be dropped?
Verifications:
* Download the src tarball: good.
* Verify the checksums and signature: good.
* Extract and build from source. openjdk version "1.8.0_131": good.
* Rat check: good.
* Download the bin tarball: good.
* Verify the checksums and signature: good.
* Extract it and verify layout visually: good.
* Start a local instance. Run the 'hbase shell' with some basic table commands:
good.
* Run ltt with 10 million rows and 2 columns/ row: good.
* Inspect logs: good.
On Wed, Nov 1, 2017 at 7:17 AM, Stack <st...@duboce.net> wrote:
> The first release candidate for HBase 2.0.0-alpha4 is up at:
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha4RC0/
>
> Maven artifacts are available from a staging directory here:
>
> https://repository.apache.org/content/repositories/orgapachehbase-1178
>
> All was signed with my key at 8ACC93D2 [1]
>
> I tagged the RC as 2.0.0-alpha4RC0
> (5c4b985f89c99cc8b0f8515a4097c811a0848835)
>
> hbase-2.0.0-alpha4 is our fourth alpha release along our march toward
> hbase-2.0.0. It includes all that was in previous alphas (new assignment
> manager, offheap read/write path, in-memory compactions, etc.), but had a
> focus on "Coprocessor Fixup": We no longer pass Coprocessors
> InterfaceAudience.Private parameters and we cut down on the access and
> ability to influence hbase core processing (See [2] on why the radical
> changes in Coprocessor Interface). If you are a Coprocessor developer or
> have Coprocessors to deploy on hbase-2.0.0, we need to hear about your
> experience now before we make an hbase-2.0.0 beta.
>
> hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production preview of
> what hbase-2.0.0 will look like. It is meant for devs and downstreamers to
> test drive and flag us early if we messed up anything ahead of our rolling
> GAs.
>
> 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]. 2.0.0-beta-1 will
> be our next release. Its theme is the "Finishing up 2.0.0" release. Here is
> the list of what we have targeted for beta-1 [5]. Check it out. Shout if
> there is anything missing. We may do a 2.0.0-beta-2 if a need. We'll see.
>
> Please take this alpha for a spin especially if you are a Coprocessor
> developer or have a Coprocessor you want to deploy on hbase-2.0.0. Please
> vote on whether it ok to put out this RC as our first alpha (bar is low for
> an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE be open
> for 72 hours (Saturday)
>
> Thanks,
> Your 2.0.0 Release Manager
>
> 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> 2. Why CPs are Incompatible:
> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> 3. https://goo.gl/scYjJr
> 4. https://goo.gl/tMHkYS
> 5. https://issues.apache.org/jira/projects/HBASE/versions/12340861
> 6.
> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> ktczrlKHK8N4SZzs/
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by ramkrishna vasudevan <ra...@gmail.com>.
Done.
https://issues.apache.org/jira/browse/HBASE-19221
Thanks Stack.
Regards
Ram
On Thu, Nov 9, 2017 at 11:36 AM, Stack <st...@duboce.net> wrote:
> Thats a dirty rotten bug I'd say. File blocker on beta-1. Thanks Ram.
> S
>
> On Wed, Nov 8, 2017 at 8:56 PM, ramkrishna vasudevan <
> ramkrishna.s.vasudevan@gmail.com> wrote:
>
> > Hi Stack
> > I tried running some IT test cases using the alpha-4 RC. I found this
> issue
> > Exception in thread "main" java.lang.NoClassDefFoundError:
> > org/hamcrest/SelfDescribing
> > at java.lang.ClassLoader.defineClass1(Native Method)
> > at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
> > at
> > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> > at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> > at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> > at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> > at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> > at java.security.AccessController.doPrivileged(Native Method)
> > at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> >
> > ...
> > at
> > org.apache.hadoop.hbase.IntegrationTestsDriver.doWork(
> > IntegrationTestsDriver.java:111)
> > at
> > org.apache.hadoop.hbase.util.AbstractHBaseTool.run(
> > AbstractHBaseTool.java:154)
> > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> > at
> > org.apache.hadoop.hbase.IntegrationTestsDriver.main(
> > IntegrationTestsDriver.java:47)
> >
> > The same when run against latest master it runs without any issues. I
> have
> > not dug in here but wanted to just mention it here so that we could fix
> it
> > in beta-1?
> >
> > Regards
> > Ram
> >
> > On Sun, Nov 5, 2017 at 3:03 AM, Jean-Marc Spaggiari <
> > jean-marc@spaggiari.org
> > > wrote:
> >
> > > Thanks for your reply Stack. I will get ready to test the next version.
> > > Excited to see 2.0 coming out!!!!
> > >
> > > 2017-11-04 14:44 GMT-04:00 Stack <st...@duboce.net>:
> > >
> > > > On Sat, Nov 4, 2017 at 1:45 AM, Jean-Marc Spaggiari <
> > > > jean-marc@spaggiari.org
> > > > > wrote:
> > > >
> > > > > Folks, are you able to run the tests?
> > > > >
> > > > > I'm trying to run this:
> > > > >
> > > > > mvn test -P runAllTests -Dsurefire.secondPartThreadCount=2
> > > > > -Dtest.build.data.basedirectory=/ram4G
> > > > >
> > > > >
> > > > > But I'm not able to get it running completely. It always fails
> > > somewhere,
> > > > > never in the same place. How are you running the tests, if you are?
> > > > >
> > > > > Else:
> > > > > MD5 and SHA files correct for both Binary and Source
> > > > > *changes.txt file doesn't seems correct. Missing last versions*
> > > > > *checkstyle.html doesn't seems to be accurate. Reports 0 files.*
> > > > > Documetation ok.
> > > > >
> > > > > Will run more tests later when I can get runAllTests pass...
> > > > >
> > > >
> > > > Test fail JMS. We have to fix all for beta-1. I should have said this
> > in
> > > > the announcement. Thanks for giving it a go boss.
> > > > S
> > > >
> > > >
> > > > >
> > > > > 2017-11-03 3:32 GMT-04:00 Yung-An He <ma...@gmail.com>:
> > > > >
> > > > > > +1 non-binding
> > > > > >
> > > > > > Checked MD5 : OK
> > > > > > Download the bin tarball : OK
> > > > > > Start from bin tar with cluster mode via docker container: OK
> > > > > > Import data with 100 million rows and 10 columns to table via
> > > > ImportTsv:
> > > > > OK
> > > > > > Execute basic command via `hbase shell`: OK
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > 2017-11-02 5:02 GMT+08:00 Mike Drob <ma...@cloudera.com>:
> > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > Verified sigs and hashes.
> > > > > > > Src tar matches git tag.
> > > > > > > Able to build from src tar w/ hadoop 2 & 3
> > > > > > > Able to start from bin tar, verified basic functionality.
> > > > > > >
> > > > > > > Filed HBASE-19151 for some warning messages on shell startup.
> > > > > > > Failed to start with Java9, but didn't expect this to work
> > anyway.
> > > > > > >
> > > > > > > On Wed, Nov 1, 2017 at 1:38 PM, Artem Ervits <
> > > artemervits@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > > Checked md5
> > > > > > > > ran LTT tool with 10k rows
> > > > > > > > ran PE tool with 6M rows
> > > > > > > > executed counter in hbase shell
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Wed, Nov 1, 2017 at 1:18 PM, Ted Yu <yu...@gmail.com>
> > > > wrote:
> > > > > > > >
> > > > > > > > > +1
> > > > > > > > >
> > > > > > > > > Checked signatures
> > > > > > > > > Built from source
> > > > > > > > > Ran load test tool with 1 mil rows.
> > > > > > > > >
> > > > > > > > > On Wed, Nov 1, 2017 at 7:17 AM, Stack <st...@duboce.net>
> > > wrote:
> > > > > > > > >
> > > > > > > > > > The first release candidate for HBase 2.0.0-alpha4 is up
> > at:
> > > > > > > > > >
> > > > > > > > > > https://dist.apache.org/repos/
> > dist/dev/hbase/hbase-2.0.0-
> > > > > > > alpha4RC0/
> > > > > > > > > >
> > > > > > > > > > Maven artifacts are available from a staging directory
> > here:
> > > > > > > > > >
> > > > > > > > > > https://repository.apache.org/
> > > content/repositories/orgapach
> > > > > > > > ehbase-1178
> > > > > > > > > >
> > > > > > > > > > All was signed with my key at 8ACC93D2 [1]
> > > > > > > > > >
> > > > > > > > > > I tagged the RC as 2.0.0-alpha4RC0
> > > > > > > > > > (5c4b985f89c99cc8b0f8515a4097c811a0848835)
> > > > > > > > > >
> > > > > > > > > > hbase-2.0.0-alpha4 is our fourth alpha release along our
> > > march
> > > > > > toward
> > > > > > > > > > hbase-2.0.0. It includes all that was in previous alphas
> > (new
> > > > > > > > assignment
> > > > > > > > > > manager, offheap read/write path, in-memory compactions,
> > > etc.),
> > > > > but
> > > > > > > > had a
> > > > > > > > > > focus on "Coprocessor Fixup": We no longer pass
> > Coprocessors
> > > > > > > > > > InterfaceAudience.Private parameters and we cut down on
> the
> > > > > access
> > > > > > > and
> > > > > > > > > > ability to influence hbase core processing (See [2] on
> why
> > > the
> > > > > > > radical
> > > > > > > > > > changes in Coprocessor Interface). If you are a
> Coprocessor
> > > > > > developer
> > > > > > > > or
> > > > > > > > > > have Coprocessors to deploy on hbase-2.0.0, we need to
> hear
> > > > about
> > > > > > > your
> > > > > > > > > > experience now before we make an hbase-2.0.0 beta.
> > > > > > > > > >
> > > > > > > > > > hbase-2.0.0-alpha4 is a rough cut ('alpha'),
> > > not-for-production
> > > > > > > preview
> > > > > > > > > of
> > > > > > > > > > what hbase-2.0.0 will look like. It is meant for devs and
> > > > > > > downstreamers
> > > > > > > > > to
> > > > > > > > > > test drive and flag us early if we messed up anything
> ahead
> > > of
> > > > > our
> > > > > > > > > rolling
> > > > > > > > > > GAs.
> > > > > > > > > >
> > > > > > > > > > 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].
> > > > > > > 2.0.0-beta-1
> > > > > > > > > will
> > > > > > > > > > be our next release. Its theme is the "Finishing up
> 2.0.0"
> > > > > release.
> > > > > > > > Here
> > > > > > > > > is
> > > > > > > > > > the list of what we have targeted for beta-1 [5]. Check
> it
> > > out.
> > > > > > Shout
> > > > > > > > if
> > > > > > > > > > there is anything missing. We may do a 2.0.0-beta-2 if a
> > > need.
> > > > > > We'll
> > > > > > > > see.
> > > > > > > > > >
> > > > > > > > > > Please take this alpha for a spin especially if you are a
> > > > > > Coprocessor
> > > > > > > > > > developer or have a Coprocessor you want to deploy on
> > > > > hbase-2.0.0.
> > > > > > > > Please
> > > > > > > > > > vote on whether it ok to put out this RC as our first
> alpha
> > > > (bar
> > > > > is
> > > > > > > low
> > > > > > > > > for
> > > > > > > > > > an 'alpha' -- e.g. CHANGES.txt has not been updated). Let
> > the
> > > > > VOTE
> > > > > > be
> > > > > > > > > open
> > > > > > > > > > for 72 hours (Saturday)
> > > > > > > > > >
> > > > > > > > > > Thanks,
> > > > > > > > > > Your 2.0.0 Release Manager
> > > > > > > > > >
> > > > > > > > > > 1. http://pgp.mit.edu/pks/lookup?op=get&search=
> > > > > 0x9816C7FC8ACC93D2
> > > > > > > > > > 2. Why CPs are Incompatible:
> > > > > > > > > > https://docs.google.com/document/d/
> > > > 1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > > > > > > > > ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> > > > > > > > > > 3. https://goo.gl/scYjJr
> > > > > > > > > > 4. https://goo.gl/tMHkYS
> > > > > > > > > > 5. https://issues.apache.org/
> jira/projects/HBASE/versions/
> > > > > 12340861
> > > > > > > > > > 6.
> > > > > > > > > > https://docs.google.com/document/d/
> > > > 1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > > > > > > > > ktczrlKHK8N4SZzs/
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Stack <st...@duboce.net>.
Thats a dirty rotten bug I'd say. File blocker on beta-1. Thanks Ram.
S
On Wed, Nov 8, 2017 at 8:56 PM, ramkrishna vasudevan <
ramkrishna.s.vasudevan@gmail.com> wrote:
> Hi Stack
> I tried running some IT test cases using the alpha-4 RC. I found this issue
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/hamcrest/SelfDescribing
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
>
> ...
> at
> org.apache.hadoop.hbase.IntegrationTestsDriver.doWork(
> IntegrationTestsDriver.java:111)
> at
> org.apache.hadoop.hbase.util.AbstractHBaseTool.run(
> AbstractHBaseTool.java:154)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at
> org.apache.hadoop.hbase.IntegrationTestsDriver.main(
> IntegrationTestsDriver.java:47)
>
> The same when run against latest master it runs without any issues. I have
> not dug in here but wanted to just mention it here so that we could fix it
> in beta-1?
>
> Regards
> Ram
>
> On Sun, Nov 5, 2017 at 3:03 AM, Jean-Marc Spaggiari <
> jean-marc@spaggiari.org
> > wrote:
>
> > Thanks for your reply Stack. I will get ready to test the next version.
> > Excited to see 2.0 coming out!!!!
> >
> > 2017-11-04 14:44 GMT-04:00 Stack <st...@duboce.net>:
> >
> > > On Sat, Nov 4, 2017 at 1:45 AM, Jean-Marc Spaggiari <
> > > jean-marc@spaggiari.org
> > > > wrote:
> > >
> > > > Folks, are you able to run the tests?
> > > >
> > > > I'm trying to run this:
> > > >
> > > > mvn test -P runAllTests -Dsurefire.secondPartThreadCount=2
> > > > -Dtest.build.data.basedirectory=/ram4G
> > > >
> > > >
> > > > But I'm not able to get it running completely. It always fails
> > somewhere,
> > > > never in the same place. How are you running the tests, if you are?
> > > >
> > > > Else:
> > > > MD5 and SHA files correct for both Binary and Source
> > > > *changes.txt file doesn't seems correct. Missing last versions*
> > > > *checkstyle.html doesn't seems to be accurate. Reports 0 files.*
> > > > Documetation ok.
> > > >
> > > > Will run more tests later when I can get runAllTests pass...
> > > >
> > >
> > > Test fail JMS. We have to fix all for beta-1. I should have said this
> in
> > > the announcement. Thanks for giving it a go boss.
> > > S
> > >
> > >
> > > >
> > > > 2017-11-03 3:32 GMT-04:00 Yung-An He <ma...@gmail.com>:
> > > >
> > > > > +1 non-binding
> > > > >
> > > > > Checked MD5 : OK
> > > > > Download the bin tarball : OK
> > > > > Start from bin tar with cluster mode via docker container: OK
> > > > > Import data with 100 million rows and 10 columns to table via
> > > ImportTsv:
> > > > OK
> > > > > Execute basic command via `hbase shell`: OK
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > 2017-11-02 5:02 GMT+08:00 Mike Drob <ma...@cloudera.com>:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > Verified sigs and hashes.
> > > > > > Src tar matches git tag.
> > > > > > Able to build from src tar w/ hadoop 2 & 3
> > > > > > Able to start from bin tar, verified basic functionality.
> > > > > >
> > > > > > Filed HBASE-19151 for some warning messages on shell startup.
> > > > > > Failed to start with Java9, but didn't expect this to work
> anyway.
> > > > > >
> > > > > > On Wed, Nov 1, 2017 at 1:38 PM, Artem Ervits <
> > artemervits@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > Checked md5
> > > > > > > ran LTT tool with 10k rows
> > > > > > > ran PE tool with 6M rows
> > > > > > > executed counter in hbase shell
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Wed, Nov 1, 2017 at 1:18 PM, Ted Yu <yu...@gmail.com>
> > > wrote:
> > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > > Checked signatures
> > > > > > > > Built from source
> > > > > > > > Ran load test tool with 1 mil rows.
> > > > > > > >
> > > > > > > > On Wed, Nov 1, 2017 at 7:17 AM, Stack <st...@duboce.net>
> > wrote:
> > > > > > > >
> > > > > > > > > The first release candidate for HBase 2.0.0-alpha4 is up
> at:
> > > > > > > > >
> > > > > > > > > https://dist.apache.org/repos/
> dist/dev/hbase/hbase-2.0.0-
> > > > > > alpha4RC0/
> > > > > > > > >
> > > > > > > > > Maven artifacts are available from a staging directory
> here:
> > > > > > > > >
> > > > > > > > > https://repository.apache.org/
> > content/repositories/orgapach
> > > > > > > ehbase-1178
> > > > > > > > >
> > > > > > > > > All was signed with my key at 8ACC93D2 [1]
> > > > > > > > >
> > > > > > > > > I tagged the RC as 2.0.0-alpha4RC0
> > > > > > > > > (5c4b985f89c99cc8b0f8515a4097c811a0848835)
> > > > > > > > >
> > > > > > > > > hbase-2.0.0-alpha4 is our fourth alpha release along our
> > march
> > > > > toward
> > > > > > > > > hbase-2.0.0. It includes all that was in previous alphas
> (new
> > > > > > > assignment
> > > > > > > > > manager, offheap read/write path, in-memory compactions,
> > etc.),
> > > > but
> > > > > > > had a
> > > > > > > > > focus on "Coprocessor Fixup": We no longer pass
> Coprocessors
> > > > > > > > > InterfaceAudience.Private parameters and we cut down on the
> > > > access
> > > > > > and
> > > > > > > > > ability to influence hbase core processing (See [2] on why
> > the
> > > > > > radical
> > > > > > > > > changes in Coprocessor Interface). If you are a Coprocessor
> > > > > developer
> > > > > > > or
> > > > > > > > > have Coprocessors to deploy on hbase-2.0.0, we need to hear
> > > about
> > > > > > your
> > > > > > > > > experience now before we make an hbase-2.0.0 beta.
> > > > > > > > >
> > > > > > > > > hbase-2.0.0-alpha4 is a rough cut ('alpha'),
> > not-for-production
> > > > > > preview
> > > > > > > > of
> > > > > > > > > what hbase-2.0.0 will look like. It is meant for devs and
> > > > > > downstreamers
> > > > > > > > to
> > > > > > > > > test drive and flag us early if we messed up anything ahead
> > of
> > > > our
> > > > > > > > rolling
> > > > > > > > > GAs.
> > > > > > > > >
> > > > > > > > > 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].
> > > > > > 2.0.0-beta-1
> > > > > > > > will
> > > > > > > > > be our next release. Its theme is the "Finishing up 2.0.0"
> > > > release.
> > > > > > > Here
> > > > > > > > is
> > > > > > > > > the list of what we have targeted for beta-1 [5]. Check it
> > out.
> > > > > Shout
> > > > > > > if
> > > > > > > > > there is anything missing. We may do a 2.0.0-beta-2 if a
> > need.
> > > > > We'll
> > > > > > > see.
> > > > > > > > >
> > > > > > > > > Please take this alpha for a spin especially if you are a
> > > > > Coprocessor
> > > > > > > > > developer or have a Coprocessor you want to deploy on
> > > > hbase-2.0.0.
> > > > > > > Please
> > > > > > > > > vote on whether it ok to put out this RC as our first alpha
> > > (bar
> > > > is
> > > > > > low
> > > > > > > > for
> > > > > > > > > an 'alpha' -- e.g. CHANGES.txt has not been updated). Let
> the
> > > > VOTE
> > > > > be
> > > > > > > > open
> > > > > > > > > for 72 hours (Saturday)
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Your 2.0.0 Release Manager
> > > > > > > > >
> > > > > > > > > 1. http://pgp.mit.edu/pks/lookup?op=get&search=
> > > > 0x9816C7FC8ACC93D2
> > > > > > > > > 2. Why CPs are Incompatible:
> > > > > > > > > https://docs.google.com/document/d/
> > > 1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > > > > > > > ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> > > > > > > > > 3. https://goo.gl/scYjJr
> > > > > > > > > 4. https://goo.gl/tMHkYS
> > > > > > > > > 5. https://issues.apache.org/jira/projects/HBASE/versions/
> > > > 12340861
> > > > > > > > > 6.
> > > > > > > > > https://docs.google.com/document/d/
> > > 1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > > > > > > > ktczrlKHK8N4SZzs/
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by ramkrishna vasudevan <ra...@gmail.com>.
Hi Stack
I tried running some IT test cases using the alpha-4 RC. I found this issue
Exception in thread "main" java.lang.NoClassDefFoundError:
org/hamcrest/SelfDescribing
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
...
at
org.apache.hadoop.hbase.IntegrationTestsDriver.doWork(IntegrationTestsDriver.java:111)
at
org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:154)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
at
org.apache.hadoop.hbase.IntegrationTestsDriver.main(IntegrationTestsDriver.java:47)
The same when run against latest master it runs without any issues. I have
not dug in here but wanted to just mention it here so that we could fix it
in beta-1?
Regards
Ram
On Sun, Nov 5, 2017 at 3:03 AM, Jean-Marc Spaggiari <jean-marc@spaggiari.org
> wrote:
> Thanks for your reply Stack. I will get ready to test the next version.
> Excited to see 2.0 coming out!!!!
>
> 2017-11-04 14:44 GMT-04:00 Stack <st...@duboce.net>:
>
> > On Sat, Nov 4, 2017 at 1:45 AM, Jean-Marc Spaggiari <
> > jean-marc@spaggiari.org
> > > wrote:
> >
> > > Folks, are you able to run the tests?
> > >
> > > I'm trying to run this:
> > >
> > > mvn test -P runAllTests -Dsurefire.secondPartThreadCount=2
> > > -Dtest.build.data.basedirectory=/ram4G
> > >
> > >
> > > But I'm not able to get it running completely. It always fails
> somewhere,
> > > never in the same place. How are you running the tests, if you are?
> > >
> > > Else:
> > > MD5 and SHA files correct for both Binary and Source
> > > *changes.txt file doesn't seems correct. Missing last versions*
> > > *checkstyle.html doesn't seems to be accurate. Reports 0 files.*
> > > Documetation ok.
> > >
> > > Will run more tests later when I can get runAllTests pass...
> > >
> >
> > Test fail JMS. We have to fix all for beta-1. I should have said this in
> > the announcement. Thanks for giving it a go boss.
> > S
> >
> >
> > >
> > > 2017-11-03 3:32 GMT-04:00 Yung-An He <ma...@gmail.com>:
> > >
> > > > +1 non-binding
> > > >
> > > > Checked MD5 : OK
> > > > Download the bin tarball : OK
> > > > Start from bin tar with cluster mode via docker container: OK
> > > > Import data with 100 million rows and 10 columns to table via
> > ImportTsv:
> > > OK
> > > > Execute basic command via `hbase shell`: OK
> > > >
> > > >
> > > >
> > > >
> > > > 2017-11-02 5:02 GMT+08:00 Mike Drob <ma...@cloudera.com>:
> > > >
> > > > > +1
> > > > >
> > > > > Verified sigs and hashes.
> > > > > Src tar matches git tag.
> > > > > Able to build from src tar w/ hadoop 2 & 3
> > > > > Able to start from bin tar, verified basic functionality.
> > > > >
> > > > > Filed HBASE-19151 for some warning messages on shell startup.
> > > > > Failed to start with Java9, but didn't expect this to work anyway.
> > > > >
> > > > > On Wed, Nov 1, 2017 at 1:38 PM, Artem Ervits <
> artemervits@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > Checked md5
> > > > > > ran LTT tool with 10k rows
> > > > > > ran PE tool with 6M rows
> > > > > > executed counter in hbase shell
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Wed, Nov 1, 2017 at 1:18 PM, Ted Yu <yu...@gmail.com>
> > wrote:
> > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > Checked signatures
> > > > > > > Built from source
> > > > > > > Ran load test tool with 1 mil rows.
> > > > > > >
> > > > > > > On Wed, Nov 1, 2017 at 7:17 AM, Stack <st...@duboce.net>
> wrote:
> > > > > > >
> > > > > > > > The first release candidate for HBase 2.0.0-alpha4 is up at:
> > > > > > > >
> > > > > > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-
> > > > > alpha4RC0/
> > > > > > > >
> > > > > > > > Maven artifacts are available from a staging directory here:
> > > > > > > >
> > > > > > > > https://repository.apache.org/
> content/repositories/orgapach
> > > > > > ehbase-1178
> > > > > > > >
> > > > > > > > All was signed with my key at 8ACC93D2 [1]
> > > > > > > >
> > > > > > > > I tagged the RC as 2.0.0-alpha4RC0
> > > > > > > > (5c4b985f89c99cc8b0f8515a4097c811a0848835)
> > > > > > > >
> > > > > > > > hbase-2.0.0-alpha4 is our fourth alpha release along our
> march
> > > > toward
> > > > > > > > hbase-2.0.0. It includes all that was in previous alphas (new
> > > > > > assignment
> > > > > > > > manager, offheap read/write path, in-memory compactions,
> etc.),
> > > but
> > > > > > had a
> > > > > > > > focus on "Coprocessor Fixup": We no longer pass Coprocessors
> > > > > > > > InterfaceAudience.Private parameters and we cut down on the
> > > access
> > > > > and
> > > > > > > > ability to influence hbase core processing (See [2] on why
> the
> > > > > radical
> > > > > > > > changes in Coprocessor Interface). If you are a Coprocessor
> > > > developer
> > > > > > or
> > > > > > > > have Coprocessors to deploy on hbase-2.0.0, we need to hear
> > about
> > > > > your
> > > > > > > > experience now before we make an hbase-2.0.0 beta.
> > > > > > > >
> > > > > > > > hbase-2.0.0-alpha4 is a rough cut ('alpha'),
> not-for-production
> > > > > preview
> > > > > > > of
> > > > > > > > what hbase-2.0.0 will look like. It is meant for devs and
> > > > > downstreamers
> > > > > > > to
> > > > > > > > test drive and flag us early if we messed up anything ahead
> of
> > > our
> > > > > > > rolling
> > > > > > > > GAs.
> > > > > > > >
> > > > > > > > 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].
> > > > > 2.0.0-beta-1
> > > > > > > will
> > > > > > > > be our next release. Its theme is the "Finishing up 2.0.0"
> > > release.
> > > > > > Here
> > > > > > > is
> > > > > > > > the list of what we have targeted for beta-1 [5]. Check it
> out.
> > > > Shout
> > > > > > if
> > > > > > > > there is anything missing. We may do a 2.0.0-beta-2 if a
> need.
> > > > We'll
> > > > > > see.
> > > > > > > >
> > > > > > > > Please take this alpha for a spin especially if you are a
> > > > Coprocessor
> > > > > > > > developer or have a Coprocessor you want to deploy on
> > > hbase-2.0.0.
> > > > > > Please
> > > > > > > > vote on whether it ok to put out this RC as our first alpha
> > (bar
> > > is
> > > > > low
> > > > > > > for
> > > > > > > > an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the
> > > VOTE
> > > > be
> > > > > > > open
> > > > > > > > for 72 hours (Saturday)
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Your 2.0.0 Release Manager
> > > > > > > >
> > > > > > > > 1. http://pgp.mit.edu/pks/lookup?op=get&search=
> > > 0x9816C7FC8ACC93D2
> > > > > > > > 2. Why CPs are Incompatible:
> > > > > > > > https://docs.google.com/document/d/
> > 1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > > > > > > ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> > > > > > > > 3. https://goo.gl/scYjJr
> > > > > > > > 4. https://goo.gl/tMHkYS
> > > > > > > > 5. https://issues.apache.org/jira/projects/HBASE/versions/
> > > 12340861
> > > > > > > > 6.
> > > > > > > > https://docs.google.com/document/d/
> > 1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > > > > > > ktczrlKHK8N4SZzs/
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Jean-Marc Spaggiari <je...@spaggiari.org>.
Thanks for your reply Stack. I will get ready to test the next version.
Excited to see 2.0 coming out!!!!
2017-11-04 14:44 GMT-04:00 Stack <st...@duboce.net>:
> On Sat, Nov 4, 2017 at 1:45 AM, Jean-Marc Spaggiari <
> jean-marc@spaggiari.org
> > wrote:
>
> > Folks, are you able to run the tests?
> >
> > I'm trying to run this:
> >
> > mvn test -P runAllTests -Dsurefire.secondPartThreadCount=2
> > -Dtest.build.data.basedirectory=/ram4G
> >
> >
> > But I'm not able to get it running completely. It always fails somewhere,
> > never in the same place. How are you running the tests, if you are?
> >
> > Else:
> > MD5 and SHA files correct for both Binary and Source
> > *changes.txt file doesn't seems correct. Missing last versions*
> > *checkstyle.html doesn't seems to be accurate. Reports 0 files.*
> > Documetation ok.
> >
> > Will run more tests later when I can get runAllTests pass...
> >
>
> Test fail JMS. We have to fix all for beta-1. I should have said this in
> the announcement. Thanks for giving it a go boss.
> S
>
>
> >
> > 2017-11-03 3:32 GMT-04:00 Yung-An He <ma...@gmail.com>:
> >
> > > +1 non-binding
> > >
> > > Checked MD5 : OK
> > > Download the bin tarball : OK
> > > Start from bin tar with cluster mode via docker container: OK
> > > Import data with 100 million rows and 10 columns to table via
> ImportTsv:
> > OK
> > > Execute basic command via `hbase shell`: OK
> > >
> > >
> > >
> > >
> > > 2017-11-02 5:02 GMT+08:00 Mike Drob <ma...@cloudera.com>:
> > >
> > > > +1
> > > >
> > > > Verified sigs and hashes.
> > > > Src tar matches git tag.
> > > > Able to build from src tar w/ hadoop 2 & 3
> > > > Able to start from bin tar, verified basic functionality.
> > > >
> > > > Filed HBASE-19151 for some warning messages on shell startup.
> > > > Failed to start with Java9, but didn't expect this to work anyway.
> > > >
> > > > On Wed, Nov 1, 2017 at 1:38 PM, Artem Ervits <ar...@gmail.com>
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > Checked md5
> > > > > ran LTT tool with 10k rows
> > > > > ran PE tool with 6M rows
> > > > > executed counter in hbase shell
> > > > >
> > > > >
> > > > >
> > > > > On Wed, Nov 1, 2017 at 1:18 PM, Ted Yu <yu...@gmail.com>
> wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > Checked signatures
> > > > > > Built from source
> > > > > > Ran load test tool with 1 mil rows.
> > > > > >
> > > > > > On Wed, Nov 1, 2017 at 7:17 AM, Stack <st...@duboce.net> wrote:
> > > > > >
> > > > > > > The first release candidate for HBase 2.0.0-alpha4 is up at:
> > > > > > >
> > > > > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-
> > > > alpha4RC0/
> > > > > > >
> > > > > > > Maven artifacts are available from a staging directory here:
> > > > > > >
> > > > > > > https://repository.apache.org/content/repositories/orgapach
> > > > > ehbase-1178
> > > > > > >
> > > > > > > All was signed with my key at 8ACC93D2 [1]
> > > > > > >
> > > > > > > I tagged the RC as 2.0.0-alpha4RC0
> > > > > > > (5c4b985f89c99cc8b0f8515a4097c811a0848835)
> > > > > > >
> > > > > > > hbase-2.0.0-alpha4 is our fourth alpha release along our march
> > > toward
> > > > > > > hbase-2.0.0. It includes all that was in previous alphas (new
> > > > > assignment
> > > > > > > manager, offheap read/write path, in-memory compactions, etc.),
> > but
> > > > > had a
> > > > > > > focus on "Coprocessor Fixup": We no longer pass Coprocessors
> > > > > > > InterfaceAudience.Private parameters and we cut down on the
> > access
> > > > and
> > > > > > > ability to influence hbase core processing (See [2] on why the
> > > > radical
> > > > > > > changes in Coprocessor Interface). If you are a Coprocessor
> > > developer
> > > > > or
> > > > > > > have Coprocessors to deploy on hbase-2.0.0, we need to hear
> about
> > > > your
> > > > > > > experience now before we make an hbase-2.0.0 beta.
> > > > > > >
> > > > > > > hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production
> > > > preview
> > > > > > of
> > > > > > > what hbase-2.0.0 will look like. It is meant for devs and
> > > > downstreamers
> > > > > > to
> > > > > > > test drive and flag us early if we messed up anything ahead of
> > our
> > > > > > rolling
> > > > > > > GAs.
> > > > > > >
> > > > > > > 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].
> > > > 2.0.0-beta-1
> > > > > > will
> > > > > > > be our next release. Its theme is the "Finishing up 2.0.0"
> > release.
> > > > > Here
> > > > > > is
> > > > > > > the list of what we have targeted for beta-1 [5]. Check it out.
> > > Shout
> > > > > if
> > > > > > > there is anything missing. We may do a 2.0.0-beta-2 if a need.
> > > We'll
> > > > > see.
> > > > > > >
> > > > > > > Please take this alpha for a spin especially if you are a
> > > Coprocessor
> > > > > > > developer or have a Coprocessor you want to deploy on
> > hbase-2.0.0.
> > > > > Please
> > > > > > > vote on whether it ok to put out this RC as our first alpha
> (bar
> > is
> > > > low
> > > > > > for
> > > > > > > an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the
> > VOTE
> > > be
> > > > > > open
> > > > > > > for 72 hours (Saturday)
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Your 2.0.0 Release Manager
> > > > > > >
> > > > > > > 1. http://pgp.mit.edu/pks/lookup?op=get&search=
> > 0x9816C7FC8ACC93D2
> > > > > > > 2. Why CPs are Incompatible:
> > > > > > > https://docs.google.com/document/d/
> 1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > > > > > ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> > > > > > > 3. https://goo.gl/scYjJr
> > > > > > > 4. https://goo.gl/tMHkYS
> > > > > > > 5. https://issues.apache.org/jira/projects/HBASE/versions/
> > 12340861
> > > > > > > 6.
> > > > > > > https://docs.google.com/document/d/
> 1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > > > > > ktczrlKHK8N4SZzs/
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Stack <st...@duboce.net>.
On Sat, Nov 4, 2017 at 1:45 AM, Jean-Marc Spaggiari <jean-marc@spaggiari.org
> wrote:
> Folks, are you able to run the tests?
>
> I'm trying to run this:
>
> mvn test -P runAllTests -Dsurefire.secondPartThreadCount=2
> -Dtest.build.data.basedirectory=/ram4G
>
>
> But I'm not able to get it running completely. It always fails somewhere,
> never in the same place. How are you running the tests, if you are?
>
> Else:
> MD5 and SHA files correct for both Binary and Source
> *changes.txt file doesn't seems correct. Missing last versions*
> *checkstyle.html doesn't seems to be accurate. Reports 0 files.*
> Documetation ok.
>
> Will run more tests later when I can get runAllTests pass...
>
Test fail JMS. We have to fix all for beta-1. I should have said this in
the announcement. Thanks for giving it a go boss.
S
>
> 2017-11-03 3:32 GMT-04:00 Yung-An He <ma...@gmail.com>:
>
> > +1 non-binding
> >
> > Checked MD5 : OK
> > Download the bin tarball : OK
> > Start from bin tar with cluster mode via docker container: OK
> > Import data with 100 million rows and 10 columns to table via ImportTsv:
> OK
> > Execute basic command via `hbase shell`: OK
> >
> >
> >
> >
> > 2017-11-02 5:02 GMT+08:00 Mike Drob <ma...@cloudera.com>:
> >
> > > +1
> > >
> > > Verified sigs and hashes.
> > > Src tar matches git tag.
> > > Able to build from src tar w/ hadoop 2 & 3
> > > Able to start from bin tar, verified basic functionality.
> > >
> > > Filed HBASE-19151 for some warning messages on shell startup.
> > > Failed to start with Java9, but didn't expect this to work anyway.
> > >
> > > On Wed, Nov 1, 2017 at 1:38 PM, Artem Ervits <ar...@gmail.com>
> > > wrote:
> > >
> > > > +1
> > > >
> > > > Checked md5
> > > > ran LTT tool with 10k rows
> > > > ran PE tool with 6M rows
> > > > executed counter in hbase shell
> > > >
> > > >
> > > >
> > > > On Wed, Nov 1, 2017 at 1:18 PM, Ted Yu <yu...@gmail.com> wrote:
> > > >
> > > > > +1
> > > > >
> > > > > Checked signatures
> > > > > Built from source
> > > > > Ran load test tool with 1 mil rows.
> > > > >
> > > > > On Wed, Nov 1, 2017 at 7:17 AM, Stack <st...@duboce.net> wrote:
> > > > >
> > > > > > The first release candidate for HBase 2.0.0-alpha4 is up at:
> > > > > >
> > > > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-
> > > alpha4RC0/
> > > > > >
> > > > > > Maven artifacts are available from a staging directory here:
> > > > > >
> > > > > > https://repository.apache.org/content/repositories/orgapach
> > > > ehbase-1178
> > > > > >
> > > > > > All was signed with my key at 8ACC93D2 [1]
> > > > > >
> > > > > > I tagged the RC as 2.0.0-alpha4RC0
> > > > > > (5c4b985f89c99cc8b0f8515a4097c811a0848835)
> > > > > >
> > > > > > hbase-2.0.0-alpha4 is our fourth alpha release along our march
> > toward
> > > > > > hbase-2.0.0. It includes all that was in previous alphas (new
> > > > assignment
> > > > > > manager, offheap read/write path, in-memory compactions, etc.),
> but
> > > > had a
> > > > > > focus on "Coprocessor Fixup": We no longer pass Coprocessors
> > > > > > InterfaceAudience.Private parameters and we cut down on the
> access
> > > and
> > > > > > ability to influence hbase core processing (See [2] on why the
> > > radical
> > > > > > changes in Coprocessor Interface). If you are a Coprocessor
> > developer
> > > > or
> > > > > > have Coprocessors to deploy on hbase-2.0.0, we need to hear about
> > > your
> > > > > > experience now before we make an hbase-2.0.0 beta.
> > > > > >
> > > > > > hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production
> > > preview
> > > > > of
> > > > > > what hbase-2.0.0 will look like. It is meant for devs and
> > > downstreamers
> > > > > to
> > > > > > test drive and flag us early if we messed up anything ahead of
> our
> > > > > rolling
> > > > > > GAs.
> > > > > >
> > > > > > 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].
> > > 2.0.0-beta-1
> > > > > will
> > > > > > be our next release. Its theme is the "Finishing up 2.0.0"
> release.
> > > > Here
> > > > > is
> > > > > > the list of what we have targeted for beta-1 [5]. Check it out.
> > Shout
> > > > if
> > > > > > there is anything missing. We may do a 2.0.0-beta-2 if a need.
> > We'll
> > > > see.
> > > > > >
> > > > > > Please take this alpha for a spin especially if you are a
> > Coprocessor
> > > > > > developer or have a Coprocessor you want to deploy on
> hbase-2.0.0.
> > > > Please
> > > > > > vote on whether it ok to put out this RC as our first alpha (bar
> is
> > > low
> > > > > for
> > > > > > an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the
> VOTE
> > be
> > > > > open
> > > > > > for 72 hours (Saturday)
> > > > > >
> > > > > > Thanks,
> > > > > > Your 2.0.0 Release Manager
> > > > > >
> > > > > > 1. http://pgp.mit.edu/pks/lookup?op=get&search=
> 0x9816C7FC8ACC93D2
> > > > > > 2. Why CPs are Incompatible:
> > > > > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > > > > ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> > > > > > 3. https://goo.gl/scYjJr
> > > > > > 4. https://goo.gl/tMHkYS
> > > > > > 5. https://issues.apache.org/jira/projects/HBASE/versions/
> 12340861
> > > > > > 6.
> > > > > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > > > > ktczrlKHK8N4SZzs/
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Jean-Marc Spaggiari <je...@spaggiari.org>.
Folks, are you able to run the tests?
I'm trying to run this:
mvn test -P runAllTests -Dsurefire.secondPartThreadCount=2
-Dtest.build.data.basedirectory=/ram4G
But I'm not able to get it running completely. It always fails somewhere,
never in the same place. How are you running the tests, if you are?
Else:
MD5 and SHA files correct for both Binary and Source
*changes.txt file doesn't seems correct. Missing last versions*
*checkstyle.html doesn't seems to be accurate. Reports 0 files.*
Documetation ok.
Will run more tests later when I can get runAllTests pass...
2017-11-03 3:32 GMT-04:00 Yung-An He <ma...@gmail.com>:
> +1 non-binding
>
> Checked MD5 : OK
> Download the bin tarball : OK
> Start from bin tar with cluster mode via docker container: OK
> Import data with 100 million rows and 10 columns to table via ImportTsv: OK
> Execute basic command via `hbase shell`: OK
>
>
>
>
> 2017-11-02 5:02 GMT+08:00 Mike Drob <ma...@cloudera.com>:
>
> > +1
> >
> > Verified sigs and hashes.
> > Src tar matches git tag.
> > Able to build from src tar w/ hadoop 2 & 3
> > Able to start from bin tar, verified basic functionality.
> >
> > Filed HBASE-19151 for some warning messages on shell startup.
> > Failed to start with Java9, but didn't expect this to work anyway.
> >
> > On Wed, Nov 1, 2017 at 1:38 PM, Artem Ervits <ar...@gmail.com>
> > wrote:
> >
> > > +1
> > >
> > > Checked md5
> > > ran LTT tool with 10k rows
> > > ran PE tool with 6M rows
> > > executed counter in hbase shell
> > >
> > >
> > >
> > > On Wed, Nov 1, 2017 at 1:18 PM, Ted Yu <yu...@gmail.com> wrote:
> > >
> > > > +1
> > > >
> > > > Checked signatures
> > > > Built from source
> > > > Ran load test tool with 1 mil rows.
> > > >
> > > > On Wed, Nov 1, 2017 at 7:17 AM, Stack <st...@duboce.net> wrote:
> > > >
> > > > > The first release candidate for HBase 2.0.0-alpha4 is up at:
> > > > >
> > > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-
> > alpha4RC0/
> > > > >
> > > > > Maven artifacts are available from a staging directory here:
> > > > >
> > > > > https://repository.apache.org/content/repositories/orgapach
> > > ehbase-1178
> > > > >
> > > > > All was signed with my key at 8ACC93D2 [1]
> > > > >
> > > > > I tagged the RC as 2.0.0-alpha4RC0
> > > > > (5c4b985f89c99cc8b0f8515a4097c811a0848835)
> > > > >
> > > > > hbase-2.0.0-alpha4 is our fourth alpha release along our march
> toward
> > > > > hbase-2.0.0. It includes all that was in previous alphas (new
> > > assignment
> > > > > manager, offheap read/write path, in-memory compactions, etc.), but
> > > had a
> > > > > focus on "Coprocessor Fixup": We no longer pass Coprocessors
> > > > > InterfaceAudience.Private parameters and we cut down on the access
> > and
> > > > > ability to influence hbase core processing (See [2] on why the
> > radical
> > > > > changes in Coprocessor Interface). If you are a Coprocessor
> developer
> > > or
> > > > > have Coprocessors to deploy on hbase-2.0.0, we need to hear about
> > your
> > > > > experience now before we make an hbase-2.0.0 beta.
> > > > >
> > > > > hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production
> > preview
> > > > of
> > > > > what hbase-2.0.0 will look like. It is meant for devs and
> > downstreamers
> > > > to
> > > > > test drive and flag us early if we messed up anything ahead of our
> > > > rolling
> > > > > GAs.
> > > > >
> > > > > 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].
> > 2.0.0-beta-1
> > > > will
> > > > > be our next release. Its theme is the "Finishing up 2.0.0" release.
> > > Here
> > > > is
> > > > > the list of what we have targeted for beta-1 [5]. Check it out.
> Shout
> > > if
> > > > > there is anything missing. We may do a 2.0.0-beta-2 if a need.
> We'll
> > > see.
> > > > >
> > > > > Please take this alpha for a spin especially if you are a
> Coprocessor
> > > > > developer or have a Coprocessor you want to deploy on hbase-2.0.0.
> > > Please
> > > > > vote on whether it ok to put out this RC as our first alpha (bar is
> > low
> > > > for
> > > > > an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE
> be
> > > > open
> > > > > for 72 hours (Saturday)
> > > > >
> > > > > Thanks,
> > > > > Your 2.0.0 Release Manager
> > > > >
> > > > > 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> > > > > 2. Why CPs are Incompatible:
> > > > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > > > ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> > > > > 3. https://goo.gl/scYjJr
> > > > > 4. https://goo.gl/tMHkYS
> > > > > 5. https://issues.apache.org/jira/projects/HBASE/versions/12340861
> > > > > 6.
> > > > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > > > ktczrlKHK8N4SZzs/
> > > > >
> > > >
> > >
> >
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Yung-An He <ma...@gmail.com>.
+1 non-binding
Checked MD5 : OK
Download the bin tarball : OK
Start from bin tar with cluster mode via docker container: OK
Import data with 100 million rows and 10 columns to table via ImportTsv: OK
Execute basic command via `hbase shell`: OK
2017-11-02 5:02 GMT+08:00 Mike Drob <ma...@cloudera.com>:
> +1
>
> Verified sigs and hashes.
> Src tar matches git tag.
> Able to build from src tar w/ hadoop 2 & 3
> Able to start from bin tar, verified basic functionality.
>
> Filed HBASE-19151 for some warning messages on shell startup.
> Failed to start with Java9, but didn't expect this to work anyway.
>
> On Wed, Nov 1, 2017 at 1:38 PM, Artem Ervits <ar...@gmail.com>
> wrote:
>
> > +1
> >
> > Checked md5
> > ran LTT tool with 10k rows
> > ran PE tool with 6M rows
> > executed counter in hbase shell
> >
> >
> >
> > On Wed, Nov 1, 2017 at 1:18 PM, Ted Yu <yu...@gmail.com> wrote:
> >
> > > +1
> > >
> > > Checked signatures
> > > Built from source
> > > Ran load test tool with 1 mil rows.
> > >
> > > On Wed, Nov 1, 2017 at 7:17 AM, Stack <st...@duboce.net> wrote:
> > >
> > > > The first release candidate for HBase 2.0.0-alpha4 is up at:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-
> alpha4RC0/
> > > >
> > > > Maven artifacts are available from a staging directory here:
> > > >
> > > > https://repository.apache.org/content/repositories/orgapach
> > ehbase-1178
> > > >
> > > > All was signed with my key at 8ACC93D2 [1]
> > > >
> > > > I tagged the RC as 2.0.0-alpha4RC0
> > > > (5c4b985f89c99cc8b0f8515a4097c811a0848835)
> > > >
> > > > hbase-2.0.0-alpha4 is our fourth alpha release along our march toward
> > > > hbase-2.0.0. It includes all that was in previous alphas (new
> > assignment
> > > > manager, offheap read/write path, in-memory compactions, etc.), but
> > had a
> > > > focus on "Coprocessor Fixup": We no longer pass Coprocessors
> > > > InterfaceAudience.Private parameters and we cut down on the access
> and
> > > > ability to influence hbase core processing (See [2] on why the
> radical
> > > > changes in Coprocessor Interface). If you are a Coprocessor developer
> > or
> > > > have Coprocessors to deploy on hbase-2.0.0, we need to hear about
> your
> > > > experience now before we make an hbase-2.0.0 beta.
> > > >
> > > > hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production
> preview
> > > of
> > > > what hbase-2.0.0 will look like. It is meant for devs and
> downstreamers
> > > to
> > > > test drive and flag us early if we messed up anything ahead of our
> > > rolling
> > > > GAs.
> > > >
> > > > 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].
> 2.0.0-beta-1
> > > will
> > > > be our next release. Its theme is the "Finishing up 2.0.0" release.
> > Here
> > > is
> > > > the list of what we have targeted for beta-1 [5]. Check it out. Shout
> > if
> > > > there is anything missing. We may do a 2.0.0-beta-2 if a need. We'll
> > see.
> > > >
> > > > Please take this alpha for a spin especially if you are a Coprocessor
> > > > developer or have a Coprocessor you want to deploy on hbase-2.0.0.
> > Please
> > > > vote on whether it ok to put out this RC as our first alpha (bar is
> low
> > > for
> > > > an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE be
> > > open
> > > > for 72 hours (Saturday)
> > > >
> > > > Thanks,
> > > > Your 2.0.0 Release Manager
> > > >
> > > > 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> > > > 2. Why CPs are Incompatible:
> > > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > > ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> > > > 3. https://goo.gl/scYjJr
> > > > 4. https://goo.gl/tMHkYS
> > > > 5. https://issues.apache.org/jira/projects/HBASE/versions/12340861
> > > > 6.
> > > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > > ktczrlKHK8N4SZzs/
> > > >
> > >
> >
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Mike Drob <ma...@cloudera.com>.
+1
Verified sigs and hashes.
Src tar matches git tag.
Able to build from src tar w/ hadoop 2 & 3
Able to start from bin tar, verified basic functionality.
Filed HBASE-19151 for some warning messages on shell startup.
Failed to start with Java9, but didn't expect this to work anyway.
On Wed, Nov 1, 2017 at 1:38 PM, Artem Ervits <ar...@gmail.com> wrote:
> +1
>
> Checked md5
> ran LTT tool with 10k rows
> ran PE tool with 6M rows
> executed counter in hbase shell
>
>
>
> On Wed, Nov 1, 2017 at 1:18 PM, Ted Yu <yu...@gmail.com> wrote:
>
> > +1
> >
> > Checked signatures
> > Built from source
> > Ran load test tool with 1 mil rows.
> >
> > On Wed, Nov 1, 2017 at 7:17 AM, Stack <st...@duboce.net> wrote:
> >
> > > The first release candidate for HBase 2.0.0-alpha4 is up at:
> > >
> > > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha4RC0/
> > >
> > > Maven artifacts are available from a staging directory here:
> > >
> > > https://repository.apache.org/content/repositories/orgapach
> ehbase-1178
> > >
> > > All was signed with my key at 8ACC93D2 [1]
> > >
> > > I tagged the RC as 2.0.0-alpha4RC0
> > > (5c4b985f89c99cc8b0f8515a4097c811a0848835)
> > >
> > > hbase-2.0.0-alpha4 is our fourth alpha release along our march toward
> > > hbase-2.0.0. It includes all that was in previous alphas (new
> assignment
> > > manager, offheap read/write path, in-memory compactions, etc.), but
> had a
> > > focus on "Coprocessor Fixup": We no longer pass Coprocessors
> > > InterfaceAudience.Private parameters and we cut down on the access and
> > > ability to influence hbase core processing (See [2] on why the radical
> > > changes in Coprocessor Interface). If you are a Coprocessor developer
> or
> > > have Coprocessors to deploy on hbase-2.0.0, we need to hear about your
> > > experience now before we make an hbase-2.0.0 beta.
> > >
> > > hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production preview
> > of
> > > what hbase-2.0.0 will look like. It is meant for devs and downstreamers
> > to
> > > test drive and flag us early if we messed up anything ahead of our
> > rolling
> > > GAs.
> > >
> > > 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]. 2.0.0-beta-1
> > will
> > > be our next release. Its theme is the "Finishing up 2.0.0" release.
> Here
> > is
> > > the list of what we have targeted for beta-1 [5]. Check it out. Shout
> if
> > > there is anything missing. We may do a 2.0.0-beta-2 if a need. We'll
> see.
> > >
> > > Please take this alpha for a spin especially if you are a Coprocessor
> > > developer or have a Coprocessor you want to deploy on hbase-2.0.0.
> Please
> > > vote on whether it ok to put out this RC as our first alpha (bar is low
> > for
> > > an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE be
> > open
> > > for 72 hours (Saturday)
> > >
> > > Thanks,
> > > Your 2.0.0 Release Manager
> > >
> > > 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> > > 2. Why CPs are Incompatible:
> > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> > > 3. https://goo.gl/scYjJr
> > > 4. https://goo.gl/tMHkYS
> > > 5. https://issues.apache.org/jira/projects/HBASE/versions/12340861
> > > 6.
> > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > ktczrlKHK8N4SZzs/
> > >
> >
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Artem Ervits <ar...@gmail.com>.
+1
Checked md5
ran LTT tool with 10k rows
ran PE tool with 6M rows
executed counter in hbase shell
On Wed, Nov 1, 2017 at 1:18 PM, Ted Yu <yu...@gmail.com> wrote:
> +1
>
> Checked signatures
> Built from source
> Ran load test tool with 1 mil rows.
>
> On Wed, Nov 1, 2017 at 7:17 AM, Stack <st...@duboce.net> wrote:
>
> > The first release candidate for HBase 2.0.0-alpha4 is up at:
> >
> > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha4RC0/
> >
> > Maven artifacts are available from a staging directory here:
> >
> > https://repository.apache.org/content/repositories/orgapachehbase-1178
> >
> > All was signed with my key at 8ACC93D2 [1]
> >
> > I tagged the RC as 2.0.0-alpha4RC0
> > (5c4b985f89c99cc8b0f8515a4097c811a0848835)
> >
> > hbase-2.0.0-alpha4 is our fourth alpha release along our march toward
> > hbase-2.0.0. It includes all that was in previous alphas (new assignment
> > manager, offheap read/write path, in-memory compactions, etc.), but had a
> > focus on "Coprocessor Fixup": We no longer pass Coprocessors
> > InterfaceAudience.Private parameters and we cut down on the access and
> > ability to influence hbase core processing (See [2] on why the radical
> > changes in Coprocessor Interface). If you are a Coprocessor developer or
> > have Coprocessors to deploy on hbase-2.0.0, we need to hear about your
> > experience now before we make an hbase-2.0.0 beta.
> >
> > hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production preview
> of
> > what hbase-2.0.0 will look like. It is meant for devs and downstreamers
> to
> > test drive and flag us early if we messed up anything ahead of our
> rolling
> > GAs.
> >
> > 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]. 2.0.0-beta-1
> will
> > be our next release. Its theme is the "Finishing up 2.0.0" release. Here
> is
> > the list of what we have targeted for beta-1 [5]. Check it out. Shout if
> > there is anything missing. We may do a 2.0.0-beta-2 if a need. We'll see.
> >
> > Please take this alpha for a spin especially if you are a Coprocessor
> > developer or have a Coprocessor you want to deploy on hbase-2.0.0. Please
> > vote on whether it ok to put out this RC as our first alpha (bar is low
> for
> > an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE be
> open
> > for 72 hours (Saturday)
> >
> > Thanks,
> > Your 2.0.0 Release Manager
> >
> > 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> > 2. Why CPs are Incompatible:
> > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> > 3. https://goo.gl/scYjJr
> > 4. https://goo.gl/tMHkYS
> > 5. https://issues.apache.org/jira/projects/HBASE/versions/12340861
> > 6.
> > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > ktczrlKHK8N4SZzs/
> >
>
Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available
Posted by Ted Yu <yu...@gmail.com>.
+1
Checked signatures
Built from source
Ran load test tool with 1 mil rows.
On Wed, Nov 1, 2017 at 7:17 AM, Stack <st...@duboce.net> wrote:
> The first release candidate for HBase 2.0.0-alpha4 is up at:
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha4RC0/
>
> Maven artifacts are available from a staging directory here:
>
> https://repository.apache.org/content/repositories/orgapachehbase-1178
>
> All was signed with my key at 8ACC93D2 [1]
>
> I tagged the RC as 2.0.0-alpha4RC0
> (5c4b985f89c99cc8b0f8515a4097c811a0848835)
>
> hbase-2.0.0-alpha4 is our fourth alpha release along our march toward
> hbase-2.0.0. It includes all that was in previous alphas (new assignment
> manager, offheap read/write path, in-memory compactions, etc.), but had a
> focus on "Coprocessor Fixup": We no longer pass Coprocessors
> InterfaceAudience.Private parameters and we cut down on the access and
> ability to influence hbase core processing (See [2] on why the radical
> changes in Coprocessor Interface). If you are a Coprocessor developer or
> have Coprocessors to deploy on hbase-2.0.0, we need to hear about your
> experience now before we make an hbase-2.0.0 beta.
>
> hbase-2.0.0-alpha4 is a rough cut ('alpha'), not-for-production preview of
> what hbase-2.0.0 will look like. It is meant for devs and downstreamers to
> test drive and flag us early if we messed up anything ahead of our rolling
> GAs.
>
> 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]. 2.0.0-beta-1 will
> be our next release. Its theme is the "Finishing up 2.0.0" release. Here is
> the list of what we have targeted for beta-1 [5]. Check it out. Shout if
> there is anything missing. We may do a 2.0.0-beta-2 if a need. We'll see.
>
> Please take this alpha for a spin especially if you are a Coprocessor
> developer or have a Coprocessor you want to deploy on hbase-2.0.0. Please
> vote on whether it ok to put out this RC as our first alpha (bar is low for
> an 'alpha' -- e.g. CHANGES.txt has not been updated). Let the VOTE be open
> for 72 hours (Saturday)
>
> Thanks,
> Your 2.0.0 Release Manager
>
> 1. http://pgp.mit.edu/pks/lookup?op=get&search=0x9816C7FC8ACC93D2
> 2. Why CPs are Incompatible:
> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> ktczrlKHK8N4SZzs/edit#heading=h.9k7mjbauv0wj
> 3. https://goo.gl/scYjJr
> 4. https://goo.gl/tMHkYS
> 5. https://issues.apache.org/jira/projects/HBASE/versions/12340861
> 6.
> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> ktczrlKHK8N4SZzs/
>