Skip to content

Different approach to corrupt config recovery.#614

Merged
kjnilsson merged 1 commit intomainfrom
handle-corrupt-config
Mar 31, 2026
Merged

Different approach to corrupt config recovery.#614
kjnilsson merged 1 commit intomainfrom
handle-corrupt-config

Conversation

@kjnilsson
Copy link
Copy Markdown
Contributor

A new ra server needs to be registered before the log is initalised as the log init writes index 0. If they are not initialised the segment writer or even the WAL may drop the write or remove the mem table causing the member to crash shortly after.

Instead we will handle corrupt config files in pre-init and unregister the UID if the config file is missing or does not contain a parsable erlang term.

A new ra server needs to be registered before the log is initalised
as the log init writes index 0. If they are not initialised the
segment writer or even the WAL may drop the write or remove the
mem table causing the member to crash shortly after.

Instead we will handle corrupt config files in pre-init and
unregister the UID if the config file is missing or does not
contain a parsable erlang term.
@kjnilsson kjnilsson force-pushed the handle-corrupt-config branch from ae8b3f9 to eacc8f2 Compare March 31, 2026 10:00
Copy link
Copy Markdown
Collaborator

@dumbbell dumbbell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me.

@kjnilsson kjnilsson marked this pull request as ready for review March 31, 2026 11:17
@kjnilsson kjnilsson merged commit 0464cdf into main Mar 31, 2026
8 checks passed
@kjnilsson kjnilsson deleted the handle-corrupt-config branch March 31, 2026 11:17
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