From c9448bc3c3acad2482bba2256fa35cbb4d7dd3f0 Mon Sep 17 00:00:00 2001 From: Sage Weil Date: Sun, 27 May 2018 09:55:04 -0500 Subject: [PATCH] mon/OSDMonitor: no_reply on MOSDFailure ops we eventually process Failure ops get attached to the failure report. Once we finally process them, mark them no_reply so that the forwarding mon will know about it. The other paths through prepare_failure() do no_reply on the messages that don't get logged in the failure_info_t::reporters. Fixes: http://tracker.ceph.com/issues/24322 Signed-off-by: Sage Weil (cherry picked from commit f6128e5b53cc8a6e1e97a66794806299c5190d3c) --- src/mon/OSDMonitor.cc | 1 + 1 file changed, 1 insertion(+) diff --git a/src/mon/OSDMonitor.cc b/src/mon/OSDMonitor.cc index c415c8ae70f9c..1f90bc97dccba 100644 --- a/src/mon/OSDMonitor.cc +++ b/src/mon/OSDMonitor.cc @@ -2561,6 +2561,7 @@ void OSDMonitor::process_failures() o->mark_event(__func__); MOSDFailure *m = o->get_req(); send_latest(o, m->get_epoch()); + mon->no_reply(o); } ls.pop_front(); } -- 2.39.5