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
doc/rados: edit change-mon-elections #51992
doc/rados: edit change-mon-elections #51992
Conversation
You can disallow a leader by running: | ||
The modes other than ``classic`` provide extra features. We recommend staying | ||
in ``classic`` mode if you don't need these extra features because it is the | ||
simplest mode. |
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.
Suggest s/extra/specific/ so the uncareful reader is perhaps less inclined to disregard advice.
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.
I think all three of these suggestions are clear improvements. They're all accepted.
you can forget history and reset them by running: | ||
Connectivity scores are expected to remain valid. However, if during | ||
troubleshooting you determine that these scores have for some reason become | ||
invalid, forget the history and reset the scores by running a command of the |
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.
Suggest s/forget/drop/ but this is marginal.
Resetting connectivity scores carries little risk: monitors will still quickly | ||
determine whether a connection is alive or dead and trend back to the previous | ||
scores if those scores were accurate. Nevertheless, resetting scores ought to | ||
be unnecessary and it is not recommended unless requested by your support team |
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.
s/requested/advised/, again marginal.
Edit doc/rados/operations/change-mon-elections.rst. https://tracker.ceph.com/issues/58485 Co-authored-by: Anthony D'Atri <anthony.datri@gmail.com> Signed-off-by: Zac Dover <zac.dover@proton.me>
d52c56f
to
dc93181
Compare
Edit doc/rados/operations/change-mon-elections.rst.
https://tracker.ceph.com/issues/58485
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "pacific"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
Checklist
Show available Jenkins commands
jenkins retest this please
jenkins test classic perf
jenkins test crimson perf
jenkins test signed
jenkins test make check
jenkins test make check arm64
jenkins test submodules
jenkins test dashboard
jenkins test dashboard cephadm
jenkins test api
jenkins test docs
jenkins render docs
jenkins test ceph-volume all
jenkins test ceph-volume tox
jenkins test windows