-
Notifications
You must be signed in to change notification settings - Fork 186
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
Shut down the connection supervisor in case of an unrecoverable replication error #2189
base: main
Are you sure you want to change the base?
Conversation
95afd17
to
d96cc2d
Compare
✅ Deploy Preview for electric-next ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
d96cc2d
to
3b9df57
Compare
# Perform supervisor shutdown in a task to avoid a circular dependency where the manager | ||
# process is waiting for the supervisor to shut down its children, one of which is the | ||
# manager process itself. | ||
Task.start(Electric.Connection.Supervisor, :shutdown, [state.stack_id, error]) |
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.
Great job, but let's dispatch_stack_event
here too, so that the control plane can be aware of what's happened and why this is down
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.
Updated. Please let me know if it looks good.
3b9df57
to
a1d6bf1
Compare
…cation error The StackSupervisor will shut itself down as a result because the connection supervisor is marked as a significant child. In a multi-tenant setup, this effectively shuts down a single tenant while the other tenants keep running.
e79f764
to
21dc633
Compare
The StackSupervisor will shut itself down as a consequence.
In a multi-tenant setup, this effectively shuts down a single tenant while allowing the other tenants to keep chugging along.
Closes #2178.