[
https://issues.apache.org/jira/browse/KUDU-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17938633#comment-17938633
]
ASF subversion and git services commented on KUDU-3481:
-------------------------------------------------------
Commit e8a8325b0fd1afaa60394a91b55a31fa63a25516 in kudu's branch
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=e8a8325b0 ]
KUDU-3481 more diagnostics on non-monotonic event IDs
This is to help understand where the issue reported by KUDU-3481
originates from: whether it's due to non-monotonic or duplicate
event IDs in the response received from HMS, or that's something else.
Change-Id: Idac2f8969e10f066442aad0570c41767b98a0b75
Reviewed-on: http://gerrit.cloudera.org:8080/22657
Tested-by: Alexey Serbin <ale...@apache.org>
Reviewed-by: Yifan Zhang <chinazhangyi...@163.com>
> 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
> Attachments: 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
(v8.20.10#820010)
