[
https://issues.apache.org/jira/browse/KUDU-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Bukor updated KUDU-3481:
-------------------------------
Fix Version/s: 1.19.0
1.18.2
> CatalogManagerConfigurations/MasterStressTest.Test/2 is flaky because of HMS
> out-of-order log event
> ---------------------------------------------------------------------------------------------------
>
> Key: KUDU-3481
> URL: https://issues.apache.org/jira/browse/KUDU-3481
> Project: Kudu
> Issue Type: Bug
> Components: hms, master, test
> Affects Versions: 1.12.0, 1.13.0, 1.14.0, 1.15.0, 1.16.0, 1.17.0
> Reporter: Alexey Serbin
> Priority: Major
> Fix For: 1.19.0, 1.18.2
>
> Attachments: a.xz, b.xz, err_msg.xz,
> master-stress-test.2.20250903.txt.xz, master-stress-test.2.txt.xz
>
>
> The {{CatalogManagerConfigurations/MasterStressTest.Test/2}} scenario of
> {{master-stress-test}} sometimes fails because HMS sends out-of-order log
> event:
> {noformat}
> F20230522 20:45:47.163322 1908 hms_notification_log_listener.cc:264]
> Received out-of-order notification log event (last processed event ID: 22):
> 22 DROP_TABLE default.table_975e93282e3f4e09833880a7c0dd094a
> {noformat}
> Apparently, that's not Kudu, but HMS-related issue (probably,
> [HIVE-19874|https://issues.apache.org/jira/browse/HIVE-19874]?). Anyways,
> I'm opening this JIRA item to track the flakiness in the test.
> The full log is attached.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)