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
mon: add MMonHealth back #20528
mon: add MMonHealth back #20528
Conversation
The failure seems real:-) |
27a65d1
to
be74d66
Compare
Just to confirm, the objective here is to gracefully simply drop MMonHealth messages during the upgrade path from before-mimic to mimic, right? |
src/mon/HealthMonitor.cc
Outdated
@@ -159,6 +160,10 @@ bool HealthMonitor::prepare_update(MonOpRequestRef op) | |||
dout(7) << "prepare_update " << *m | |||
<< " from " << m->get_orig_source_inst() << dendl; | |||
switch (m->get_type()) { | |||
case MSG_MON_HEALTH: |
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.
you'll also need to handle the message in Monitor::dispatch_op()
, to redirect it to the HealthMonitor.
@jecluis exactly. |
This partially reverts commit 7b4a741. we need to at least decode MMonHealth sent from luminous monitors in mimic. and in luminous, we could drop the support of this message, if we can only upgrade from mimic. Fixes: http://tracker.ceph.com/issues/22462 Signed-off-by: Kefu Chai <kchai@redhat.com>
@jecluis fixed and repushed. the message is now dropped in |
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
This partially reverts commit 7b4a741.
we need to at least decode MMonHealth sent from luminous monitors in
mimic. and in luminous, we could drop the support of this message, if we
can only upgrade from mimic.
Fixes: http://tracker.ceph.com/issues/22462
Signed-off-by: Kefu Chai kchai@redhat.com