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

Document PC recovery feature #65

Closed
temeo opened this issue Jun 17, 2014 · 1 comment
Closed

Document PC recovery feature #65

temeo opened this issue Jun 17, 2014 · 1 comment
Assignees
Milestone

Comments

@temeo
Copy link
Contributor

temeo commented Jun 17, 2014

3.x branch has a new wsrep provider option pc.recovery (boolean). If the value for this parameter is set to true, primary component state is stored to disk and recovered from there when node is started.

Primary component is recovered automatically when all of the nodes that were present in the last known primary component have established communication between each other.

This feature solves two use cases:

  • Automatic recovery from full cluster crash (for example full data center power outage)
  • Graceful full cluster restart without the need for bootstrapping new primary component explicitly

Known limitations:

  • If the wsrep position differs between nodes during the recovery, full SST is required
  • ...
@temeo temeo added this to the 3.6 milestone Jun 17, 2014
kennethpjdyer added a commit that referenced this issue Jun 20, 2014
kennethpjdyer added a commit that referenced this issue Sep 2, 2014
…tations and the header page. Page added to admin guide documenting the pc.recovery feature.
@temeo
Copy link
Contributor Author

temeo commented Sep 20, 2014

Documentation and open issues moved to https://github.com/codership/documentation/.

@temeo temeo closed this as completed Sep 20, 2014
janlindstrom pushed a commit to MariaDB/galera that referenced this issue Oct 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants