Re: [ANNOUNCE] New HBase committer Allan Yang

2017-06-08 Thread Guanghao Zhang 
Congratulations!

2017-06-09 13:41 GMT+08:00 Jingcheng Du :

> Congratulations!
>
> 2017-06-09 13:20 GMT+08:00 Karan Mehta :
>
> > Congratulations, Allan!! :)
> >
> > Thanks,
> > Karan
> > ᐧ
> >
> > On Thu, Jun 8, 2017 at 10:11 PM, Stack  wrote:
> >
> > > Hurray!
> > >
> > > On Thu, Jun 8, 2017 at 8:49 PM, Yu Li  wrote:
> > >
> > > > On behalf of the Apache HBase PMC, I am pleased to announce that
> Allan
> > > Yang
> > > > has accepted the PMC's invitation to become a committer on the
> > > > project. We appreciate all of Allan's generous contributions thus far
> > and
> > > > look forward to his continued involvement.
> > > >
> > > > Congratulations and welcome, Allan!
> > > >
> > >
> >
>

Re: [ANNOUNCE] New HBase committer Allan Yang

2017-06-08 Thread Jingcheng Du 
Congratulations!

2017-06-09 13:20 GMT+08:00 Karan Mehta :

> Congratulations, Allan!! :)
>
> Thanks,
> Karan
> ᐧ
>
> On Thu, Jun 8, 2017 at 10:11 PM, Stack  wrote:
>
> > Hurray!
> >
> > On Thu, Jun 8, 2017 at 8:49 PM, Yu Li  wrote:
> >
> > > On behalf of the Apache HBase PMC, I am pleased to announce that Allan
> > Yang
> > > has accepted the PMC's invitation to become a committer on the
> > > project. We appreciate all of Allan's generous contributions thus far
> and
> > > look forward to his continued involvement.
> > >
> > > Congratulations and welcome, Allan!
> > >
> >
>

Re: [ANNOUNCE] New HBase committer Allan Yang

2017-06-08 Thread Karan Mehta 
Congratulations, Allan!! :)

Thanks,
Karan
ᐧ

On Thu, Jun 8, 2017 at 10:11 PM, Stack  wrote:

> Hurray!
>
> On Thu, Jun 8, 2017 at 8:49 PM, Yu Li  wrote:
>
> > On behalf of the Apache HBase PMC, I am pleased to announce that Allan
> Yang
> > has accepted the PMC's invitation to become a committer on the
> > project. We appreciate all of Allan's generous contributions thus far and
> > look forward to his continued involvement.
> >
> > Congratulations and welcome, Allan!
> >
>

Re: [VOTE] First hbase-2.0.0-alpha-1 Release Candidate is available

2017-06-08 Thread Stack 
On Thu, Jun 8, 2017 at 9:05 PM, Yu Li  wrote:

> Bravo! Our first branch-2 RC! Will try my best to vote in time.
>
> Minor: the 4th reference (new features) seems incorrect, should be the
> below one?:
> https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20HBASE%20%20and%20(%20fixVersion%20%3D%202.0.0)%20and%20(status%20%3D%
> 20Resolved)%20and%20(type%20%3D%20%22New%20Feature%22)
>
>
Thanks for the correction Yu Li.
St.Ack




> Best Regards,
> Yu
>
> On 9 June 2017 at 09:38, 张铎(Duo Zhang)  wrote:
>
> > There are no 2.0.0-alpha1 and 2.0.0-alpha2 tag on jira yet?
> >
> > 2017-06-09 5:36 GMT+08:00 Umesh Agashe :
> >
> > > +1
> > >
> > > - Downloaded the src tarball.
> > >   - Verified the checksums and signature. Looks good.
> > >   - Built from source. openjdk version "1.8.0_102"
> > >   - mvn apache-rat:check   Passed
> > >
> > > - Download the bin tarball.
> > >   - Verified the checksums and signature. Looks good.
> > >   - Extracted it. Layout looks good.
> > >   - Started a local instance. Ran the 'hbase shell' with some basic
> table
> > > commands. Looks good.
> > >   - Ran ltt with 10 million rows and 2 columns/ row
> > >
> > > Note:
> > >   - Did not run unit tests. There are a problems with the build. See:
> > > https://builds.apache.org/job/HBase-2.0/jdk=JDK%201.8%20(
> > > latest),label=Hadoop/10/console
> > >   - Noticed a few errors in the log file like:
> > > WARN  [MemStoreFlusher.1] io.FSDataInputStreamWrapper: Failed to invoke
> > > 'unbuffer' method in class class org.apache.hadoop.fs.
> FSDataInputStream
> > .
> > > So there may be a TCP socket connection left open in CLOSE_WAIT state.
> > >
> > >
> > > On Thu, Jun 8, 2017 at 8:33 AM, Stack  wrote:
> > >
> > > > On Thu, Jun 8, 2017 at 7:52 AM, Sean Busbey 
> wrote:
> > > >
> > > > > The minimum voting period is 72 hours for a PMC to bless a release.
> > > > > Can we aim for that?
> > > > >
> > > > >
> > > > Sure (Stickler!)
> > > > St.Ack
> > > >
> > > >
> > > >
> > > > > On Thu, Jun 8, 2017 at 2:33 AM, Stack  wrote:
> > > > > > The first release candidate for HBase 2.0.0-alpha-1 is up at:
> > > > > >
> > > > > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-
> > > alpha-1RC0/
> > > > > >
> > > > > > Maven artifacts are available from a staging directory here:
> > > > > >
> > > > > >  https://repository.apache.org/content/repositories/
> > > > orgapachehbase-1169
> > > > > >
> > > > > > All was signed w/ my key 8ACC93D2
> > > > > > 
> > > > > >
> > > > > > I tagged the RC as 2.0.0-alpha-1RC0
> > > > > > (c830a0f47f58d4892dd3300032c8244d6278aecc).
> > > > > >
> > > > > > hbase-2.0.0-alpha-1 will be our first 2.0.0 release. It is a
> rough
> > > cut
> > > > > > ('alpha') not-for-production preview of what hbase-2.0.0 will
> look
> > > > like.
> > > > > It
> > > > > > is what we used to call a 'Developer' release[1] meant mostly for
> > > devs
> > > > > and
> > > > > > downstreamers to test drive and flag us early if we there are
> > issues
> > > > > we’ve
> > > > > > missed ahead of our rolling a production-worthy release.
> > > > > >
> > > > > > hbase-2.0.0 includes a fleet of new features that include a new
> > > > > assignment
> > > > > > manager, means for keeping read and write path off-heap,
> in-memory
> > > > > > compactions, and more. I have been keeping a running doc on the
> > state
> > > > of
> > > > > > 2.0.0 here [2]. There is much to do still (see aforementioned
> doc).
> > > > > >
> > > > > > The list of features addressed in 2.0.0 so far can be found here
> > [4].
> > > > > There
> > > > > > are about 2500. The list of ~500 fixes in 2.0.0 exclusively can
> be
> > > > found
> > > > > > here [3].
> > > > > >
> > > > > > Please take it for a spin and vote on whether it ok to put out as
> > our
> > > > > first
> > > > > > alpha (bar is low for an 'alpha'). Let the VOTE be open for 24
> > hours.
> > > > > >
> > > > > > Thanks,
> > > > > > St.Ack
> > > > > >
> > > > > > 1. http://hbase.apache.org/book.html#hbase.versioning.pre10
> > > > > > 2.
> > > > > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > > > ktczrlKHK8N4SZzs/edit#heading=h.v21r9nz8g01j
> > > > > > 3.
> > > > > > https://issues.apache.org/jira/browse/HBASE-17852?jql=
> > > > > project%20%3D%20HBASE%20%20and%20fixVersion%20%3D%202.
> > > > > 0.0%20and%20fixVersion%20not%20in%20(1.0.0%2C%201.0.1%2C%
> > > > > 201.0.2%2C%201.0.3%2C%201.0.4%2C%201.0.5%2C%201.0.6%2C%201.
> > > > > 1.0%2C%201.1.1%2C%201.1.2%2C%201.1.3%2C%201.1.4%2C%201.1.5%
> > > > > 2C%201.1.6%2C%201.1.7%2C%201.1.8%2C%201.1.9%2C%201.1.10%2C%
> > > > > 201.2.0%2C%201.2.1%2C%201.2.2%2C%201.2.3%2C%201.2.4%2C%201.
> > > > > 2.5%2C%201.2.6%2C%201.3.0%2C%201.3.1%2C%201.4.0)%20and%20%
> > > > > 20(status%20%3D%20Open%20or%20status%20%3D%20%22Patch%
> > 20Available%22)
> > > > > > 4.
> > > > > >

Re: [VOTE] First hbase-2.0.0-alpha-1 Release Candidate is available

2017-06-08 Thread Stack 
Fixed. Thanks Duo. Added:

2.0.0-alpha-1
2.0.0-alpha-2
2.0.0-alpha-3
2.0.0-beta-1
2.0.0-beta-2

We can always delete if labels go unused.
St.Ack


On Thu, Jun 8, 2017 at 6:38 PM, 张铎(Duo Zhang)  wrote:

> There are no 2.0.0-alpha1 and 2.0.0-alpha2 tag on jira yet?
>
> 2017-06-09 5:36 GMT+08:00 Umesh Agashe :
>
> > +1
> >
> > - Downloaded the src tarball.
> >   - Verified the checksums and signature. Looks good.
> >   - Built from source. openjdk version "1.8.0_102"
> >   - mvn apache-rat:check   Passed
> >
> > - Download the bin tarball.
> >   - Verified the checksums and signature. Looks good.
> >   - Extracted it. Layout looks good.
> >   - Started a local instance. Ran the 'hbase shell' with some basic table
> > commands. Looks good.
> >   - Ran ltt with 10 million rows and 2 columns/ row
> >
> > Note:
> >   - Did not run unit tests. There are a problems with the build. See:
> > https://builds.apache.org/job/HBase-2.0/jdk=JDK%201.8%20(
> > latest),label=Hadoop/10/console
> >   - Noticed a few errors in the log file like:
> > WARN  [MemStoreFlusher.1] io.FSDataInputStreamWrapper: Failed to invoke
> > 'unbuffer' method in class class org.apache.hadoop.fs.FSDataInputStream
> .
> > So there may be a TCP socket connection left open in CLOSE_WAIT state.
> >
> >
> > On Thu, Jun 8, 2017 at 8:33 AM, Stack  wrote:
> >
> > > On Thu, Jun 8, 2017 at 7:52 AM, Sean Busbey  wrote:
> > >
> > > > The minimum voting period is 72 hours for a PMC to bless a release.
> > > > Can we aim for that?
> > > >
> > > >
> > > Sure (Stickler!)
> > > St.Ack
> > >
> > >
> > >
> > > > On Thu, Jun 8, 2017 at 2:33 AM, Stack  wrote:
> > > > > The first release candidate for HBase 2.0.0-alpha-1 is up at:
> > > > >
> > > > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-
> > alpha-1RC0/
> > > > >
> > > > > Maven artifacts are available from a staging directory here:
> > > > >
> > > > >  https://repository.apache.org/content/repositories/
> > > orgapachehbase-1169
> > > > >
> > > > > All was signed w/ my key 8ACC93D2
> > > > > 
> > > > >
> > > > > I tagged the RC as 2.0.0-alpha-1RC0
> > > > > (c830a0f47f58d4892dd3300032c8244d6278aecc).
> > > > >
> > > > > hbase-2.0.0-alpha-1 will be our first 2.0.0 release. It is a rough
> > cut
> > > > > ('alpha') not-for-production preview of what hbase-2.0.0 will look
> > > like.
> > > > It
> > > > > is what we used to call a 'Developer' release[1] meant mostly for
> > devs
> > > > and
> > > > > downstreamers to test drive and flag us early if we there are
> issues
> > > > we’ve
> > > > > missed ahead of our rolling a production-worthy release.
> > > > >
> > > > > hbase-2.0.0 includes a fleet of new features that include a new
> > > > assignment
> > > > > manager, means for keeping read and write path off-heap, in-memory
> > > > > compactions, and more. I have been keeping a running doc on the
> state
> > > of
> > > > > 2.0.0 here [2]. There is much to do still (see aforementioned doc).
> > > > >
> > > > > The list of features addressed in 2.0.0 so far can be found here
> [4].
> > > > There
> > > > > are about 2500. The list of ~500 fixes in 2.0.0 exclusively can be
> > > found
> > > > > here [3].
> > > > >
> > > > > Please take it for a spin and vote on whether it ok to put out as
> our
> > > > first
> > > > > alpha (bar is low for an 'alpha'). Let the VOTE be open for 24
> hours.
> > > > >
> > > > > Thanks,
> > > > > St.Ack
> > > > >
> > > > > 1. http://hbase.apache.org/book.html#hbase.versioning.pre10
> > > > > 2.
> > > > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > > ktczrlKHK8N4SZzs/edit#heading=h.v21r9nz8g01j
> > > > > 3.
> > > > > https://issues.apache.org/jira/browse/HBASE-17852?jql=
> > > > project%20%3D%20HBASE%20%20and%20fixVersion%20%3D%202.
> > > > 0.0%20and%20fixVersion%20not%20in%20(1.0.0%2C%201.0.1%2C%
> > > > 201.0.2%2C%201.0.3%2C%201.0.4%2C%201.0.5%2C%201.0.6%2C%201.
> > > > 1.0%2C%201.1.1%2C%201.1.2%2C%201.1.3%2C%201.1.4%2C%201.1.5%
> > > > 2C%201.1.6%2C%201.1.7%2C%201.1.8%2C%201.1.9%2C%201.1.10%2C%
> > > > 201.2.0%2C%201.2.1%2C%201.2.2%2C%201.2.3%2C%201.2.4%2C%201.
> > > > 2.5%2C%201.2.6%2C%201.3.0%2C%201.3.1%2C%201.4.0)%20and%20%
> > > > 20(status%20%3D%20Open%20or%20status%20%3D%20%22Patch%
> 20Available%22)
> > > > > 4.
> > > > > https://issues.apache.org/jira/browse/HBASE-18191?jql=
> > > > project%20%3D%20HBASE%20%20and%20(%20fixVersion%20%3D%
> > > > 202.0.0)%20and%20(status%20%3D%20Resolved)
> > > >
> > >
> >
>

Re: [VOTE] First hbase-2.0.0-alpha-1 Release Candidate is available

2017-06-08 Thread Stack 
Oh, maybe file issues for what you found boss?
St.Ack

On Thu, Jun 8, 2017 at 10:15 PM, Stack  wrote:

> Thanks Umesh!
>
> On Thu, Jun 8, 2017 at 2:36 PM, Umesh Agashe  wrote:
>
>> +1
>>
>> - Downloaded the src tarball.
>>   - Verified the checksums and signature. Looks good.
>>   - Built from source. openjdk version "1.8.0_102"
>>   - mvn apache-rat:check   Passed
>>
>> - Download the bin tarball.
>>   - Verified the checksums and signature. Looks good.
>>   - Extracted it. Layout looks good.
>>   - Started a local instance. Ran the 'hbase shell' with some basic table
>> commands. Looks good.
>>   - Ran ltt with 10 million rows and 2 columns/ row
>>
>> Note:
>>   - Did not run unit tests. There are a problems with the build. See:
>> https://builds.apache.org/job/HBase-2.0/jdk=JDK%201.8%20(lat
>> est),label=Hadoop/10/console
>>   - Noticed a few errors in the log file like:
>> WARN  [MemStoreFlusher.1] io.FSDataInputStreamWrapper: Failed to invoke
>> 'unbuffer' method in class class org.apache.hadoop.fs.FSDataInputStream .
>> So there may be a TCP socket connection left open in CLOSE_WAIT state.
>>
>>
>> On Thu, Jun 8, 2017 at 8:33 AM, Stack  wrote:
>>
>> > On Thu, Jun 8, 2017 at 7:52 AM, Sean Busbey  wrote:
>> >
>> > > The minimum voting period is 72 hours for a PMC to bless a release.
>> > > Can we aim for that?
>> > >
>> > >
>> > Sure (Stickler!)
>> > St.Ack
>> >
>> >
>> >
>> > > On Thu, Jun 8, 2017 at 2:33 AM, Stack  wrote:
>> > > > The first release candidate for HBase 2.0.0-alpha-1 is up at:
>> > > >
>> > > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alp
>> ha-1RC0/
>> > > >
>> > > > Maven artifacts are available from a staging directory here:
>> > > >
>> > > >  https://repository.apache.org/content/repositories/
>> > orgapachehbase-1169
>> > > >
>> > > > All was signed w/ my key 8ACC93D2
>> > > > 
>> > > >
>> > > > I tagged the RC as 2.0.0-alpha-1RC0
>> > > > (c830a0f47f58d4892dd3300032c8244d6278aecc).
>> > > >
>> > > > hbase-2.0.0-alpha-1 will be our first 2.0.0 release. It is a rough
>> cut
>> > > > ('alpha') not-for-production preview of what hbase-2.0.0 will look
>> > like.
>> > > It
>> > > > is what we used to call a 'Developer' release[1] meant mostly for
>> devs
>> > > and
>> > > > downstreamers to test drive and flag us early if we there are issues
>> > > we’ve
>> > > > missed ahead of our rolling a production-worthy release.
>> > > >
>> > > > hbase-2.0.0 includes a fleet of new features that include a new
>> > > assignment
>> > > > manager, means for keeping read and write path off-heap, in-memory
>> > > > compactions, and more. I have been keeping a running doc on the
>> state
>> > of
>> > > > 2.0.0 here [2]. There is much to do still (see aforementioned doc).
>> > > >
>> > > > The list of features addressed in 2.0.0 so far can be found here
>> [4].
>> > > There
>> > > > are about 2500. The list of ~500 fixes in 2.0.0 exclusively can be
>> > found
>> > > > here [3].
>> > > >
>> > > > Please take it for a spin and vote on whether it ok to put out as
>> our
>> > > first
>> > > > alpha (bar is low for an 'alpha'). Let the VOTE be open for 24
>> hours.
>> > > >
>> > > > Thanks,
>> > > > St.Ack
>> > > >
>> > > > 1. http://hbase.apache.org/book.html#hbase.versioning.pre10
>> > > > 2.
>> > > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
>> > > ktczrlKHK8N4SZzs/edit#heading=h.v21r9nz8g01j
>> > > > 3.
>> > > > https://issues.apache.org/jira/browse/HBASE-17852?jql=
>> > > project%20%3D%20HBASE%20%20and%20fixVersion%20%3D%202.
>> > > 0.0%20and%20fixVersion%20not%20in%20(1.0.0%2C%201.0.1%2C%
>> > > 201.0.2%2C%201.0.3%2C%201.0.4%2C%201.0.5%2C%201.0.6%2C%201.
>> > > 1.0%2C%201.1.1%2C%201.1.2%2C%201.1.3%2C%201.1.4%2C%201.1.5%
>> > > 2C%201.1.6%2C%201.1.7%2C%201.1.8%2C%201.1.9%2C%201.1.10%2C%
>> > > 201.2.0%2C%201.2.1%2C%201.2.2%2C%201.2.3%2C%201.2.4%2C%201.
>> > > 2.5%2C%201.2.6%2C%201.3.0%2C%201.3.1%2C%201.4.0)%20and%20%
>> > > 20(status%20%3D%20Open%20or%20status%20%3D%20%22Patch%20Available%22)
>> > > > 4.
>> > > > https://issues.apache.org/jira/browse/HBASE-18191?jql=
>> > > project%20%3D%20HBASE%20%20and%20(%20fixVersion%20%3D%
>> > > 202.0.0)%20and%20(status%20%3D%20Resolved)
>> > >
>> >
>>
>
>

Re: [VOTE] First hbase-2.0.0-alpha-1 Release Candidate is available

2017-06-08 Thread Stack 
Thanks Umesh!

On Thu, Jun 8, 2017 at 2:36 PM, Umesh Agashe  wrote:

> +1
>
> - Downloaded the src tarball.
>   - Verified the checksums and signature. Looks good.
>   - Built from source. openjdk version "1.8.0_102"
>   - mvn apache-rat:check   Passed
>
> - Download the bin tarball.
>   - Verified the checksums and signature. Looks good.
>   - Extracted it. Layout looks good.
>   - Started a local instance. Ran the 'hbase shell' with some basic table
> commands. Looks good.
>   - Ran ltt with 10 million rows and 2 columns/ row
>
> Note:
>   - Did not run unit tests. There are a problems with the build. See:
> https://builds.apache.org/job/HBase-2.0/jdk=JDK%201.8%20(
> latest),label=Hadoop/10/console
>   - Noticed a few errors in the log file like:
> WARN  [MemStoreFlusher.1] io.FSDataInputStreamWrapper: Failed to invoke
> 'unbuffer' method in class class org.apache.hadoop.fs.FSDataInputStream .
> So there may be a TCP socket connection left open in CLOSE_WAIT state.
>
>
> On Thu, Jun 8, 2017 at 8:33 AM, Stack  wrote:
>
> > On Thu, Jun 8, 2017 at 7:52 AM, Sean Busbey  wrote:
> >
> > > The minimum voting period is 72 hours for a PMC to bless a release.
> > > Can we aim for that?
> > >
> > >
> > Sure (Stickler!)
> > St.Ack
> >
> >
> >
> > > On Thu, Jun 8, 2017 at 2:33 AM, Stack  wrote:
> > > > The first release candidate for HBase 2.0.0-alpha-1 is up at:
> > > >
> > > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-
> alpha-1RC0/
> > > >
> > > > Maven artifacts are available from a staging directory here:
> > > >
> > > >  https://repository.apache.org/content/repositories/
> > orgapachehbase-1169
> > > >
> > > > All was signed w/ my key 8ACC93D2
> > > > 
> > > >
> > > > I tagged the RC as 2.0.0-alpha-1RC0
> > > > (c830a0f47f58d4892dd3300032c8244d6278aecc).
> > > >
> > > > hbase-2.0.0-alpha-1 will be our first 2.0.0 release. It is a rough
> cut
> > > > ('alpha') not-for-production preview of what hbase-2.0.0 will look
> > like.
> > > It
> > > > is what we used to call a 'Developer' release[1] meant mostly for
> devs
> > > and
> > > > downstreamers to test drive and flag us early if we there are issues
> > > we’ve
> > > > missed ahead of our rolling a production-worthy release.
> > > >
> > > > hbase-2.0.0 includes a fleet of new features that include a new
> > > assignment
> > > > manager, means for keeping read and write path off-heap, in-memory
> > > > compactions, and more. I have been keeping a running doc on the state
> > of
> > > > 2.0.0 here [2]. There is much to do still (see aforementioned doc).
> > > >
> > > > The list of features addressed in 2.0.0 so far can be found here [4].
> > > There
> > > > are about 2500. The list of ~500 fixes in 2.0.0 exclusively can be
> > found
> > > > here [3].
> > > >
> > > > Please take it for a spin and vote on whether it ok to put out as our
> > > first
> > > > alpha (bar is low for an 'alpha'). Let the VOTE be open for 24 hours.
> > > >
> > > > Thanks,
> > > > St.Ack
> > > >
> > > > 1. http://hbase.apache.org/book.html#hbase.versioning.pre10
> > > > 2.
> > > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > ktczrlKHK8N4SZzs/edit#heading=h.v21r9nz8g01j
> > > > 3.
> > > > https://issues.apache.org/jira/browse/HBASE-17852?jql=
> > > project%20%3D%20HBASE%20%20and%20fixVersion%20%3D%202.
> > > 0.0%20and%20fixVersion%20not%20in%20(1.0.0%2C%201.0.1%2C%
> > > 201.0.2%2C%201.0.3%2C%201.0.4%2C%201.0.5%2C%201.0.6%2C%201.
> > > 1.0%2C%201.1.1%2C%201.1.2%2C%201.1.3%2C%201.1.4%2C%201.1.5%
> > > 2C%201.1.6%2C%201.1.7%2C%201.1.8%2C%201.1.9%2C%201.1.10%2C%
> > > 201.2.0%2C%201.2.1%2C%201.2.2%2C%201.2.3%2C%201.2.4%2C%201.
> > > 2.5%2C%201.2.6%2C%201.3.0%2C%201.3.1%2C%201.4.0)%20and%20%
> > > 20(status%20%3D%20Open%20or%20status%20%3D%20%22Patch%20Available%22)
> > > > 4.
> > > > https://issues.apache.org/jira/browse/HBASE-18191?jql=
> > > project%20%3D%20HBASE%20%20and%20(%20fixVersion%20%3D%
> > > 202.0.0)%20and%20(status%20%3D%20Resolved)
> > >
> >
>

Re: [ANNOUNCE] New HBase committer Allan Yang

2017-06-08 Thread Stack 
Hurray!

On Thu, Jun 8, 2017 at 8:49 PM, Yu Li  wrote:

> On behalf of the Apache HBase PMC, I am pleased to announce that Allan Yang
> has accepted the PMC's invitation to become a committer on the
> project. We appreciate all of Allan's generous contributions thus far and
> look forward to his continued involvement.
>
> Congratulations and welcome, Allan!
>

Re: [ANNOUNCE] New HBase committer Allan Yang

2017-06-08 Thread Phil Yang 
Congratulations!

Thanks,
Phil


2017-06-09 12:13 GMT+08:00 Anoop John :

> Congrats Allan..   Welcome !!
>
> -Anoop-
>
> On Fri, Jun 9, 2017 at 9:27 AM, 张铎(Duo Zhang) 
> wrote:
> > Congratulations!
> >
> > 2017-06-09 11:55 GMT+08:00 Ted Yu :
> >
> >> Congratulations, Allan !
> >>
> >> On Thu, Jun 8, 2017 at 8:49 PM, Yu Li  wrote:
> >>
> >> > On behalf of the Apache HBase PMC, I am pleased to announce that Allan
> >> Yang
> >> > has accepted the PMC's invitation to become a committer on the
> >> > project. We appreciate all of Allan's generous contributions thus far
> and
> >> > look forward to his continued involvement.
> >> >
> >> > Congratulations and welcome, Allan!
> >> >
> >>
>

Re: [ANNOUNCE] New HBase committer Allan Yang

2017-06-08 Thread Anoop John 
Congrats Allan..   Welcome !!

-Anoop-

On Fri, Jun 9, 2017 at 9:27 AM, 张铎(Duo Zhang)  wrote:
> Congratulations!
>
> 2017-06-09 11:55 GMT+08:00 Ted Yu :
>
>> Congratulations, Allan !
>>
>> On Thu, Jun 8, 2017 at 8:49 PM, Yu Li  wrote:
>>
>> > On behalf of the Apache HBase PMC, I am pleased to announce that Allan
>> Yang
>> > has accepted the PMC's invitation to become a committer on the
>> > project. We appreciate all of Allan's generous contributions thus far and
>> > look forward to his continued involvement.
>> >
>> > Congratulations and welcome, Allan!
>> >
>>

Re: [VOTE] First hbase-2.0.0-alpha-1 Release Candidate is available

2017-06-08 Thread Yu Li 
Bravo! Our first branch-2 RC! Will try my best to vote in time.

Minor: the 4th reference (new features) seems incorrect, should be the
below one?:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20HBASE%20%20and%20(%20fixVersion%20%3D%202.0.0)%20and%20(status%20%3D%20Resolved)%20and%20(type%20%3D%20%22New%20Feature%22)

Best Regards,
Yu

On 9 June 2017 at 09:38, 张铎(Duo Zhang)  wrote:

> There are no 2.0.0-alpha1 and 2.0.0-alpha2 tag on jira yet?
>
> 2017-06-09 5:36 GMT+08:00 Umesh Agashe :
>
> > +1
> >
> > - Downloaded the src tarball.
> >   - Verified the checksums and signature. Looks good.
> >   - Built from source. openjdk version "1.8.0_102"
> >   - mvn apache-rat:check   Passed
> >
> > - Download the bin tarball.
> >   - Verified the checksums and signature. Looks good.
> >   - Extracted it. Layout looks good.
> >   - Started a local instance. Ran the 'hbase shell' with some basic table
> > commands. Looks good.
> >   - Ran ltt with 10 million rows and 2 columns/ row
> >
> > Note:
> >   - Did not run unit tests. There are a problems with the build. See:
> > https://builds.apache.org/job/HBase-2.0/jdk=JDK%201.8%20(
> > latest),label=Hadoop/10/console
> >   - Noticed a few errors in the log file like:
> > WARN  [MemStoreFlusher.1] io.FSDataInputStreamWrapper: Failed to invoke
> > 'unbuffer' method in class class org.apache.hadoop.fs.FSDataInputStream
> .
> > So there may be a TCP socket connection left open in CLOSE_WAIT state.
> >
> >
> > On Thu, Jun 8, 2017 at 8:33 AM, Stack  wrote:
> >
> > > On Thu, Jun 8, 2017 at 7:52 AM, Sean Busbey  wrote:
> > >
> > > > The minimum voting period is 72 hours for a PMC to bless a release.
> > > > Can we aim for that?
> > > >
> > > >
> > > Sure (Stickler!)
> > > St.Ack
> > >
> > >
> > >
> > > > On Thu, Jun 8, 2017 at 2:33 AM, Stack  wrote:
> > > > > The first release candidate for HBase 2.0.0-alpha-1 is up at:
> > > > >
> > > > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-
> > alpha-1RC0/
> > > > >
> > > > > Maven artifacts are available from a staging directory here:
> > > > >
> > > > >  https://repository.apache.org/content/repositories/
> > > orgapachehbase-1169
> > > > >
> > > > > All was signed w/ my key 8ACC93D2
> > > > > 
> > > > >
> > > > > I tagged the RC as 2.0.0-alpha-1RC0
> > > > > (c830a0f47f58d4892dd3300032c8244d6278aecc).
> > > > >
> > > > > hbase-2.0.0-alpha-1 will be our first 2.0.0 release. It is a rough
> > cut
> > > > > ('alpha') not-for-production preview of what hbase-2.0.0 will look
> > > like.
> > > > It
> > > > > is what we used to call a 'Developer' release[1] meant mostly for
> > devs
> > > > and
> > > > > downstreamers to test drive and flag us early if we there are
> issues
> > > > we’ve
> > > > > missed ahead of our rolling a production-worthy release.
> > > > >
> > > > > hbase-2.0.0 includes a fleet of new features that include a new
> > > > assignment
> > > > > manager, means for keeping read and write path off-heap, in-memory
> > > > > compactions, and more. I have been keeping a running doc on the
> state
> > > of
> > > > > 2.0.0 here [2]. There is much to do still (see aforementioned doc).
> > > > >
> > > > > The list of features addressed in 2.0.0 so far can be found here
> [4].
> > > > There
> > > > > are about 2500. The list of ~500 fixes in 2.0.0 exclusively can be
> > > found
> > > > > here [3].
> > > > >
> > > > > Please take it for a spin and vote on whether it ok to put out as
> our
> > > > first
> > > > > alpha (bar is low for an 'alpha'). Let the VOTE be open for 24
> hours.
> > > > >
> > > > > Thanks,
> > > > > St.Ack
> > > > >
> > > > > 1. http://hbase.apache.org/book.html#hbase.versioning.pre10
> > > > > 2.
> > > > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > > ktczrlKHK8N4SZzs/edit#heading=h.v21r9nz8g01j
> > > > > 3.
> > > > > https://issues.apache.org/jira/browse/HBASE-17852?jql=
> > > > project%20%3D%20HBASE%20%20and%20fixVersion%20%3D%202.
> > > > 0.0%20and%20fixVersion%20not%20in%20(1.0.0%2C%201.0.1%2C%
> > > > 201.0.2%2C%201.0.3%2C%201.0.4%2C%201.0.5%2C%201.0.6%2C%201.
> > > > 1.0%2C%201.1.1%2C%201.1.2%2C%201.1.3%2C%201.1.4%2C%201.1.5%
> > > > 2C%201.1.6%2C%201.1.7%2C%201.1.8%2C%201.1.9%2C%201.1.10%2C%
> > > > 201.2.0%2C%201.2.1%2C%201.2.2%2C%201.2.3%2C%201.2.4%2C%201.
> > > > 2.5%2C%201.2.6%2C%201.3.0%2C%201.3.1%2C%201.4.0)%20and%20%
> > > > 20(status%20%3D%20Open%20or%20status%20%3D%20%22Patch%
> 20Available%22)
> > > > > 4.
> > > > > https://issues.apache.org/jira/browse/HBASE-18191?jql=
> > > > project%20%3D%20HBASE%20%20and%20(%20fixVersion%20%3D%
> > > > 202.0.0)%20and%20(status%20%3D%20Resolved)
> > > >
> > >
> >
>

Re: [ANNOUNCE] New HBase committer Allan Yang

2017-06-08 Thread Duo Zhang 
Congratulations!

2017-06-09 11:55 GMT+08:00 Ted Yu :

> Congratulations, Allan !
>
> On Thu, Jun 8, 2017 at 8:49 PM, Yu Li  wrote:
>
> > On behalf of the Apache HBase PMC, I am pleased to announce that Allan
> Yang
> > has accepted the PMC's invitation to become a committer on the
> > project. We appreciate all of Allan's generous contributions thus far and
> > look forward to his continued involvement.
> >
> > Congratulations and welcome, Allan!
> >
>

Re: [ANNOUNCE] New HBase committer Allan Yang

2017-06-08 Thread Ted Yu 
Congratulations, Allan !

On Thu, Jun 8, 2017 at 8:49 PM, Yu Li  wrote:

> On behalf of the Apache HBase PMC, I am pleased to announce that Allan Yang
> has accepted the PMC's invitation to become a committer on the
> project. We appreciate all of Allan's generous contributions thus far and
> look forward to his continued involvement.
>
> Congratulations and welcome, Allan!
>

[ANNOUNCE] New HBase committer Allan Yang

2017-06-08 Thread Yu Li 
On behalf of the Apache HBase PMC, I am pleased to announce that Allan Yang
has accepted the PMC's invitation to become a committer on the
project. We appreciate all of Allan's generous contributions thus far and
look forward to his continued involvement.

Congratulations and welcome, Allan!

[jira] [Created] (HBASE-18196) Fix historical FindBugs/Javadoc issues in branch-1.1

2017-06-08 Thread Zheng Hu (JIRA) 
Zheng Hu created HBASE-18196:


 Summary: Fix historical FindBugs/Javadoc issues in branch-1.1 
 Key: HBASE-18196
 URL: https://issues.apache.org/jira/browse/HBASE-18196
 Project: HBase
  Issue Type: Improvement
Reporter: Zheng Hu
Priority: Minor


See  
https://issues.apache.org/jira/browse/HBASE-17678?focusedCommentId=16042572=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16042572



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [VOTE] First hbase-2.0.0-alpha-1 Release Candidate is available

2017-06-08 Thread Duo Zhang 
There are no 2.0.0-alpha1 and 2.0.0-alpha2 tag on jira yet?

2017-06-09 5:36 GMT+08:00 Umesh Agashe :

> +1
>
> - Downloaded the src tarball.
>   - Verified the checksums and signature. Looks good.
>   - Built from source. openjdk version "1.8.0_102"
>   - mvn apache-rat:check   Passed
>
> - Download the bin tarball.
>   - Verified the checksums and signature. Looks good.
>   - Extracted it. Layout looks good.
>   - Started a local instance. Ran the 'hbase shell' with some basic table
> commands. Looks good.
>   - Ran ltt with 10 million rows and 2 columns/ row
>
> Note:
>   - Did not run unit tests. There are a problems with the build. See:
> https://builds.apache.org/job/HBase-2.0/jdk=JDK%201.8%20(
> latest),label=Hadoop/10/console
>   - Noticed a few errors in the log file like:
> WARN  [MemStoreFlusher.1] io.FSDataInputStreamWrapper: Failed to invoke
> 'unbuffer' method in class class org.apache.hadoop.fs.FSDataInputStream .
> So there may be a TCP socket connection left open in CLOSE_WAIT state.
>
>
> On Thu, Jun 8, 2017 at 8:33 AM, Stack  wrote:
>
> > On Thu, Jun 8, 2017 at 7:52 AM, Sean Busbey  wrote:
> >
> > > The minimum voting period is 72 hours for a PMC to bless a release.
> > > Can we aim for that?
> > >
> > >
> > Sure (Stickler!)
> > St.Ack
> >
> >
> >
> > > On Thu, Jun 8, 2017 at 2:33 AM, Stack  wrote:
> > > > The first release candidate for HBase 2.0.0-alpha-1 is up at:
> > > >
> > > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-
> alpha-1RC0/
> > > >
> > > > Maven artifacts are available from a staging directory here:
> > > >
> > > >  https://repository.apache.org/content/repositories/
> > orgapachehbase-1169
> > > >
> > > > All was signed w/ my key 8ACC93D2
> > > > 
> > > >
> > > > I tagged the RC as 2.0.0-alpha-1RC0
> > > > (c830a0f47f58d4892dd3300032c8244d6278aecc).
> > > >
> > > > hbase-2.0.0-alpha-1 will be our first 2.0.0 release. It is a rough
> cut
> > > > ('alpha') not-for-production preview of what hbase-2.0.0 will look
> > like.
> > > It
> > > > is what we used to call a 'Developer' release[1] meant mostly for
> devs
> > > and
> > > > downstreamers to test drive and flag us early if we there are issues
> > > we’ve
> > > > missed ahead of our rolling a production-worthy release.
> > > >
> > > > hbase-2.0.0 includes a fleet of new features that include a new
> > > assignment
> > > > manager, means for keeping read and write path off-heap, in-memory
> > > > compactions, and more. I have been keeping a running doc on the state
> > of
> > > > 2.0.0 here [2]. There is much to do still (see aforementioned doc).
> > > >
> > > > The list of features addressed in 2.0.0 so far can be found here [4].
> > > There
> > > > are about 2500. The list of ~500 fixes in 2.0.0 exclusively can be
> > found
> > > > here [3].
> > > >
> > > > Please take it for a spin and vote on whether it ok to put out as our
> > > first
> > > > alpha (bar is low for an 'alpha'). Let the VOTE be open for 24 hours.
> > > >
> > > > Thanks,
> > > > St.Ack
> > > >
> > > > 1. http://hbase.apache.org/book.html#hbase.versioning.pre10
> > > > 2.
> > > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > > ktczrlKHK8N4SZzs/edit#heading=h.v21r9nz8g01j
> > > > 3.
> > > > https://issues.apache.org/jira/browse/HBASE-17852?jql=
> > > project%20%3D%20HBASE%20%20and%20fixVersion%20%3D%202.
> > > 0.0%20and%20fixVersion%20not%20in%20(1.0.0%2C%201.0.1%2C%
> > > 201.0.2%2C%201.0.3%2C%201.0.4%2C%201.0.5%2C%201.0.6%2C%201.
> > > 1.0%2C%201.1.1%2C%201.1.2%2C%201.1.3%2C%201.1.4%2C%201.1.5%
> > > 2C%201.1.6%2C%201.1.7%2C%201.1.8%2C%201.1.9%2C%201.1.10%2C%
> > > 201.2.0%2C%201.2.1%2C%201.2.2%2C%201.2.3%2C%201.2.4%2C%201.
> > > 2.5%2C%201.2.6%2C%201.3.0%2C%201.3.1%2C%201.4.0)%20and%20%
> > > 20(status%20%3D%20Open%20or%20status%20%3D%20%22Patch%20Available%22)
> > > > 4.
> > > > https://issues.apache.org/jira/browse/HBASE-18191?jql=
> > > project%20%3D%20HBASE%20%20and%20(%20fixVersion%20%3D%
> > > 202.0.0)%20and%20(status%20%3D%20Resolved)
> > >
> >
>

[jira] [Resolved] (HBASE-18037) Do not expose implementation classes to CP

2017-06-08 Thread Duo Zhang (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-18037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang resolved HBASE-18037.
---
   Resolution: Fixed
 Assignee: Duo Zhang
Fix Version/s: 3.0.0

Resolve as all sub tasks have been resolved.

> Do not expose implementation classes to CP
> --
>
> Key: HBASE-18037
> URL: https://issues.apache.org/jira/browse/HBASE-18037
> Project: HBase
>  Issue Type: Umbrella
>  Components: Coprocessors
>Affects Versions: 2.0.0
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 2.0.0, 3.0.0
>
>
> For example, StoreFile. Expose the implementation classes to CP will make it 
> harder to implement new features or improve the old implementation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Proposal for HBASE-16415 (Replication in different namespace)

2017-06-08 Thread Ted Yu 
Mind putting the below proposal on HBASE-16415 ?

Thanks

On Thu, Jun 8, 2017 at 3:24 PM, Jan Kunigk  wrote:

> Hi, with regards to the above JIRA I would like to make the following
> contribution.
> I am looking very much forward to feedback and comments.
>
> ReplicationSourceWALReaderThread continuously follows WALEntries to be
> replicated for a specified WAL via WAL.Reader's next() method and adds them
> to WALEntryBatches
>
> As far as I can see, those WALEntries are copies of the originally
> persisted local WALs. In order to direct these Entries to TableNames,
> different to the source, I propose to intercept the copied WALEntries on
> the source cluster and probe if they belong to a TableName, which is to be
> re-written.
>
> If such a probe is successful, then the WALKey of any such WALEntry needs
> to be changed accordingly. WALKey provides a getTableName() method, but
> currently not a setTableName() method, which would simply have to be added
> to change the private TableName member.
>
> I propose to intercept the entries via a new method redirectEntry(), which
> is invoked shortly before the entry is added to its WALEntryBatch and
> immediately after the entry has been filtered by filterEntry() like so:
>
> Entry entry = entryStream.next();
> if (updateSerialReplPos(batch, entry)) {
>   batch.lastWalPosition = entryStream.getPosition();
>   break;
> }
> entry = filterEntry(entry);
> entry = redirectEntry(entry); // <--
> if (entry != null) {
>   WALEdit edit = entry.getEdit();
>   if (edit != null && !edit.isEmpty()) {
> long entrySize = getEntrySize(entry);
> batch.addEntry(entry);
>
> redirectEntry() bases its decisions on a 'Map
> redirections', where the keys are the source table name and the values the
> destination table name. The Map would be included in the
> ReplicationPeerConfig, which can be obtained from within
> ReplicationSourceWALReaderThread via the instance of
> ReplicationSourceManager, which is in turn passed as an argument to both
> available constructors.
>
> When a TableName object from a WALKey from the WALEntryStream matches the
> key of any of the entries in the redirections map, that WALKey's TableName
> is replaced by the the value of that entry.
>
> The rationale for intercepting on the sending side is that the setup and
> peer management is performed on the source today already and there is no
> mechanism I can see which would carry the redirection rules themselves
> across.
>
> Similarly to the way that the hbase shell allows to specify the tables and
> column families to be replicated (set_peer_table_CFs), I propose a new
> command (also on the sending side) 'set_peer_table_redirections', which
> accepts a map of Strings, corresponding to the required final specification
> of the redirections as TableNames:
>
> set_peer_redirections['ns_source1:table_source1' : 'ns_dest1:table_dest1',
> 'ns_source2:table_source2' : 'ns_dest2:table_dest2', ...
> 'ns_sourcen:table_sourcen' : 'ns_destn:table_destn', ]
>
> Thanks, best, J
>

Proposal for HBASE-16415 (Replication in different namespace)

2017-06-08 Thread Jan Kunigk 
Hi, with regards to the above JIRA I would like to make the following
contribution.
I am looking very much forward to feedback and comments.

ReplicationSourceWALReaderThread continuously follows WALEntries to be
replicated for a specified WAL via WAL.Reader's next() method and adds them
to WALEntryBatches

As far as I can see, those WALEntries are copies of the originally
persisted local WALs. In order to direct these Entries to TableNames,
different to the source, I propose to intercept the copied WALEntries on
the source cluster and probe if they belong to a TableName, which is to be
re-written.

If such a probe is successful, then the WALKey of any such WALEntry needs
to be changed accordingly. WALKey provides a getTableName() method, but
currently not a setTableName() method, which would simply have to be added
to change the private TableName member.

I propose to intercept the entries via a new method redirectEntry(), which
is invoked shortly before the entry is added to its WALEntryBatch and
immediately after the entry has been filtered by filterEntry() like so:

Entry entry = entryStream.next();
if (updateSerialReplPos(batch, entry)) {
  batch.lastWalPosition = entryStream.getPosition();
  break;
}
entry = filterEntry(entry);
entry = redirectEntry(entry); // <--
if (entry != null) {
  WALEdit edit = entry.getEdit();
  if (edit != null && !edit.isEmpty()) {
long entrySize = getEntrySize(entry);
batch.addEntry(entry);

redirectEntry() bases its decisions on a 'Map
redirections', where the keys are the source table name and the values the
destination table name. The Map would be included in the
ReplicationPeerConfig, which can be obtained from within
ReplicationSourceWALReaderThread via the instance of
ReplicationSourceManager, which is in turn passed as an argument to both
available constructors.

When a TableName object from a WALKey from the WALEntryStream matches the
key of any of the entries in the redirections map, that WALKey's TableName
is replaced by the the value of that entry.

The rationale for intercepting on the sending side is that the setup and
peer management is performed on the source today already and there is no
mechanism I can see which would carry the redirection rules themselves
across.

Similarly to the way that the hbase shell allows to specify the tables and
column families to be replicated (set_peer_table_CFs), I propose a new
command (also on the sending side) 'set_peer_table_redirections', which
accepts a map of Strings, corresponding to the required final specification
of the redirections as TableNames:

set_peer_redirections['ns_source1:table_source1' : 'ns_dest1:table_dest1',
'ns_source2:table_source2' : 'ns_dest2:table_dest2', ...
'ns_sourcen:table_sourcen' : 'ns_destn:table_destn', ]

Thanks, best, J

[jira] [Created] (HBASE-18195) Remove redundant single quote from start message for HMaster and HRegionServer

2017-06-08 Thread Umesh Agashe (JIRA) 
Umesh Agashe created HBASE-18195:


 Summary: Remove redundant single quote from start message for 
HMaster and HRegionServer
 Key: HBASE-18195
 URL: https://issues.apache.org/jira/browse/HBASE-18195
 Project: HBase
  Issue Type: Bug
  Components: master, regionserver
Reporter: Umesh Agashe
Assignee: Umesh Agashe
Priority: Minor


Message in the log shows up as:
{code}
INFO  [main] master.HMaster: STARTING service 'HMaster
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [VOTE] First hbase-2.0.0-alpha-1 Release Candidate is available

2017-06-08 Thread Umesh Agashe 
+1

- Downloaded the src tarball.
  - Verified the checksums and signature. Looks good.
  - Built from source. openjdk version "1.8.0_102"
  - mvn apache-rat:check   Passed

- Download the bin tarball.
  - Verified the checksums and signature. Looks good.
  - Extracted it. Layout looks good.
  - Started a local instance. Ran the 'hbase shell' with some basic table
commands. Looks good.
  - Ran ltt with 10 million rows and 2 columns/ row

Note:
  - Did not run unit tests. There are a problems with the build. See:
https://builds.apache.org/job/HBase-2.0/jdk=JDK%201.8%20(latest),label=Hadoop/10/console
  - Noticed a few errors in the log file like:
WARN  [MemStoreFlusher.1] io.FSDataInputStreamWrapper: Failed to invoke
'unbuffer' method in class class org.apache.hadoop.fs.FSDataInputStream .
So there may be a TCP socket connection left open in CLOSE_WAIT state.


On Thu, Jun 8, 2017 at 8:33 AM, Stack  wrote:

> On Thu, Jun 8, 2017 at 7:52 AM, Sean Busbey  wrote:
>
> > The minimum voting period is 72 hours for a PMC to bless a release.
> > Can we aim for that?
> >
> >
> Sure (Stickler!)
> St.Ack
>
>
>
> > On Thu, Jun 8, 2017 at 2:33 AM, Stack  wrote:
> > > The first release candidate for HBase 2.0.0-alpha-1 is up at:
> > >
> > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha-1RC0/
> > >
> > > Maven artifacts are available from a staging directory here:
> > >
> > >  https://repository.apache.org/content/repositories/
> orgapachehbase-1169
> > >
> > > All was signed w/ my key 8ACC93D2
> > > 
> > >
> > > I tagged the RC as 2.0.0-alpha-1RC0
> > > (c830a0f47f58d4892dd3300032c8244d6278aecc).
> > >
> > > hbase-2.0.0-alpha-1 will be our first 2.0.0 release. It is a rough cut
> > > ('alpha') not-for-production preview of what hbase-2.0.0 will look
> like.
> > It
> > > is what we used to call a 'Developer' release[1] meant mostly for devs
> > and
> > > downstreamers to test drive and flag us early if we there are issues
> > we’ve
> > > missed ahead of our rolling a production-worthy release.
> > >
> > > hbase-2.0.0 includes a fleet of new features that include a new
> > assignment
> > > manager, means for keeping read and write path off-heap, in-memory
> > > compactions, and more. I have been keeping a running doc on the state
> of
> > > 2.0.0 here [2]. There is much to do still (see aforementioned doc).
> > >
> > > The list of features addressed in 2.0.0 so far can be found here [4].
> > There
> > > are about 2500. The list of ~500 fixes in 2.0.0 exclusively can be
> found
> > > here [3].
> > >
> > > Please take it for a spin and vote on whether it ok to put out as our
> > first
> > > alpha (bar is low for an 'alpha'). Let the VOTE be open for 24 hours.
> > >
> > > Thanks,
> > > St.Ack
> > >
> > > 1. http://hbase.apache.org/book.html#hbase.versioning.pre10
> > > 2.
> > > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> > ktczrlKHK8N4SZzs/edit#heading=h.v21r9nz8g01j
> > > 3.
> > > https://issues.apache.org/jira/browse/HBASE-17852?jql=
> > project%20%3D%20HBASE%20%20and%20fixVersion%20%3D%202.
> > 0.0%20and%20fixVersion%20not%20in%20(1.0.0%2C%201.0.1%2C%
> > 201.0.2%2C%201.0.3%2C%201.0.4%2C%201.0.5%2C%201.0.6%2C%201.
> > 1.0%2C%201.1.1%2C%201.1.2%2C%201.1.3%2C%201.1.4%2C%201.1.5%
> > 2C%201.1.6%2C%201.1.7%2C%201.1.8%2C%201.1.9%2C%201.1.10%2C%
> > 201.2.0%2C%201.2.1%2C%201.2.2%2C%201.2.3%2C%201.2.4%2C%201.
> > 2.5%2C%201.2.6%2C%201.3.0%2C%201.3.1%2C%201.4.0)%20and%20%
> > 20(status%20%3D%20Open%20or%20status%20%3D%20%22Patch%20Available%22)
> > > 4.
> > > https://issues.apache.org/jira/browse/HBASE-18191?jql=
> > project%20%3D%20HBASE%20%20and%20(%20fixVersion%20%3D%
> > 202.0.0)%20and%20(status%20%3D%20Resolved)
> >
>

Re: HBaseCon2017 Registration is now Open!

2017-06-08 Thread Stack 
On Thu, Jun 8, 2017 at 12:16 PM, Stack  wrote:

> On Thu, Jun 8, 2017 at 11:47 AM, Vladimir Rodionov  > wrote:
>
>> >>We'll do a hard-core press before the event so that those who are unable
>> to
>> >> attend actually relinquish their spots for the likes of yourself.
>>
>>  You take my spot. I won't be able to attend conf next week
>>
>> This is tough. Google require picture-id to go along w/ registration
> (Stephen, you might have a hard time passing as Vlad).
>
> Please relinquish your spots if you are unable to attend. There are a
> bunch on the waiting list.
>
>
And the earlier this is done, the more likely someone else will actually
attend (Giving up your spot Sunday night will probably mean the spot goes
unused).

Thanks,
S



> Let me ask about broadcast
>
> St.Ack
>
>
>
>> -Vlad
>>
>> On Thu, Jun 8, 2017 at 11:29 AM, Stephen Jiang 
>> wrote:
>>
>> > Last year's PhoenixCon live stream the talk.
>> >
>> > In the past, people paid entry fee to come to HBaseCon, so I understand
>> > that the recording would be delayed.  This year, the conference is free
>> > (thanks to Google), I just wonder whether live stream the talks is
>> possible
>> > (or considered).
>> >
>> > Thanks
>> > Stephen
>> >
>> > On Thu, Apr 20, 2017 at 10:36 AM, Stack  wrote:
>> >
>> > > On Thu, Apr 20, 2017 at 10:08 AM, clara xiong 
>> > > wrote:
>> > >
>> > > > Hi Stack,
>> > > >
>> > > > I was a bit late and it is sold out now. Is there anyway to get in
>> as
>> > > > standby?
>> > > >
>> > > >
>> > > Yes, its full but for sure sign up. You'll be added to the waiting
>> list.
>> > >
>> > > We'll do a hard-core press before the event so that those who are
>> unable
>> > to
>> > > attend actually relinquish their spots for the likes of yourself.
>> > >
>> > > St.Ack
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > > Thanks.
>> > > >
>> > > > On Tue, Mar 28, 2017 at 12:43 PM, stack  wrote:
>> > > >
>> > > > > The HBaseCon West 2017 registration website is up [1].
>> Registration
>> > is
>> > > > > no-charge (Courtesy of our gracious hosts). Space is limited so be
>> > sure
>> > > > to
>> > > > > register early (This means YOU!, the HBase Community). Note,
>> HBaseCon
>> > > > will
>> > > > > be in Mountain View @ Google, NOT in San Francisco, on June 12th
>> (The
>> > > day
>> > > > > before DataWorks Summit, San Jose)
>> > > > >
>> > > > > The CfP is still open [2]. It closes April 24th so get those talks
>> > in;
>> > > > we'd
>> > > > > love to hear from you.
>> > > > >
>> > > > > Yours,
>> > > > > The HBaseCon2017 Program Committee
>> > > > >
>> > > > > 1. Visit hbasecon.com and you will be redirected to eventbrite
>> > > > > 2. https://easychair.org/cfp/hbasecon2017
>> > > > >
>> > > >
>> > >
>> >
>>
>
>

Re: HBaseCon2017 Registration is now Open!

2017-06-08 Thread Vladimir Rodionov 
>>We'll do a hard-core press before the event so that those who are unable
to
>> attend actually relinquish their spots for the likes of yourself.

 You take my spot. I won't be able to attend conf next week

-Vlad

On Thu, Jun 8, 2017 at 11:29 AM, Stephen Jiang 
wrote:

> Last year's PhoenixCon live stream the talk.
>
> In the past, people paid entry fee to come to HBaseCon, so I understand
> that the recording would be delayed.  This year, the conference is free
> (thanks to Google), I just wonder whether live stream the talks is possible
> (or considered).
>
> Thanks
> Stephen
>
> On Thu, Apr 20, 2017 at 10:36 AM, Stack  wrote:
>
> > On Thu, Apr 20, 2017 at 10:08 AM, clara xiong 
> > wrote:
> >
> > > Hi Stack,
> > >
> > > I was a bit late and it is sold out now. Is there anyway to get in as
> > > standby?
> > >
> > >
> > Yes, its full but for sure sign up. You'll be added to the waiting list.
> >
> > We'll do a hard-core press before the event so that those who are unable
> to
> > attend actually relinquish their spots for the likes of yourself.
> >
> > St.Ack
> >
> >
> >
> >
> >
> > > Thanks.
> > >
> > > On Tue, Mar 28, 2017 at 12:43 PM, stack  wrote:
> > >
> > > > The HBaseCon West 2017 registration website is up [1]. Registration
> is
> > > > no-charge (Courtesy of our gracious hosts). Space is limited so be
> sure
> > > to
> > > > register early (This means YOU!, the HBase Community). Note, HBaseCon
> > > will
> > > > be in Mountain View @ Google, NOT in San Francisco, on June 12th (The
> > day
> > > > before DataWorks Summit, San Jose)
> > > >
> > > > The CfP is still open [2]. It closes April 24th so get those talks
> in;
> > > we'd
> > > > love to hear from you.
> > > >
> > > > Yours,
> > > > The HBaseCon2017 Program Committee
> > > >
> > > > 1. Visit hbasecon.com and you will be redirected to eventbrite
> > > > 2. https://easychair.org/cfp/hbasecon2017
> > > >
> > >
> >
>

[jira] [Created] (HBASE-18194) Feature to get IO characteristics at query level

2017-06-08 Thread NITIN VERMA (JIRA) 
NITIN VERMA created HBASE-18194:
---

 Summary: Feature to get IO characteristics at query level
 Key: HBASE-18194
 URL: https://issues.apache.org/jira/browse/HBASE-18194
 Project: HBase
  Issue Type: New Feature
  Components: regionserver
Reporter: NITIN VERMA
Priority: Minor


Relational databases like SQL Server, Oracle and Sybase provides a way to get 
IO characteristics at query level. We need similar feature with HBase, where, 
when requested, we should be able to get metrics like how many IO's satisfied 
from Block Cache, how many from Bucket Cache and how many ended up in HDFS.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: HBaseCon2017 Registration is now Open!

2017-06-08 Thread Stephen Jiang 
Last year's PhoenixCon live stream the talk.

In the past, people paid entry fee to come to HBaseCon, so I understand
that the recording would be delayed.  This year, the conference is free
(thanks to Google), I just wonder whether live stream the talks is possible
(or considered).

Thanks
Stephen

On Thu, Apr 20, 2017 at 10:36 AM, Stack  wrote:

> On Thu, Apr 20, 2017 at 10:08 AM, clara xiong 
> wrote:
>
> > Hi Stack,
> >
> > I was a bit late and it is sold out now. Is there anyway to get in as
> > standby?
> >
> >
> Yes, its full but for sure sign up. You'll be added to the waiting list.
>
> We'll do a hard-core press before the event so that those who are unable to
> attend actually relinquish their spots for the likes of yourself.
>
> St.Ack
>
>
>
>
>
> > Thanks.
> >
> > On Tue, Mar 28, 2017 at 12:43 PM, stack  wrote:
> >
> > > The HBaseCon West 2017 registration website is up [1]. Registration is
> > > no-charge (Courtesy of our gracious hosts). Space is limited so be sure
> > to
> > > register early (This means YOU!, the HBase Community). Note, HBaseCon
> > will
> > > be in Mountain View @ Google, NOT in San Francisco, on June 12th (The
> day
> > > before DataWorks Summit, San Jose)
> > >
> > > The CfP is still open [2]. It closes April 24th so get those talks in;
> > we'd
> > > love to hear from you.
> > >
> > > Yours,
> > > The HBaseCon2017 Program Committee
> > >
> > > 1. Visit hbasecon.com and you will be redirected to eventbrite
> > > 2. https://easychair.org/cfp/hbasecon2017
> > >
> >
>

[jira] [Resolved] (HBASE-17529) MergeTableRegionsProcedure failed due to ArrayIndexOutOfBoundsException

2017-06-08 Thread Ted Yu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-17529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu resolved HBASE-17529.

Resolution: Cannot Reproduce

> MergeTableRegionsProcedure failed due to ArrayIndexOutOfBoundsException
> ---
>
> Key: HBASE-17529
> URL: https://issues.apache.org/jira/browse/HBASE-17529
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>  Labels: rpc
> Attachments: 17529-master.log
>
>
> I built tar ball using master branch based on commit 
> 616f4801b06a8427a03ceca9fb8345700ce1ad71.
> Was running the following command:
> hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList 
> -DinMemoryCompaction=BASIC Loop 4 6 100 /tmp/hbase-biglinkedlist-verify 6 
> --monkey slowDeterministic
> Here was related snippet:
> {code}
> 2017-01-24 21:29:00,107 DEBUG 
> [RpcServer.deafult.FPBQ.Fifo.handler=0,queue=0,port=16000] 
> procedure2.ProcedureExecutor: Stored MergeTableRegionsProcedure 
> (table=IntegrationTestBigLinkedList 
> regions=[IntegrationTestBigLinkedList,,1485292220242.4c5ea240e86ef22ec7264b1153dd557d.,
>  
> IntegrationTestBigLinkedList,\x0E8\xE3\x8E8\xE3\x8E8,1485292220242.6cdb98dfed41ea689b3cd66478c2c580.
>  ] forcible=false), procId=12, owner=hbase, 
> state=RUNNABLE:MERGE_TABLE_REGIONS_PREPARE
> 2017-01-24 21:29:00,108 DEBUG [ProcedureExecutorWorker-14] 
> wal.WALProcedureStore: Set running procedure count=1, slots=24
> 2017-01-24 21:29:00,127 ERROR [ProcedureExecutorWorker-14] 
> procedure2.ProcedureExecutor: CODE-BUG: Uncatched runtime exception for 
> procedure: MergeTableRegionsProcedure (table=IntegrationTestBigLinkedList 
> regions=[IntegrationTestBigLinkedList,,1485292220242.4c5ea240e86ef22ec7264b1153dd557d.,
>  
> IntegrationTestBigLinkedList,\x0E8\xE3\x8E8\xE3\x8E8,1485292220242.6cdb98dfed41ea689b3cd66478c2c580.
>  ] forcible=false), procId=12, owner=hbase, 
> state=RUNNABLE:MERGE_TABLE_REGIONS_MOVE_REGION_TO_SAME_RS
> java.lang.ArrayIndexOutOfBoundsException
> at 
> org.apache.hadoop.hbase.util.ByteBufferUtils.copyFromBufferToArray(ByteBufferUtils.java:1024)
> at 
> org.apache.hadoop.hbase.nio.MultiByteBuff.get(MultiByteBuff.java:628)
> at 
> org.apache.hadoop.hbase.ipc.RpcServer$ByteBuffByteInput.read(RpcServer.java:1483)
> at 
> org.apache.hadoop.hbase.shaded.com.google.protobuf.ByteInputByteString.copyToInternal(ByteInputByteString.java:105)
> at 
> org.apache.hadoop.hbase.shaded.com.google.protobuf.ByteString.toByteArray(ByteString.java:651)
> at org.apache.hadoop.hbase.RegionLoad.getName(RegionLoad.java:50)
> at 
> org.apache.hadoop.hbase.ServerLoad.getRegionsLoad(ServerLoad.java:236)
> at 
> org.apache.hadoop.hbase.master.procedure.MergeTableRegionsProcedure.getRegionLoad(MergeTableRegionsProcedure.java:774)
> at 
> org.apache.hadoop.hbase.master.procedure.MergeTableRegionsProcedure.MoveRegionsToSameRS(MergeTableRegionsProcedure.java:461)
> at 
> org.apache.hadoop.hbase.master.procedure.MergeTableRegionsProcedure.executeFromState(MergeTableRegionsProcedure.java:142)
> at 
> org.apache.hadoop.hbase.master.procedure.MergeTableRegionsProcedure.executeFromState(MergeTableRegionsProcedure.java:72)
> at 
> org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:154)
> at 
> org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:708)
> at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1332)
> at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1133)
> at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$800(ProcedureExecutor.java:76)
> at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:1588)
> {code}
> Master log to be attached.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [VOTE] First hbase-2.0.0-alpha-1 Release Candidate is available

2017-06-08 Thread Stack 
On Thu, Jun 8, 2017 at 7:52 AM, Sean Busbey  wrote:

> The minimum voting period is 72 hours for a PMC to bless a release.
> Can we aim for that?
>
>
Sure (Stickler!)
St.Ack



> On Thu, Jun 8, 2017 at 2:33 AM, Stack  wrote:
> > The first release candidate for HBase 2.0.0-alpha-1 is up at:
> >
> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha-1RC0/
> >
> > Maven artifacts are available from a staging directory here:
> >
> >  https://repository.apache.org/content/repositories/orgapachehbase-1169
> >
> > All was signed w/ my key 8ACC93D2
> > 
> >
> > I tagged the RC as 2.0.0-alpha-1RC0
> > (c830a0f47f58d4892dd3300032c8244d6278aecc).
> >
> > hbase-2.0.0-alpha-1 will be our first 2.0.0 release. It is a rough cut
> > ('alpha') not-for-production preview of what hbase-2.0.0 will look like.
> It
> > is what we used to call a 'Developer' release[1] meant mostly for devs
> and
> > downstreamers to test drive and flag us early if we there are issues
> we’ve
> > missed ahead of our rolling a production-worthy release.
> >
> > hbase-2.0.0 includes a fleet of new features that include a new
> assignment
> > manager, means for keeping read and write path off-heap, in-memory
> > compactions, and more. I have been keeping a running doc on the state of
> > 2.0.0 here [2]. There is much to do still (see aforementioned doc).
> >
> > The list of features addressed in 2.0.0 so far can be found here [4].
> There
> > are about 2500. The list of ~500 fixes in 2.0.0 exclusively can be found
> > here [3].
> >
> > Please take it for a spin and vote on whether it ok to put out as our
> first
> > alpha (bar is low for an 'alpha'). Let the VOTE be open for 24 hours.
> >
> > Thanks,
> > St.Ack
> >
> > 1. http://hbase.apache.org/book.html#hbase.versioning.pre10
> > 2.
> > https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_
> ktczrlKHK8N4SZzs/edit#heading=h.v21r9nz8g01j
> > 3.
> > https://issues.apache.org/jira/browse/HBASE-17852?jql=
> project%20%3D%20HBASE%20%20and%20fixVersion%20%3D%202.
> 0.0%20and%20fixVersion%20not%20in%20(1.0.0%2C%201.0.1%2C%
> 201.0.2%2C%201.0.3%2C%201.0.4%2C%201.0.5%2C%201.0.6%2C%201.
> 1.0%2C%201.1.1%2C%201.1.2%2C%201.1.3%2C%201.1.4%2C%201.1.5%
> 2C%201.1.6%2C%201.1.7%2C%201.1.8%2C%201.1.9%2C%201.1.10%2C%
> 201.2.0%2C%201.2.1%2C%201.2.2%2C%201.2.3%2C%201.2.4%2C%201.
> 2.5%2C%201.2.6%2C%201.3.0%2C%201.3.1%2C%201.4.0)%20and%20%
> 20(status%20%3D%20Open%20or%20status%20%3D%20%22Patch%20Available%22)
> > 4.
> > https://issues.apache.org/jira/browse/HBASE-18191?jql=
> project%20%3D%20HBASE%20%20and%20(%20fixVersion%20%3D%
> 202.0.0)%20and%20(status%20%3D%20Resolved)
>

Re: [VOTE] First hbase-2.0.0-alpha-1 Release Candidate is available

2017-06-08 Thread Sean Busbey 
The minimum voting period is 72 hours for a PMC to bless a release.
Can we aim for that?

On Thu, Jun 8, 2017 at 2:33 AM, Stack  wrote:
> The first release candidate for HBase 2.0.0-alpha-1 is up at:
>
>  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha-1RC0/
>
> Maven artifacts are available from a staging directory here:
>
>  https://repository.apache.org/content/repositories/orgapachehbase-1169
>
> All was signed w/ my key 8ACC93D2
> 
>
> I tagged the RC as 2.0.0-alpha-1RC0
> (c830a0f47f58d4892dd3300032c8244d6278aecc).
>
> hbase-2.0.0-alpha-1 will be our first 2.0.0 release. It is a rough cut
> ('alpha') not-for-production preview of what hbase-2.0.0 will look like. It
> is what we used to call a 'Developer' release[1] meant mostly for devs and
> downstreamers to test drive and flag us early if we there are issues we’ve
> missed ahead of our rolling a production-worthy release.
>
> hbase-2.0.0 includes a fleet of new features that include a new assignment
> manager, means for keeping read and write path off-heap, in-memory
> compactions, and more. I have been keeping a running doc on the state of
> 2.0.0 here [2]. There is much to do still (see aforementioned doc).
>
> The list of features addressed in 2.0.0 so far can be found here [4]. There
> are about 2500. The list of ~500 fixes in 2.0.0 exclusively can be found
> here [3].
>
> Please take it for a spin and vote on whether it ok to put out as our first
> alpha (bar is low for an 'alpha'). Let the VOTE be open for 24 hours.
>
> Thanks,
> St.Ack
>
> 1. http://hbase.apache.org/book.html#hbase.versioning.pre10
> 2.
> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_ktczrlKHK8N4SZzs/edit#heading=h.v21r9nz8g01j
> 3.
> https://issues.apache.org/jira/browse/HBASE-17852?jql=project%20%3D%20HBASE%20%20and%20fixVersion%20%3D%202.0.0%20and%20fixVersion%20not%20in%20(1.0.0%2C%201.0.1%2C%201.0.2%2C%201.0.3%2C%201.0.4%2C%201.0.5%2C%201.0.6%2C%201.1.0%2C%201.1.1%2C%201.1.2%2C%201.1.3%2C%201.1.4%2C%201.1.5%2C%201.1.6%2C%201.1.7%2C%201.1.8%2C%201.1.9%2C%201.1.10%2C%201.2.0%2C%201.2.1%2C%201.2.2%2C%201.2.3%2C%201.2.4%2C%201.2.5%2C%201.2.6%2C%201.3.0%2C%201.3.1%2C%201.4.0)%20and%20%20(status%20%3D%20Open%20or%20status%20%3D%20%22Patch%20Available%22)
> 4.
> https://issues.apache.org/jira/browse/HBASE-18191?jql=project%20%3D%20HBASE%20%20and%20(%20fixVersion%20%3D%202.0.0)%20and%20(status%20%3D%20Resolved)

[jira] [Created] (HBASE-18193) Master web UI presents the incorrect number of regions

2017-06-08 Thread Chia-Ping Tsai (JIRA) 
Chia-Ping Tsai created HBASE-18193:
--

 Summary: Master web UI presents the incorrect number of regions
 Key: HBASE-18193
 URL: https://issues.apache.org/jira/browse/HBASE-18193
 Project: HBase
  Issue Type: Bug
Affects Versions: 2.0.0, 3.0.0
Reporter: Chia-Ping Tsai
Assignee: Chia-Ping Tsai
Priority: Minor


{code:title=RegionStates.java}
  public Map 
getRegionByStateOfTable(TableName tableName) {
final State[] states = State.values();
final Map tableRegions =
new HashMap(states.length);
for (int i = 0; i < states.length; ++i) {
  tableRegions.put(states[i], new ArrayList());
}

for (RegionStateNode node: regionsMap.values()) {
  tableRegions.get(node.getState()).add(node.getRegionInfo());
}
return tableRegions;
  }
{code}
It always returns all regions...



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[VOTE] First hbase-2.0.0-alpha-1 Release Candidate is available

2017-06-08 Thread Stack 
The first release candidate for HBase 2.0.0-alpha-1 is up at:

 https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-alpha-1RC0/

Maven artifacts are available from a staging directory here:

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

All was signed w/ my key 8ACC93D2


I tagged the RC as 2.0.0-alpha-1RC0
(c830a0f47f58d4892dd3300032c8244d6278aecc).

hbase-2.0.0-alpha-1 will be our first 2.0.0 release. It is a rough cut
('alpha') not-for-production preview of what hbase-2.0.0 will look like. It
is what we used to call a 'Developer' release[1] meant mostly for devs and
downstreamers to test drive and flag us early if we there are issues we’ve
missed ahead of our rolling a production-worthy release.

hbase-2.0.0 includes a fleet of new features that include a new assignment
manager, means for keeping read and write path off-heap, in-memory
compactions, and more. I have been keeping a running doc on the state of
2.0.0 here [2]. There is much to do still (see aforementioned doc).

The list of features addressed in 2.0.0 so far can be found here [4]. There
are about 2500. The list of ~500 fixes in 2.0.0 exclusively can be found
here [3].

Please take it for a spin and vote on whether it ok to put out as our first
alpha (bar is low for an 'alpha'). Let the VOTE be open for 24 hours.

Thanks,
St.Ack

1. http://hbase.apache.org/book.html#hbase.versioning.pre10
2.
https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_ktczrlKHK8N4SZzs/edit#heading=h.v21r9nz8g01j
3.
https://issues.apache.org/jira/browse/HBASE-17852?jql=project%20%3D%20HBASE%20%20and%20fixVersion%20%3D%202.0.0%20and%20fixVersion%20not%20in%20(1.0.0%2C%201.0.1%2C%201.0.2%2C%201.0.3%2C%201.0.4%2C%201.0.5%2C%201.0.6%2C%201.1.0%2C%201.1.1%2C%201.1.2%2C%201.1.3%2C%201.1.4%2C%201.1.5%2C%201.1.6%2C%201.1.7%2C%201.1.8%2C%201.1.9%2C%201.1.10%2C%201.2.0%2C%201.2.1%2C%201.2.2%2C%201.2.3%2C%201.2.4%2C%201.2.5%2C%201.2.6%2C%201.3.0%2C%201.3.1%2C%201.4.0)%20and%20%20(status%20%3D%20Open%20or%20status%20%3D%20%22Patch%20Available%22)
4.
https://issues.apache.org/jira/browse/HBASE-18191?jql=project%20%3D%20HBASE%20%20and%20(%20fixVersion%20%3D%202.0.0)%20and%20(status%20%3D%20Resolved)

[jira] [Resolved] (HBASE-17876) Release 1.2.6

2017-06-08 Thread Sean Busbey (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HBASE-17876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey resolved HBASE-17876.
-
Resolution: Fixed

> Release 1.2.6
> -
>
> Key: HBASE-17876
> URL: https://issues.apache.org/jira/browse/HBASE-17876
> Project: HBase
>  Issue Type: Task
>  Components: community
>Reporter: Sean Busbey
>Assignee: Sean Busbey
> Fix For: 1.2.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (HBASE-18192) Replication drops recovered queues on region server shutdown

2017-06-08 Thread Ashu Pachauri (JIRA) 
Ashu Pachauri created HBASE-18192:
-

 Summary: Replication drops recovered queues on region server 
shutdown
 Key: HBASE-18192
 URL: https://issues.apache.org/jira/browse/HBASE-18192
 Project: HBase
  Issue Type: Bug
  Components: Replication
Affects Versions: 1.2.6, 1.3.1, 2.0.0, 1.4.0
Reporter: Ashu Pachauri
Assignee: Ashu Pachauri
Priority: Blocker
 Fix For: 2.0.0, 1.4.0, 1.3.2, 1.2.7


When a recovered queue has only one active ReplicationWorkerThread, the 
recovered queue is completely dropped on a region server shutdown. This will 
happen in situation when 
1. DefaultWALProvider is used.
2. RegionGroupingProvider provider is used but replication is stuck on one WAL 
group for some reason (for example HBASE-18137)
3. All other replication workers have died due to unhandled exception, and the 
only one finishes. This will cause the recovered queue to get deleted without a 
regionserver shutdown. This can happen on deployments without fix for 
HBASE-17381.

The problematic piece of code is:
{Code}
while (isWorkerActive()){
// The worker thread run loop...
}
if (replicationQueueInfo.isQueueRecovered()) {
// use synchronize to make sure one last thread will clean the queue
synchronized (workerThreads) {
  Threads.sleep(100);// wait a short while for other worker thread to 
fully exit
  boolean allOtherTaskDone = true;
  for (ReplicationSourceWorkerThread worker : workerThreads.values()) {
if (!worker.equals(this) && worker.isAlive()) {
  allOtherTaskDone = false;
  break;
}
  }
  if (allOtherTaskDone) {
manager.closeRecoveredQueue(this.source);
LOG.info("Finished recovering queue " + peerClusterZnode
+ " with the following stats: " + getStats());
  }
}
{Code}

The conceptual issue is that isWorkerActive() tells whether a worker is 
currently running or not and it's being used as a proxy for whether a worker 
has finished it's work. But, in fact, "Should a worker should exit?" and "Has 
completed it's work?" are two different questions.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[ANNOUNCE] Apache HBase 1.2.6 is now available for download

2017-06-08 Thread Sean Busbey 
The HBase team is happy to announce the immediate availability of Apache
HBase 1.2.6.

Apache HBase is an open-source, distributed, versioned, non-relational
database. Apache HBase gives you low latency random access to billions of
rows with millions of columns atop non-specialized hardware. To learn more
about HBase, see https://hbase.apache.org/.

HBase 1.2.6 is the latest maintenance release in the HBase 1.2 line,
continuing on the theme of bringing a stable, reliable database to the
Hadoop and NoSQL communities. This release includes over 25
bug fixes since 1.2.5.

Critical fixes include:

* HBASE-17287 - Master becomes a zombie if filesystem object closes
* HBASE-16630 - Fragmentation in long running Bucket Cache
* HBASE-17717 - Incorrect ZK ACL set for HBase superuser
* HBASE-15941 - HBCK repair should not unsplit healthy splitted region

The full list of fixes included in this release is available at:

https://s.apache.org/hbase-1.2.6-jira-release-notes

and in the CHANGES.txt file included in the distribution.

Download through an ASF mirror near you:

https://www.apache.org/dyn/closer.lua/hbase/1.2.6

The relevant checksums files are available at:

https://www.apache.org/dist/hbase/1.2.6/hbase-1.2.6-src.tar.gz.mds
https://www.apache.org/dist/hbase/1.2.6/hbase-1.2.6-bin.tar.gz.mds

Project member signature keys can be found at

https://www.apache.org/dist/hbase/KEYS

PGP signatures are available at:

https://www.apache.org/dist/hbase/1.2.6/hbase-1.2.6-src.tar.gz.asc
https://www.apache.org/dist/hbase/1.2.6/hbase-1.2.6-bin.tar.gz.asc

For instructions on verifying ASF release downloads, please see

https://www.apache.org/dyn/closer.cgi#verify

Question, comments, and problems are always welcome at:
dev@hbase.apache.org.

Cheers,
The HBase Dev Team