Re: [VOTE] The second release candidate for HBase 2.0.4 is available

[Stack <st...@duboce.net>]

On Sun, Dec 30, 2018 at 5:46 PM 张铎(Duo Zhang) <pa...@gmail.com> wrote:

> +1(binding)
>
> Built from src: OK
> Checked sums & sigs: All matched
> Run all UTs(jdk8u151): Basically fine. TestExportSnapshot related UTs
> always timeout under the runAllTests profile, but can pass if I remove the
> profile and run them sequentially in the hbase-mapreduce module, maybe we
> need to split them?
>

Filed HBASE-21666 to break up the tests. Thanks for trying 2.0.4RC1 Duo.
S




> Started a 5 nodes cluster: OK, the master UI is fine
> Run basic shell cmds: OK, create, disable, drop, and also snapshot and
> clone_snapshot
> Run LTT with 1M rows: Read & Write, both OK, and then execute the count
> command in shell, also 1M rows returned.
>
> Stack <st...@duboce.net> 于2018年12月30日周日 上午12:45写道：
>
> > The second release candidate for HBase 2.0.4 is available for download:
> >
> >  *https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.4RC1/
> > <https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.4RC1/>*
> >
> > Maven artifacts are also available in a staging repository at:
> >
> >  https://repository.apache.org/content/repositories/orgapachehbase-1246
> >
> > Artifacts are signed with my key (DB9D313DA7874F29) published in our
> > KEYS file at http://www.apache.org/dist/hbase/KEYS
> >
> > The RC corresponds to the signed tag 2.0.4RC1, which currently points
> > to commit
> >
> >   205e39c5704bf38568b34926dde9f1ee76e6b5d0
> >
> > HBase 2.0.4 is the fourth maintenance release in the HBase 2.0 line,
> > continuing on the theme of bringing a stable, reliable database to
> > the Hadoop and NoSQL communities. It fixes a critical issue found
> > in the recent 2.0.3 and 2.1.1 releases (only), HBASE-21551. 2.0.4
> > includes ~31 bug and improvement fixes done since the 2.0.3,
> > ~ a month ago.
> >
> > The detailed source and binary compatibility report vs 2.0.3 has been
> > published for your review, at:
> >
> >
> >
> >
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.4RC1/compatibility_report_2.0.3vs2.0.4.html
> >
> > The report shows no incompatibilities.
> >
> > The full list of fixes included in this release is available in
> > the CHANGES.md that ships as part of the release also available
> > here:
> >
> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.4RC1/CHANGES.md
> >
> > The RELEASENOTES.md are here:
> >
> >
> >
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.4RC1/RELEASENOTES.md
> >
> > Please try out this candidate and vote +1/-1 on whether we should
> > release these artifacts as HBase 2.0.4.
> >
> > The VOTE will remain open for at least 72 hours. It'll probably take
> longer
> > given
> > its the holidays. I'll close the vote when sufficient votes after
> Tuesday,
> > January
> > 1st, 2019.
> >
> > Thanks,
> > S
> >
>

Re: [VOTE] The second release candidate for HBase 2.0.4 is available

[Allan Yang <al...@apache.org>]

+1 (binding)

-- Build from src - OK

-- SHA and Signatures(both src and bin) - OK

-- start in distributed mode - OK

-- Basic shell commands[create/drop/alter/get/put/scan] - OK

-- Check Web UI - OK

-- ITBLL 1B row for 1 run - OK


Best Regards
Allan Yang


Stack <st...@duboce.net> 于2019年1月3日周四 上午1:19写道：

> On Sun, Dec 30, 2018 at 5:46 PM 张铎(Duo Zhang) <pa...@gmail.com>
> wrote:
>
> > +1(binding)
> >
> > Built from src: OK
> > Checked sums & sigs: All matched
> > Run all UTs(jdk8u151): Basically fine. TestExportSnapshot related UTs
> > always timeout under the runAllTests profile, but can pass if I remove
> the
> > profile and run them sequentially in the hbase-mapreduce module, maybe we
> > need to split them?
> >
>
> Filed HBASE-21666 to break up the tests. Thanks for trying 2.0.4RC1 Duo.
> S
>
>
>
>
> > Started a 5 nodes cluster: OK, the master UI is fine
> > Run basic shell cmds: OK, create, disable, drop, and also snapshot and
> > clone_snapshot
> > Run LTT with 1M rows: Read & Write, both OK, and then execute the count
> > command in shell, also 1M rows returned.
> >
> > Stack <st...@duboce.net> 于2018年12月30日周日 上午12:45写道：
> >
> > > The second release candidate for HBase 2.0.4 is available for download:
> > >
> > >  *https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.4RC1/
> > > <https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.4RC1/>*
> > >
> > > Maven artifacts are also available in a staging repository at:
> > >
> > >
> https://repository.apache.org/content/repositories/orgapachehbase-1246
> > >
> > > Artifacts are signed with my key (DB9D313DA7874F29) published in our
> > > KEYS file at http://www.apache.org/dist/hbase/KEYS
> > >
> > > The RC corresponds to the signed tag 2.0.4RC1, which currently points
> > > to commit
> > >
> > >   205e39c5704bf38568b34926dde9f1ee76e6b5d0
> > >
> > > HBase 2.0.4 is the fourth maintenance release in the HBase 2.0 line,
> > > continuing on the theme of bringing a stable, reliable database to
> > > the Hadoop and NoSQL communities. It fixes a critical issue found
> > > in the recent 2.0.3 and 2.1.1 releases (only), HBASE-21551. 2.0.4
> > > includes ~31 bug and improvement fixes done since the 2.0.3,
> > > ~ a month ago.
> > >
> > > The detailed source and binary compatibility report vs 2.0.3 has been
> > > published for your review, at:
> > >
> > >
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.4RC1/compatibility_report_2.0.3vs2.0.4.html
> > >
> > > The report shows no incompatibilities.
> > >
> > > The full list of fixes included in this release is available in
> > > the CHANGES.md that ships as part of the release also available
> > > here:
> > >
> > >
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.4RC1/CHANGES.md
> > >
> > > The RELEASENOTES.md are here:
> > >
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.4RC1/RELEASENOTES.md
> > >
> > > Please try out this candidate and vote +1/-1 on whether we should
> > > release these artifacts as HBase 2.0.4.
> > >
> > > The VOTE will remain open for at least 72 hours. It'll probably take
> > longer
> > > given
> > > its the holidays. I'll close the vote when sufficient votes after
> > Tuesday,
> > > January
> > > 1st, 2019.
> > >
> > > Thanks,
> > > S
> > >
> >
>