You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Duo Zhang <zh...@apache.org> on 2020/04/01 04:15:41 UTC
[VOTE] Second release candidate for HBase 2.1.10 is available for download
Please vote on this Apache hbase release candidate,
hbase-2.1.10RC1
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache hbase 2.1.10
[ ] -1 Do not release this package because ...
The tag to be voted on is 2.1.10RC1:
https://github.com/apache/hbase/tree/2.1.10RC1
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.1.10RC1/
Maven artifacts are available in a staging repository at:
https://repository.apache.org/content/repositories/orgapachehbase-1387/
Artifacts were signed with the 9AD2AE49 key which can be found in:
https://dist.apache.org/repos/dist/release/hbase/KEYS
2.1.10 includes ~23 bug and improvement fixes done since the 2.1.9.
To learn more about apache hbase, please see
http://hbase.apache.org/
Thanks,
Your HBase Release Manager
Re: [VOTE] Second release candidate for HBase 2.1.10 is available for download
Posted by Viraj Jasani <vj...@apache.org>.
+1 (non-binding)
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_172): ok
- mvn clean apache-rat:check
* Built from source (1.8.0_172): ok
- mvn clean install -DskipTests
* Unit tests pass (1.8.0_172): ok
- mvn package -P runAllTests
On 2020/04/01 19:06:48, Balazs Meszaros <ba...@cloudera.com.INVALID> wrote:
> +1
>
> - signatures, checksums: OK
> - rat check: OK
> - built from source (8u242): OK
> - unit tests (8u242): OK
> - ltt with 1M rows: OK
> - web UI: OK
> - shell and basic commands: OK
>
> Best regards,
> Balazs
>
> On Wed, Apr 1, 2020 at 6:15 AM Duo Zhang <zh...@apache.org> wrote:
>
> > Please vote on this Apache hbase release candidate,
> > hbase-2.1.10RC1
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache hbase 2.1.10
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 2.1.10RC1:
> >
> > https://github.com/apache/hbase/tree/2.1.10RC1
> >
> > 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.1.10RC1/
> >
> > Maven artifacts are available in a staging repository at:
> >
> > https://repository.apache.org/content/repositories/orgapachehbase-1387/
> >
> > Artifacts were signed with the 9AD2AE49 key which can be found in:
> >
> > https://dist.apache.org/repos/dist/release/hbase/KEYS
> >
> > 2.1.10 includes ~23 bug and improvement fixes done since the 2.1.9.
> >
> > To learn more about apache hbase, please see
> > http://hbase.apache.org/
> >
> > Thanks,
> > Your HBase Release Manager
> >
>
Re: [VOTE] Second release candidate for HBase 2.1.10 is available for download
Posted by Balazs Meszaros <ba...@cloudera.com.INVALID>.
+1
- signatures, checksums: OK
- rat check: OK
- built from source (8u242): OK
- unit tests (8u242): OK
- ltt with 1M rows: OK
- web UI: OK
- shell and basic commands: OK
Best regards,
Balazs
On Wed, Apr 1, 2020 at 6:15 AM Duo Zhang <zh...@apache.org> wrote:
> Please vote on this Apache hbase release candidate,
> hbase-2.1.10RC1
>
> The VOTE will remain open for at least 72 hours.
>
> [ ] +1 Release this package as Apache hbase 2.1.10
> [ ] -1 Do not release this package because ...
>
> The tag to be voted on is 2.1.10RC1:
>
> https://github.com/apache/hbase/tree/2.1.10RC1
>
> 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.1.10RC1/
>
> Maven artifacts are available in a staging repository at:
>
> https://repository.apache.org/content/repositories/orgapachehbase-1387/
>
> Artifacts were signed with the 9AD2AE49 key which can be found in:
>
> https://dist.apache.org/repos/dist/release/hbase/KEYS
>
> 2.1.10 includes ~23 bug and improvement fixes done since the 2.1.9.
>
> To learn more about apache hbase, please see
> http://hbase.apache.org/
>
> Thanks,
> Your HBase Release Manager
>
Re: [VOTE] Second release candidate for HBase 2.1.10 is available for download
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
The TestCanaryTool is a mess, the output is flooded with "Failed to renew
lease" but I could get a successful run, finally.
This is my jdk version
openjdk version "1.8.0_222"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_222-b10)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.222-b10, mixed mode)
Andrew Purtell <an...@gmail.com> 于2020年4月3日周五 上午11:40写道：
> Thanks. Since you can’t reproduce I’ll change my vote to -0.
>
> Weird you don’t see the TestCanaryTool failure. Perhaps that is because of
> differing JDK versions.
>
> > On Apr 2, 2020, at 8:27 PM, 张铎(Duo Zhang) <pa...@gmail.com> wrote:
> >
> > I can not reproduce these failure locally.
> >
> > And for testScanAfterDeletingSpecifiedRowV2, maybe the problem is the
> > timestamp. If your computer is fast enough, the later several puts may
> have
> > the same timestamp with the delete at the beginning, so the later put
> will
> > be masked by the previous delete, which lead to the failure. You could
> try
> > to set the same timestamp for all the delete and put, then you will get a
> > failure like this
> >
> > java.lang.AssertionError: expected:<3> but was:<0>
> > at org.junit.Assert.fail(Assert.java:88)
> > at org.junit.Assert.failNotEquals(Assert.java:834)
> > at org.junit.Assert.assertEquals(Assert.java:645)
> > at org.junit.Assert.assertEquals(Assert.java:631)
> > at
> >
> org.apache.hadoop.hbase.client.TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2(TestFromClientSide3.java:253)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:498)
> > at
> >
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> > at
> >
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> > at
> >
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> > at
> >
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> > at
> >
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> > at
> >
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> > at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> > at
> >
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> > at
> >
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> > at
> >
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> > at
> >
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> > at
> >
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> > at
> >
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> > at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> > at java.lang.Thread.run(Thread.java:748)
> >
> > So I do not think this is a blocker one, just a test issue.
> >
> > Thanks.
> >
> > Andrew Purtell <ap...@apache.org> 于2020年4月3日周五 上午9:53写道：
> >
> >> -1 (binding)
> >>
> >> * Signature: ok
> >> * Checksum : ok
> >> * Rat check (1.8.0_232): ok
> >> - mvn clean apache-rat:check
> >> * Built from source (1.8.0_232): ok
> >> - mvn clean install -DskipTests
> >> * Unit tests pass (1.8.0_232): failed
> >> - mvn package -P runAllTests
> >>
> >> TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue 100%
> >> failure
> >>
> >>
> >>
> org.apache.hadoop.hbase.regionserver.TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue
> >> Run 1:
> >>
> >>
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> >> expected:<true> but was:<false>
> >> Run 2:
> >>
> >>
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> >> expected:<true> but was:<false>
> >> Run 3:
> >>
> >>
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> >> expected:<true> but was:<false>
> >> Run 4:
> >>
> >>
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> >> expected:<true> but was:<false>
> >>
> >> TestCanaryTool is broken, lots of these:
> >>
> >> [ERROR] Run 2: TestCanaryTool.testReadTableTimeouts:218
> >> Argument(s) are different! Wanted:
> >> mockAppender.doAppend(
> >> <custom argument matcher>
> >> );
> >> -> at
> >>
> >>
> org.apache.hadoop.hbase.tool.TestCanaryTool.testReadTableTimeouts(TestCanaryTool.java:218)
> >> Actual invocations have different arguments:
> >> mockAppender.doAppend(
> >> org.apache.log4j.spi.LoggingEvent@5c21284d
> >> );
> >> Some flakes. The TestFromClientSide3 results are concerning because they
> >> could be a correctness issue:
> >>
> >> org.apache.hadoop.hbase.regionserver.TestRegionReplicas.null
> >> Run 1:
> >> TestRegionReplicas.testVerifySecondaryAbilityToReadWithOnFiles:476 »
> >> TestTimedOut
> >> Run 2: PASS
> >>
> >>
> >>
> org.apache.hadoop.hbase.client.TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2
> >> Run 1: TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> >> expected:<3> but was:<2>
> >> Run 2: TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> >> expected:<3> but was:<2>
> >> Run 3: PASS
> >>
> >> org.apache.hadoop.hbase.master.assignment.TestRegionMoveAndAbandon.test
> >> Run 1: TestRegionMoveAndAbandon.test:118 » Runtime
> >> org.apache.hadoop.hbase.client.Ret...
> >> Run 2: PASS
> >>
> >>
> >>
> org.apache.hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures.testDisableTableWithFailover
> >> Run 1: TestMasterFailoverWithProcedures.setup:76 » IO Shutting down
> >> Run 2: PASS
> >>
> >>
> >>
> org.apache.hadoop.hbase.replication.regionserver.TestReplicator.testReplicatorWithErrors
> >> Run 1: TestReplicator.testReplicatorWithErrors:158 We did not
> replicate
> >> enough rows expected:<10> but was:<6>
> >> Run 2: PASS
> >>
> >>
> >>
> org.apache.hadoop.hbase.util.TestFromClientSide3WoUnsafe.testScanAfterDeletingSpecifiedRowV2
> >> Run 1:
> >>
> >>
> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> >> expected:<3> but was:<2>
> >> Run 2:
> >>
> >>
> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> >> expected:<3> but was:<2>
> >> Run 3: PASS
> >>
> >>
> >>> On Tue, Mar 31, 2020 at 9:15 PM Duo Zhang <zh...@apache.org> wrote:
> >>>
> >>> Please vote on this Apache hbase release candidate,
> >>> hbase-2.1.10RC1
> >>>
> >>> The VOTE will remain open for at least 72 hours.
> >>>
> >>> [ ] +1 Release this package as Apache hbase 2.1.10
> >>> [ ] -1 Do not release this package because ...
> >>>
> >>> The tag to be voted on is 2.1.10RC1:
> >>>
> >>> https://github.com/apache/hbase/tree/2.1.10RC1
> >>>
> >>> 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.1.10RC1/
> >>>
> >>> Maven artifacts are available in a staging repository at:
> >>>
> >>>
> https://repository.apache.org/content/repositories/orgapachehbase-1387/
> >>>
> >>> Artifacts were signed with the 9AD2AE49 key which can be found in:
> >>>
> >>> https://dist.apache.org/repos/dist/release/hbase/KEYS
> >>>
> >>> 2.1.10 includes ~23 bug and improvement fixes done since the 2.1.9.
> >>>
> >>> To learn more about apache hbase, please see
> >>> http://hbase.apache.org/
> >>>
> >>> Thanks,
> >>> Your HBase Release Manager
> >>>
> >>
> >>
> >> --
> >> Best regards,
> >> Andrew
> >>
> >> Words like orphans lost among the crosstalk, meaning torn from truth's
> >> decrepit hands
> >> - A23, Crosstalk
> >>
>
Re: [VOTE] Second release candidate for HBase 2.1.10 is available for download
Posted by Andrew Purtell <an...@gmail.com>.
Thanks. Since you can’t reproduce I’ll change my vote to -0.
Weird you don’t see the TestCanaryTool failure. Perhaps that is because of differing JDK versions.
> On Apr 2, 2020, at 8:27 PM, 张铎(Duo Zhang) <pa...@gmail.com> wrote:
>
> I can not reproduce these failure locally.
>
> And for testScanAfterDeletingSpecifiedRowV2, maybe the problem is the
> timestamp. If your computer is fast enough, the later several puts may have
> the same timestamp with the delete at the beginning, so the later put will
> be masked by the previous delete, which lead to the failure. You could try
> to set the same timestamp for all the delete and put, then you will get a
> failure like this
>
> java.lang.AssertionError: expected:<3> but was:<0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.junit.Assert.assertEquals(Assert.java:631)
> at
> org.apache.hadoop.hbase.client.TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2(TestFromClientSide3.java:253)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.lang.Thread.run(Thread.java:748)
>
> So I do not think this is a blocker one, just a test issue.
>
> Thanks.
>
> Andrew Purtell <ap...@apache.org> 于2020年4月3日周五 上午9:53写道：
>
>> -1 (binding)
>>
>> * Signature: ok
>> * Checksum : ok
>> * Rat check (1.8.0_232): ok
>> - mvn clean apache-rat:check
>> * Built from source (1.8.0_232): ok
>> - mvn clean install -DskipTests
>> * Unit tests pass (1.8.0_232): failed
>> - mvn package -P runAllTests
>>
>> TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue 100%
>> failure
>>
>>
>> org.apache.hadoop.hbase.regionserver.TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue
>> Run 1:
>>
>> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
>> expected:<true> but was:<false>
>> Run 2:
>>
>> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
>> expected:<true> but was:<false>
>> Run 3:
>>
>> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
>> expected:<true> but was:<false>
>> Run 4:
>>
>> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
>> expected:<true> but was:<false>
>>
>> TestCanaryTool is broken, lots of these:
>>
>> [ERROR] Run 2: TestCanaryTool.testReadTableTimeouts:218
>> Argument(s) are different! Wanted:
>> mockAppender.doAppend(
>> <custom argument matcher>
>> );
>> -> at
>>
>> org.apache.hadoop.hbase.tool.TestCanaryTool.testReadTableTimeouts(TestCanaryTool.java:218)
>> Actual invocations have different arguments:
>> mockAppender.doAppend(
>> org.apache.log4j.spi.LoggingEvent@5c21284d
>> );
>> Some flakes. The TestFromClientSide3 results are concerning because they
>> could be a correctness issue:
>>
>> org.apache.hadoop.hbase.regionserver.TestRegionReplicas.null
>> Run 1:
>> TestRegionReplicas.testVerifySecondaryAbilityToReadWithOnFiles:476 »
>> TestTimedOut
>> Run 2: PASS
>>
>>
>> org.apache.hadoop.hbase.client.TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2
>> Run 1: TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
>> expected:<3> but was:<2>
>> Run 2: TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
>> expected:<3> but was:<2>
>> Run 3: PASS
>>
>> org.apache.hadoop.hbase.master.assignment.TestRegionMoveAndAbandon.test
>> Run 1: TestRegionMoveAndAbandon.test:118 » Runtime
>> org.apache.hadoop.hbase.client.Ret...
>> Run 2: PASS
>>
>>
>> org.apache.hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures.testDisableTableWithFailover
>> Run 1: TestMasterFailoverWithProcedures.setup:76 » IO Shutting down
>> Run 2: PASS
>>
>>
>> org.apache.hadoop.hbase.replication.regionserver.TestReplicator.testReplicatorWithErrors
>> Run 1: TestReplicator.testReplicatorWithErrors:158 We did not replicate
>> enough rows expected:<10> but was:<6>
>> Run 2: PASS
>>
>>
>> org.apache.hadoop.hbase.util.TestFromClientSide3WoUnsafe.testScanAfterDeletingSpecifiedRowV2
>> Run 1:
>>
>> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
>> expected:<3> but was:<2>
>> Run 2:
>>
>> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
>> expected:<3> but was:<2>
>> Run 3: PASS
>>
>>
>>> On Tue, Mar 31, 2020 at 9:15 PM Duo Zhang <zh...@apache.org> wrote:
>>>
>>> Please vote on this Apache hbase release candidate,
>>> hbase-2.1.10RC1
>>>
>>> The VOTE will remain open for at least 72 hours.
>>>
>>> [ ] +1 Release this package as Apache hbase 2.1.10
>>> [ ] -1 Do not release this package because ...
>>>
>>> The tag to be voted on is 2.1.10RC1:
>>>
>>> https://github.com/apache/hbase/tree/2.1.10RC1
>>>
>>> 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.1.10RC1/
>>>
>>> Maven artifacts are available in a staging repository at:
>>>
>>> https://repository.apache.org/content/repositories/orgapachehbase-1387/
>>>
>>> Artifacts were signed with the 9AD2AE49 key which can be found in:
>>>
>>> https://dist.apache.org/repos/dist/release/hbase/KEYS
>>>
>>> 2.1.10 includes ~23 bug and improvement fixes done since the 2.1.9.
>>>
>>> To learn more about apache hbase, please see
>>> http://hbase.apache.org/
>>>
>>> Thanks,
>>> Your HBase Release Manager
>>>
>>
>>
>> --
>> Best regards,
>> Andrew
>>
>> Words like orphans lost among the crosstalk, meaning torn from truth's
>> decrepit hands
>> - A23, Crosstalk
>>
Re: [VOTE] Second release candidate for HBase 2.1.10 is available for download
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
I can not reproduce these failure locally.
And for testScanAfterDeletingSpecifiedRowV2, maybe the problem is the
timestamp. If your computer is fast enough, the later several puts may have
the same timestamp with the delete at the beginning, so the later put will
be masked by the previous delete, which lead to the failure. You could try
to set the same timestamp for all the delete and put, then you will get a
failure like this
java.lang.AssertionError: expected:<3> but was:<0>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at
org.apache.hadoop.hbase.client.TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2(TestFromClientSide3.java:253)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
at
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.lang.Thread.run(Thread.java:748)
So I do not think this is a blocker one, just a test issue.
Thanks.
Andrew Purtell <ap...@apache.org> 于2020年4月3日周五 上午9:53写道：
> -1 (binding)
>
> * Signature: ok
> * Checksum : ok
> * Rat check (1.8.0_232): ok
> - mvn clean apache-rat:check
> * Built from source (1.8.0_232): ok
> - mvn clean install -DskipTests
> * Unit tests pass (1.8.0_232): failed
> - mvn package -P runAllTests
>
> TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue 100%
> failure
>
>
> org.apache.hadoop.hbase.regionserver.TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue
> Run 1:
>
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> expected:<true> but was:<false>
> Run 2:
>
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> expected:<true> but was:<false>
> Run 3:
>
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> expected:<true> but was:<false>
> Run 4:
>
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> expected:<true> but was:<false>
>
> TestCanaryTool is broken, lots of these:
>
> [ERROR] Run 2: TestCanaryTool.testReadTableTimeouts:218
> Argument(s) are different! Wanted:
> mockAppender.doAppend(
> <custom argument matcher>
> );
> -> at
>
> org.apache.hadoop.hbase.tool.TestCanaryTool.testReadTableTimeouts(TestCanaryTool.java:218)
> Actual invocations have different arguments:
> mockAppender.doAppend(
> org.apache.log4j.spi.LoggingEvent@5c21284d
> );
> Some flakes. The TestFromClientSide3 results are concerning because they
> could be a correctness issue:
>
> org.apache.hadoop.hbase.regionserver.TestRegionReplicas.null
> Run 1:
> TestRegionReplicas.testVerifySecondaryAbilityToReadWithOnFiles:476 »
> TestTimedOut
> Run 2: PASS
>
>
> org.apache.hadoop.hbase.client.TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2
> Run 1: TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> expected:<3> but was:<2>
> Run 2: TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> expected:<3> but was:<2>
> Run 3: PASS
>
> org.apache.hadoop.hbase.master.assignment.TestRegionMoveAndAbandon.test
> Run 1: TestRegionMoveAndAbandon.test:118 » Runtime
> org.apache.hadoop.hbase.client.Ret...
> Run 2: PASS
>
>
> org.apache.hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures.testDisableTableWithFailover
> Run 1: TestMasterFailoverWithProcedures.setup:76 » IO Shutting down
> Run 2: PASS
>
>
> org.apache.hadoop.hbase.replication.regionserver.TestReplicator.testReplicatorWithErrors
> Run 1: TestReplicator.testReplicatorWithErrors:158 We did not replicate
> enough rows expected:<10> but was:<6>
> Run 2: PASS
>
>
> org.apache.hadoop.hbase.util.TestFromClientSide3WoUnsafe.testScanAfterDeletingSpecifiedRowV2
> Run 1:
>
> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> expected:<3> but was:<2>
> Run 2:
>
> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> expected:<3> but was:<2>
> Run 3: PASS
>
>
> On Tue, Mar 31, 2020 at 9:15 PM Duo Zhang <zh...@apache.org> wrote:
>
> > Please vote on this Apache hbase release candidate,
> > hbase-2.1.10RC1
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache hbase 2.1.10
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 2.1.10RC1:
> >
> > https://github.com/apache/hbase/tree/2.1.10RC1
> >
> > 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.1.10RC1/
> >
> > Maven artifacts are available in a staging repository at:
> >
> > https://repository.apache.org/content/repositories/orgapachehbase-1387/
> >
> > Artifacts were signed with the 9AD2AE49 key which can be found in:
> >
> > https://dist.apache.org/repos/dist/release/hbase/KEYS
> >
> > 2.1.10 includes ~23 bug and improvement fixes done since the 2.1.9.
> >
> > To learn more about apache hbase, please see
> > http://hbase.apache.org/
> >
> > Thanks,
> > Your HBase Release Manager
> >
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
> - A23, Crosstalk
>
Re: [VOTE] Second release candidate for HBase 2.1.10 is available for download
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
Looking at the flaky list here:
https://builds.apache.org/job/HBASE-Find-Flaky-Tests/job/branch-2.1/lastSuccessfulBuild/artifact/dashboard.html
The TestQuotasShell was a problem and has been fixed already.
I could get a successful UT run locally.
With -PrunAllTests several tests in hbase-server module failed but when
running all UTs under hbase-server sequentially I can get a successful
result.
Let me try the these UTs.
Yu Li <ca...@gmail.com> 于2020年4月3日周五 上午10:24写道：
> -1 (binding)
>
> Checked sums and signatures: ok
> Built from source: ok (8u101)
> RAT check: ok (8u101)
> Unit tests: failed (8u101)
> - TestHFileCleaner.testHFileCleaning failed stably and could be reproduced
> by single run
> - 6 Errors caused by test timed out of this invocation
> path:
> TestExportSnapshot.testExportWithTargetName:190->testExportFileSystemState:195->testExportFileSystemState:202->testExportFileSystemState:230
> - Command to run the UT:
>
>
>
>
>
>
>
>
> * mvn -B -PrunAllTests\ -DreuseForks=false\
> -Dmaven.test.redirectTestOutputToFile=true\
> -Dsurefire.rerunFailingTestsCount=2\ -Dit.test=noItTest\
> -Dmaven.test.failure.ignore=true\ -Dsurefire.testFailureIgnore=true\
> -Dmaven.test.error.ignore=true\ test*
>
> Best Regards,
> Yu
>
>
> On Fri, 3 Apr 2020 at 09:53, Andrew Purtell <ap...@apache.org> wrote:
>
> > -1 (binding)
> >
> > * Signature: ok
> > * Checksum : ok
> > * Rat check (1.8.0_232): ok
> > - mvn clean apache-rat:check
> > * Built from source (1.8.0_232): ok
> > - mvn clean install -DskipTests
> > * Unit tests pass (1.8.0_232): failed
> > - mvn package -P runAllTests
> >
> > TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue 100%
> > failure
> >
> >
> >
> org.apache.hadoop.hbase.regionserver.TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue
> > Run 1:
> >
> >
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> > expected:<true> but was:<false>
> > Run 2:
> >
> >
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> > expected:<true> but was:<false>
> > Run 3:
> >
> >
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> > expected:<true> but was:<false>
> > Run 4:
> >
> >
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> > expected:<true> but was:<false>
> >
> > TestCanaryTool is broken, lots of these:
> >
> > [ERROR] Run 2: TestCanaryTool.testReadTableTimeouts:218
> > Argument(s) are different! Wanted:
> > mockAppender.doAppend(
> > <custom argument matcher>
> > );
> > -> at
> >
> >
> org.apache.hadoop.hbase.tool.TestCanaryTool.testReadTableTimeouts(TestCanaryTool.java:218)
> > Actual invocations have different arguments:
> > mockAppender.doAppend(
> > org.apache.log4j.spi.LoggingEvent@5c21284d
> > );
> > Some flakes. The TestFromClientSide3 results are concerning because they
> > could be a correctness issue:
> >
> > org.apache.hadoop.hbase.regionserver.TestRegionReplicas.null
> > Run 1:
> > TestRegionReplicas.testVerifySecondaryAbilityToReadWithOnFiles:476 »
> > TestTimedOut
> > Run 2: PASS
> >
> >
> >
> org.apache.hadoop.hbase.client.TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2
> > Run 1: TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> > expected:<3> but was:<2>
> > Run 2: TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> > expected:<3> but was:<2>
> > Run 3: PASS
> >
> > org.apache.hadoop.hbase.master.assignment.TestRegionMoveAndAbandon.test
> > Run 1: TestRegionMoveAndAbandon.test:118 » Runtime
> > org.apache.hadoop.hbase.client.Ret...
> > Run 2: PASS
> >
> >
> >
> org.apache.hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures.testDisableTableWithFailover
> > Run 1: TestMasterFailoverWithProcedures.setup:76 » IO Shutting down
> > Run 2: PASS
> >
> >
> >
> org.apache.hadoop.hbase.replication.regionserver.TestReplicator.testReplicatorWithErrors
> > Run 1: TestReplicator.testReplicatorWithErrors:158 We did not
> replicate
> > enough rows expected:<10> but was:<6>
> > Run 2: PASS
> >
> >
> >
> org.apache.hadoop.hbase.util.TestFromClientSide3WoUnsafe.testScanAfterDeletingSpecifiedRowV2
> > Run 1:
> >
> >
> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> > expected:<3> but was:<2>
> > Run 2:
> >
> >
> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> > expected:<3> but was:<2>
> > Run 3: PASS
> >
> >
> > On Tue, Mar 31, 2020 at 9:15 PM Duo Zhang <zh...@apache.org> wrote:
> >
> > > Please vote on this Apache hbase release candidate,
> > > hbase-2.1.10RC1
> > >
> > > The VOTE will remain open for at least 72 hours.
> > >
> > > [ ] +1 Release this package as Apache hbase 2.1.10
> > > [ ] -1 Do not release this package because ...
> > >
> > > The tag to be voted on is 2.1.10RC1:
> > >
> > > https://github.com/apache/hbase/tree/2.1.10RC1
> > >
> > > 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.1.10RC1/
> > >
> > > Maven artifacts are available in a staging repository at:
> > >
> > >
> https://repository.apache.org/content/repositories/orgapachehbase-1387/
> > >
> > > Artifacts were signed with the 9AD2AE49 key which can be found in:
> > >
> > > https://dist.apache.org/repos/dist/release/hbase/KEYS
> > >
> > > 2.1.10 includes ~23 bug and improvement fixes done since the 2.1.9.
> > >
> > > To learn more about apache hbase, please see
> > > http://hbase.apache.org/
> > >
> > > Thanks,
> > > Your HBase Release Manager
> > >
> >
> >
> > --
> > Best regards,
> > Andrew
> >
> > Words like orphans lost among the crosstalk, meaning torn from truth's
> > decrepit hands
> > - A23, Crosstalk
> >
>
Re: [VOTE] Second release candidate for HBase 2.1.10 is available for download
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
With 3 binding +1s, 1 -0, and 1 non-binding +1s, the vote passed.
Let me push out 2.1.10.
Thanks all for voting!
张铎(Duo Zhang) <pa...@gmail.com> 于2020年4月8日周三 上午9:02写道：
> Here is my +1.
>
> 张铎(Duo Zhang) <pa...@gmail.com> 于2020年4月8日周三 上午8:59写道：
>
>> Got it. Thanks for helping analyzing it.
>>
>> Yu Li <ca...@gmail.com> 于2020年4月7日周二 下午10:16写道：
>>
>>> Sorry for the late response due to vacation.
>>>
>>> I could reproduce the failure by running `mvn
>>> -Dtest=TestHFileCleaner#testHFileCleaning clean test`, and from the log I
>>> found the root cause, simply because my username on the test machine
>>> includes a dot, and the error message is like:
>>> ===============================
>>>
>>> *2020-04-07 21:59:10,396 ERROR [dir-scan-pool1-thread-1]
>>> mob.ManualMobMaintHFileCleaner(90): Failed to determine mob status of
>>> 'hdfs://localhost:54176/user/
>>> jueding.ly/test-data/42c5e99f-1b41-40d4-6117-394851f2bad9/archive/someHFileThatWouldBeAUUID.1586267949800
>>> <
>>> http://jueding.ly/test-data/42c5e99f-1b41-40d4-6117-394851f2bad9/archive/someHFileThatWouldBeAUUID.1586267949800
>>> >',
>>> keeping it just in case.java.lang.IllegalArgumentException: Illegal
>>> character <.> at 7. Namespaces may only contain 'alphanumeric characters'
>>> from any language and digits: jueding.ly <http://jueding.ly>*
>>> ===============================
>>>
>>> It would be better if we could harden the test case, but since it
>>> indicates
>>> no real bug, I don't think it should block the release.
>>>
>>> Since the stably failed case is confirmed to be environment related and
>>> the
>>> timed out cases could pass in single local run, I'm changing my vote to
>>> +1.
>>>
>>> And to be explicit:
>>>
>>> +1 (binding)
>>>
>>> Checked sums and signatures: ok
>>> Built from source: ok (8u101)
>>> RAT check: ok (8u101)
>>> Unit tests: ok (8u101)
>>> Server web UI: ok, checked master/RS UI, table details page, debug dump,
>>> metrics dump, everything looks good
>>> Shell commands: ok (8u101), ran DDL/DML/flush/compact/split/merge_region
>>> commands, everything looks good
>>>
>>> Best Regards,
>>> Yu
>>>
>>>
>>> On Sun, 5 Apr 2020 at 15:49, 张铎(Duo Zhang) <pa...@gmail.com>
>>> wrote:
>>>
>>> > Hi, Yu Li, I can not see these failures. Could you please confirm them
>>> > again? What is the detailed failure message?
>>> >
>>> > Thanks.
>>> >
>>> > Yu Li <ca...@gmail.com> 于2020年4月3日周五 上午10:24写道：
>>> >
>>> > > -1 (binding)
>>> > >
>>> > > Checked sums and signatures: ok
>>> > > Built from source: ok (8u101)
>>> > > RAT check: ok (8u101)
>>> > > Unit tests: failed (8u101)
>>> > > - TestHFileCleaner.testHFileCleaning failed stably and could be
>>> > reproduced
>>> > > by single run
>>> > > - 6 Errors caused by test timed out of this invocation
>>> > > path:
>>> > >
>>> >
>>> TestExportSnapshot.testExportWithTargetName:190->testExportFileSystemState:195->testExportFileSystemState:202->testExportFileSystemState:230
>>> > > - Command to run the UT:
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > * mvn -B -PrunAllTests\ -DreuseForks=false\
>>> > > -Dmaven.test.redirectTestOutputToFile=true\
>>> > > -Dsurefire.rerunFailingTestsCount=2\ -Dit.test=noItTest\
>>> > > -Dmaven.test.failure.ignore=true\
>>> -Dsurefire.testFailureIgnore=true\
>>> > > -Dmaven.test.error.ignore=true\ test*
>>> > >
>>> > > Best Regards,
>>> > > Yu
>>> > >
>>> > >
>>> > > On Fri, 3 Apr 2020 at 09:53, Andrew Purtell <ap...@apache.org>
>>> wrote:
>>> > >
>>> > > > -1 (binding)
>>> > > >
>>> > > > * Signature: ok
>>> > > > * Checksum : ok
>>> > > > * Rat check (1.8.0_232): ok
>>> > > > - mvn clean apache-rat:check
>>> > > > * Built from source (1.8.0_232): ok
>>> > > > - mvn clean install -DskipTests
>>> > > > * Unit tests pass (1.8.0_232): failed
>>> > > > - mvn package -P runAllTests
>>> > > >
>>> > > > TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue
>>> 100%
>>> > > > failure
>>> > > >
>>> > > >
>>> > > >
>>> > >
>>> >
>>> org.apache.hadoop.hbase.regionserver.TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue
>>> > > > Run 1:
>>> > > >
>>> > > >
>>> > >
>>> >
>>> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
>>> > > > expected:<true> but was:<false>
>>> > > > Run 2:
>>> > > >
>>> > > >
>>> > >
>>> >
>>> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
>>> > > > expected:<true> but was:<false>
>>> > > > Run 3:
>>> > > >
>>> > > >
>>> > >
>>> >
>>> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
>>> > > > expected:<true> but was:<false>
>>> > > > Run 4:
>>> > > >
>>> > > >
>>> > >
>>> >
>>> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
>>> > > > expected:<true> but was:<false>
>>> > > >
>>> > > > TestCanaryTool is broken, lots of these:
>>> > > >
>>> > > > [ERROR] Run 2: TestCanaryTool.testReadTableTimeouts:218
>>> > > > Argument(s) are different! Wanted:
>>> > > > mockAppender.doAppend(
>>> > > > <custom argument matcher>
>>> > > > );
>>> > > > -> at
>>> > > >
>>> > > >
>>> > >
>>> >
>>> org.apache.hadoop.hbase.tool.TestCanaryTool.testReadTableTimeouts(TestCanaryTool.java:218)
>>> > > > Actual invocations have different arguments:
>>> > > > mockAppender.doAppend(
>>> > > > org.apache.log4j.spi.LoggingEvent@5c21284d
>>> > > > );
>>> > > > Some flakes. The TestFromClientSide3 results are concerning because
>>> > they
>>> > > > could be a correctness issue:
>>> > > >
>>> > > > org.apache.hadoop.hbase.regionserver.TestRegionReplicas.null
>>> > > > Run 1:
>>> > > > TestRegionReplicas.testVerifySecondaryAbilityToReadWithOnFiles:476
>>> »
>>> > > > TestTimedOut
>>> > > > Run 2: PASS
>>> > > >
>>> > > >
>>> > > >
>>> > >
>>> >
>>> org.apache.hadoop.hbase.client.TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2
>>> > > > Run 1:
>>> TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
>>> > > > expected:<3> but was:<2>
>>> > > > Run 2:
>>> TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
>>> > > > expected:<3> but was:<2>
>>> > > > Run 3: PASS
>>> > > >
>>> > > >
>>> org.apache.hadoop.hbase.master.assignment.TestRegionMoveAndAbandon.test
>>> > > > Run 1: TestRegionMoveAndAbandon.test:118 » Runtime
>>> > > > org.apache.hadoop.hbase.client.Ret...
>>> > > > Run 2: PASS
>>> > > >
>>> > > >
>>> > > >
>>> > >
>>> >
>>> org.apache.hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures.testDisableTableWithFailover
>>> > > > Run 1: TestMasterFailoverWithProcedures.setup:76 » IO Shutting
>>> down
>>> > > > Run 2: PASS
>>> > > >
>>> > > >
>>> > > >
>>> > >
>>> >
>>> org.apache.hadoop.hbase.replication.regionserver.TestReplicator.testReplicatorWithErrors
>>> > > > Run 1: TestReplicator.testReplicatorWithErrors:158 We did not
>>> > > replicate
>>> > > > enough rows expected:<10> but was:<6>
>>> > > > Run 2: PASS
>>> > > >
>>> > > >
>>> > > >
>>> > >
>>> >
>>> org.apache.hadoop.hbase.util.TestFromClientSide3WoUnsafe.testScanAfterDeletingSpecifiedRowV2
>>> > > > Run 1:
>>> > > >
>>> > > >
>>> > >
>>> >
>>> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
>>> > > > expected:<3> but was:<2>
>>> > > > Run 2:
>>> > > >
>>> > > >
>>> > >
>>> >
>>> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
>>> > > > expected:<3> but was:<2>
>>> > > > Run 3: PASS
>>> > > >
>>> > > >
>>> > > > On Tue, Mar 31, 2020 at 9:15 PM Duo Zhang <zh...@apache.org>
>>> wrote:
>>> > > >
>>> > > > > Please vote on this Apache hbase release candidate,
>>> > > > > hbase-2.1.10RC1
>>> > > > >
>>> > > > > The VOTE will remain open for at least 72 hours.
>>> > > > >
>>> > > > > [ ] +1 Release this package as Apache hbase 2.1.10
>>> > > > > [ ] -1 Do not release this package because ...
>>> > > > >
>>> > > > > The tag to be voted on is 2.1.10RC1:
>>> > > > >
>>> > > > > https://github.com/apache/hbase/tree/2.1.10RC1
>>> > > > >
>>> > > > > 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.1.10RC1/
>>> > > > >
>>> > > > > Maven artifacts are available in a staging repository at:
>>> > > > >
>>> > > > >
>>> > >
>>> https://repository.apache.org/content/repositories/orgapachehbase-1387/
>>> > > > >
>>> > > > > Artifacts were signed with the 9AD2AE49 key which can be found
>>> in:
>>> > > > >
>>> > > > > https://dist.apache.org/repos/dist/release/hbase/KEYS
>>> > > > >
>>> > > > > 2.1.10 includes ~23 bug and improvement fixes done since the
>>> 2.1.9.
>>> > > > >
>>> > > > > To learn more about apache hbase, please see
>>> > > > > http://hbase.apache.org/
>>> > > > >
>>> > > > > Thanks,
>>> > > > > Your HBase Release Manager
>>> > > > >
>>> > > >
>>> > > >
>>> > > > --
>>> > > > Best regards,
>>> > > > Andrew
>>> > > >
>>> > > > Words like orphans lost among the crosstalk, meaning torn from
>>> truth's
>>> > > > decrepit hands
>>> > > > - A23, Crosstalk
>>> > > >
>>> > >
>>> >
>>>
>>
Re: [VOTE] Second release candidate for HBase 2.1.10 is available for download
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
Here is my +1.
张铎(Duo Zhang) <pa...@gmail.com> 于2020年4月8日周三 上午8:59写道：
> Got it. Thanks for helping analyzing it.
>
> Yu Li <ca...@gmail.com> 于2020年4月7日周二 下午10:16写道：
>
>> Sorry for the late response due to vacation.
>>
>> I could reproduce the failure by running `mvn
>> -Dtest=TestHFileCleaner#testHFileCleaning clean test`, and from the log I
>> found the root cause, simply because my username on the test machine
>> includes a dot, and the error message is like:
>> ===============================
>>
>> *2020-04-07 21:59:10,396 ERROR [dir-scan-pool1-thread-1]
>> mob.ManualMobMaintHFileCleaner(90): Failed to determine mob status of
>> 'hdfs://localhost:54176/user/
>> jueding.ly/test-data/42c5e99f-1b41-40d4-6117-394851f2bad9/archive/someHFileThatWouldBeAUUID.1586267949800
>> <
>> http://jueding.ly/test-data/42c5e99f-1b41-40d4-6117-394851f2bad9/archive/someHFileThatWouldBeAUUID.1586267949800
>> >',
>> keeping it just in case.java.lang.IllegalArgumentException: Illegal
>> character <.> at 7. Namespaces may only contain 'alphanumeric characters'
>> from any language and digits: jueding.ly <http://jueding.ly>*
>> ===============================
>>
>> It would be better if we could harden the test case, but since it
>> indicates
>> no real bug, I don't think it should block the release.
>>
>> Since the stably failed case is confirmed to be environment related and
>> the
>> timed out cases could pass in single local run, I'm changing my vote to
>> +1.
>>
>> And to be explicit:
>>
>> +1 (binding)
>>
>> Checked sums and signatures: ok
>> Built from source: ok (8u101)
>> RAT check: ok (8u101)
>> Unit tests: ok (8u101)
>> Server web UI: ok, checked master/RS UI, table details page, debug dump,
>> metrics dump, everything looks good
>> Shell commands: ok (8u101), ran DDL/DML/flush/compact/split/merge_region
>> commands, everything looks good
>>
>> Best Regards,
>> Yu
>>
>>
>> On Sun, 5 Apr 2020 at 15:49, 张铎(Duo Zhang) <pa...@gmail.com> wrote:
>>
>> > Hi, Yu Li, I can not see these failures. Could you please confirm them
>> > again? What is the detailed failure message?
>> >
>> > Thanks.
>> >
>> > Yu Li <ca...@gmail.com> 于2020年4月3日周五 上午10:24写道：
>> >
>> > > -1 (binding)
>> > >
>> > > Checked sums and signatures: ok
>> > > Built from source: ok (8u101)
>> > > RAT check: ok (8u101)
>> > > Unit tests: failed (8u101)
>> > > - TestHFileCleaner.testHFileCleaning failed stably and could be
>> > reproduced
>> > > by single run
>> > > - 6 Errors caused by test timed out of this invocation
>> > > path:
>> > >
>> >
>> TestExportSnapshot.testExportWithTargetName:190->testExportFileSystemState:195->testExportFileSystemState:202->testExportFileSystemState:230
>> > > - Command to run the UT:
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > * mvn -B -PrunAllTests\ -DreuseForks=false\
>> > > -Dmaven.test.redirectTestOutputToFile=true\
>> > > -Dsurefire.rerunFailingTestsCount=2\ -Dit.test=noItTest\
>> > > -Dmaven.test.failure.ignore=true\
>> -Dsurefire.testFailureIgnore=true\
>> > > -Dmaven.test.error.ignore=true\ test*
>> > >
>> > > Best Regards,
>> > > Yu
>> > >
>> > >
>> > > On Fri, 3 Apr 2020 at 09:53, Andrew Purtell <ap...@apache.org>
>> wrote:
>> > >
>> > > > -1 (binding)
>> > > >
>> > > > * Signature: ok
>> > > > * Checksum : ok
>> > > > * Rat check (1.8.0_232): ok
>> > > > - mvn clean apache-rat:check
>> > > > * Built from source (1.8.0_232): ok
>> > > > - mvn clean install -DskipTests
>> > > > * Unit tests pass (1.8.0_232): failed
>> > > > - mvn package -P runAllTests
>> > > >
>> > > > TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue
>> 100%
>> > > > failure
>> > > >
>> > > >
>> > > >
>> > >
>> >
>> org.apache.hadoop.hbase.regionserver.TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue
>> > > > Run 1:
>> > > >
>> > > >
>> > >
>> >
>> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
>> > > > expected:<true> but was:<false>
>> > > > Run 2:
>> > > >
>> > > >
>> > >
>> >
>> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
>> > > > expected:<true> but was:<false>
>> > > > Run 3:
>> > > >
>> > > >
>> > >
>> >
>> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
>> > > > expected:<true> but was:<false>
>> > > > Run 4:
>> > > >
>> > > >
>> > >
>> >
>> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
>> > > > expected:<true> but was:<false>
>> > > >
>> > > > TestCanaryTool is broken, lots of these:
>> > > >
>> > > > [ERROR] Run 2: TestCanaryTool.testReadTableTimeouts:218
>> > > > Argument(s) are different! Wanted:
>> > > > mockAppender.doAppend(
>> > > > <custom argument matcher>
>> > > > );
>> > > > -> at
>> > > >
>> > > >
>> > >
>> >
>> org.apache.hadoop.hbase.tool.TestCanaryTool.testReadTableTimeouts(TestCanaryTool.java:218)
>> > > > Actual invocations have different arguments:
>> > > > mockAppender.doAppend(
>> > > > org.apache.log4j.spi.LoggingEvent@5c21284d
>> > > > );
>> > > > Some flakes. The TestFromClientSide3 results are concerning because
>> > they
>> > > > could be a correctness issue:
>> > > >
>> > > > org.apache.hadoop.hbase.regionserver.TestRegionReplicas.null
>> > > > Run 1:
>> > > > TestRegionReplicas.testVerifySecondaryAbilityToReadWithOnFiles:476 »
>> > > > TestTimedOut
>> > > > Run 2: PASS
>> > > >
>> > > >
>> > > >
>> > >
>> >
>> org.apache.hadoop.hbase.client.TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2
>> > > > Run 1:
>> TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
>> > > > expected:<3> but was:<2>
>> > > > Run 2:
>> TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
>> > > > expected:<3> but was:<2>
>> > > > Run 3: PASS
>> > > >
>> > > >
>> org.apache.hadoop.hbase.master.assignment.TestRegionMoveAndAbandon.test
>> > > > Run 1: TestRegionMoveAndAbandon.test:118 » Runtime
>> > > > org.apache.hadoop.hbase.client.Ret...
>> > > > Run 2: PASS
>> > > >
>> > > >
>> > > >
>> > >
>> >
>> org.apache.hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures.testDisableTableWithFailover
>> > > > Run 1: TestMasterFailoverWithProcedures.setup:76 » IO Shutting
>> down
>> > > > Run 2: PASS
>> > > >
>> > > >
>> > > >
>> > >
>> >
>> org.apache.hadoop.hbase.replication.regionserver.TestReplicator.testReplicatorWithErrors
>> > > > Run 1: TestReplicator.testReplicatorWithErrors:158 We did not
>> > > replicate
>> > > > enough rows expected:<10> but was:<6>
>> > > > Run 2: PASS
>> > > >
>> > > >
>> > > >
>> > >
>> >
>> org.apache.hadoop.hbase.util.TestFromClientSide3WoUnsafe.testScanAfterDeletingSpecifiedRowV2
>> > > > Run 1:
>> > > >
>> > > >
>> > >
>> >
>> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
>> > > > expected:<3> but was:<2>
>> > > > Run 2:
>> > > >
>> > > >
>> > >
>> >
>> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
>> > > > expected:<3> but was:<2>
>> > > > Run 3: PASS
>> > > >
>> > > >
>> > > > On Tue, Mar 31, 2020 at 9:15 PM Duo Zhang <zh...@apache.org>
>> wrote:
>> > > >
>> > > > > Please vote on this Apache hbase release candidate,
>> > > > > hbase-2.1.10RC1
>> > > > >
>> > > > > The VOTE will remain open for at least 72 hours.
>> > > > >
>> > > > > [ ] +1 Release this package as Apache hbase 2.1.10
>> > > > > [ ] -1 Do not release this package because ...
>> > > > >
>> > > > > The tag to be voted on is 2.1.10RC1:
>> > > > >
>> > > > > https://github.com/apache/hbase/tree/2.1.10RC1
>> > > > >
>> > > > > 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.1.10RC1/
>> > > > >
>> > > > > Maven artifacts are available in a staging repository at:
>> > > > >
>> > > > >
>> > >
>> https://repository.apache.org/content/repositories/orgapachehbase-1387/
>> > > > >
>> > > > > Artifacts were signed with the 9AD2AE49 key which can be found in:
>> > > > >
>> > > > > https://dist.apache.org/repos/dist/release/hbase/KEYS
>> > > > >
>> > > > > 2.1.10 includes ~23 bug and improvement fixes done since the
>> 2.1.9.
>> > > > >
>> > > > > To learn more about apache hbase, please see
>> > > > > http://hbase.apache.org/
>> > > > >
>> > > > > Thanks,
>> > > > > Your HBase Release Manager
>> > > > >
>> > > >
>> > > >
>> > > > --
>> > > > Best regards,
>> > > > Andrew
>> > > >
>> > > > Words like orphans lost among the crosstalk, meaning torn from
>> truth's
>> > > > decrepit hands
>> > > > - A23, Crosstalk
>> > > >
>> > >
>> >
>>
>
Re: [VOTE] Second release candidate for HBase 2.1.10 is available for download
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
Got it. Thanks for helping analyzing it.
Yu Li <ca...@gmail.com> 于2020年4月7日周二 下午10:16写道：
> Sorry for the late response due to vacation.
>
> I could reproduce the failure by running `mvn
> -Dtest=TestHFileCleaner#testHFileCleaning clean test`, and from the log I
> found the root cause, simply because my username on the test machine
> includes a dot, and the error message is like:
> ===============================
>
> *2020-04-07 21:59:10,396 ERROR [dir-scan-pool1-thread-1]
> mob.ManualMobMaintHFileCleaner(90): Failed to determine mob status of
> 'hdfs://localhost:54176/user/
> jueding.ly/test-data/42c5e99f-1b41-40d4-6117-394851f2bad9/archive/someHFileThatWouldBeAUUID.1586267949800
> <
> http://jueding.ly/test-data/42c5e99f-1b41-40d4-6117-394851f2bad9/archive/someHFileThatWouldBeAUUID.1586267949800
> >',
> keeping it just in case.java.lang.IllegalArgumentException: Illegal
> character <.> at 7. Namespaces may only contain 'alphanumeric characters'
> from any language and digits: jueding.ly <http://jueding.ly>*
> ===============================
>
> It would be better if we could harden the test case, but since it indicates
> no real bug, I don't think it should block the release.
>
> Since the stably failed case is confirmed to be environment related and the
> timed out cases could pass in single local run, I'm changing my vote to +1.
>
> And to be explicit:
>
> +1 (binding)
>
> Checked sums and signatures: ok
> Built from source: ok (8u101)
> RAT check: ok (8u101)
> Unit tests: ok (8u101)
> Server web UI: ok, checked master/RS UI, table details page, debug dump,
> metrics dump, everything looks good
> Shell commands: ok (8u101), ran DDL/DML/flush/compact/split/merge_region
> commands, everything looks good
>
> Best Regards,
> Yu
>
>
> On Sun, 5 Apr 2020 at 15:49, 张铎(Duo Zhang) <pa...@gmail.com> wrote:
>
> > Hi, Yu Li, I can not see these failures. Could you please confirm them
> > again? What is the detailed failure message?
> >
> > Thanks.
> >
> > Yu Li <ca...@gmail.com> 于2020年4月3日周五 上午10:24写道：
> >
> > > -1 (binding)
> > >
> > > Checked sums and signatures: ok
> > > Built from source: ok (8u101)
> > > RAT check: ok (8u101)
> > > Unit tests: failed (8u101)
> > > - TestHFileCleaner.testHFileCleaning failed stably and could be
> > reproduced
> > > by single run
> > > - 6 Errors caused by test timed out of this invocation
> > > path:
> > >
> >
> TestExportSnapshot.testExportWithTargetName:190->testExportFileSystemState:195->testExportFileSystemState:202->testExportFileSystemState:230
> > > - Command to run the UT:
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > * mvn -B -PrunAllTests\ -DreuseForks=false\
> > > -Dmaven.test.redirectTestOutputToFile=true\
> > > -Dsurefire.rerunFailingTestsCount=2\ -Dit.test=noItTest\
> > > -Dmaven.test.failure.ignore=true\ -Dsurefire.testFailureIgnore=true\
> > > -Dmaven.test.error.ignore=true\ test*
> > >
> > > Best Regards,
> > > Yu
> > >
> > >
> > > On Fri, 3 Apr 2020 at 09:53, Andrew Purtell <ap...@apache.org>
> wrote:
> > >
> > > > -1 (binding)
> > > >
> > > > * Signature: ok
> > > > * Checksum : ok
> > > > * Rat check (1.8.0_232): ok
> > > > - mvn clean apache-rat:check
> > > > * Built from source (1.8.0_232): ok
> > > > - mvn clean install -DskipTests
> > > > * Unit tests pass (1.8.0_232): failed
> > > > - mvn package -P runAllTests
> > > >
> > > > TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue 100%
> > > > failure
> > > >
> > > >
> > > >
> > >
> >
> org.apache.hadoop.hbase.regionserver.TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue
> > > > Run 1:
> > > >
> > > >
> > >
> >
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> > > > expected:<true> but was:<false>
> > > > Run 2:
> > > >
> > > >
> > >
> >
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> > > > expected:<true> but was:<false>
> > > > Run 3:
> > > >
> > > >
> > >
> >
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> > > > expected:<true> but was:<false>
> > > > Run 4:
> > > >
> > > >
> > >
> >
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> > > > expected:<true> but was:<false>
> > > >
> > > > TestCanaryTool is broken, lots of these:
> > > >
> > > > [ERROR] Run 2: TestCanaryTool.testReadTableTimeouts:218
> > > > Argument(s) are different! Wanted:
> > > > mockAppender.doAppend(
> > > > <custom argument matcher>
> > > > );
> > > > -> at
> > > >
> > > >
> > >
> >
> org.apache.hadoop.hbase.tool.TestCanaryTool.testReadTableTimeouts(TestCanaryTool.java:218)
> > > > Actual invocations have different arguments:
> > > > mockAppender.doAppend(
> > > > org.apache.log4j.spi.LoggingEvent@5c21284d
> > > > );
> > > > Some flakes. The TestFromClientSide3 results are concerning because
> > they
> > > > could be a correctness issue:
> > > >
> > > > org.apache.hadoop.hbase.regionserver.TestRegionReplicas.null
> > > > Run 1:
> > > > TestRegionReplicas.testVerifySecondaryAbilityToReadWithOnFiles:476 »
> > > > TestTimedOut
> > > > Run 2: PASS
> > > >
> > > >
> > > >
> > >
> >
> org.apache.hadoop.hbase.client.TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2
> > > > Run 1: TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> > > > expected:<3> but was:<2>
> > > > Run 2: TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> > > > expected:<3> but was:<2>
> > > > Run 3: PASS
> > > >
> > > >
> org.apache.hadoop.hbase.master.assignment.TestRegionMoveAndAbandon.test
> > > > Run 1: TestRegionMoveAndAbandon.test:118 » Runtime
> > > > org.apache.hadoop.hbase.client.Ret...
> > > > Run 2: PASS
> > > >
> > > >
> > > >
> > >
> >
> org.apache.hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures.testDisableTableWithFailover
> > > > Run 1: TestMasterFailoverWithProcedures.setup:76 » IO Shutting
> down
> > > > Run 2: PASS
> > > >
> > > >
> > > >
> > >
> >
> org.apache.hadoop.hbase.replication.regionserver.TestReplicator.testReplicatorWithErrors
> > > > Run 1: TestReplicator.testReplicatorWithErrors:158 We did not
> > > replicate
> > > > enough rows expected:<10> but was:<6>
> > > > Run 2: PASS
> > > >
> > > >
> > > >
> > >
> >
> org.apache.hadoop.hbase.util.TestFromClientSide3WoUnsafe.testScanAfterDeletingSpecifiedRowV2
> > > > Run 1:
> > > >
> > > >
> > >
> >
> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> > > > expected:<3> but was:<2>
> > > > Run 2:
> > > >
> > > >
> > >
> >
> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> > > > expected:<3> but was:<2>
> > > > Run 3: PASS
> > > >
> > > >
> > > > On Tue, Mar 31, 2020 at 9:15 PM Duo Zhang <zh...@apache.org>
> wrote:
> > > >
> > > > > Please vote on this Apache hbase release candidate,
> > > > > hbase-2.1.10RC1
> > > > >
> > > > > The VOTE will remain open for at least 72 hours.
> > > > >
> > > > > [ ] +1 Release this package as Apache hbase 2.1.10
> > > > > [ ] -1 Do not release this package because ...
> > > > >
> > > > > The tag to be voted on is 2.1.10RC1:
> > > > >
> > > > > https://github.com/apache/hbase/tree/2.1.10RC1
> > > > >
> > > > > 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.1.10RC1/
> > > > >
> > > > > Maven artifacts are available in a staging repository at:
> > > > >
> > > > >
> > >
> https://repository.apache.org/content/repositories/orgapachehbase-1387/
> > > > >
> > > > > Artifacts were signed with the 9AD2AE49 key which can be found in:
> > > > >
> > > > > https://dist.apache.org/repos/dist/release/hbase/KEYS
> > > > >
> > > > > 2.1.10 includes ~23 bug and improvement fixes done since the 2.1.9.
> > > > >
> > > > > To learn more about apache hbase, please see
> > > > > http://hbase.apache.org/
> > > > >
> > > > > Thanks,
> > > > > Your HBase Release Manager
> > > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Andrew
> > > >
> > > > Words like orphans lost among the crosstalk, meaning torn from
> truth's
> > > > decrepit hands
> > > > - A23, Crosstalk
> > > >
> > >
> >
>
Re: [VOTE] Second release candidate for HBase 2.1.10 is available for download
Posted by Yu Li <ca...@gmail.com>.
Sorry for the late response due to vacation.
I could reproduce the failure by running `mvn
-Dtest=TestHFileCleaner#testHFileCleaning clean test`, and from the log I
found the root cause, simply because my username on the test machine
includes a dot, and the error message is like:
===============================
*2020-04-07 21:59:10,396 ERROR [dir-scan-pool1-thread-1]
mob.ManualMobMaintHFileCleaner(90): Failed to determine mob status of
'hdfs://localhost:54176/user/jueding.ly/test-data/42c5e99f-1b41-40d4-6117-394851f2bad9/archive/someHFileThatWouldBeAUUID.1586267949800
<http://jueding.ly/test-data/42c5e99f-1b41-40d4-6117-394851f2bad9/archive/someHFileThatWouldBeAUUID.1586267949800>',
keeping it just in case.java.lang.IllegalArgumentException: Illegal
character <.> at 7. Namespaces may only contain 'alphanumeric characters'
from any language and digits: jueding.ly <http://jueding.ly>*
===============================
It would be better if we could harden the test case, but since it indicates
no real bug, I don't think it should block the release.
Since the stably failed case is confirmed to be environment related and the
timed out cases could pass in single local run, I'm changing my vote to +1.
And to be explicit:
+1 (binding)
Checked sums and signatures: ok
Built from source: ok (8u101)
RAT check: ok (8u101)
Unit tests: ok (8u101)
Server web UI: ok, checked master/RS UI, table details page, debug dump,
metrics dump, everything looks good
Shell commands: ok (8u101), ran DDL/DML/flush/compact/split/merge_region
commands, everything looks good
Best Regards,
Yu
On Sun, 5 Apr 2020 at 15:49, 张铎(Duo Zhang) <pa...@gmail.com> wrote:
> Hi, Yu Li, I can not see these failures. Could you please confirm them
> again? What is the detailed failure message?
>
> Thanks.
>
> Yu Li <ca...@gmail.com> 于2020年4月3日周五 上午10:24写道：
>
> > -1 (binding)
> >
> > Checked sums and signatures: ok
> > Built from source: ok (8u101)
> > RAT check: ok (8u101)
> > Unit tests: failed (8u101)
> > - TestHFileCleaner.testHFileCleaning failed stably and could be
> reproduced
> > by single run
> > - 6 Errors caused by test timed out of this invocation
> > path:
> >
> TestExportSnapshot.testExportWithTargetName:190->testExportFileSystemState:195->testExportFileSystemState:202->testExportFileSystemState:230
> > - Command to run the UT:
> >
> >
> >
> >
> >
> >
> >
> >
> > * mvn -B -PrunAllTests\ -DreuseForks=false\
> > -Dmaven.test.redirectTestOutputToFile=true\
> > -Dsurefire.rerunFailingTestsCount=2\ -Dit.test=noItTest\
> > -Dmaven.test.failure.ignore=true\ -Dsurefire.testFailureIgnore=true\
> > -Dmaven.test.error.ignore=true\ test*
> >
> > Best Regards,
> > Yu
> >
> >
> > On Fri, 3 Apr 2020 at 09:53, Andrew Purtell <ap...@apache.org> wrote:
> >
> > > -1 (binding)
> > >
> > > * Signature: ok
> > > * Checksum : ok
> > > * Rat check (1.8.0_232): ok
> > > - mvn clean apache-rat:check
> > > * Built from source (1.8.0_232): ok
> > > - mvn clean install -DskipTests
> > > * Unit tests pass (1.8.0_232): failed
> > > - mvn package -P runAllTests
> > >
> > > TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue 100%
> > > failure
> > >
> > >
> > >
> >
> org.apache.hadoop.hbase.regionserver.TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue
> > > Run 1:
> > >
> > >
> >
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> > > expected:<true> but was:<false>
> > > Run 2:
> > >
> > >
> >
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> > > expected:<true> but was:<false>
> > > Run 3:
> > >
> > >
> >
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> > > expected:<true> but was:<false>
> > > Run 4:
> > >
> > >
> >
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> > > expected:<true> but was:<false>
> > >
> > > TestCanaryTool is broken, lots of these:
> > >
> > > [ERROR] Run 2: TestCanaryTool.testReadTableTimeouts:218
> > > Argument(s) are different! Wanted:
> > > mockAppender.doAppend(
> > > <custom argument matcher>
> > > );
> > > -> at
> > >
> > >
> >
> org.apache.hadoop.hbase.tool.TestCanaryTool.testReadTableTimeouts(TestCanaryTool.java:218)
> > > Actual invocations have different arguments:
> > > mockAppender.doAppend(
> > > org.apache.log4j.spi.LoggingEvent@5c21284d
> > > );
> > > Some flakes. The TestFromClientSide3 results are concerning because
> they
> > > could be a correctness issue:
> > >
> > > org.apache.hadoop.hbase.regionserver.TestRegionReplicas.null
> > > Run 1:
> > > TestRegionReplicas.testVerifySecondaryAbilityToReadWithOnFiles:476 »
> > > TestTimedOut
> > > Run 2: PASS
> > >
> > >
> > >
> >
> org.apache.hadoop.hbase.client.TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2
> > > Run 1: TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> > > expected:<3> but was:<2>
> > > Run 2: TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> > > expected:<3> but was:<2>
> > > Run 3: PASS
> > >
> > > org.apache.hadoop.hbase.master.assignment.TestRegionMoveAndAbandon.test
> > > Run 1: TestRegionMoveAndAbandon.test:118 » Runtime
> > > org.apache.hadoop.hbase.client.Ret...
> > > Run 2: PASS
> > >
> > >
> > >
> >
> org.apache.hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures.testDisableTableWithFailover
> > > Run 1: TestMasterFailoverWithProcedures.setup:76 » IO Shutting down
> > > Run 2: PASS
> > >
> > >
> > >
> >
> org.apache.hadoop.hbase.replication.regionserver.TestReplicator.testReplicatorWithErrors
> > > Run 1: TestReplicator.testReplicatorWithErrors:158 We did not
> > replicate
> > > enough rows expected:<10> but was:<6>
> > > Run 2: PASS
> > >
> > >
> > >
> >
> org.apache.hadoop.hbase.util.TestFromClientSide3WoUnsafe.testScanAfterDeletingSpecifiedRowV2
> > > Run 1:
> > >
> > >
> >
> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> > > expected:<3> but was:<2>
> > > Run 2:
> > >
> > >
> >
> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> > > expected:<3> but was:<2>
> > > Run 3: PASS
> > >
> > >
> > > On Tue, Mar 31, 2020 at 9:15 PM Duo Zhang <zh...@apache.org> wrote:
> > >
> > > > Please vote on this Apache hbase release candidate,
> > > > hbase-2.1.10RC1
> > > >
> > > > The VOTE will remain open for at least 72 hours.
> > > >
> > > > [ ] +1 Release this package as Apache hbase 2.1.10
> > > > [ ] -1 Do not release this package because ...
> > > >
> > > > The tag to be voted on is 2.1.10RC1:
> > > >
> > > > https://github.com/apache/hbase/tree/2.1.10RC1
> > > >
> > > > 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.1.10RC1/
> > > >
> > > > Maven artifacts are available in a staging repository at:
> > > >
> > > >
> > https://repository.apache.org/content/repositories/orgapachehbase-1387/
> > > >
> > > > Artifacts were signed with the 9AD2AE49 key which can be found in:
> > > >
> > > > https://dist.apache.org/repos/dist/release/hbase/KEYS
> > > >
> > > > 2.1.10 includes ~23 bug and improvement fixes done since the 2.1.9.
> > > >
> > > > To learn more about apache hbase, please see
> > > > http://hbase.apache.org/
> > > >
> > > > Thanks,
> > > > Your HBase Release Manager
> > > >
> > >
> > >
> > > --
> > > Best regards,
> > > Andrew
> > >
> > > Words like orphans lost among the crosstalk, meaning torn from truth's
> > > decrepit hands
> > > - A23, Crosstalk
> > >
> >
>
Re: [VOTE] Second release candidate for HBase 2.1.10 is available for download
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
Hi, Yu Li, I can not see these failures. Could you please confirm them
again? What is the detailed failure message?
Thanks.
Yu Li <ca...@gmail.com> 于2020年4月3日周五 上午10:24写道：
> -1 (binding)
>
> Checked sums and signatures: ok
> Built from source: ok (8u101)
> RAT check: ok (8u101)
> Unit tests: failed (8u101)
> - TestHFileCleaner.testHFileCleaning failed stably and could be reproduced
> by single run
> - 6 Errors caused by test timed out of this invocation
> path:
> TestExportSnapshot.testExportWithTargetName:190->testExportFileSystemState:195->testExportFileSystemState:202->testExportFileSystemState:230
> - Command to run the UT:
>
>
>
>
>
>
>
>
> * mvn -B -PrunAllTests\ -DreuseForks=false\
> -Dmaven.test.redirectTestOutputToFile=true\
> -Dsurefire.rerunFailingTestsCount=2\ -Dit.test=noItTest\
> -Dmaven.test.failure.ignore=true\ -Dsurefire.testFailureIgnore=true\
> -Dmaven.test.error.ignore=true\ test*
>
> Best Regards,
> Yu
>
>
> On Fri, 3 Apr 2020 at 09:53, Andrew Purtell <ap...@apache.org> wrote:
>
> > -1 (binding)
> >
> > * Signature: ok
> > * Checksum : ok
> > * Rat check (1.8.0_232): ok
> > - mvn clean apache-rat:check
> > * Built from source (1.8.0_232): ok
> > - mvn clean install -DskipTests
> > * Unit tests pass (1.8.0_232): failed
> > - mvn package -P runAllTests
> >
> > TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue 100%
> > failure
> >
> >
> >
> org.apache.hadoop.hbase.regionserver.TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue
> > Run 1:
> >
> >
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> > expected:<true> but was:<false>
> > Run 2:
> >
> >
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> > expected:<true> but was:<false>
> > Run 3:
> >
> >
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> > expected:<true> but was:<false>
> > Run 4:
> >
> >
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> > expected:<true> but was:<false>
> >
> > TestCanaryTool is broken, lots of these:
> >
> > [ERROR] Run 2: TestCanaryTool.testReadTableTimeouts:218
> > Argument(s) are different! Wanted:
> > mockAppender.doAppend(
> > <custom argument matcher>
> > );
> > -> at
> >
> >
> org.apache.hadoop.hbase.tool.TestCanaryTool.testReadTableTimeouts(TestCanaryTool.java:218)
> > Actual invocations have different arguments:
> > mockAppender.doAppend(
> > org.apache.log4j.spi.LoggingEvent@5c21284d
> > );
> > Some flakes. The TestFromClientSide3 results are concerning because they
> > could be a correctness issue:
> >
> > org.apache.hadoop.hbase.regionserver.TestRegionReplicas.null
> > Run 1:
> > TestRegionReplicas.testVerifySecondaryAbilityToReadWithOnFiles:476 »
> > TestTimedOut
> > Run 2: PASS
> >
> >
> >
> org.apache.hadoop.hbase.client.TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2
> > Run 1: TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> > expected:<3> but was:<2>
> > Run 2: TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> > expected:<3> but was:<2>
> > Run 3: PASS
> >
> > org.apache.hadoop.hbase.master.assignment.TestRegionMoveAndAbandon.test
> > Run 1: TestRegionMoveAndAbandon.test:118 » Runtime
> > org.apache.hadoop.hbase.client.Ret...
> > Run 2: PASS
> >
> >
> >
> org.apache.hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures.testDisableTableWithFailover
> > Run 1: TestMasterFailoverWithProcedures.setup:76 » IO Shutting down
> > Run 2: PASS
> >
> >
> >
> org.apache.hadoop.hbase.replication.regionserver.TestReplicator.testReplicatorWithErrors
> > Run 1: TestReplicator.testReplicatorWithErrors:158 We did not
> replicate
> > enough rows expected:<10> but was:<6>
> > Run 2: PASS
> >
> >
> >
> org.apache.hadoop.hbase.util.TestFromClientSide3WoUnsafe.testScanAfterDeletingSpecifiedRowV2
> > Run 1:
> >
> >
> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> > expected:<3> but was:<2>
> > Run 2:
> >
> >
> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> > expected:<3> but was:<2>
> > Run 3: PASS
> >
> >
> > On Tue, Mar 31, 2020 at 9:15 PM Duo Zhang <zh...@apache.org> wrote:
> >
> > > Please vote on this Apache hbase release candidate,
> > > hbase-2.1.10RC1
> > >
> > > The VOTE will remain open for at least 72 hours.
> > >
> > > [ ] +1 Release this package as Apache hbase 2.1.10
> > > [ ] -1 Do not release this package because ...
> > >
> > > The tag to be voted on is 2.1.10RC1:
> > >
> > > https://github.com/apache/hbase/tree/2.1.10RC1
> > >
> > > 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.1.10RC1/
> > >
> > > Maven artifacts are available in a staging repository at:
> > >
> > >
> https://repository.apache.org/content/repositories/orgapachehbase-1387/
> > >
> > > Artifacts were signed with the 9AD2AE49 key which can be found in:
> > >
> > > https://dist.apache.org/repos/dist/release/hbase/KEYS
> > >
> > > 2.1.10 includes ~23 bug and improvement fixes done since the 2.1.9.
> > >
> > > To learn more about apache hbase, please see
> > > http://hbase.apache.org/
> > >
> > > Thanks,
> > > Your HBase Release Manager
> > >
> >
> >
> > --
> > Best regards,
> > Andrew
> >
> > Words like orphans lost among the crosstalk, meaning torn from truth's
> > decrepit hands
> > - A23, Crosstalk
> >
>
Re: [VOTE] Second release candidate for HBase 2.1.10 is available for download
Posted by Yu Li <ca...@gmail.com>.
-1 (binding)
Checked sums and signatures: ok
Built from source: ok (8u101)
RAT check: ok (8u101)
Unit tests: failed (8u101)
- TestHFileCleaner.testHFileCleaning failed stably and could be reproduced
by single run
- 6 Errors caused by test timed out of this invocation
path: TestExportSnapshot.testExportWithTargetName:190->testExportFileSystemState:195->testExportFileSystemState:202->testExportFileSystemState:230
- Command to run the UT:
* mvn -B -PrunAllTests\ -DreuseForks=false\
-Dmaven.test.redirectTestOutputToFile=true\
-Dsurefire.rerunFailingTestsCount=2\ -Dit.test=noItTest\
-Dmaven.test.failure.ignore=true\ -Dsurefire.testFailureIgnore=true\
-Dmaven.test.error.ignore=true\ test*
Best Regards,
Yu
On Fri, 3 Apr 2020 at 09:53, Andrew Purtell <ap...@apache.org> wrote:
> -1 (binding)
>
> * Signature: ok
> * Checksum : ok
> * Rat check (1.8.0_232): ok
> - mvn clean apache-rat:check
> * Built from source (1.8.0_232): ok
> - mvn clean install -DskipTests
> * Unit tests pass (1.8.0_232): failed
> - mvn package -P runAllTests
>
> TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue 100%
> failure
>
>
> org.apache.hadoop.hbase.regionserver.TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue
> Run 1:
>
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> expected:<true> but was:<false>
> Run 2:
>
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> expected:<true> but was:<false>
> Run 3:
>
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> expected:<true> but was:<false>
> Run 4:
>
> TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
> expected:<true> but was:<false>
>
> TestCanaryTool is broken, lots of these:
>
> [ERROR] Run 2: TestCanaryTool.testReadTableTimeouts:218
> Argument(s) are different! Wanted:
> mockAppender.doAppend(
> <custom argument matcher>
> );
> -> at
>
> org.apache.hadoop.hbase.tool.TestCanaryTool.testReadTableTimeouts(TestCanaryTool.java:218)
> Actual invocations have different arguments:
> mockAppender.doAppend(
> org.apache.log4j.spi.LoggingEvent@5c21284d
> );
> Some flakes. The TestFromClientSide3 results are concerning because they
> could be a correctness issue:
>
> org.apache.hadoop.hbase.regionserver.TestRegionReplicas.null
> Run 1:
> TestRegionReplicas.testVerifySecondaryAbilityToReadWithOnFiles:476 »
> TestTimedOut
> Run 2: PASS
>
>
> org.apache.hadoop.hbase.client.TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2
> Run 1: TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> expected:<3> but was:<2>
> Run 2: TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> expected:<3> but was:<2>
> Run 3: PASS
>
> org.apache.hadoop.hbase.master.assignment.TestRegionMoveAndAbandon.test
> Run 1: TestRegionMoveAndAbandon.test:118 » Runtime
> org.apache.hadoop.hbase.client.Ret...
> Run 2: PASS
>
>
> org.apache.hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures.testDisableTableWithFailover
> Run 1: TestMasterFailoverWithProcedures.setup:76 » IO Shutting down
> Run 2: PASS
>
>
> org.apache.hadoop.hbase.replication.regionserver.TestReplicator.testReplicatorWithErrors
> Run 1: TestReplicator.testReplicatorWithErrors:158 We did not replicate
> enough rows expected:<10> but was:<6>
> Run 2: PASS
>
>
> org.apache.hadoop.hbase.util.TestFromClientSide3WoUnsafe.testScanAfterDeletingSpecifiedRowV2
> Run 1:
>
> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> expected:<3> but was:<2>
> Run 2:
>
> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
> expected:<3> but was:<2>
> Run 3: PASS
>
>
> On Tue, Mar 31, 2020 at 9:15 PM Duo Zhang <zh...@apache.org> wrote:
>
> > Please vote on this Apache hbase release candidate,
> > hbase-2.1.10RC1
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache hbase 2.1.10
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 2.1.10RC1:
> >
> > https://github.com/apache/hbase/tree/2.1.10RC1
> >
> > 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.1.10RC1/
> >
> > Maven artifacts are available in a staging repository at:
> >
> > https://repository.apache.org/content/repositories/orgapachehbase-1387/
> >
> > Artifacts were signed with the 9AD2AE49 key which can be found in:
> >
> > https://dist.apache.org/repos/dist/release/hbase/KEYS
> >
> > 2.1.10 includes ~23 bug and improvement fixes done since the 2.1.9.
> >
> > To learn more about apache hbase, please see
> > http://hbase.apache.org/
> >
> > Thanks,
> > Your HBase Release Manager
> >
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
> - A23, Crosstalk
>
Re: [VOTE] Second release candidate for HBase 2.1.10 is available for download
Posted by Andrew Purtell <ap...@apache.org>.
-1 (binding)
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_232): ok
- mvn clean apache-rat:check
* Built from source (1.8.0_232): ok
- mvn clean install -DskipTests
* Unit tests pass (1.8.0_232): failed
- mvn package -P runAllTests
TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue 100%
failure
org.apache.hadoop.hbase.regionserver.TestHRegionWithInMemoryFlush.testCheckAndMutate_WithCorrectValue
Run 1:
TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
expected:<true> but was:<false>
Run 2:
TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
expected:<true> but was:<false>
Run 3:
TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
expected:<true> but was:<false>
Run 4:
TestHRegionWithInMemoryFlush>TestHRegion.testCheckAndMutate_WithCorrectValue:1986
expected:<true> but was:<false>
TestCanaryTool is broken, lots of these:
[ERROR] Run 2: TestCanaryTool.testReadTableTimeouts:218
Argument(s) are different! Wanted:
mockAppender.doAppend(
<custom argument matcher>
);
-> at
org.apache.hadoop.hbase.tool.TestCanaryTool.testReadTableTimeouts(TestCanaryTool.java:218)
Actual invocations have different arguments:
mockAppender.doAppend(
org.apache.log4j.spi.LoggingEvent@5c21284d
);
Some flakes. The TestFromClientSide3 results are concerning because they
could be a correctness issue:
org.apache.hadoop.hbase.regionserver.TestRegionReplicas.null
Run 1:
TestRegionReplicas.testVerifySecondaryAbilityToReadWithOnFiles:476 »
TestTimedOut
Run 2: PASS
org.apache.hadoop.hbase.client.TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2
Run 1: TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
expected:<3> but was:<2>
Run 2: TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
expected:<3> but was:<2>
Run 3: PASS
org.apache.hadoop.hbase.master.assignment.TestRegionMoveAndAbandon.test
Run 1: TestRegionMoveAndAbandon.test:118 » Runtime
org.apache.hadoop.hbase.client.Ret...
Run 2: PASS
org.apache.hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures.testDisableTableWithFailover
Run 1: TestMasterFailoverWithProcedures.setup:76 » IO Shutting down
Run 2: PASS
org.apache.hadoop.hbase.replication.regionserver.TestReplicator.testReplicatorWithErrors
Run 1: TestReplicator.testReplicatorWithErrors:158 We did not replicate
enough rows expected:<10> but was:<6>
Run 2: PASS
org.apache.hadoop.hbase.util.TestFromClientSide3WoUnsafe.testScanAfterDeletingSpecifiedRowV2
Run 1:
TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
expected:<3> but was:<2>
Run 2:
TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:253
expected:<3> but was:<2>
Run 3: PASS
On Tue, Mar 31, 2020 at 9:15 PM Duo Zhang <zh...@apache.org> wrote:
> Please vote on this Apache hbase release candidate,
> hbase-2.1.10RC1
>
> The VOTE will remain open for at least 72 hours.
>
> [ ] +1 Release this package as Apache hbase 2.1.10
> [ ] -1 Do not release this package because ...
>
> The tag to be voted on is 2.1.10RC1:
>
> https://github.com/apache/hbase/tree/2.1.10RC1
>
> 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.1.10RC1/
>
> Maven artifacts are available in a staging repository at:
>
> https://repository.apache.org/content/repositories/orgapachehbase-1387/
>
> Artifacts were signed with the 9AD2AE49 key which can be found in:
>
> https://dist.apache.org/repos/dist/release/hbase/KEYS
>
> 2.1.10 includes ~23 bug and improvement fixes done since the 2.1.9.
>
> To learn more about apache hbase, please see
> http://hbase.apache.org/
>
> Thanks,
> Your HBase Release Manager
>
--
Best regards,
Andrew
Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
- A23, Crosstalk