-1 non-binding
download src & bin tar ball - OK
signatures & sums - OK
build from source (openjdk version "1.8.0_151") - OK
rat check -
OK
Unit tests -
NOT OK
Following unit tests fails with:
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.apache.hadoop.hbase.regionserver.TestHStore
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
2.327 s <<< FAILURE! - in org.apache.hadoop.hbase.regionserver.TestHStore
[ERROR] testFlushSizeSizing(org.apache.hadoop.hbase.regionserver.TestHStore)
Time elapsed: 1.548 s <<< FAILURE!
java.lang.AssertionError: expected: org.apache.hadoop.hbase.
regionserver.MemStoreSizing<dataSize=32 , heapSize=312 , offHeapSize=0> but
was: org.apache.hadoop.hbase.regionserver.MemStoreSize<dataSize=32 ,
heapSize=312 , offHeapSize=0>
at org.apache.hadoop.hbase.regionserver.TestHStore.testFlushSizeSizing(
TestHStore.java:251)
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] TestHStore.testFlushSizeSizing:251 expected:
org.apache.hadoop.hbase.regionserver.MemStoreSizing<dataSize=32 ,
heapSize=312 , offHeapSize=0> but was: org.apache.hadoop.hbase.
regionserver.MemStoreSize<dataSize=32 , heapSize=312 , offHeapSize=0>
[INFO]
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
>From surefire report:
2018-04-20 15:01:55,386 INFO [Time-limited test]
hbase.ResourceChecker(172): after: regionserver.TestHStore#testFlushSizeSizing
Thread=18 (was 8)
Potentially hanging thread: Time-limited test-MemStoreChunkPool Statistics
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.parkNanos(
LockSupport.java:215)
java.util.concurrent.locks.AbstractQueuedSynchronizer$
ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
java.util.concurrent.ScheduledThreadPoolExecutor$
DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
java.util.concurrent.ScheduledThreadPoolExecutor$
DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
java.util.concurrent.ThreadPoolExecutor.getTask(
ThreadPoolExecutor.java:1074)
java.util.concurrent.ThreadPoolExecutor.runWorker(
ThreadPoolExecutor.java:1134)
java.util.concurrent.ThreadPoolExecutor$Worker.run(
ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)
Potentially hanging thread: Monitor thread for TaskMonitor
java.lang.Thread.sleep(Native Method)
org.apache.hadoop.hbase.monitoring.TaskMonitor$MonitorRunnable.run(
TaskMonitor.java:302)
java.lang.Thread.run(Thread.java:748)
...
Potentially hanging thread: AsyncFSWAL-0
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
java.util.concurrent.locks.AbstractQueuedSynchronizer$
ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
java.util.concurrent.LinkedBlockingQueue.take(
LinkedBlockingQueue.java:442)
java.util.concurrent.ThreadPoolExecutor.getTask(
ThreadPoolExecutor.java:1074)
java.util.concurrent.ThreadPoolExecutor.runWorker(
ThreadPoolExecutor.java:1134)
java.util.concurrent.ThreadPoolExecutor$Worker.run(
ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)
- Thread LEAK? -, OpenFileDescriptor=237 (was 232) - OpenFileDescriptor
LEAK? -, MaxFileDescriptor=1048576 (was 1048576), SystemLoadAverage=185
(was 167) - SystemLoadAverage LEAK? -, ProcessCount=123 (was 123),
AvailableMemoryMB=3609 (was 3728)
On Fri, Apr 20, 2018 at 11:04 AM, Stack <st...@duboce.net> wrote:
> The second 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.0RC1/
>
> Maven artifacts are available in the staging repository at:
>
> https://repository.apache.org/content/repositories/orgapachehbase-1211
>
> 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.0RC1 at
> hash d8985e04bf6adfc3d00660c3e04e27a5f5bacb4b
>
> 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. A
> bundled compatibility report showing difference from 1.2.6 may be of help
> [3].
>
> 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 Friday, April 27, 2018 @ 11: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
> 3.
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC1/
> compatibiliity_report_1.2.6vs2.0.0RC1.html
>
