+1 (binding)

- Signature & Checksum: OK
- Rat check (8u102) : OK
- Built from source (8u102): OK
- Unit tests pass (8u102)(Except TestRSGroupsKillRS): OK
- LTT 2M rows (8u102):  OK
- WEB UI(master/RS/TableDetails): OK
- Basic shell commands (CRUD/flush/compact/split): OK

Sakthi <[email protected]> 于2019年10月24日周四 下午9:56写道:

> +1 (binding)
>
> Java Version - Corretto 1.8.0_222-b10
>
> Fully-Distributed Mode (3 Nodes)
>
> Hadoop Version - 2.8.5
>
>
>
>    -
>
>    Built bin tarball tarball from Source
>    -
>
>    Checksums & Signatures - OK
>    -
>
>    RAT check - OK
>    -
>
>    ITBLL (8M) rows (& MR Tasks using Resource Manager [Verified]) - OK
>    -
>
>    Shell [CRUD Operations] - OK
>    -
>
>    Web UI, Logs - OK
>    -
>
>    REST Server - OK
>    -
>
>       CRUD Operations, Web UI, Logs - OK
>       -
>
>    Thrift Server - OK
>    -
>
>       CRUD Operations, Web UI, Logs - OK
>       -
>
>    HDFS directory structure - OK
>    -
>
>    CHANGES, RELEASENOTES - *OK*
>
> Just to make sure, the incompatible change in "ClusterMetrics" is being
> allowed just because the @InterfaceStability annotation is not used in the
> interface because of which the default annotation defaults to "unstable"?
>
> On Thu, Oct 24, 2019 at 1:10 AM Guanghao Zhang <[email protected]> wrote:
>
> > +1 (binding)
> >
> > hbase-2.2.2-bin.tar.gz (openjdk 1.8.0_202)
> > - Verified sha512: ok
> > - Start HBase in standalone mode: ok
> > - Verified with shell, create/get/put/scan/delete/disable/drop: ok
> > - Checked master/regionserver/table/region Web UI: ok
> >
> > hbase-2.2.2-src.tar.gz (openjdk 1.8.0_202)
> > - Verified sha512: ok
> > - Build tarball: ok
> > - Start HBase in standalone mode: ok
> > - Verified with shell, create/get/put/scan/delete/disable/drop: ok
> > - Checked master/regionserver/table/region Web UI: ok
> >
> > hbase-2.2.2-client-bin.tar.gz
> > - Verified sha512: ok
> >
> > Sakthi <[email protected]> 于2019年10月24日周四 上午11:06写道:
> >
> > > Will be casting a Vote soon, Duo
> > >
> > > On Wed, Oct 23, 2019 at 7:54 PM Duo Zhang <[email protected]> wrote:
> > >
> > > > Reminder. We need more votes here.
> > > >
> > > > Thanks.
> > > >
> > > > Duo Zhang <[email protected]> 于2019年10月20日周日 下午8:09写道:
> > > >
> > > > > Note that TestRSGroupsKillRS is broken, but I think it is only a
> test
> > > > > issue, the ConnectionImplementation has been like this for a long
> > time
> > > > so I
> > > > > do not think it is enough to sink an RC.
> > > > >
> > > > > Filed HBASE-23193 for this. Thanks.
> > > > >
> > > > > Duo Zhang <[email protected]> 于2019年10月20日周日 下午2:16写道:
> > > > >
> > > > >> Please vote on this Apache hbase release candidate,
> > > > >> hbase-2.2.2RC0
> > > > >>
> > > > >> The VOTE will remain open for at least 72 hours.
> > > > >>
> > > > >> [ ] +1 Release this package as Apache hbase 2.2.2
> > > > >> [ ] -1 Do not release this package because ...
> > > > >>
> > > > >> The tag to be voted on is 2.2.2RC0:
> > > > >>
> > > > >> https://github.com/apache/hbase/tree/2.2.2RC0
> > > > >>
> > > > >> The release files, including signatures, digests, as well as
> > > CHANGES.md
> > > > >> and RELEASENOTES.md included in this RC can be found at:
> > > > >>
> > > > >>  https://dist.apache.org/repos/dist/dev/hbase/2.2.2RC0/
> > > > >>
> > > > >> Maven artifacts are available in a staging repository at:
> > > > >>
> > > > >>
> > > >
> > https://repository.apache.org/content/repositories/orgapachehbase-1370/
> > > > >>
> > > > >> Artifacts were signed with the 9AD2AE49 key which can be found in:
> > > > >>
> > > > >>  https://dist.apache.org/repos/dist/release/hbase/KEYS
> > > > >>
> > > > >> 2.2.2 includes ~71 bug and improvement fixes done since the 2.2.1.
> > We
> > > > >> upgrade jackson to 2.9.10 due to CVE-2019-16335 and
> CVE-2019-14540.
> > > > There
> > > > >> is also a very nice new feature hbtop, please see HBASE-11062 for
> > more
> > > > >> details.
> > > > >>
> > > > >>  To learn more about apache hbase, please see
> > > > >> http://hbase.apache.org/
> > > > >>
> > > > >> Thanks,
> > > > >> Your HBase Release Manager
> > > > >>
> > > > >
> > > >
> > >
> >
>

Reply via email to