Actually let me change my vote to +1. None of these results are serious enough to sink the RC, although if someone besides myself can reproduce the TestClusterScopeQuotaThrottle result, we should have a JIRA and the release announcement could point to the JIRA as indication that particular feature might need a bugfix.
On Tue, May 21, 2019 at 3:43 PM Andrew Purtell <[email protected]> wrote: > +0 at this time > > Signatures and sums: ok > RAT check: ok > Build from source: ok > Unit tests: some consistent failures > > This could be a problem with the test: > > [ERROR] > org.apache.hadoop.hbase.client.TestAsyncTableRSCrashPublish.test(org.apache.hadoop.hbase.client.TestAsyncTableRSCrashPublish) > [ERROR] Run 1: TestAsyncTableRSCrashPublish.test:77 Waiting timed out > after [60,000] msec > [ERROR] Run 2: TestAsyncTableRSCrashPublish.test:77 Waiting timed out > after [60,000] msec > [ERROR] Run 3: TestAsyncTableRSCrashPublish.test:77 Waiting timed out > after [60,000] msec > [ERROR] Run 4: TestAsyncTableRSCrashPublish.test:77 Waiting timed out > after [60,000] msec > > This is an interesting assertion failure: > > [ERROR] TestClusterRestartFailover.test:89 serverNode should not be null > when restart whole cluster > > These failures suggest cluster scope quotas might have an implementation > issue, this one is of most concern to me: > > [ERROR] > org.apache.hadoop.hbase.quotas.TestClusterScopeQuotaThrottle.testNamespaceClusterScopeQuota(org.apache.hadoop.hbase.quotas.TestClusterScopeQuotaThrottle) > [ERROR] Run 1: > TestClusterScopeQuotaThrottle.testNamespaceClusterScopeQuota:128 > expected:<6> but was:<3> > [ERROR] Run 2: > TestClusterScopeQuotaThrottle.testNamespaceClusterScopeQuota:128 > expected:<6> but was:<3> > [ERROR] Run 3: > TestClusterScopeQuotaThrottle.testNamespaceClusterScopeQuota:128 > expected:<6> but was:<3> > [ERROR] > org.apache.hadoop.hbase.quotas.TestClusterScopeQuotaThrottle.testUserClusterScopeQuota(org.apache.hadoop.hbase.quotas.TestClusterScopeQuotaThrottle) > [ERROR] Run 1: > TestClusterScopeQuotaThrottle.testUserClusterScopeQuota:177 expected:<6> > but was:<0> > [ERROR] Run 2: > TestClusterScopeQuotaThrottle.testUserClusterScopeQuota:177 expected:<6> > but was:<10> > [ERROR] Run 3: > TestClusterScopeQuotaThrottle.testUserClusterScopeQuota:177 expected:<6> > but was:<10> > > > On Fri, May 17, 2019 at 11:12 PM Guanghao Zhang <[email protected]> > wrote: > >> Please vote on this release candidate (RC) for Apache HBase 2.2.0. >> This is the first release of the branch-2.2 line. >> >> The VOTE will remain open for at least 72 hours. >> [] +1 >> [] +0/-0 Because ... >> [] -1 Do not release this package because ... >> >> The tag to be voted on is 2.2.0RC4. The release files, including >> signatures, digests, etc. can be found at: >> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC4/ >> >> Maven artifacts are available in a staging repository at: >> https://repository.apache.org/content/repositories/orgapachehbase-1312 >> >> Signatures used for HBase RCs can be found in this file: >> https://dist.apache.org/repos/dist/release/hbase/KEYS >> >> The list of bug fixes going into 2.2.0 can be found in included >> CHANGES.md and RELEASENOTES.md available here: >> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC4/CHANGES.md >> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC4/RELEASENOTES.md >> >> A detailed source and binary compatibility report for this release is >> available at >> >> https://dist.apache.org/repos/dist/dev/hbase/2.2.0RC4/api_compare_2.2.0RC4_to_2.1.4.html >> >> To learn more about Apache HBase, please see http://hbase.apache.org/ >> >> Thanks, >> Guanghao Zhang >> > > > -- > Best regards, > Andrew > > Words like orphans lost among the crosstalk, meaning torn from truth's > decrepit hands > - A23, Crosstalk > -- Best regards, Andrew Words like orphans lost among the crosstalk, meaning torn from truth's decrepit hands - A23, Crosstalk
