Documentation Suggestion: Add further clarification to pc.recovery option
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.5 |
Invalid
|
Undecided
|
Unassigned | |||
5.6 |
Confirmed
|
Low
|
Alexey Zhebel |
Bug Description
Documentation Suggestion: Add further clarification to pc.recovery option
The variable, pc.recovery, is defined here:
https:/
And it says:
"When this variable is set to true the node stores the Primary Component state to disk. The Primary Component can then recover automatically when all nodes that were part of the last saved state re-establish communications with each other. This feature allows automatic recovery from full cluster crashes, such as in the case of a data center power outage and graceful full cluster restarts without the need for explicitly bootstrapping a new Primary Component."
I would like to ask if further clarification could be added to denote the cluster must have already been started (and bootstrapped) initially. The last sentence, if examined on its own, could lead one to believe that bootstrapping is not necessary when initially starting the cluster (and that you must have had a valid cluster started at one point). I also think it would help to explicitly state a gwvstate.dat file must exist as well, if this is to work as expected (assuming that is a correct statement).
Thank you.
affects: | percona-server → percona-xtradb-cluster |
I think the documentation is pretty clear but assumes the knowledge what a Primary Component is and how it's achieved in the first place. /www.percona. com/doc/ percona- xtradb- cluster/ 5.6/manual/ bootstrap. html) and to the gvwstate.dat file description in https:/ /www.percona. com/doc/ percona- xtradb- cluster/ 5.6/wsrep- files-index. html
I think that indeed we should mention and link to boostrapping (https:/