-
Notifications
You must be signed in to change notification settings - Fork 15
Documented changed upgrade procedure design #180
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
Conversation
neunhoef
left a comment
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.
LGTM. See two (related) suggestions.
docs/upgrade_spec.md
Outdated
| upgrade failure, or `false` otherwise. | ||
| - `reason` a string that describes the state of the upgrade plan in a | ||
| human readable form. | ||
| - `servers_upgraded` an integer containing the number of servers that have |
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.
Why not put the list of upgraded instances in here?
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.
done
docs/upgrade_spec.md
Outdated
| human readable form. | ||
| - `servers_upgraded` an integer containing the number of servers that have | ||
| been upgraded. | ||
| - `servers_remaining` an integer containing the number of servers that have |
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.
Same here, sounds like useful information to me.
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.
done
|
Oh, I forgot something: The |
|
Likewise, we need to put the restarting of the starters itself in somewhere. |
1 similar comment
|
Likewise, we need to put the restarting of the starters itself in somewhere. |
|
This PR documents the changed upgrade procedure needed for 3.4 resulting in an automatic upgrade of all servers of a starter cluster with agents, then dbservers, then coordinators.