Skip to content

Conversation

@dumbbell
Copy link
Collaborator

Why

The code assumed that the transaction would always succeed. It was kind of the case with Mnesia because it would throw an exception if it failed.

Khepri returns an error instead. The code has to handle it. In particular, we see timeouts in CI and before this patch, they caused a crash because the list comprehension was asked to work on a tuple.

How

We now retry a few times for 10 seconds.

[Why]
The code assumed that the transaction would always succeed. It was kind
of the case with Mnesia because it would throw an exception if it
failed.

Khepri returns an error instead. The code has to handle it. In
particular, we see timeouts in CI and before this patch, they caused a
crash because the list comprehension was asked to work on a tuple.

[How]
We now retry a few times for 10 seconds.
@dumbbell dumbbell self-assigned this Nov 29, 2024
@dumbbell dumbbell marked this pull request as ready for review November 29, 2024 11:35
@dumbbell dumbbell merged commit 84607b7 into main Nov 29, 2024
273 checks passed
@dumbbell dumbbell deleted the mirrored-sup-retry-update-after-db-timeout branch November 29, 2024 11:35
michaelklishin added a commit that referenced this pull request Dec 2, 2024
mirrored_supervisor: Catch timeout from Khepri in `hanlde_info/2` (backport #12853)
@michaelklishin michaelklishin added this to the 4.1.0 milestone Apr 23, 2025
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.

3 participants