Skip to content

Start cleanup/reset after request is done#310

Merged
roosterfish merged 1 commit into
canonical:v3from
roosterfish:fix_reset
Jan 13, 2025
Merged

Start cleanup/reset after request is done#310
roosterfish merged 1 commit into
canonical:v3from
roosterfish:fix_reset

Conversation

@roosterfish
Copy link
Copy Markdown
Contributor

Found this whilst reasoning about the effect of this change.

When resetting a cluster member the shutdown procedures should be invoked only after the connection that was used to trigger the reset has been closed (context cancelled). The database might be already stopped but the request's context isn't yet cancelled.

Furthermore the state directory should be cleaned after all the listeners are closed (including inotify) to prevent any errors trying to read the state directory.

When resetting a cluster member the shutdown procedures should be invoked only after the connection
that was used to trigger the reset has been closed (context cancelled).
The database might be already stopped but the request's context isn't yet cancelled.

Furthermore the state directory should be cleaned after all the listeners are closed (including inotify)
to prevent any errors trying to read the state directory.

Signed-off-by: Julian Pelizäus <julian.pelizaeus@canonical.com>
@roosterfish roosterfish merged commit 8a7c94c into canonical:v3 Jan 13, 2025
@roosterfish roosterfish deleted the fix_reset branch January 13, 2025 08:12
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