[RESULT] [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Stack]

This RC failed. It had a binding +1 and two -1s inside the voting allotment
but discussion says a new RC will get more attention.

S

On Wed, Apr 18, 2018 at 2:37 PM, Josh Elser  wrote:

> I like that plan. I'll try to dig into what a "better" fix might be for
> the random ports stuff tonight.
>
>
> On 4/18/18 5:35 PM, Stack wrote:
>
>> On Wed, Apr 18, 2018 at 12:58 PM, Josh Elser  wrote:
>>
>> +1 (binding)
>>>
>>> There are rough edges, of course, but I think this is more than enough
>>> quality for a 2.0.0. Putting a line in the sand for 2.0 will help us
>>> continue to make changes that improve the product going forward with more
>>> focus and get those changes into the hands of folks downstream.
>>>
>>>
>>> I'm in line with this sort of thinking. The diff between RC0 and current
>> tip is below. There's some pretty important changes in the list I'd say.
>> How about I put up another RC tonight/tomorrow with some more doc fixes,
>> the HBCK, and if you have something for test random ports, that too...
>> Then
>> you show up again w/ the above philosophizing (girded by the accompanying
>> +1)?
>>
>> St.Ack
>>
>>
>> f168689 HBASE-19994 Create a new class for RPC throttling exception, make
>> it retryable
>> 10f74df HBASE-20404 Fixes to CleanChore correctness and operability.
>> c7c0861 HBASE-20398 Redirect doesn't work on web UI
>> acc73b1 HBASE-20399 Fix merge layout
>> 10a2905 HBASE-19963 TestFSHDFSUtils assumes wrong default port for Hadoop
>> 3.0.1+
>> bbe1551 HBASE-20409 Set hbase.client.meta.operation.timeout in
>> TestClientOperationTimeout
>> fb01cc4 HBASE-20364 ensure jira comment from nightly reflects results of
>> run comment comes from.
>> a825bf1 HBASE-20415 branches-2 don't need scala tooling.
>> f5f03f9 HBASE-20233 Remove redundant region server metric
>> 4de3d7d HBASE-20389 Move website building flags into a profile.
>> 4176237 HBASE-20335 ensure each stage of the nightly job gathers machine
>> information.
>> 7704d3b HBASE-20410 update protoc to 3.5.1-1 for rhel6
>> 8ca2d0f HBASE-20394 HBase over rides the value of HBASE_OPTS (if any) set
>> by client
>> ed3a656 HBASE-20379 shadedjars yetus plugin should add a footer link
>> 0d8262f HBASE-20112 register nightly junit over hadoop3 results with
>> jenkins.
>> cba88d1 HBASE-20224 Web UI is broken in standalone mode - addendum for
>> hbase-endpoint and hbase-rsgroup modules
>> ee3c430 HBASE-20224 Web UI is broken in standalone mode - addendum for
>> hbase-archetypes module
>> 0eacb3e HBASE-20338 WALProcedureStore#recoverLease() should have fixed
>> sleeps for retrying rollWriter()
>> 263cc8d HBASE-20376 RowCounter and CellCounter documentations are
>> incorrect
>> e72a1c6 HBASE-20330 ProcedureExecutor.start() gets stuck in recover lease
>> on store
>> 0d2b18b HBASE-20350 NullPointerException in Scanner during close()
>> 6a081d3 HBASE-20310 Fixed false inconsistency shown by hbck -metaonly
>> option on HBase 2
>> 0e8d42b HBASE-20219 An error occurs when scanning with reversed=true and
>> loadColumnFamiliesOnDemand=true
>> 907b264 HBASE-20358 Fix bin/hbase thrift usage text
>> 200afa1 HBASE-20382 If RSGroups not enabled, rsgroup.jsp prints stack
>> trace
>> e05b318 HBASE-20386 [DOC] Align WALPlayer help text and refguide
>> 63125ea HBASE-20385 Purge md5-making from our little make_rc.sh script
>> 47128f5 HBASE-20384 [AMv2] Logging format improvements; use encoded name
>> rather than full region name marking transitions
>> 9320c5d HBASE-20253. Error message is missing for restore_snapshot
>> b3ec5f0 HBASE-15291 FileSystem not closed in secure bulkLoad
>> 2e6eff0 HBASE-20182 Addendum throw IOException instead of
>> NoServerForRegionException because it is a DoNotRetryRegionException
>> 3887648 HBASE-20335 nightly job bash cleanup.
>> 86f4686 HBASE-20068 personality tests for Apache Yetus should use the
>> maven
>> plugin to exec maven.
>>
>>
>>
>>
>>
>> Well done, Stack.
>>>
>>> On 4/10/18 4:47 PM, Stack wrote:
>>>
>>> The first release candidate for Apache HBase 2.0.0 is available for
 downloading and testing.

 Artifacts are available here:

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

 Maven artifacts are available in the staging repository at:

https://repository.apache.org/content/repositories/orgap
 achehbase-1209

 All artifacts are signed with my signing key 8ACC93D2, which is also
 in the project KEYS file at

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

 These artifacts were tagged 2.0.0RC0 at
 hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46

 Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
 Reference Guide before installing or upgrading for a list of
 incompatibilities, major changes, and notable new features. Be aware
 that
 according to our adopted Semantic Versioning guidelines[1], we've allow
 ourselves to make breaking changes in this major version 

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Josh Elser]

I like that plan. I'll try to dig into what a "better" fix might be for 
the random ports stuff tonight.


On 4/18/18 5:35 PM, Stack wrote:

On Wed, Apr 18, 2018 at 12:58 PM, Josh Elser  wrote:


+1 (binding)

There are rough edges, of course, but I think this is more than enough
quality for a 2.0.0. Putting a line in the sand for 2.0 will help us
continue to make changes that improve the product going forward with more
focus and get those changes into the hands of folks downstream.



I'm in line with this sort of thinking. The diff between RC0 and current
tip is below. There's some pretty important changes in the list I'd say.
How about I put up another RC tonight/tomorrow with some more doc fixes,
the HBCK, and if you have something for test random ports, that too... Then
you show up again w/ the above philosophizing (girded by the accompanying
+1)?

St.Ack


f168689 HBASE-19994 Create a new class for RPC throttling exception, make
it retryable
10f74df HBASE-20404 Fixes to CleanChore correctness and operability.
c7c0861 HBASE-20398 Redirect doesn't work on web UI
acc73b1 HBASE-20399 Fix merge layout
10a2905 HBASE-19963 TestFSHDFSUtils assumes wrong default port for Hadoop
3.0.1+
bbe1551 HBASE-20409 Set hbase.client.meta.operation.timeout in
TestClientOperationTimeout
fb01cc4 HBASE-20364 ensure jira comment from nightly reflects results of
run comment comes from.
a825bf1 HBASE-20415 branches-2 don't need scala tooling.
f5f03f9 HBASE-20233 Remove redundant region server metric
4de3d7d HBASE-20389 Move website building flags into a profile.
4176237 HBASE-20335 ensure each stage of the nightly job gathers machine
information.
7704d3b HBASE-20410 update protoc to 3.5.1-1 for rhel6
8ca2d0f HBASE-20394 HBase over rides the value of HBASE_OPTS (if any) set
by client
ed3a656 HBASE-20379 shadedjars yetus plugin should add a footer link
0d8262f HBASE-20112 register nightly junit over hadoop3 results with
jenkins.
cba88d1 HBASE-20224 Web UI is broken in standalone mode - addendum for
hbase-endpoint and hbase-rsgroup modules
ee3c430 HBASE-20224 Web UI is broken in standalone mode - addendum for
hbase-archetypes module
0eacb3e HBASE-20338 WALProcedureStore#recoverLease() should have fixed
sleeps for retrying rollWriter()
263cc8d HBASE-20376 RowCounter and CellCounter documentations are incorrect
e72a1c6 HBASE-20330 ProcedureExecutor.start() gets stuck in recover lease
on store
0d2b18b HBASE-20350 NullPointerException in Scanner during close()
6a081d3 HBASE-20310 Fixed false inconsistency shown by hbck -metaonly
option on HBase 2
0e8d42b HBASE-20219 An error occurs when scanning with reversed=true and
loadColumnFamiliesOnDemand=true
907b264 HBASE-20358 Fix bin/hbase thrift usage text
200afa1 HBASE-20382 If RSGroups not enabled, rsgroup.jsp prints stack trace
e05b318 HBASE-20386 [DOC] Align WALPlayer help text and refguide
63125ea HBASE-20385 Purge md5-making from our little make_rc.sh script
47128f5 HBASE-20384 [AMv2] Logging format improvements; use encoded name
rather than full region name marking transitions
9320c5d HBASE-20253. Error message is missing for restore_snapshot
b3ec5f0 HBASE-15291 FileSystem not closed in secure bulkLoad
2e6eff0 HBASE-20182 Addendum throw IOException instead of
NoServerForRegionException because it is a DoNotRetryRegionException
3887648 HBASE-20335 nightly job bash cleanup.
86f4686 HBASE-20068 personality tests for Apache Yetus should use the maven
plugin to exec maven.






Well done, Stack.

On 4/10/18 4:47 PM, Stack wrote:


The first release candidate for Apache HBase 2.0.0 is available for
downloading and testing.

Artifacts are available here:

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

Maven artifacts are available in the staging repository at:

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

All artifacts are signed with my signing key 8ACC93D2, which is also
in the project KEYS file at

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

These artifacts were tagged 2.0.0RC0 at
hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46

Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
Reference Guide before installing or upgrading for a list of
incompatibilities, major changes, and notable new features. Be aware that
according to our adopted Semantic Versioning guidelines[1], we've allow
ourselves to make breaking changes in this major version release. For
example, Coprocessors will need to be recast to fit more constrained CP
APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x without
downtime is (currently) not possible. That said, a bunch of effort has
been
expended mitigating differences; a hbase-1.x client can perform DML
against
an hbase-2 cluster.

For the full list of ~6k issues addressed, see [2]. There are also
CHANGES.md and RELEASENOTES.md in the root directory of the source
tarball.

Please take a few minutes to verify the release and vote on releasing it:

[ ] +1 Release this package as 

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Stack]

On Wed, Apr 18, 2018 at 12:58 PM, Josh Elser  wrote:

> +1 (binding)
>
> There are rough edges, of course, but I think this is more than enough
> quality for a 2.0.0. Putting a line in the sand for 2.0 will help us
> continue to make changes that improve the product going forward with more
> focus and get those changes into the hands of folks downstream.
>
>
I'm in line with this sort of thinking. The diff between RC0 and current
tip is below. There's some pretty important changes in the list I'd say.
How about I put up another RC tonight/tomorrow with some more doc fixes,
the HBCK, and if you have something for test random ports, that too... Then
you show up again w/ the above philosophizing (girded by the accompanying
+1)?

St.Ack


f168689 HBASE-19994 Create a new class for RPC throttling exception, make
it retryable
10f74df HBASE-20404 Fixes to CleanChore correctness and operability.
c7c0861 HBASE-20398 Redirect doesn't work on web UI
acc73b1 HBASE-20399 Fix merge layout
10a2905 HBASE-19963 TestFSHDFSUtils assumes wrong default port for Hadoop
3.0.1+
bbe1551 HBASE-20409 Set hbase.client.meta.operation.timeout in
TestClientOperationTimeout
fb01cc4 HBASE-20364 ensure jira comment from nightly reflects results of
run comment comes from.
a825bf1 HBASE-20415 branches-2 don't need scala tooling.
f5f03f9 HBASE-20233 Remove redundant region server metric
4de3d7d HBASE-20389 Move website building flags into a profile.
4176237 HBASE-20335 ensure each stage of the nightly job gathers machine
information.
7704d3b HBASE-20410 update protoc to 3.5.1-1 for rhel6
8ca2d0f HBASE-20394 HBase over rides the value of HBASE_OPTS (if any) set
by client
ed3a656 HBASE-20379 shadedjars yetus plugin should add a footer link
0d8262f HBASE-20112 register nightly junit over hadoop3 results with
jenkins.
cba88d1 HBASE-20224 Web UI is broken in standalone mode - addendum for
hbase-endpoint and hbase-rsgroup modules
ee3c430 HBASE-20224 Web UI is broken in standalone mode - addendum for
hbase-archetypes module
0eacb3e HBASE-20338 WALProcedureStore#recoverLease() should have fixed
sleeps for retrying rollWriter()
263cc8d HBASE-20376 RowCounter and CellCounter documentations are incorrect
e72a1c6 HBASE-20330 ProcedureExecutor.start() gets stuck in recover lease
on store
0d2b18b HBASE-20350 NullPointerException in Scanner during close()
6a081d3 HBASE-20310 Fixed false inconsistency shown by hbck -metaonly
option on HBase 2
0e8d42b HBASE-20219 An error occurs when scanning with reversed=true and
loadColumnFamiliesOnDemand=true
907b264 HBASE-20358 Fix bin/hbase thrift usage text
200afa1 HBASE-20382 If RSGroups not enabled, rsgroup.jsp prints stack trace
e05b318 HBASE-20386 [DOC] Align WALPlayer help text and refguide
63125ea HBASE-20385 Purge md5-making from our little make_rc.sh script
47128f5 HBASE-20384 [AMv2] Logging format improvements; use encoded name
rather than full region name marking transitions
9320c5d HBASE-20253. Error message is missing for restore_snapshot
b3ec5f0 HBASE-15291 FileSystem not closed in secure bulkLoad
2e6eff0 HBASE-20182 Addendum throw IOException instead of
NoServerForRegionException because it is a DoNotRetryRegionException
3887648 HBASE-20335 nightly job bash cleanup.
86f4686 HBASE-20068 personality tests for Apache Yetus should use the maven
plugin to exec maven.





> Well done, Stack.
>
> On 4/10/18 4:47 PM, Stack wrote:
>
>> The first release candidate for Apache HBase 2.0.0 is available for
>> downloading and testing.
>>
>> Artifacts are available here:
>>
>>   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
>>
>> Maven artifacts are available in the staging repository at:
>>
>>   https://repository.apache.org/content/repositories/orgapachehbase-1209
>>
>> All artifacts are signed with my signing key 8ACC93D2, which is also
>> in the project KEYS file at
>>
>>   http://www.apache.org/dist/hbase/KEYS
>>
>> These artifacts were tagged 2.0.0RC0 at
>> hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
>>
>> Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
>> Reference Guide before installing or upgrading for a list of
>> incompatibilities, major changes, and notable new features. Be aware that
>> according to our adopted Semantic Versioning guidelines[1], we've allow
>> ourselves to make breaking changes in this major version release. For
>> example, Coprocessors will need to be recast to fit more constrained CP
>> APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x without
>> downtime is (currently) not possible. That said, a bunch of effort has
>> been
>> expended mitigating differences; a hbase-1.x client can perform DML
>> against
>> an hbase-2 cluster.
>>
>> For the full list of ~6k issues addressed, see [2]. There are also
>> CHANGES.md and RELEASENOTES.md in the root directory of the source
>> tarball.
>>
>> Please take a few minutes to verify the release and vote on releasing it:
>>
>> [ ] +1 Release this package as Apache HBase 2.0.0
>> 

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Stack]

On Tue, Apr 17, 2018 at 6:25 PM, Sean Busbey <bus...@apache.org> wrote:

> I've been using it and have some concerns wrt our shaded clients
> (tracking in HBASE-20331). I've been hesitant to vote -1 due to them
> because the work isn't done yet. But I hope to have it wrapped by end
> of week.
>
>
Should HBASE-20331 be a blocker?


> Reviewing  HBASE-18792, I'm also concerned that it isn't included in
> the current RC. But again, hasn't landed yet.
>
> HBASE-20244 looks bad, but I agree that running on Hadoop 3 shouldn't
> be a blocker. Yay for the asyncfs log message looking reasonable in
> the face of failure though!
>
> I've only been kind of half-following along for the perf saga in
> HBASE-20188. We have enough info yet to get some guidance into the
> upgrade section of the ref guide?
>
>
Perf is taking time. There are a few of us at it. Calibrating
understanding, expectations, and tooling has taken a bunch of time. We're
making progress though. For the upgrade section, I was thinking of adding a
general note that perf profile changes in hbase2 -- it will likely run
faster but it may be slower in some instances -- and then refer readers to
the perf chapter which we can fill in findings as we go (post hbase2
release even).

Thanks,
St.Ack


>
> On Tue, Apr 17, 2018 at 4:59 PM, Stack <st...@duboce.net> wrote:
> > Yeah, what Ashish says Umesh (and yeah, checkout HBASE-20385 for the why
> > sir).
> >
> > Any one else given the RC a try? Its seven days now. Time is about up. I
> > have two -1s, one of which I think I can overturn. Any other feedback on
> > the RC? Any PMCers tried it?
> >
> > Thanks,
> >
> > St.Ack
> >
> >
> > On Mon, Apr 16, 2018 at 9:41 PM, ashish singhi <ashish.sin...@huawei.com
> >
> > wrote:
> >
> >> bq. signatures & sums-
> NOT
> >> OK
> >> (md5 checksums missing)
> >>
> >> This is intentional I think, check HBASE-20385.
> >>
> >> Regards,
> >> Ashish
> >>
> >> -Original Message-
> >> From: Umesh Agashe [mailto:uaga...@cloudera.com]
> >> Sent: Tuesday, April 17, 2018 4:01 AM
> >> To: dev@hbase.apache.org
> >> Subject: Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is
> >> available
> >>
> >> -1 non-binding (hbck with write operations disabled not included)
> >>
> >> download src & bin tar ball   - OK
> >> signatures & sums- NOT
> OK
> >> (md5 checksums missing)
> >> build from source (openjdk version "1.8.0_151")  - OK
> >> rat check
>  -
> >> OK
> >> start local instance from bin & CRUD from shell  - OK
> >> LTT write, read1 million rows, 2 cols/row  - OK
> >> check logs
>  - OK
> >>
> >>
> >> On Fri, Apr 13, 2018 at 10:55 AM, Stack <st...@duboce.net> wrote:
> >>
> >> > On Fri, Apr 13, 2018 at 10:53 AM, Josh Elser <els...@apache.org>
> wrote:
> >> >
> >> > > Was poking around with PE on a few nodes (I forget the exact
> >> > > circumstances, need to look back at this), and ran into a case where
> >> > > ~35 regions were left as RIT
> >> > >
> >> > > 2018-04-12 22:05:24,431 ERROR
> >> > > [master/ctr-e138-1518143905142-221855-01-
> >> > 02:16000]
> >> > > procedure2.ProcedureExecutor: Corrupt pid=3580, ppid=3534,
> >> > > state=RUNNABLE:REGION_TRANSITION_QUEUE; AssignProcedure
> >> table=TestTable,
> >> > > region=71fef  ffe6b5b3cf1cb6d3328a5a58690
> >> > >
> >> > > Saw entries like this (I think) for each region which was stuck. A
> >> > > simple `assign` in the shell brought them back, but I need to dig in
> >> > > some more
> >> > to
> >> > > understand what went wrong.
> >> > >
> >> > >
> >> > Log?
> >> >
> >> > HBASE-18152?
> >> >
> >> > Thanks Josh,
> >> > S
> >> >
> >> >
> >> >
> >> >
> >> > >
> >> > > On 4/10/18 4:47 PM, Stack wrote:
> >> > >
> >> > >> The first release candidate for Apache HBase 2.0.0 is available for
> >> > >> downloading and testing.
> >> > >>
> >> > >> Artifacts are 

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Josh Elser]

+1 (binding)

There are rough edges, of course, but I think this is more than enough 
quality for a 2.0.0. Putting a line in the sand for 2.0 will help us 
continue to make changes that improve the product going forward with 
more focus and get those changes into the hands of folks downstream.


Well done, Stack.

On 4/10/18 4:47 PM, Stack wrote:

The first release candidate for Apache HBase 2.0.0 is available for
downloading and testing.

Artifacts are available here:

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

Maven artifacts are available in the staging repository at:

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

All artifacts are signed with my signing key 8ACC93D2, which is also
in the project KEYS file at

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

These artifacts were tagged 2.0.0RC0 at
hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46

Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
Reference Guide before installing or upgrading for a list of
incompatibilities, major changes, and notable new features. Be aware that
according to our adopted Semantic Versioning guidelines[1], we've allow
ourselves to make breaking changes in this major version release. For
example, Coprocessors will need to be recast to fit more constrained CP
APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x without
downtime is (currently) not possible. That said, a bunch of effort has been
expended mitigating differences; a hbase-1.x client can perform DML against
an hbase-2 cluster.

For the full list of ~6k issues addressed, see [2]. There are also
CHANGES.md and RELEASENOTES.md in the root directory of the source tarball.

Please take a few minutes to verify the release and vote on releasing it:

[ ] +1 Release this package as Apache HBase 2.0.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...

This VOTE will run for one week and close Tuesday, April 17, 2018 @ 13:00
PST.

Thanks to the myriad who have helped out with this release,
Your 2.0.0 Release Manager

1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
2.  https://s.apache.org/zwS9

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Sean Busbey]

I've been using it and have some concerns wrt our shaded clients
(tracking in HBASE-20331). I've been hesitant to vote -1 due to them
because the work isn't done yet. But I hope to have it wrapped by end
of week.

Reviewing  HBASE-18792, I'm also concerned that it isn't included in
the current RC. But again, hasn't landed yet.

HBASE-20244 looks bad, but I agree that running on Hadoop 3 shouldn't
be a blocker. Yay for the asyncfs log message looking reasonable in
the face of failure though!

I've only been kind of half-following along for the perf saga in
HBASE-20188. We have enough info yet to get some guidance into the
upgrade section of the ref guide?


On Tue, Apr 17, 2018 at 4:59 PM, Stack <st...@duboce.net> wrote:
> Yeah, what Ashish says Umesh (and yeah, checkout HBASE-20385 for the why
> sir).
>
> Any one else given the RC a try? Its seven days now. Time is about up. I
> have two -1s, one of which I think I can overturn. Any other feedback on
> the RC? Any PMCers tried it?
>
> Thanks,
>
> St.Ack
>
>
> On Mon, Apr 16, 2018 at 9:41 PM, ashish singhi <ashish.sin...@huawei.com>
> wrote:
>
>> bq. signatures & sums- NOT
>> OK
>> (md5 checksums missing)
>>
>> This is intentional I think, check HBASE-20385.
>>
>> Regards,
>> Ashish
>>
>> -Original Message-
>> From: Umesh Agashe [mailto:uaga...@cloudera.com]
>> Sent: Tuesday, April 17, 2018 4:01 AM
>> To: dev@hbase.apache.org
>> Subject: Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is
>> available
>>
>> -1 non-binding (hbck with write operations disabled not included)
>>
>> download src & bin tar ball   - OK
>> signatures & sums- NOT OK
>> (md5 checksums missing)
>> build from source (openjdk version "1.8.0_151")  - OK
>> rat check   -
>> OK
>> start local instance from bin & CRUD from shell  - OK
>> LTT write, read1 million rows, 2 cols/row  - OK
>> check logs - OK
>>
>>
>> On Fri, Apr 13, 2018 at 10:55 AM, Stack <st...@duboce.net> wrote:
>>
>> > On Fri, Apr 13, 2018 at 10:53 AM, Josh Elser <els...@apache.org> wrote:
>> >
>> > > Was poking around with PE on a few nodes (I forget the exact
>> > > circumstances, need to look back at this), and ran into a case where
>> > > ~35 regions were left as RIT
>> > >
>> > > 2018-04-12 22:05:24,431 ERROR
>> > > [master/ctr-e138-1518143905142-221855-01-
>> > 02:16000]
>> > > procedure2.ProcedureExecutor: Corrupt pid=3580, ppid=3534,
>> > > state=RUNNABLE:REGION_TRANSITION_QUEUE; AssignProcedure
>> table=TestTable,
>> > > region=71fef  ffe6b5b3cf1cb6d3328a5a58690
>> > >
>> > > Saw entries like this (I think) for each region which was stuck. A
>> > > simple `assign` in the shell brought them back, but I need to dig in
>> > > some more
>> > to
>> > > understand what went wrong.
>> > >
>> > >
>> > Log?
>> >
>> > HBASE-18152?
>> >
>> > Thanks Josh,
>> > S
>> >
>> >
>> >
>> >
>> > >
>> > > On 4/10/18 4:47 PM, Stack wrote:
>> > >
>> > >> The first release candidate for Apache HBase 2.0.0 is available for
>> > >> downloading and testing.
>> > >>
>> > >> Artifacts are available here:
>> > >>
>> > >>   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
>> > >>
>> > >> Maven artifacts are available in the staging repository at:
>> > >>
>> > >>   https://repository.apache.org/content/repositories/
>> > orgapachehbase-1209
>> > >>
>> > >> All artifacts are signed with my signing key 8ACC93D2, which is
>> > >> also in the project KEYS file at
>> > >>
>> > >>   http://www.apache.org/dist/hbase/KEYS
>> > >>
>> > >> These artifacts were tagged 2.0.0RC0 at hash
>> > >> 011dd2dae33456b3a2bcc2513e9fdd29de23be46
>> > >>
>> > >> Please review 'Upgrading from 1.x to 2.x' in the bundled HBase
>> > >> 2.0.0 Reference Guide before installing or upgrading for a list of
>> > >> incompat

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Duo Zhang]

I do not think it is a blocker as you can run a HDFS 3.0.1 cluster and use
a 3.0.0 client to communicate with it. +1 on taking care of this when we
have a production ready release of hadoop 3.x.

2018-04-18 7:52 GMT+08:00 Stack <st...@duboce.net>:

> Thanks for voting Wei-Chiu Chuang.
>
> We should run on hadoop3, yeah, but I wouldn't call it a blocker given
> current state of hadoop3 (3.0.1, 3.0.2, 3.1.0, not-yet-production-ready...
> What do others think?). Perhaps by hbase2.1 it'd be a blocker?
>
> (Thanks for the help over on the likes of HBASE-20244).
>
> St.Ack
>
> On Tue, Apr 17, 2018 at 4:14 PM, Wei-Chiu Chuang <weic...@cloudera.com>
> wrote:
>
> > -1 (non-binding)
> > Hbase 2 will break on Hadoop 3.0.1 or above, due to HBASE-20244 caused by
> > the refactor in HDFS-12574.
> > Is Hbase 2 on Hadoop 3 a requirement for the release?
> >
> > On Tue, Apr 17, 2018 at 2:59 PM, Stack <st...@duboce.net> wrote:
> >
> > > Yeah, what Ashish says Umesh (and yeah, checkout HBASE-20385 for the
> why
> > > sir).
> > >
> > > Any one else given the RC a try? Its seven days now. Time is about up.
> I
> > > have two -1s, one of which I think I can overturn. Any other feedback
> on
> > > the RC? Any PMCers tried it?
> > >
> > > Thanks,
> > >
> > > St.Ack
> > >
> > >
> > > On Mon, Apr 16, 2018 at 9:41 PM, ashish singhi <
> ashish.sin...@huawei.com
> > >
> > > wrote:
> > >
> > > > bq. signatures & sums
> -
> > > NOT
> > > > OK
> > > > (md5 checksums missing)
> > > >
> > > > This is intentional I think, check HBASE-20385.
> > > >
> > > > Regards,
> > > > Ashish
> > > >
> > > > -Original Message-
> > > > From: Umesh Agashe [mailto:uaga...@cloudera.com]
> > > > Sent: Tuesday, April 17, 2018 4:01 AM
> > > > To: dev@hbase.apache.org
> > > > Subject: Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is
> > > > available
> > > >
> > > > -1 non-binding (hbck with write operations disabled not included)
> > > >
> > > > download src & bin tar ball   - OK
> > > > signatures & sums-
> NOT
> > OK
> > > > (md5 checksums missing)
> > > > build from source (openjdk version "1.8.0_151")  - OK
> > > > rat check
> >  -
> > > > OK
> > > > start local instance from bin & CRUD from shell  - OK
> > > > LTT write, read1 million rows, 2 cols/row  - OK
> > > > check logs
> >  -
> > > OK
> > > >
> > > >
> > > > On Fri, Apr 13, 2018 at 10:55 AM, Stack <st...@duboce.net> wrote:
> > > >
> > > > > On Fri, Apr 13, 2018 at 10:53 AM, Josh Elser <els...@apache.org>
> > > wrote:
> > > > >
> > > > > > Was poking around with PE on a few nodes (I forget the exact
> > > > > > circumstances, need to look back at this), and ran into a case
> > where
> > > > > > ~35 regions were left as RIT
> > > > > >
> > > > > > 2018-04-12 22:05:24,431 ERROR
> > > > > > [master/ctr-e138-1518143905142-221855-01-
> > > > > 02:16000]
> > > > > > procedure2.ProcedureExecutor: Corrupt pid=3580, ppid=3534,
> > > > > > state=RUNNABLE:REGION_TRANSITION_QUEUE; AssignProcedure
> > > > table=TestTable,
> > > > > > region=71fef  ffe6b5b3cf1cb6d3328a5a58690
> > > > > >
> > > > > > Saw entries like this (I think) for each region which was stuck.
> A
> > > > > > simple `assign` in the shell brought them back, but I need to dig
> > in
> > > > > > some more
> > > > > to
> > > > > > understand what went wrong.
> > > > > >
> > > > > >
> > > > > Log?
> > > > >
> > > > > HBASE-18152?
> > > > >
> > > > > Thanks Josh,
> > > > > S
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > On 4/10/18 4:47 PM, Stack wrote:
> > > > > >
> > > > > >> The first release candidate for Ap

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Stack]

Thanks for voting Wei-Chiu Chuang.

We should run on hadoop3, yeah, but I wouldn't call it a blocker given
current state of hadoop3 (3.0.1, 3.0.2, 3.1.0, not-yet-production-ready...
What do others think?). Perhaps by hbase2.1 it'd be a blocker?

(Thanks for the help over on the likes of HBASE-20244).

St.Ack

On Tue, Apr 17, 2018 at 4:14 PM, Wei-Chiu Chuang <weic...@cloudera.com>
wrote:

> -1 (non-binding)
> Hbase 2 will break on Hadoop 3.0.1 or above, due to HBASE-20244 caused by
> the refactor in HDFS-12574.
> Is Hbase 2 on Hadoop 3 a requirement for the release?
>
> On Tue, Apr 17, 2018 at 2:59 PM, Stack <st...@duboce.net> wrote:
>
> > Yeah, what Ashish says Umesh (and yeah, checkout HBASE-20385 for the why
> > sir).
> >
> > Any one else given the RC a try? Its seven days now. Time is about up. I
> > have two -1s, one of which I think I can overturn. Any other feedback on
> > the RC? Any PMCers tried it?
> >
> > Thanks,
> >
> > St.Ack
> >
> >
> > On Mon, Apr 16, 2018 at 9:41 PM, ashish singhi <ashish.sin...@huawei.com
> >
> > wrote:
> >
> > > bq. signatures & sums-
> > NOT
> > > OK
> > > (md5 checksums missing)
> > >
> > > This is intentional I think, check HBASE-20385.
> > >
> > > Regards,
> > > Ashish
> > >
> > > -Original Message-
> > > From: Umesh Agashe [mailto:uaga...@cloudera.com]
> > > Sent: Tuesday, April 17, 2018 4:01 AM
> > > To: dev@hbase.apache.org
> > > Subject: Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is
> > > available
> > >
> > > -1 non-binding (hbck with write operations disabled not included)
> > >
> > > download src & bin tar ball   - OK
> > > signatures & sums- NOT
> OK
> > > (md5 checksums missing)
> > > build from source (openjdk version "1.8.0_151")  - OK
> > > rat check
>  -
> > > OK
> > > start local instance from bin & CRUD from shell  - OK
> > > LTT write, read1 million rows, 2 cols/row  - OK
> > > check logs
>  -
> > OK
> > >
> > >
> > > On Fri, Apr 13, 2018 at 10:55 AM, Stack <st...@duboce.net> wrote:
> > >
> > > > On Fri, Apr 13, 2018 at 10:53 AM, Josh Elser <els...@apache.org>
> > wrote:
> > > >
> > > > > Was poking around with PE on a few nodes (I forget the exact
> > > > > circumstances, need to look back at this), and ran into a case
> where
> > > > > ~35 regions were left as RIT
> > > > >
> > > > > 2018-04-12 22:05:24,431 ERROR
> > > > > [master/ctr-e138-1518143905142-221855-01-
> > > > 02:16000]
> > > > > procedure2.ProcedureExecutor: Corrupt pid=3580, ppid=3534,
> > > > > state=RUNNABLE:REGION_TRANSITION_QUEUE; AssignProcedure
> > > table=TestTable,
> > > > > region=71fef  ffe6b5b3cf1cb6d3328a5a58690
> > > > >
> > > > > Saw entries like this (I think) for each region which was stuck. A
> > > > > simple `assign` in the shell brought them back, but I need to dig
> in
> > > > > some more
> > > > to
> > > > > understand what went wrong.
> > > > >
> > > > >
> > > > Log?
> > > >
> > > > HBASE-18152?
> > > >
> > > > Thanks Josh,
> > > > S
> > > >
> > > >
> > > >
> > > >
> > > > >
> > > > > On 4/10/18 4:47 PM, Stack wrote:
> > > > >
> > > > >> The first release candidate for Apache HBase 2.0.0 is available
> for
> > > > >> downloading and testing.
> > > > >>
> > > > >> Artifacts are available here:
> > > > >>
> > > > >>   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> > > > >>
> > > > >> Maven artifacts are available in the staging repository at:
> > > > >>
> > > > >>   https://repository.apache.org/content/repositories/
> > > > orgapachehbase-1209
> > > > >>
> > > > >> All artifacts are signed with my signing key 8ACC93D2, which is
> > > > >> also in the project KEYS file at
> > > > >>
> &

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Wei-Chiu Chuang]

-1 (non-binding)
Hbase 2 will break on Hadoop 3.0.1 or above, due to HBASE-20244 caused by
the refactor in HDFS-12574.
Is Hbase 2 on Hadoop 3 a requirement for the release?

On Tue, Apr 17, 2018 at 2:59 PM, Stack <st...@duboce.net> wrote:

> Yeah, what Ashish says Umesh (and yeah, checkout HBASE-20385 for the why
> sir).
>
> Any one else given the RC a try? Its seven days now. Time is about up. I
> have two -1s, one of which I think I can overturn. Any other feedback on
> the RC? Any PMCers tried it?
>
> Thanks,
>
> St.Ack
>
>
> On Mon, Apr 16, 2018 at 9:41 PM, ashish singhi <ashish.sin...@huawei.com>
> wrote:
>
> > bq. signatures & sums-
> NOT
> > OK
> > (md5 checksums missing)
> >
> > This is intentional I think, check HBASE-20385.
> >
> > Regards,
> > Ashish
> >
> > -Original Message-
> > From: Umesh Agashe [mailto:uaga...@cloudera.com]
> > Sent: Tuesday, April 17, 2018 4:01 AM
> > To: dev@hbase.apache.org
> > Subject: Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is
> > available
> >
> > -1 non-binding (hbck with write operations disabled not included)
> >
> > download src & bin tar ball   - OK
> > signatures & sums- NOT OK
> > (md5 checksums missing)
> > build from source (openjdk version "1.8.0_151")  - OK
> > rat check   -
> > OK
> > start local instance from bin & CRUD from shell  - OK
> > LTT write, read1 million rows, 2 cols/row  - OK
> > check logs -
> OK
> >
> >
> > On Fri, Apr 13, 2018 at 10:55 AM, Stack <st...@duboce.net> wrote:
> >
> > > On Fri, Apr 13, 2018 at 10:53 AM, Josh Elser <els...@apache.org>
> wrote:
> > >
> > > > Was poking around with PE on a few nodes (I forget the exact
> > > > circumstances, need to look back at this), and ran into a case where
> > > > ~35 regions were left as RIT
> > > >
> > > > 2018-04-12 22:05:24,431 ERROR
> > > > [master/ctr-e138-1518143905142-221855-01-
> > > 02:16000]
> > > > procedure2.ProcedureExecutor: Corrupt pid=3580, ppid=3534,
> > > > state=RUNNABLE:REGION_TRANSITION_QUEUE; AssignProcedure
> > table=TestTable,
> > > > region=71fef  ffe6b5b3cf1cb6d3328a5a58690
> > > >
> > > > Saw entries like this (I think) for each region which was stuck. A
> > > > simple `assign` in the shell brought them back, but I need to dig in
> > > > some more
> > > to
> > > > understand what went wrong.
> > > >
> > > >
> > > Log?
> > >
> > > HBASE-18152?
> > >
> > > Thanks Josh,
> > > S
> > >
> > >
> > >
> > >
> > > >
> > > > On 4/10/18 4:47 PM, Stack wrote:
> > > >
> > > >> The first release candidate for Apache HBase 2.0.0 is available for
> > > >> downloading and testing.
> > > >>
> > > >> Artifacts are available here:
> > > >>
> > > >>   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> > > >>
> > > >> Maven artifacts are available in the staging repository at:
> > > >>
> > > >>   https://repository.apache.org/content/repositories/
> > > orgapachehbase-1209
> > > >>
> > > >> All artifacts are signed with my signing key 8ACC93D2, which is
> > > >> also in the project KEYS file at
> > > >>
> > > >>   http://www.apache.org/dist/hbase/KEYS
> > > >>
> > > >> These artifacts were tagged 2.0.0RC0 at hash
> > > >> 011dd2dae33456b3a2bcc2513e9fdd29de23be46
> > > >>
> > > >> Please review 'Upgrading from 1.x to 2.x' in the bundled HBase
> > > >> 2.0.0 Reference Guide before installing or upgrading for a list of
> > > >> incompatibilities, major changes, and notable new features. Be
> > > >> aware
> > > that
> > > >> according to our adopted Semantic Versioning guidelines[1], we've
> > > >> allow ourselves to make breaking changes in this major version
> > > >> release. For example, Coprocessors will need to be recast to fit
> > > >&

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Stack]

Yeah, what Ashish says Umesh (and yeah, checkout HBASE-20385 for the why
sir).

Any one else given the RC a try? Its seven days now. Time is about up. I
have two -1s, one of which I think I can overturn. Any other feedback on
the RC? Any PMCers tried it?

Thanks,

St.Ack


On Mon, Apr 16, 2018 at 9:41 PM, ashish singhi <ashish.sin...@huawei.com>
wrote:

> bq. signatures & sums- NOT
> OK
> (md5 checksums missing)
>
> This is intentional I think, check HBASE-20385.
>
> Regards,
> Ashish
>
> -Original Message-
> From: Umesh Agashe [mailto:uaga...@cloudera.com]
> Sent: Tuesday, April 17, 2018 4:01 AM
> To: dev@hbase.apache.org
> Subject: Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is
> available
>
> -1 non-binding (hbck with write operations disabled not included)
>
> download src & bin tar ball   - OK
> signatures & sums- NOT OK
> (md5 checksums missing)
> build from source (openjdk version "1.8.0_151")  - OK
> rat check   -
> OK
> start local instance from bin & CRUD from shell  - OK
> LTT write, read1 million rows, 2 cols/row  - OK
> check logs - OK
>
>
> On Fri, Apr 13, 2018 at 10:55 AM, Stack <st...@duboce.net> wrote:
>
> > On Fri, Apr 13, 2018 at 10:53 AM, Josh Elser <els...@apache.org> wrote:
> >
> > > Was poking around with PE on a few nodes (I forget the exact
> > > circumstances, need to look back at this), and ran into a case where
> > > ~35 regions were left as RIT
> > >
> > > 2018-04-12 22:05:24,431 ERROR
> > > [master/ctr-e138-1518143905142-221855-01-
> > 02:16000]
> > > procedure2.ProcedureExecutor: Corrupt pid=3580, ppid=3534,
> > > state=RUNNABLE:REGION_TRANSITION_QUEUE; AssignProcedure
> table=TestTable,
> > > region=71fef  ffe6b5b3cf1cb6d3328a5a58690
> > >
> > > Saw entries like this (I think) for each region which was stuck. A
> > > simple `assign` in the shell brought them back, but I need to dig in
> > > some more
> > to
> > > understand what went wrong.
> > >
> > >
> > Log?
> >
> > HBASE-18152?
> >
> > Thanks Josh,
> > S
> >
> >
> >
> >
> > >
> > > On 4/10/18 4:47 PM, Stack wrote:
> > >
> > >> The first release candidate for Apache HBase 2.0.0 is available for
> > >> downloading and testing.
> > >>
> > >> Artifacts are available here:
> > >>
> > >>   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> > >>
> > >> Maven artifacts are available in the staging repository at:
> > >>
> > >>   https://repository.apache.org/content/repositories/
> > orgapachehbase-1209
> > >>
> > >> All artifacts are signed with my signing key 8ACC93D2, which is
> > >> also in the project KEYS file at
> > >>
> > >>   http://www.apache.org/dist/hbase/KEYS
> > >>
> > >> These artifacts were tagged 2.0.0RC0 at hash
> > >> 011dd2dae33456b3a2bcc2513e9fdd29de23be46
> > >>
> > >> Please review 'Upgrading from 1.x to 2.x' in the bundled HBase
> > >> 2.0.0 Reference Guide before installing or upgrading for a list of
> > >> incompatibilities, major changes, and notable new features. Be
> > >> aware
> > that
> > >> according to our adopted Semantic Versioning guidelines[1], we've
> > >> allow ourselves to make breaking changes in this major version
> > >> release. For example, Coprocessors will need to be recast to fit
> > >> more constrained CP APIs and a rolling upgrade of an hbase-1.x
> > >> install to hbase-2.x without downtime is (currently) not possible.
> > >> That said, a bunch of effort has been expended mitigating
> > >> differences; a hbase-1.x client can perform DML against an hbase-2
> > >> cluster.
> > >>
> > >> For the full list of ~6k issues addressed, see [2]. There are also
> > >> CHANGES.md and RELEASENOTES.md in the root directory of the source
> > >> tarball.
> > >>
> > >> Please take a few minutes to verify the release and vote on
> > >> releasing
> > it:
> > >>
> > >> [ ] +1 Release this package as Apache HBase 2.0.0 [ ] +0 no opinion
> > >> [ ] -1 Do not release this package because...
> > >>
> > >> This VOTE will run for one week and close Tuesday, April 17, 2018 @
> > 13:00
> > >> PST.
> > >>
> > >> Thanks to the myriad who have helped out with this release, Your
> > >> 2.0.0 Release Manager
> > >>
> > >> 1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
> > >> 2.  https://s.apache.org/zwS9
> > >>
> > >>
> >
>

RE: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[ashish singhi]

bq. signatures & sums- NOT OK
(md5 checksums missing)

This is intentional I think, check HBASE-20385.

Regards,
Ashish 

-Original Message-
From: Umesh Agashe [mailto:uaga...@cloudera.com] 
Sent: Tuesday, April 17, 2018 4:01 AM
To: dev@hbase.apache.org
Subject: Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

-1 non-binding (hbck with write operations disabled not included)

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


On Fri, Apr 13, 2018 at 10:55 AM, Stack <st...@duboce.net> wrote:

> On Fri, Apr 13, 2018 at 10:53 AM, Josh Elser <els...@apache.org> wrote:
>
> > Was poking around with PE on a few nodes (I forget the exact 
> > circumstances, need to look back at this), and ran into a case where 
> > ~35 regions were left as RIT
> >
> > 2018-04-12 22:05:24,431 ERROR 
> > [master/ctr-e138-1518143905142-221855-01-
> 02:16000]
> > procedure2.ProcedureExecutor: Corrupt pid=3580, ppid=3534, 
> > state=RUNNABLE:REGION_TRANSITION_QUEUE; AssignProcedure table=TestTable,
> > region=71fef  ffe6b5b3cf1cb6d3328a5a58690
> >
> > Saw entries like this (I think) for each region which was stuck. A 
> > simple `assign` in the shell brought them back, but I need to dig in 
> > some more
> to
> > understand what went wrong.
> >
> >
> Log?
>
> HBASE-18152?
>
> Thanks Josh,
> S
>
>
>
>
> >
> > On 4/10/18 4:47 PM, Stack wrote:
> >
> >> The first release candidate for Apache HBase 2.0.0 is available for 
> >> downloading and testing.
> >>
> >> Artifacts are available here:
> >>
> >>   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> >>
> >> Maven artifacts are available in the staging repository at:
> >>
> >>   https://repository.apache.org/content/repositories/
> orgapachehbase-1209
> >>
> >> All artifacts are signed with my signing key 8ACC93D2, which is 
> >> also in the project KEYS file at
> >>
> >>   http://www.apache.org/dist/hbase/KEYS
> >>
> >> These artifacts were tagged 2.0.0RC0 at hash 
> >> 011dd2dae33456b3a2bcc2513e9fdd29de23be46
> >>
> >> Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 
> >> 2.0.0 Reference Guide before installing or upgrading for a list of 
> >> incompatibilities, major changes, and notable new features. Be 
> >> aware
> that
> >> according to our adopted Semantic Versioning guidelines[1], we've 
> >> allow ourselves to make breaking changes in this major version 
> >> release. For example, Coprocessors will need to be recast to fit 
> >> more constrained CP APIs and a rolling upgrade of an hbase-1.x 
> >> install to hbase-2.x without downtime is (currently) not possible. 
> >> That said, a bunch of effort has been expended mitigating 
> >> differences; a hbase-1.x client can perform DML against an hbase-2 
> >> cluster.
> >>
> >> For the full list of ~6k issues addressed, see [2]. There are also 
> >> CHANGES.md and RELEASENOTES.md in the root directory of the source 
> >> tarball.
> >>
> >> Please take a few minutes to verify the release and vote on 
> >> releasing
> it:
> >>
> >> [ ] +1 Release this package as Apache HBase 2.0.0 [ ] +0 no opinion 
> >> [ ] -1 Do not release this package because...
> >>
> >> This VOTE will run for one week and close Tuesday, April 17, 2018 @
> 13:00
> >> PST.
> >>
> >> Thanks to the myriad who have helped out with this release, Your 
> >> 2.0.0 Release Manager
> >>
> >> 1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
> >> 2.  https://s.apache.org/zwS9
> >>
> >>
>

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Umesh Agashe]

-1 non-binding (hbck with write operations disabled not included)

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


On Fri, Apr 13, 2018 at 10:55 AM, Stack  wrote:

> On Fri, Apr 13, 2018 at 10:53 AM, Josh Elser  wrote:
>
> > Was poking around with PE on a few nodes (I forget the exact
> > circumstances, need to look back at this), and ran into a case where ~35
> > regions were left as RIT
> >
> > 2018-04-12 22:05:24,431 ERROR [master/ctr-e138-1518143905142-221855-01-
> 02:16000]
> > procedure2.ProcedureExecutor: Corrupt pid=3580, ppid=3534,
> > state=RUNNABLE:REGION_TRANSITION_QUEUE; AssignProcedure table=TestTable,
> > region=71fef  ffe6b5b3cf1cb6d3328a5a58690
> >
> > Saw entries like this (I think) for each region which was stuck. A simple
> > `assign` in the shell brought them back, but I need to dig in some more
> to
> > understand what went wrong.
> >
> >
> Log?
>
> HBASE-18152?
>
> Thanks Josh,
> S
>
>
>
>
> >
> > On 4/10/18 4:47 PM, Stack wrote:
> >
> >> The first release candidate for Apache HBase 2.0.0 is available for
> >> downloading and testing.
> >>
> >> Artifacts are available here:
> >>
> >>   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> >>
> >> Maven artifacts are available in the staging repository at:
> >>
> >>   https://repository.apache.org/content/repositories/
> orgapachehbase-1209
> >>
> >> All artifacts are signed with my signing key 8ACC93D2, which is also
> >> in the project KEYS file at
> >>
> >>   http://www.apache.org/dist/hbase/KEYS
> >>
> >> These artifacts were tagged 2.0.0RC0 at
> >> hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
> >>
> >> Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
> >> Reference Guide before installing or upgrading for a list of
> >> incompatibilities, major changes, and notable new features. Be aware
> that
> >> according to our adopted Semantic Versioning guidelines[1], we've allow
> >> ourselves to make breaking changes in this major version release. For
> >> example, Coprocessors will need to be recast to fit more constrained CP
> >> APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x without
> >> downtime is (currently) not possible. That said, a bunch of effort has
> >> been
> >> expended mitigating differences; a hbase-1.x client can perform DML
> >> against
> >> an hbase-2 cluster.
> >>
> >> For the full list of ~6k issues addressed, see [2]. There are also
> >> CHANGES.md and RELEASENOTES.md in the root directory of the source
> >> tarball.
> >>
> >> Please take a few minutes to verify the release and vote on releasing
> it:
> >>
> >> [ ] +1 Release this package as Apache HBase 2.0.0
> >> [ ] +0 no opinion
> >> [ ] -1 Do not release this package because...
> >>
> >> This VOTE will run for one week and close Tuesday, April 17, 2018 @
> 13:00
> >> PST.
> >>
> >> Thanks to the myriad who have helped out with this release,
> >> Your 2.0.0 Release Manager
> >>
> >> 1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
> >> 2.  https://s.apache.org/zwS9
> >>
> >>
>

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Stack]

On Fri, Apr 13, 2018 at 10:53 AM, Josh Elser  wrote:

> Was poking around with PE on a few nodes (I forget the exact
> circumstances, need to look back at this), and ran into a case where ~35
> regions were left as RIT
>
> 2018-04-12 22:05:24,431 ERROR 
> [master/ctr-e138-1518143905142-221855-01-02:16000]
> procedure2.ProcedureExecutor: Corrupt pid=3580, ppid=3534,
> state=RUNNABLE:REGION_TRANSITION_QUEUE; AssignProcedure table=TestTable,
> region=71fef  ffe6b5b3cf1cb6d3328a5a58690
>
> Saw entries like this (I think) for each region which was stuck. A simple
> `assign` in the shell brought them back, but I need to dig in some more to
> understand what went wrong.
>
>
Log?

HBASE-18152?

Thanks Josh,
S




>
> On 4/10/18 4:47 PM, Stack wrote:
>
>> The first release candidate for Apache HBase 2.0.0 is available for
>> downloading and testing.
>>
>> Artifacts are available here:
>>
>>   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
>>
>> Maven artifacts are available in the staging repository at:
>>
>>   https://repository.apache.org/content/repositories/orgapachehbase-1209
>>
>> All artifacts are signed with my signing key 8ACC93D2, which is also
>> in the project KEYS file at
>>
>>   http://www.apache.org/dist/hbase/KEYS
>>
>> These artifacts were tagged 2.0.0RC0 at
>> hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
>>
>> Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
>> Reference Guide before installing or upgrading for a list of
>> incompatibilities, major changes, and notable new features. Be aware that
>> according to our adopted Semantic Versioning guidelines[1], we've allow
>> ourselves to make breaking changes in this major version release. For
>> example, Coprocessors will need to be recast to fit more constrained CP
>> APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x without
>> downtime is (currently) not possible. That said, a bunch of effort has
>> been
>> expended mitigating differences; a hbase-1.x client can perform DML
>> against
>> an hbase-2 cluster.
>>
>> For the full list of ~6k issues addressed, see [2]. There are also
>> CHANGES.md and RELEASENOTES.md in the root directory of the source
>> tarball.
>>
>> Please take a few minutes to verify the release and vote on releasing it:
>>
>> [ ] +1 Release this package as Apache HBase 2.0.0
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because...
>>
>> This VOTE will run for one week and close Tuesday, April 17, 2018 @ 13:00
>> PST.
>>
>> Thanks to the myriad who have helped out with this release,
>> Your 2.0.0 Release Manager
>>
>> 1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
>> 2.  https://s.apache.org/zwS9
>>
>>

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Josh Elser]

Was poking around with PE on a few nodes (I forget the exact 
circumstances, need to look back at this), and ran into a case where ~35 
regions were left as RIT


2018-04-12 22:05:24,431 ERROR 
[master/ctr-e138-1518143905142-221855-01-02:16000] 
procedure2.ProcedureExecutor: Corrupt pid=3580, ppid=3534, 
state=RUNNABLE:REGION_TRANSITION_QUEUE; AssignProcedure table=TestTable, 
region=71fef  ffe6b5b3cf1cb6d3328a5a58690


Saw entries like this (I think) for each region which was stuck. A 
simple `assign` in the shell brought them back, but I need to dig in 
some more to understand what went wrong.


On 4/10/18 4:47 PM, Stack wrote:

The first release candidate for Apache HBase 2.0.0 is available for
downloading and testing.

Artifacts are available here:

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

Maven artifacts are available in the staging repository at:

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

All artifacts are signed with my signing key 8ACC93D2, which is also
in the project KEYS file at

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

These artifacts were tagged 2.0.0RC0 at
hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46

Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
Reference Guide before installing or upgrading for a list of
incompatibilities, major changes, and notable new features. Be aware that
according to our adopted Semantic Versioning guidelines[1], we've allow
ourselves to make breaking changes in this major version release. For
example, Coprocessors will need to be recast to fit more constrained CP
APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x without
downtime is (currently) not possible. That said, a bunch of effort has been
expended mitigating differences; a hbase-1.x client can perform DML against
an hbase-2 cluster.

For the full list of ~6k issues addressed, see [2]. There are also
CHANGES.md and RELEASENOTES.md in the root directory of the source tarball.

Please take a few minutes to verify the release and vote on releasing it:

[ ] +1 Release this package as Apache HBase 2.0.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...

This VOTE will run for one week and close Tuesday, April 17, 2018 @ 13:00
PST.

Thanks to the myriad who have helped out with this release,
Your 2.0.0 Release Manager

1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
2.  https://s.apache.org/zwS9

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Stack]

On Fri, Apr 13, 2018 at 8:07 AM, Peter Somogyi  wrote:

> -1
>
> Tests under hbase-rsgroup fail in setup phase. It is related to
> HBASE-20224, some addendums were not backported to branch-2.0 which causes
> the failure. I'm reopening HBASE-20224 and backport 2 missing commits.
>
>
Thanks Peter. Yeah, go for the backports. That issue was a bit of a mess.

I'm trying to see why we didn't catch this in the nightlies.

Lets not shut down the RC yet. I'd like to see if there are other issues
out there before cutting new RC.

Good stuff,
St.Ack





> On Fri, Apr 13, 2018 at 3:54 PM, Jean-Marc Spaggiari <
> jean-m...@spaggiari.org> wrote:
>
> > Exactly what I was looking for! Thanks Sean!
> >
> > 2018-04-13 9:37 GMT-04:00 Sean Busbey :
> >
> > > Hi JMS!
> > >
> > > Current flaky results for branch-2.0, generated today AFAICT:
> > >
> > > https://builds.apache.org/view/H-L/view/HBase/job/HBase-
> > > Find-Flaky-Tests-branch2.0/lastSuccessfulBuild/artifact/
> > >
> > > you can look at the "dashboard.html" artifact for a human usable idea
> > > of what we think is broken.
> > >
> > > you can fetch the excludes file to get a pattern you can pass to Maven.
> > >
> > >
> > > On Fri, Apr 13, 2018 at 7:40 AM, Jean-Marc Spaggiari
> > >  wrote:
> > > > Do we have a list of tests that we know will not pass this release?
> > > >
> > > > I got those failures so far, but since I want to run multiple runs, I
> > > want
> > > > to make sure to exclude the un-stable tests.
> > > >
> > > > TestAssignmentManagerMetrics.testRITAssignmentManagerMetrics:152
> > Metrics
> > > > Should be equal expected:<1> but was:<0>
> > > > TestReplicationSmallTests.testDisableEnable:198 Replication wasn't
> > > disabled
> > > > TestReplicationSmallTests.testSimplePutDelete:168->
> > TestReplicationBase.
> > > runSimplePutDeleteTest:266
> > > > Waited too much time for put replication
> > > > TestClientOperationTimeout.setUp:99 » SocketTimeout callTimeout=500,
> > > > callDurat...
> > > >
> > > > Thanks,
> > > >
> > > > JMS
> > > >
> > > >
> > > > 2018-04-13 0:19 GMT-04:00 Yu Li :
> > > >
> > > >> bq. I'd imagine that if the difference were large, then yes, it
> should
> > > >> be a blocker
> > > >> -- or we as a community can decide to work on it in a follow-on
> > release
> > > >> making perf a priority (say, 2.1.0).
> > > >> I see, thanks for the clarification boss, makes sense.
> > > >>
> > > >> Best Regards,
> > > >> Yu
> > > >>
> > > >> On 13 April 2018 at 06:02, Stack  wrote:
> > > >>
> > > >> > On Thu, Apr 12, 2018 at 1:47 PM, Stack  wrote:
> > > >> >
> > > >> > > On Tue, Apr 10, 2018 at 2:50 PM, Sean Busbey  >
> > > >> wrote:
> > > >> > >
> > > >> > >> no compat report in the RC directory. does that mean we won't
> > have
> > > one
> > > >> > >> in the dist area?
> > > >> > >>
> > > >> > >>
> > > >> > >> not a blocker; we've been inconsistent on it in prior releases,
> > but
> > > >> > >> the trend seemed to be towards including it.
> > > >> > >>
> > > >> > >>
> > > >> > >
> > > >> > > HBASE-18622 has current state of compatibility compare. Let me
> do
> > a
> > > new
> > > >> > > run and add it to the RC dir.
> > > >> > >
> > > >> >
> > > >> > I just added
> > > >> > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> > > >> > compat-check-v1.2.6-v2.0.0.report.html
> > > >> >
> > > >> > Thanks,
> > > >> > S
> > > >> >
> > > >> >
> > > >> >
> > > >> > > St.Ack
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > >>
> > > >> > >> On Tue, Apr 10, 2018 at 3:47 PM, Stack 
> wrote:
> > > >> > >> > The first release candidate for Apache HBase 2.0.0 is
> available
> > > for
> > > >> > >> > downloading and testing.
> > > >> > >> >
> > > >> > >> > Artifacts are available here:
> > > >> > >> >
> > > >> > >> >  https://dist.apache.org/repos/
> dist/dev/hbase/hbase-2.0.0RC0/
> > > >> > >> >
> > > >> > >> > Maven artifacts are available in the staging repository at:
> > > >> > >> >
> > > >> > >> >  https://repository.apache.org/content/repositories/
> > > >> > orgapachehbase-1209
> > > >> > >> >
> > > >> > >> > All artifacts are signed with my signing key 8ACC93D2, which
> is
> > > also
> > > >> > >> > in the project KEYS file at
> > > >> > >> >
> > > >> > >> >  http://www.apache.org/dist/hbase/KEYS
> > > >> > >> >
> > > >> > >> > These artifacts were tagged 2.0.0RC0 at
> > > >> > >> > hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
> > > >> > >> >
> > > >> > >> > Please review 'Upgrading from 1.x to 2.x' in the bundled
> HBase
> > > 2.0.0
> > > >> > >> > Reference Guide before installing or upgrading for a list of
> > > >> > >> > incompatibilities, major changes, and notable new features.
> Be
> > > aware
> > > >> > >> that
> > > >> > >> > according to our adopted Semantic Versioning guidelines[1],
> > we've
> > > >> > allow
> > > >> > >> > ourselves to make breaking changes in this major 

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Stack]

On Fri, Apr 13, 2018 at 5:40 AM, Jean-Marc Spaggiari <
jean-m...@spaggiari.org> wrote:

> Do we have a list of tests that we know will not pass this release?
>
> I got those failures so far, but since I want to run multiple runs, I want
> to make sure to exclude the un-stable tests.
>
> TestAssignmentManagerMetrics.testRITAssignmentManagerMetrics:152 Metrics
> Should be equal expected:<1> but was:<0>
> TestReplicationSmallTests.testDisableEnable:198 Replication wasn't
> disabled
> TestReplicationSmallTests.testSimplePutDelete:168->TestReplicationBase.
> runSimplePutDeleteTest:266
> Waited too much time for put replication
> TestClientOperationTimeout.setUp:99 » SocketTimeout callTimeout=500,
> callDurat...
>
>
Sorry about that JMS. We just had a nice set of stable runs but a little
bit of rot seems to have set in in the last day or so. Probably needs a
little attention to shut down the new set of flakies.

Thanks,
St.Ack



> Thanks,
>
> JMS
>
>
> 2018-04-13 0:19 GMT-04:00 Yu Li :
>
> > bq. I'd imagine that if the difference were large, then yes, it should
> > be a blocker
> > -- or we as a community can decide to work on it in a follow-on release
> > making perf a priority (say, 2.1.0).
> > I see, thanks for the clarification boss, makes sense.
> >
> > Best Regards,
> > Yu
> >
> > On 13 April 2018 at 06:02, Stack  wrote:
> >
> > > On Thu, Apr 12, 2018 at 1:47 PM, Stack  wrote:
> > >
> > > > On Tue, Apr 10, 2018 at 2:50 PM, Sean Busbey 
> > wrote:
> > > >
> > > >> no compat report in the RC directory. does that mean we won't have
> one
> > > >> in the dist area?
> > > >>
> > > >>
> > > >> not a blocker; we've been inconsistent on it in prior releases, but
> > > >> the trend seemed to be towards including it.
> > > >>
> > > >>
> > > >
> > > > HBASE-18622 has current state of compatibility compare. Let me do a
> new
> > > > run and add it to the RC dir.
> > > >
> > >
> > > I just added
> > > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> > > compat-check-v1.2.6-v2.0.0.report.html
> > >
> > > Thanks,
> > > S
> > >
> > >
> > >
> > > > St.Ack
> > > >
> > > >
> > > >
> > > >>
> > > >> On Tue, Apr 10, 2018 at 3:47 PM, Stack  wrote:
> > > >> > The first release candidate for Apache HBase 2.0.0 is available
> for
> > > >> > downloading and testing.
> > > >> >
> > > >> > Artifacts are available here:
> > > >> >
> > > >> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> > > >> >
> > > >> > Maven artifacts are available in the staging repository at:
> > > >> >
> > > >> >  https://repository.apache.org/content/repositories/
> > > orgapachehbase-1209
> > > >> >
> > > >> > All artifacts are signed with my signing key 8ACC93D2, which is
> also
> > > >> > in the project KEYS file at
> > > >> >
> > > >> >  http://www.apache.org/dist/hbase/KEYS
> > > >> >
> > > >> > These artifacts were tagged 2.0.0RC0 at
> > > >> > hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
> > > >> >
> > > >> > Please review 'Upgrading from 1.x to 2.x' in the bundled HBase
> 2.0.0
> > > >> > Reference Guide before installing or upgrading for a list of
> > > >> > incompatibilities, major changes, and notable new features. Be
> aware
> > > >> that
> > > >> > according to our adopted Semantic Versioning guidelines[1], we've
> > > allow
> > > >> > ourselves to make breaking changes in this major version release.
> > For
> > > >> > example, Coprocessors will need to be recast to fit more
> constrained
> > > CP
> > > >> > APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x
> > > without
> > > >> > downtime is (currently) not possible. That said, a bunch of effort
> > has
> > > >> been
> > > >> > expended mitigating differences; a hbase-1.x client can perform
> DML
> > > >> against
> > > >> > an hbase-2 cluster.
> > > >> >
> > > >> > For the full list of ~6k issues addressed, see [2]. There are also
> > > >> > CHANGES.md and RELEASENOTES.md in the root directory of the source
> > > >> tarball.
> > > >> >
> > > >> > Please take a few minutes to verify the release and vote on
> > releasing
> > > >> it:
> > > >> >
> > > >> > [ ] +1 Release this package as Apache HBase 2.0.0
> > > >> > [ ] +0 no opinion
> > > >> > [ ] -1 Do not release this package because...
> > > >> >
> > > >> > This VOTE will run for one week and close Tuesday, April 17, 2018
> @
> > > >> 13:00
> > > >> > PST.
> > > >> >
> > > >> > Thanks to the myriad who have helped out with this release,
> > > >> > Your 2.0.0 Release Manager
> > > >> >
> > > >> > 1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
> > > >> > 2.  https://s.apache.org/zwS9
> > > >>
> > > >
> > > >
> > >
> >
>

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Peter Somogyi]

-1

Tests under hbase-rsgroup fail in setup phase. It is related to
HBASE-20224, some addendums were not backported to branch-2.0 which causes
the failure. I'm reopening HBASE-20224 and backport 2 missing commits.

On Fri, Apr 13, 2018 at 3:54 PM, Jean-Marc Spaggiari <
jean-m...@spaggiari.org> wrote:

> Exactly what I was looking for! Thanks Sean!
>
> 2018-04-13 9:37 GMT-04:00 Sean Busbey :
>
> > Hi JMS!
> >
> > Current flaky results for branch-2.0, generated today AFAICT:
> >
> > https://builds.apache.org/view/H-L/view/HBase/job/HBase-
> > Find-Flaky-Tests-branch2.0/lastSuccessfulBuild/artifact/
> >
> > you can look at the "dashboard.html" artifact for a human usable idea
> > of what we think is broken.
> >
> > you can fetch the excludes file to get a pattern you can pass to Maven.
> >
> >
> > On Fri, Apr 13, 2018 at 7:40 AM, Jean-Marc Spaggiari
> >  wrote:
> > > Do we have a list of tests that we know will not pass this release?
> > >
> > > I got those failures so far, but since I want to run multiple runs, I
> > want
> > > to make sure to exclude the un-stable tests.
> > >
> > > TestAssignmentManagerMetrics.testRITAssignmentManagerMetrics:152
> Metrics
> > > Should be equal expected:<1> but was:<0>
> > > TestReplicationSmallTests.testDisableEnable:198 Replication wasn't
> > disabled
> > > TestReplicationSmallTests.testSimplePutDelete:168->
> TestReplicationBase.
> > runSimplePutDeleteTest:266
> > > Waited too much time for put replication
> > > TestClientOperationTimeout.setUp:99 » SocketTimeout callTimeout=500,
> > > callDurat...
> > >
> > > Thanks,
> > >
> > > JMS
> > >
> > >
> > > 2018-04-13 0:19 GMT-04:00 Yu Li :
> > >
> > >> bq. I'd imagine that if the difference were large, then yes, it should
> > >> be a blocker
> > >> -- or we as a community can decide to work on it in a follow-on
> release
> > >> making perf a priority (say, 2.1.0).
> > >> I see, thanks for the clarification boss, makes sense.
> > >>
> > >> Best Regards,
> > >> Yu
> > >>
> > >> On 13 April 2018 at 06:02, Stack  wrote:
> > >>
> > >> > On Thu, Apr 12, 2018 at 1:47 PM, Stack  wrote:
> > >> >
> > >> > > On Tue, Apr 10, 2018 at 2:50 PM, Sean Busbey 
> > >> wrote:
> > >> > >
> > >> > >> no compat report in the RC directory. does that mean we won't
> have
> > one
> > >> > >> in the dist area?
> > >> > >>
> > >> > >>
> > >> > >> not a blocker; we've been inconsistent on it in prior releases,
> but
> > >> > >> the trend seemed to be towards including it.
> > >> > >>
> > >> > >>
> > >> > >
> > >> > > HBASE-18622 has current state of compatibility compare. Let me do
> a
> > new
> > >> > > run and add it to the RC dir.
> > >> > >
> > >> >
> > >> > I just added
> > >> > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> > >> > compat-check-v1.2.6-v2.0.0.report.html
> > >> >
> > >> > Thanks,
> > >> > S
> > >> >
> > >> >
> > >> >
> > >> > > St.Ack
> > >> > >
> > >> > >
> > >> > >
> > >> > >>
> > >> > >> On Tue, Apr 10, 2018 at 3:47 PM, Stack  wrote:
> > >> > >> > The first release candidate for Apache HBase 2.0.0 is available
> > for
> > >> > >> > downloading and testing.
> > >> > >> >
> > >> > >> > Artifacts are available here:
> > >> > >> >
> > >> > >> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> > >> > >> >
> > >> > >> > Maven artifacts are available in the staging repository at:
> > >> > >> >
> > >> > >> >  https://repository.apache.org/content/repositories/
> > >> > orgapachehbase-1209
> > >> > >> >
> > >> > >> > All artifacts are signed with my signing key 8ACC93D2, which is
> > also
> > >> > >> > in the project KEYS file at
> > >> > >> >
> > >> > >> >  http://www.apache.org/dist/hbase/KEYS
> > >> > >> >
> > >> > >> > These artifacts were tagged 2.0.0RC0 at
> > >> > >> > hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
> > >> > >> >
> > >> > >> > Please review 'Upgrading from 1.x to 2.x' in the bundled HBase
> > 2.0.0
> > >> > >> > Reference Guide before installing or upgrading for a list of
> > >> > >> > incompatibilities, major changes, and notable new features. Be
> > aware
> > >> > >> that
> > >> > >> > according to our adopted Semantic Versioning guidelines[1],
> we've
> > >> > allow
> > >> > >> > ourselves to make breaking changes in this major version
> release.
> > >> For
> > >> > >> > example, Coprocessors will need to be recast to fit more
> > constrained
> > >> > CP
> > >> > >> > APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x
> > >> > without
> > >> > >> > downtime is (currently) not possible. That said, a bunch of
> > effort
> > >> has
> > >> > >> been
> > >> > >> > expended mitigating differences; a hbase-1.x client can perform
> > DML
> > >> > >> against
> > >> > >> > an hbase-2 cluster.
> > >> > >> >
> > >> > >> > For the full list of ~6k issues addressed, see [2]. There are
> > also
> > >> > >> > CHANGES.md and RELEASENOTES.md in the root 

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Jean-Marc Spaggiari]

Exactly what I was looking for! Thanks Sean!

2018-04-13 9:37 GMT-04:00 Sean Busbey :

> Hi JMS!
>
> Current flaky results for branch-2.0, generated today AFAICT:
>
> https://builds.apache.org/view/H-L/view/HBase/job/HBase-
> Find-Flaky-Tests-branch2.0/lastSuccessfulBuild/artifact/
>
> you can look at the "dashboard.html" artifact for a human usable idea
> of what we think is broken.
>
> you can fetch the excludes file to get a pattern you can pass to Maven.
>
>
> On Fri, Apr 13, 2018 at 7:40 AM, Jean-Marc Spaggiari
>  wrote:
> > Do we have a list of tests that we know will not pass this release?
> >
> > I got those failures so far, but since I want to run multiple runs, I
> want
> > to make sure to exclude the un-stable tests.
> >
> > TestAssignmentManagerMetrics.testRITAssignmentManagerMetrics:152 Metrics
> > Should be equal expected:<1> but was:<0>
> > TestReplicationSmallTests.testDisableEnable:198 Replication wasn't
> disabled
> > TestReplicationSmallTests.testSimplePutDelete:168->TestReplicationBase.
> runSimplePutDeleteTest:266
> > Waited too much time for put replication
> > TestClientOperationTimeout.setUp:99 » SocketTimeout callTimeout=500,
> > callDurat...
> >
> > Thanks,
> >
> > JMS
> >
> >
> > 2018-04-13 0:19 GMT-04:00 Yu Li :
> >
> >> bq. I'd imagine that if the difference were large, then yes, it should
> >> be a blocker
> >> -- or we as a community can decide to work on it in a follow-on release
> >> making perf a priority (say, 2.1.0).
> >> I see, thanks for the clarification boss, makes sense.
> >>
> >> Best Regards,
> >> Yu
> >>
> >> On 13 April 2018 at 06:02, Stack  wrote:
> >>
> >> > On Thu, Apr 12, 2018 at 1:47 PM, Stack  wrote:
> >> >
> >> > > On Tue, Apr 10, 2018 at 2:50 PM, Sean Busbey 
> >> wrote:
> >> > >
> >> > >> no compat report in the RC directory. does that mean we won't have
> one
> >> > >> in the dist area?
> >> > >>
> >> > >>
> >> > >> not a blocker; we've been inconsistent on it in prior releases, but
> >> > >> the trend seemed to be towards including it.
> >> > >>
> >> > >>
> >> > >
> >> > > HBASE-18622 has current state of compatibility compare. Let me do a
> new
> >> > > run and add it to the RC dir.
> >> > >
> >> >
> >> > I just added
> >> > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> >> > compat-check-v1.2.6-v2.0.0.report.html
> >> >
> >> > Thanks,
> >> > S
> >> >
> >> >
> >> >
> >> > > St.Ack
> >> > >
> >> > >
> >> > >
> >> > >>
> >> > >> On Tue, Apr 10, 2018 at 3:47 PM, Stack  wrote:
> >> > >> > The first release candidate for Apache HBase 2.0.0 is available
> for
> >> > >> > downloading and testing.
> >> > >> >
> >> > >> > Artifacts are available here:
> >> > >> >
> >> > >> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> >> > >> >
> >> > >> > Maven artifacts are available in the staging repository at:
> >> > >> >
> >> > >> >  https://repository.apache.org/content/repositories/
> >> > orgapachehbase-1209
> >> > >> >
> >> > >> > All artifacts are signed with my signing key 8ACC93D2, which is
> also
> >> > >> > in the project KEYS file at
> >> > >> >
> >> > >> >  http://www.apache.org/dist/hbase/KEYS
> >> > >> >
> >> > >> > These artifacts were tagged 2.0.0RC0 at
> >> > >> > hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
> >> > >> >
> >> > >> > Please review 'Upgrading from 1.x to 2.x' in the bundled HBase
> 2.0.0
> >> > >> > Reference Guide before installing or upgrading for a list of
> >> > >> > incompatibilities, major changes, and notable new features. Be
> aware
> >> > >> that
> >> > >> > according to our adopted Semantic Versioning guidelines[1], we've
> >> > allow
> >> > >> > ourselves to make breaking changes in this major version release.
> >> For
> >> > >> > example, Coprocessors will need to be recast to fit more
> constrained
> >> > CP
> >> > >> > APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x
> >> > without
> >> > >> > downtime is (currently) not possible. That said, a bunch of
> effort
> >> has
> >> > >> been
> >> > >> > expended mitigating differences; a hbase-1.x client can perform
> DML
> >> > >> against
> >> > >> > an hbase-2 cluster.
> >> > >> >
> >> > >> > For the full list of ~6k issues addressed, see [2]. There are
> also
> >> > >> > CHANGES.md and RELEASENOTES.md in the root directory of the
> source
> >> > >> tarball.
> >> > >> >
> >> > >> > Please take a few minutes to verify the release and vote on
> >> releasing
> >> > >> it:
> >> > >> >
> >> > >> > [ ] +1 Release this package as Apache HBase 2.0.0
> >> > >> > [ ] +0 no opinion
> >> > >> > [ ] -1 Do not release this package because...
> >> > >> >
> >> > >> > This VOTE will run for one week and close Tuesday, April 17,
> 2018 @
> >> > >> 13:00
> >> > >> > PST.
> >> > >> >
> >> > >> > Thanks to the myriad who have helped out with this release,
> >> > >> > Your 2.0.0 Release Manager
> >> > >> >
> >> > >> > 

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Sean Busbey]

Hi JMS!

Current flaky results for branch-2.0, generated today AFAICT:

https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests-branch2.0/lastSuccessfulBuild/artifact/

you can look at the "dashboard.html" artifact for a human usable idea
of what we think is broken.

you can fetch the excludes file to get a pattern you can pass to Maven.


On Fri, Apr 13, 2018 at 7:40 AM, Jean-Marc Spaggiari
 wrote:
> Do we have a list of tests that we know will not pass this release?
>
> I got those failures so far, but since I want to run multiple runs, I want
> to make sure to exclude the un-stable tests.
>
> TestAssignmentManagerMetrics.testRITAssignmentManagerMetrics:152 Metrics
> Should be equal expected:<1> but was:<0>
> TestReplicationSmallTests.testDisableEnable:198 Replication wasn't disabled
> TestReplicationSmallTests.testSimplePutDelete:168->TestReplicationBase.runSimplePutDeleteTest:266
> Waited too much time for put replication
> TestClientOperationTimeout.setUp:99 » SocketTimeout callTimeout=500,
> callDurat...
>
> Thanks,
>
> JMS
>
>
> 2018-04-13 0:19 GMT-04:00 Yu Li :
>
>> bq. I'd imagine that if the difference were large, then yes, it should
>> be a blocker
>> -- or we as a community can decide to work on it in a follow-on release
>> making perf a priority (say, 2.1.0).
>> I see, thanks for the clarification boss, makes sense.
>>
>> Best Regards,
>> Yu
>>
>> On 13 April 2018 at 06:02, Stack  wrote:
>>
>> > On Thu, Apr 12, 2018 at 1:47 PM, Stack  wrote:
>> >
>> > > On Tue, Apr 10, 2018 at 2:50 PM, Sean Busbey 
>> wrote:
>> > >
>> > >> no compat report in the RC directory. does that mean we won't have one
>> > >> in the dist area?
>> > >>
>> > >>
>> > >> not a blocker; we've been inconsistent on it in prior releases, but
>> > >> the trend seemed to be towards including it.
>> > >>
>> > >>
>> > >
>> > > HBASE-18622 has current state of compatibility compare. Let me do a new
>> > > run and add it to the RC dir.
>> > >
>> >
>> > I just added
>> > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
>> > compat-check-v1.2.6-v2.0.0.report.html
>> >
>> > Thanks,
>> > S
>> >
>> >
>> >
>> > > St.Ack
>> > >
>> > >
>> > >
>> > >>
>> > >> On Tue, Apr 10, 2018 at 3:47 PM, Stack  wrote:
>> > >> > The first release candidate for Apache HBase 2.0.0 is available for
>> > >> > downloading and testing.
>> > >> >
>> > >> > Artifacts are available here:
>> > >> >
>> > >> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
>> > >> >
>> > >> > Maven artifacts are available in the staging repository at:
>> > >> >
>> > >> >  https://repository.apache.org/content/repositories/
>> > orgapachehbase-1209
>> > >> >
>> > >> > All artifacts are signed with my signing key 8ACC93D2, which is also
>> > >> > in the project KEYS file at
>> > >> >
>> > >> >  http://www.apache.org/dist/hbase/KEYS
>> > >> >
>> > >> > These artifacts were tagged 2.0.0RC0 at
>> > >> > hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
>> > >> >
>> > >> > Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
>> > >> > Reference Guide before installing or upgrading for a list of
>> > >> > incompatibilities, major changes, and notable new features. Be aware
>> > >> that
>> > >> > according to our adopted Semantic Versioning guidelines[1], we've
>> > allow
>> > >> > ourselves to make breaking changes in this major version release.
>> For
>> > >> > example, Coprocessors will need to be recast to fit more constrained
>> > CP
>> > >> > APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x
>> > without
>> > >> > downtime is (currently) not possible. That said, a bunch of effort
>> has
>> > >> been
>> > >> > expended mitigating differences; a hbase-1.x client can perform DML
>> > >> against
>> > >> > an hbase-2 cluster.
>> > >> >
>> > >> > For the full list of ~6k issues addressed, see [2]. There are also
>> > >> > CHANGES.md and RELEASENOTES.md in the root directory of the source
>> > >> tarball.
>> > >> >
>> > >> > Please take a few minutes to verify the release and vote on
>> releasing
>> > >> it:
>> > >> >
>> > >> > [ ] +1 Release this package as Apache HBase 2.0.0
>> > >> > [ ] +0 no opinion
>> > >> > [ ] -1 Do not release this package because...
>> > >> >
>> > >> > This VOTE will run for one week and close Tuesday, April 17, 2018 @
>> > >> 13:00
>> > >> > PST.
>> > >> >
>> > >> > Thanks to the myriad who have helped out with this release,
>> > >> > Your 2.0.0 Release Manager
>> > >> >
>> > >> > 1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
>> > >> > 2.  https://s.apache.org/zwS9
>> > >>
>> > >
>> > >
>> >
>>

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Jean-Marc Spaggiari]

Do we have a list of tests that we know will not pass this release?

I got those failures so far, but since I want to run multiple runs, I want
to make sure to exclude the un-stable tests.

TestAssignmentManagerMetrics.testRITAssignmentManagerMetrics:152 Metrics
Should be equal expected:<1> but was:<0>
TestReplicationSmallTests.testDisableEnable:198 Replication wasn't disabled
TestReplicationSmallTests.testSimplePutDelete:168->TestReplicationBase.runSimplePutDeleteTest:266
Waited too much time for put replication
TestClientOperationTimeout.setUp:99 » SocketTimeout callTimeout=500,
callDurat...

Thanks,

JMS


2018-04-13 0:19 GMT-04:00 Yu Li :

> bq. I'd imagine that if the difference were large, then yes, it should
> be a blocker
> -- or we as a community can decide to work on it in a follow-on release
> making perf a priority (say, 2.1.0).
> I see, thanks for the clarification boss, makes sense.
>
> Best Regards,
> Yu
>
> On 13 April 2018 at 06:02, Stack  wrote:
>
> > On Thu, Apr 12, 2018 at 1:47 PM, Stack  wrote:
> >
> > > On Tue, Apr 10, 2018 at 2:50 PM, Sean Busbey 
> wrote:
> > >
> > >> no compat report in the RC directory. does that mean we won't have one
> > >> in the dist area?
> > >>
> > >>
> > >> not a blocker; we've been inconsistent on it in prior releases, but
> > >> the trend seemed to be towards including it.
> > >>
> > >>
> > >
> > > HBASE-18622 has current state of compatibility compare. Let me do a new
> > > run and add it to the RC dir.
> > >
> >
> > I just added
> > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> > compat-check-v1.2.6-v2.0.0.report.html
> >
> > Thanks,
> > S
> >
> >
> >
> > > St.Ack
> > >
> > >
> > >
> > >>
> > >> On Tue, Apr 10, 2018 at 3:47 PM, Stack  wrote:
> > >> > The first release candidate for Apache HBase 2.0.0 is available for
> > >> > downloading and testing.
> > >> >
> > >> > Artifacts are available here:
> > >> >
> > >> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> > >> >
> > >> > Maven artifacts are available in the staging repository at:
> > >> >
> > >> >  https://repository.apache.org/content/repositories/
> > orgapachehbase-1209
> > >> >
> > >> > All artifacts are signed with my signing key 8ACC93D2, which is also
> > >> > in the project KEYS file at
> > >> >
> > >> >  http://www.apache.org/dist/hbase/KEYS
> > >> >
> > >> > These artifacts were tagged 2.0.0RC0 at
> > >> > hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
> > >> >
> > >> > Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
> > >> > Reference Guide before installing or upgrading for a list of
> > >> > incompatibilities, major changes, and notable new features. Be aware
> > >> that
> > >> > according to our adopted Semantic Versioning guidelines[1], we've
> > allow
> > >> > ourselves to make breaking changes in this major version release.
> For
> > >> > example, Coprocessors will need to be recast to fit more constrained
> > CP
> > >> > APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x
> > without
> > >> > downtime is (currently) not possible. That said, a bunch of effort
> has
> > >> been
> > >> > expended mitigating differences; a hbase-1.x client can perform DML
> > >> against
> > >> > an hbase-2 cluster.
> > >> >
> > >> > For the full list of ~6k issues addressed, see [2]. There are also
> > >> > CHANGES.md and RELEASENOTES.md in the root directory of the source
> > >> tarball.
> > >> >
> > >> > Please take a few minutes to verify the release and vote on
> releasing
> > >> it:
> > >> >
> > >> > [ ] +1 Release this package as Apache HBase 2.0.0
> > >> > [ ] +0 no opinion
> > >> > [ ] -1 Do not release this package because...
> > >> >
> > >> > This VOTE will run for one week and close Tuesday, April 17, 2018 @
> > >> 13:00
> > >> > PST.
> > >> >
> > >> > Thanks to the myriad who have helped out with this release,
> > >> > Your 2.0.0 Release Manager
> > >> >
> > >> > 1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
> > >> > 2.  https://s.apache.org/zwS9
> > >>
> > >
> > >
> >
>

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Yu Li]

bq. I'd imagine that if the difference were large, then yes, it should
be a blocker
-- or we as a community can decide to work on it in a follow-on release
making perf a priority (say, 2.1.0).
I see, thanks for the clarification boss, makes sense.

Best Regards,
Yu

On 13 April 2018 at 06:02, Stack  wrote:

> On Thu, Apr 12, 2018 at 1:47 PM, Stack  wrote:
>
> > On Tue, Apr 10, 2018 at 2:50 PM, Sean Busbey  wrote:
> >
> >> no compat report in the RC directory. does that mean we won't have one
> >> in the dist area?
> >>
> >>
> >> not a blocker; we've been inconsistent on it in prior releases, but
> >> the trend seemed to be towards including it.
> >>
> >>
> >
> > HBASE-18622 has current state of compatibility compare. Let me do a new
> > run and add it to the RC dir.
> >
>
> I just added
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> compat-check-v1.2.6-v2.0.0.report.html
>
> Thanks,
> S
>
>
>
> > St.Ack
> >
> >
> >
> >>
> >> On Tue, Apr 10, 2018 at 3:47 PM, Stack  wrote:
> >> > The first release candidate for Apache HBase 2.0.0 is available for
> >> > downloading and testing.
> >> >
> >> > Artifacts are available here:
> >> >
> >> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> >> >
> >> > Maven artifacts are available in the staging repository at:
> >> >
> >> >  https://repository.apache.org/content/repositories/
> orgapachehbase-1209
> >> >
> >> > All artifacts are signed with my signing key 8ACC93D2, which is also
> >> > in the project KEYS file at
> >> >
> >> >  http://www.apache.org/dist/hbase/KEYS
> >> >
> >> > These artifacts were tagged 2.0.0RC0 at
> >> > hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
> >> >
> >> > Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
> >> > Reference Guide before installing or upgrading for a list of
> >> > incompatibilities, major changes, and notable new features. Be aware
> >> that
> >> > according to our adopted Semantic Versioning guidelines[1], we've
> allow
> >> > ourselves to make breaking changes in this major version release. For
> >> > example, Coprocessors will need to be recast to fit more constrained
> CP
> >> > APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x
> without
> >> > downtime is (currently) not possible. That said, a bunch of effort has
> >> been
> >> > expended mitigating differences; a hbase-1.x client can perform DML
> >> against
> >> > an hbase-2 cluster.
> >> >
> >> > For the full list of ~6k issues addressed, see [2]. There are also
> >> > CHANGES.md and RELEASENOTES.md in the root directory of the source
> >> tarball.
> >> >
> >> > Please take a few minutes to verify the release and vote on releasing
> >> it:
> >> >
> >> > [ ] +1 Release this package as Apache HBase 2.0.0
> >> > [ ] +0 no opinion
> >> > [ ] -1 Do not release this package because...
> >> >
> >> > This VOTE will run for one week and close Tuesday, April 17, 2018 @
> >> 13:00
> >> > PST.
> >> >
> >> > Thanks to the myriad who have helped out with this release,
> >> > Your 2.0.0 Release Manager
> >> >
> >> > 1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
> >> > 2.  https://s.apache.org/zwS9
> >>
> >
> >
>

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Stack]

On Thu, Apr 12, 2018 at 1:47 PM, Stack  wrote:

> On Tue, Apr 10, 2018 at 2:50 PM, Sean Busbey  wrote:
>
>> no compat report in the RC directory. does that mean we won't have one
>> in the dist area?
>>
>>
>> not a blocker; we've been inconsistent on it in prior releases, but
>> the trend seemed to be towards including it.
>>
>>
>
> HBASE-18622 has current state of compatibility compare. Let me do a new
> run and add it to the RC dir.
>

I just added
https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/compat-check-v1.2.6-v2.0.0.report.html

Thanks,
S



> St.Ack
>
>
>
>>
>> On Tue, Apr 10, 2018 at 3:47 PM, Stack  wrote:
>> > The first release candidate for Apache HBase 2.0.0 is available for
>> > downloading and testing.
>> >
>> > Artifacts are available here:
>> >
>> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
>> >
>> > Maven artifacts are available in the staging repository at:
>> >
>> >  https://repository.apache.org/content/repositories/orgapachehbase-1209
>> >
>> > All artifacts are signed with my signing key 8ACC93D2, which is also
>> > in the project KEYS file at
>> >
>> >  http://www.apache.org/dist/hbase/KEYS
>> >
>> > These artifacts were tagged 2.0.0RC0 at
>> > hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
>> >
>> > Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
>> > Reference Guide before installing or upgrading for a list of
>> > incompatibilities, major changes, and notable new features. Be aware
>> that
>> > according to our adopted Semantic Versioning guidelines[1], we've allow
>> > ourselves to make breaking changes in this major version release. For
>> > example, Coprocessors will need to be recast to fit more constrained CP
>> > APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x without
>> > downtime is (currently) not possible. That said, a bunch of effort has
>> been
>> > expended mitigating differences; a hbase-1.x client can perform DML
>> against
>> > an hbase-2 cluster.
>> >
>> > For the full list of ~6k issues addressed, see [2]. There are also
>> > CHANGES.md and RELEASENOTES.md in the root directory of the source
>> tarball.
>> >
>> > Please take a few minutes to verify the release and vote on releasing
>> it:
>> >
>> > [ ] +1 Release this package as Apache HBase 2.0.0
>> > [ ] +0 no opinion
>> > [ ] -1 Do not release this package because...
>> >
>> > This VOTE will run for one week and close Tuesday, April 17, 2018 @
>> 13:00
>> > PST.
>> >
>> > Thanks to the myriad who have helped out with this release,
>> > Your 2.0.0 Release Manager
>> >
>> > 1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
>> > 2.  https://s.apache.org/zwS9
>>
>
>

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Stack]

On Tue, Apr 10, 2018 at 8:58 PM, Yu Li  wrote:

> HBASE-20188 is comparing latest 2.0 to our stable pointer 1.2.7, and there
> seems to be no conclusion yet, JFYI. While yes I believe more numbers could
> give us a broader view :-)
>
>
Yeah, what Yu Li says above. As is, hbase2 is much better than hbase1 under
mixed loading but does worse when pure read or write workloads.



> And I'm not sure but is performance regression some kind of a blocker for
> the release? Thanks.
>
>
I'd imagine that if the difference were large, then yes, it should be a
blocker -- or we as a community can decide to work on it in a follow-on
release making perf a priority (say, 2.1.0).

Thanks,
S




> Best Regards,
> Yu
>
> On 11 April 2018 at 08:39, 张铎(Duo Zhang)  wrote:
>
> > Do we have a ITBLL result and also some performance numbers? I could help
> > getting some performance numbers comparing to the version we use...
> >
> > 2018-04-11 5:50 GMT+08:00 Sean Busbey :
> >
> > > no compat report in the RC directory. does that mean we won't have one
> > > in the dist area?
> > >
> > >
> > > not a blocker; we've been inconsistent on it in prior releases, but
> > > the trend seemed to be towards including it.
> > >
> > >
> > > On Tue, Apr 10, 2018 at 3:47 PM, Stack  wrote:
> > > > The first release candidate for Apache HBase 2.0.0 is available for
> > > > downloading and testing.
> > > >
> > > > Artifacts are available here:
> > > >
> > > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> > > >
> > > > Maven artifacts are available in the staging repository at:
> > > >
> > > >  https://repository.apache.org/content/repositories/
> > orgapachehbase-1209
> > > >
> > > > All artifacts are signed with my signing key 8ACC93D2, which is also
> > > > in the project KEYS file at
> > > >
> > > >  http://www.apache.org/dist/hbase/KEYS
> > > >
> > > > These artifacts were tagged 2.0.0RC0 at
> > > > hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
> > > >
> > > > Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
> > > > Reference Guide before installing or upgrading for a list of
> > > > incompatibilities, major changes, and notable new features. Be aware
> > that
> > > > according to our adopted Semantic Versioning guidelines[1], we've
> allow
> > > > ourselves to make breaking changes in this major version release. For
> > > > example, Coprocessors will need to be recast to fit more constrained
> CP
> > > > APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x
> without
> > > > downtime is (currently) not possible. That said, a bunch of effort
> has
> > > been
> > > > expended mitigating differences; a hbase-1.x client can perform DML
> > > against
> > > > an hbase-2 cluster.
> > > >
> > > > For the full list of ~6k issues addressed, see [2]. There are also
> > > > CHANGES.md and RELEASENOTES.md in the root directory of the source
> > > tarball.
> > > >
> > > > Please take a few minutes to verify the release and vote on releasing
> > it:
> > > >
> > > > [ ] +1 Release this package as Apache HBase 2.0.0
> > > > [ ] +0 no opinion
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > This VOTE will run for one week and close Tuesday, April 17, 2018 @
> > 13:00
> > > > PST.
> > > >
> > > > Thanks to the myriad who have helped out with this release,
> > > > Your 2.0.0 Release Manager
> > > >
> > > > 1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
> > > > 2.  https://s.apache.org/zwS9
> > >
> >
>

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Stack]

On Tue, Apr 10, 2018 at 2:50 PM, Sean Busbey  wrote:

> no compat report in the RC directory. does that mean we won't have one
> in the dist area?
>
>
> not a blocker; we've been inconsistent on it in prior releases, but
> the trend seemed to be towards including it.
>
>

HBASE-18622 has current state of compatibility compare. Let me do a new run
and add it to the RC dir.
St.Ack



>
> On Tue, Apr 10, 2018 at 3:47 PM, Stack  wrote:
> > The first release candidate for Apache HBase 2.0.0 is available for
> > downloading and testing.
> >
> > Artifacts are available here:
> >
> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> >
> > Maven artifacts are available in the staging repository at:
> >
> >  https://repository.apache.org/content/repositories/orgapachehbase-1209
> >
> > All artifacts are signed with my signing key 8ACC93D2, which is also
> > in the project KEYS file at
> >
> >  http://www.apache.org/dist/hbase/KEYS
> >
> > These artifacts were tagged 2.0.0RC0 at
> > hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
> >
> > Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
> > Reference Guide before installing or upgrading for a list of
> > incompatibilities, major changes, and notable new features. Be aware that
> > according to our adopted Semantic Versioning guidelines[1], we've allow
> > ourselves to make breaking changes in this major version release. For
> > example, Coprocessors will need to be recast to fit more constrained CP
> > APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x without
> > downtime is (currently) not possible. That said, a bunch of effort has
> been
> > expended mitigating differences; a hbase-1.x client can perform DML
> against
> > an hbase-2 cluster.
> >
> > For the full list of ~6k issues addressed, see [2]. There are also
> > CHANGES.md and RELEASENOTES.md in the root directory of the source
> tarball.
> >
> > Please take a few minutes to verify the release and vote on releasing it:
> >
> > [ ] +1 Release this package as Apache HBase 2.0.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
> > This VOTE will run for one week and close Tuesday, April 17, 2018 @ 13:00
> > PST.
> >
> > Thanks to the myriad who have helped out with this release,
> > Your 2.0.0 Release Manager
> >
> > 1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
> > 2.  https://s.apache.org/zwS9
>

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Yu Li]

HBASE-20188 is comparing latest 2.0 to our stable pointer 1.2.7, and there
seems to be no conclusion yet, JFYI. While yes I believe more numbers could
give us a broader view :-)

And I'm not sure but is performance regression some kind of a blocker for
the release? Thanks.

Best Regards,
Yu

On 11 April 2018 at 08:39, 张铎(Duo Zhang)  wrote:

> Do we have a ITBLL result and also some performance numbers? I could help
> getting some performance numbers comparing to the version we use...
>
> 2018-04-11 5:50 GMT+08:00 Sean Busbey :
>
> > no compat report in the RC directory. does that mean we won't have one
> > in the dist area?
> >
> >
> > not a blocker; we've been inconsistent on it in prior releases, but
> > the trend seemed to be towards including it.
> >
> >
> > On Tue, Apr 10, 2018 at 3:47 PM, Stack  wrote:
> > > The first release candidate for Apache HBase 2.0.0 is available for
> > > downloading and testing.
> > >
> > > Artifacts are available here:
> > >
> > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> > >
> > > Maven artifacts are available in the staging repository at:
> > >
> > >  https://repository.apache.org/content/repositories/
> orgapachehbase-1209
> > >
> > > All artifacts are signed with my signing key 8ACC93D2, which is also
> > > in the project KEYS file at
> > >
> > >  http://www.apache.org/dist/hbase/KEYS
> > >
> > > These artifacts were tagged 2.0.0RC0 at
> > > hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
> > >
> > > Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
> > > Reference Guide before installing or upgrading for a list of
> > > incompatibilities, major changes, and notable new features. Be aware
> that
> > > according to our adopted Semantic Versioning guidelines[1], we've allow
> > > ourselves to make breaking changes in this major version release. For
> > > example, Coprocessors will need to be recast to fit more constrained CP
> > > APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x without
> > > downtime is (currently) not possible. That said, a bunch of effort has
> > been
> > > expended mitigating differences; a hbase-1.x client can perform DML
> > against
> > > an hbase-2 cluster.
> > >
> > > For the full list of ~6k issues addressed, see [2]. There are also
> > > CHANGES.md and RELEASENOTES.md in the root directory of the source
> > tarball.
> > >
> > > Please take a few minutes to verify the release and vote on releasing
> it:
> > >
> > > [ ] +1 Release this package as Apache HBase 2.0.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > This VOTE will run for one week and close Tuesday, April 17, 2018 @
> 13:00
> > > PST.
> > >
> > > Thanks to the myriad who have helped out with this release,
> > > Your 2.0.0 Release Manager
> > >
> > > 1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
> > > 2.  https://s.apache.org/zwS9
> >
>

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Duo Zhang]

Do we have a ITBLL result and also some performance numbers? I could help
getting some performance numbers comparing to the version we use...

2018-04-11 5:50 GMT+08:00 Sean Busbey :

> no compat report in the RC directory. does that mean we won't have one
> in the dist area?
>
>
> not a blocker; we've been inconsistent on it in prior releases, but
> the trend seemed to be towards including it.
>
>
> On Tue, Apr 10, 2018 at 3:47 PM, Stack  wrote:
> > The first release candidate for Apache HBase 2.0.0 is available for
> > downloading and testing.
> >
> > Artifacts are available here:
> >
> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> >
> > Maven artifacts are available in the staging repository at:
> >
> >  https://repository.apache.org/content/repositories/orgapachehbase-1209
> >
> > All artifacts are signed with my signing key 8ACC93D2, which is also
> > in the project KEYS file at
> >
> >  http://www.apache.org/dist/hbase/KEYS
> >
> > These artifacts were tagged 2.0.0RC0 at
> > hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
> >
> > Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
> > Reference Guide before installing or upgrading for a list of
> > incompatibilities, major changes, and notable new features. Be aware that
> > according to our adopted Semantic Versioning guidelines[1], we've allow
> > ourselves to make breaking changes in this major version release. For
> > example, Coprocessors will need to be recast to fit more constrained CP
> > APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x without
> > downtime is (currently) not possible. That said, a bunch of effort has
> been
> > expended mitigating differences; a hbase-1.x client can perform DML
> against
> > an hbase-2 cluster.
> >
> > For the full list of ~6k issues addressed, see [2]. There are also
> > CHANGES.md and RELEASENOTES.md in the root directory of the source
> tarball.
> >
> > Please take a few minutes to verify the release and vote on releasing it:
> >
> > [ ] +1 Release this package as Apache HBase 2.0.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
> > This VOTE will run for one week and close Tuesday, April 17, 2018 @ 13:00
> > PST.
> >
> > Thanks to the myriad who have helped out with this release,
> > Your 2.0.0 Release Manager
> >
> > 1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
> > 2.  https://s.apache.org/zwS9
>

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Sean Busbey]

no compat report in the RC directory. does that mean we won't have one
in the dist area?


not a blocker; we've been inconsistent on it in prior releases, but
the trend seemed to be towards including it.


On Tue, Apr 10, 2018 at 3:47 PM, Stack  wrote:
> The first release candidate for Apache HBase 2.0.0 is available for
> downloading and testing.
>
> Artifacts are available here:
>
>  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
>
> Maven artifacts are available in the staging repository at:
>
>  https://repository.apache.org/content/repositories/orgapachehbase-1209
>
> All artifacts are signed with my signing key 8ACC93D2, which is also
> in the project KEYS file at
>
>  http://www.apache.org/dist/hbase/KEYS
>
> These artifacts were tagged 2.0.0RC0 at
> hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
>
> Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
> Reference Guide before installing or upgrading for a list of
> incompatibilities, major changes, and notable new features. Be aware that
> according to our adopted Semantic Versioning guidelines[1], we've allow
> ourselves to make breaking changes in this major version release. For
> example, Coprocessors will need to be recast to fit more constrained CP
> APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x without
> downtime is (currently) not possible. That said, a bunch of effort has been
> expended mitigating differences; a hbase-1.x client can perform DML against
> an hbase-2 cluster.
>
> For the full list of ~6k issues addressed, see [2]. There are also
> CHANGES.md and RELEASENOTES.md in the root directory of the source tarball.
>
> Please take a few minutes to verify the release and vote on releasing it:
>
> [ ] +1 Release this package as Apache HBase 2.0.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> This VOTE will run for one week and close Tuesday, April 17, 2018 @ 13:00
> PST.
>
> Thanks to the myriad who have helped out with this release,
> Your 2.0.0 Release Manager
>
> 1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
> 2.  https://s.apache.org/zwS9

[VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Stack]

The first release candidate for Apache HBase 2.0.0 is available for
downloading and testing.

Artifacts are available here:

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

Maven artifacts are available in the staging repository at:

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

All artifacts are signed with my signing key 8ACC93D2, which is also
in the project KEYS file at

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

These artifacts were tagged 2.0.0RC0 at
hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46

Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
Reference Guide before installing or upgrading for a list of
incompatibilities, major changes, and notable new features. Be aware that
according to our adopted Semantic Versioning guidelines[1], we've allow
ourselves to make breaking changes in this major version release. For
example, Coprocessors will need to be recast to fit more constrained CP
APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x without
downtime is (currently) not possible. That said, a bunch of effort has been
expended mitigating differences; a hbase-1.x client can perform DML against
an hbase-2 cluster.

For the full list of ~6k issues addressed, see [2]. There are also
CHANGES.md and RELEASENOTES.md in the root directory of the source tarball.

Please take a few minutes to verify the release and vote on releasing it:

[ ] +1 Release this package as Apache HBase 2.0.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...

This VOTE will run for one week and close Tuesday, April 17, 2018 @ 13:00
PST.

Thanks to the myriad who have helped out with this release,
Your 2.0.0 Release Manager

1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
2.  https://s.apache.org/zwS9