Skip to content
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

Add read-only instances to Cartridge replicaset #1843

Closed
yngvar-antonsson opened this issue Jun 15, 2022 · 1 comment · Fixed by #1894
Closed

Add read-only instances to Cartridge replicaset #1843

yngvar-antonsson opened this issue Jun 15, 2022 · 1 comment · Fixed by #1894
Assignees

Comments

@yngvar-antonsson
Copy link
Collaborator

No we can't restrict Cartridge failover (in Eventual and Stateful mode) to switch on any instance, they're all the same for failover. We could provide argparse option (e.g. CARTRIDGE_READ_ONLY) or smth like this to forbid switching on such instance

@R-omk
Copy link
Contributor

R-omk commented Jun 24, 2022

I think that all hosts should start in this mode (ro / voter) and only then the cartridge decides who can become the master (candidate).

It should also work at runtime so that api can force any host to stop being the master or stop being a candidate master.

This feature is needed for the rolling upgrade process to prevent the possibility to elect a node with an old version if a master with a new version has already been elected at least once before.

@yngvar-antonsson yngvar-antonsson changed the title [RFC] Add read-only instances to Cartridge replicaset Add read-only instances to Cartridge replicaset Aug 4, 2022
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 a pull request may close this issue.

2 participants