+1 (non-binding)

Hadoop 2.7.5 pseudo-distributed
Binary Release MD5: OK
HBase 1.4.1 rolling upgrade to 1.4.2 - OK
hbase shell: put, scan, get, list, count, create snapshot, restore
snapshot, disable, drop, list_regions - OK
LTT 1M rows: OK
PE 1k rows: OK

JDK: 1.8.0.161
SRC MD5: OK
compile with empty M2: OK



On Mon, Feb 19, 2018 at 2:58 PM, Chia-Ping Tsai <chia7...@apache.org> wrote:

> +1 (binding)
>
> run 1000W rows (openjdk 8u151):
> 1.4.2 (server) + 1.4.2(client) - ok
> 1.4.2 (server) + 1.3.1(client) - ok
> 1.4.2 (server) + 1.2.6(client) - ok
>
> Unit test suite (openjdk 8u151):
> TestZKPermissionWatcher is flaky. It is traced by
> https://issues.apache.org/jira/browse/HBASE-19970
>
> On 2018/02/16 21:46:17, Andrew Purtell <apurt...@apache.org> wrote:
> > The first HBase 1.4.2 release candidate (RC0) is available for download
> at
> > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.2RC0/ and Maven
> > artifacts are available in the temporary repository
> > https://repository.apache.org/content/repositories/orgapachehbase-1195/
> .
> >
> > The git tag corresponding to the candidate is '1.4.2RC0' (9519ec2ead).
> >
> > A detailed source and binary compatibility report for this release is
> > available for your review at https://dist.apache.org/repos/
> > dist/dev/hbase/hbase-1.4.2RC0/compat-check-report.html .
> >
> > A list of the 19 issues resolved in this release can be found at
> > https://s.apache.org/aGcb .
> >
> > Please try out the candidate and vote +1/0/-1.
> >
> > This vote will be open for at least 72 hours. Unless objection I will try
> > to close it Friday February 23, 2018 if we have sufficient votes.
> >
> > Prior to making this announcement I made the following preflight checks:
> >
> >    - RAT check passes (7u80)
> >    - Unit test suite passes (8u131)
> >    - LTT load 1M rows with 100% verification and 20% updates (8u131)
> >    - PE sequentialWrite, sequentialRead, randomWrite, randomRead,
> >    scanRange100 (8u131)
> >    - ITBLL Loop 1 100M rows (8u131)
> >
> >
> > --
> > Best regards,
> > Andrew
> >
>

Reply via email to