Skip to content

Improve recovery #46

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

Merged
merged 1 commit into from
Sep 4, 2024
Merged

Improve recovery #46

merged 1 commit into from
Sep 4, 2024

Conversation

acogoluegnes
Copy link
Collaborator

No description provided.

@acogoluegnes acogoluegnes changed the title Force ClientFutureFactory to "progressive" Improve recovery Aug 13, 2024
@lukebakken lukebakken self-requested a review August 13, 2024 13:56
@acogoluegnes acogoluegnes force-pushed the cluster-recovery branch 2 times, most recently from 51a8e01 to caccc09 Compare September 4, 2024 06:30
Schedule reconnection attempts instead of waiting and blocking the
thread.
Use platform threads for the environment scheduler.
Use a common event loop to record topology.

Virtual threads do not behave as expected, especially for long-running
tasks (e.g. polling a blocking queue for new tasks to process), which
makes recovery fails. They will be used only for short-lived task, like
polling a future to get the settlement.
@acogoluegnes acogoluegnes marked this pull request as ready for review September 4, 2024 09:23
@acogoluegnes acogoluegnes merged commit 833672d into main Sep 4, 2024
1 check passed
@acogoluegnes acogoluegnes deleted the cluster-recovery branch September 4, 2024 09:24
github-actions bot pushed a commit that referenced this pull request Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants