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 (Jira)" <ji...@apache.org> on 2022/09/09 15:10:00 UTC
[jira] [Resolved] (HBASE-27360) The trace related assertions are flaky for async client tests
[ https://issues.apache.org/jira/browse/HBASE-27360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duo Zhang resolved HBASE-27360.
-------------------------------
Fix Version/s: 2.6.0
2.5.1
3.0.0-alpha-4
Hadoop Flags: Reviewed
Resolution: Fixed
Pushed to branch-2.5+.
Thanks [~GeorryHuang] for reviewing!
> The trace related assertions are flaky for async client tests
> -------------------------------------------------------------
>
> Key: HBASE-27360
> URL: https://issues.apache.org/jira/browse/HBASE-27360
> Project: HBase
> Issue Type: Bug
> Components: test, tracing
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4
>
>
> https://ci-hbase.apache.org/job/HBase-Flaky-Tests/job/master/4167/testReport/junit/org.apache.hadoop.hbase.client/TestAsyncTableScanner/testScanWrongColumnFamily_0__table_raw__scan_normal_/
> The failure message is kinda unreadable... I guess the problem is we do not wait enough time as the completion of the span can be executed concurrently with normal scan operation.
> And also I saw this in the test code
> {code}
> // RawAsyncTableImpl never invokes the callback to `onScanMetricsCreated` -- bug?
> {code}
> This is not a bug as you need to manually enable scan metrics by calling Scan.setScanMetricsEnabled(true).
> Let me also fix this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)