On Fri, Apr 27, 2018 at 3:54 AM, 张铎(Duo Zhang) <palomino...@gmail.com> wrote:
> -0 > > See https://issues.apache.org/jira/browse/HBASE-20476 > > There is a race between reportRegionTransition and regionServerReport which > could lead to openSeqNum go backwards. But the sequence id at RS side is > correct so I'm not sure whether it is worth to sink a RC. > > > Thanks Duo. Skimmed the issue. Is the worst thing that will happen be an over-play of edits on recovery? Or do you see other implications? Thanks, M > > 2018-04-26 15:59 GMT+08:00 Peter Somogyi <psomo...@apache.org>: > > > +1 (non-binding) > > > > Checksum, signature: ok > > Rat check: ok > > Build from source (8_163): ok > > Start from bin in pseudo distributed mode w/ HDFS: ok > > LTT 1M rows: ok > > Simple shell commands: ok > > Test RSGroup: ok > > Web UI: ok > > REST server: ok > > > > NOTE: Using the new JDK (8_171) TestSaslFanOutOneBlockAsyncDFSOutput > > fails. > > It is due to new feature called 'Enhanced KeyStore Mechanisms'[1] > > introduced in this JDK release. The bug is actually not in HBase but > > Hadoop: see HDFS-13494. > > > > [1] > > http://www.oracle.com/technetwork/java/javase/8u171- > > relnotes-4308888.html#JDK-8189997 > > > > > > On Mon, Apr 23, 2018 at 7:10 AM, Stack <st...@duboce.net> wrote: > > > > > The third 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.0RC2/ > > > > > > Maven artifacts are available in the staging repository at: > > > > > > https://repository.apache.org/content/repositories/orgapachehbase-1213 > > > > > > 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.0RC2 at hash > > 7483b111e4da77adbfc8062b3b22cb > > > e7c2cb91c1 > > > > > > 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 Sunday, April 29, 2018 @ > 21: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.0RC2/ > > compatibiliity_report_1.2.6vs2.0.0RC2.html > > > > > >
