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
systemd: Start OSDs after MONs #13097
Conversation
Currently, we start/stop OSDs and MONs simultaneously. This may cause problems especially when we are shutting down the system. Once the mon goes down it causes a re-election and the MONs can miss the message from the OSD that is going down. Resolves: http://tracker.ceph.com/issues/18516 Signed-off-by: Boris Ranto <branto@redhat.com>
retest this please |
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.
Reviewed-by: Greg Farnum gfarnum@redhat.com
This looks good to me, but I'll leave it open to make sure we didn't bust those unit tests and in case anybody else with more systemd experience wants to comment. |
@smithfarm What do you think? Can we merge this? |
Rebased to latest master and pushed |
After it builds, will run a |
|
@smithfarm great, thanks! |
ah, nevermind, |
Tracker issue has empty backport field, so this is master-only until that changes, JFYI |
Currently, we start/stop OSDs and MONs simultaneously. This may cause
problems especially when we are shutting down the system. Once the mon
goes down it causes a re-election and the MONs can miss the message
from the OSD that is going down.
Resolves: http://tracker.ceph.com/issues/18516
Signed-off-by: Boris Ranto branto@redhat.com