You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/04/30 02:12:00 UTC
[jira] [Resolved] (HBASE-26602) [aarch64] TestAsyncNonMetaRegionLocator is flaky
[ https://issues.apache.org/jira/browse/HBASE-26602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kyle Purtell resolved HBASE-26602.
-----------------------------------------
Fix Version/s: (was: 2.5.0)
(was: 2.6.0)
(was: 3.0.0-alpha-3)
(was: 2.4.12)
Resolution: Cannot Reproduce
Does not reproduce with 2.4.12-SNAPSHOT
> [aarch64] TestAsyncNonMetaRegionLocator is flaky
> ------------------------------------------------
>
> Key: HBASE-26602
> URL: https://issues.apache.org/jira/browse/HBASE-26602
> Project: HBase
> Issue Type: Bug
> Components: asyncclient, test
> Affects Versions: 2.4.9
> Reporter: Andrew Kyle Purtell
> Priority: Minor
>
> There was an earlier issue where the problem was diagnosed as a race (see HBASE-20822). The test is flaky again now on MacOS aarch64, which is likely a timing/race issue again. The underlying hardware memory model is different so the JVM will be using memory barriers in more places on aarch64 than x86_64 etc. and multithreaded timings and interactions can be expected to be slightly different.
> org.apache.hadoop.hbase.client.TestAsyncNonMetaRegionLocator.testMultiRegionTable[1]
> [ERROR] Run 1: TestAsyncNonMetaRegionLocator.testMultiRegionTable:251->lambda$testMultiRegionTable$5:251->lambda$null$4:253->assertLocEquals:196 array lengths differed, expected.length=3 actual.length=0; arrays first differed at element [0]; expected:<49> but was:<end of array>
> [INFO] Run 2: PASS
> org.apache.hadoop.hbase.client.TestAsyncNonMetaRegionLocator.testRegionMove[1]
> [ERROR] Run 1: TestAsyncNonMetaRegionLocator.testRegionMove:292->assertLocEquals:197 expected:<192.168.1.25,64070,1639793242964> but was:<192.168.1.25,64053,1639793242927>
> [INFO] Run 2: PASS
> org.apache.hadoop.hbase.client.TestAsyncNonMetaRegionLocator.testRegionReplicas[1]
> [ERROR] Run 1: TestAsyncNonMetaRegionLocator.testRegionReplicas:433 expected:<3> but was:<1>
> [INFO] Run 2: PASS
> org.apache.hadoop.hbase.client.TestAsyncNonMetaRegionLocator.testReload[1]
> [ERROR] Run 1: TestAsyncNonMetaRegionLocator.testReload:365->assertLocEquals:197 expected:<192.168.1.25,64083,1639793243015> but was:<192.168.1.25,64053,1639793242927>
> [INFO] Run 2: PASS
> org.apache.hadoop.hbase.client.TestAsyncNonMetaRegionLocator.testSingleRegionTable[1]
> [ERROR] Run 1: TestAsyncNonMetaRegionLocator.testSingleRegionTable:205->assertLocEquals:197 expected:<192.168.1.25,64070,1639793242964> but was:<192.168.1.25,64053,1639793242927>
> [INFO] Run 2: PASS
--
This message was sent by Atlassian Jira
(v8.20.7#820007)