-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use exponential backoff retry strategy for glue client #23039
Use exponential backoff retry strategy for glue client #23039
Conversation
/test-with-secrets sha=61c3c5e23162890cb76fb3b2340fdfdd2c2a8b27 |
The CI workflow run with tests that require additional secrets finished as failure: https://github.com/trinodb/trino/actions/runs/10388756346 |
@ebyhr is there anything I can do to retry job, or you need to schedule retry? I see there seems to be 1 clickhouse flaky test |
@oskar-szwajkowski We can ignore the failure because we're sure that ClickHouse connector is unrelated to this change. @electrum Could you review this PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing this
plugin/trino-hive/src/main/java/io/trino/plugin/hive/metastore/glue/GlueMetastoreModule.java
Outdated
Show resolved
Hide resolved
c1ca644
to
8dd12b4
Compare
Default strategy was not good enough for handling concurrent modifications, which led to flaky behavior in concurrent modifications tests like TestIcebergGlueCatalogConnectorSmokeTest#testDeleteRowsConcurrently
8dd12b4
to
f4b839f
Compare
Let me merge to fix flaky tests. |
Description
After merging #22814, @ebyhr reporter that
TestIcebergGlueCatalogConnectorSmokeTest#testDeleteRowsConcurrently
became flakyAfter running it several times locally, I found that commit 4b28d9b seems to be problematic
Default retry strategy, which brings default backoff strategy, wasn't good enough when dealing with such concurrent use cases. After changing to exponential backoff strategy it feels much more stable now.
Additional context and related issues
#22814
Release notes
( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(X) Release notes are required, with the following suggested text: