-
Notifications
You must be signed in to change notification settings - Fork 316
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
Evaluate what conditions should automatically trigger a service election #7486
Comments
I'm ended up with decision that nowadays it is impossible to use leader-follower topology at all. Now I want to upgrade services to something minor. But stopping the service is not triggering election, so it not possible to upgrade without downtime. I also cannot stop supervisor itself, because it is running other services. Digging into source code I found a "hack" with |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you. |
not stale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you. |
1 similar comment
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you. |
This issue is for discuss Chef Habitats' election best behavior .
I see that stop/start service doesn't trigger election.
Now elections only triggered when leader supervisor goes down.
Probably, we should trigger a new election:
My real use-case example now: I'm building postgresql streaming replication service. And I need a master node always be master. So if it goes down - new temporary leader will be elected (postgres stays in readonly mode). When master goes back online - it should be the leader.
To achieve this I create suitability hook which always returns
10
for a leader,5
for a follower, and0
when uninitialized.Picture gets more complicated when you starting think about "should suitability hook be triggered before service start, after start, after health-check passed, after post-run?
The text was updated successfully, but these errors were encountered: