crimson/osd/osd: handle_scrub_message on any core

Matan-B · Matan-B · commit cbad3e4517e9 · 2024-03-10T12:16:54.000Z
After enabling multicore cluster messenger, there is no
guarantee which core will handle the request.
See: OSDSingletonState::send_to_osd()

Signed-off-by: Matan Breizman &lt;mbreizma@redhat.com&gt;
diff --git a/src/crimson/osd/osd.cc b/src/crimson/osd/osd.cc
@@ -1268,7 +1268,6 @@ seastar::future<> OSD::handle_scrub_message(
   crimson::net::ConnectionRef conn,
   Ref<MOSDFastDispatchOp> m)
 {
-  ceph_assert(seastar::this_shard_id() == PRIMARY_CORE);
   return pg_shard_manager.start_pg_operation<
     crimson::osd::ScrubMessage
     >(m, conn, m->get_min_epoch(), m->get_spg()).second;

Original file line number	Diff line number	Diff line change
`@@ -1268,7 +1268,6 @@ seastar::future<> OSD::handle_scrub_message(`
`1268`	`1268`	`crimson::net::ConnectionRef conn,`
`1269`	`1269`	`Ref<MOSDFastDispatchOp> m)`
`1270`	`1270`	`{`
`1271`		`- ceph_assert(seastar::this_shard_id() == PRIMARY_CORE);`
`1272`	`1271`	`return pg_shard_manager.start_pg_operation<`
`1273`	`1272`	`crimson::osd::ScrubMessage`
`1274`	`1273`	`>(m, conn, m->get_min_epoch(), m->get_spg()).second;`