PrimaryLogPG::maybe_kick_recovery: simply use CEPH_MSG_PRIO_HIGH

Not all schedulers necessarily depend on a particular strict/non-strict
cutoff.  Instead, simply shedule at CEPH_MSG_PRIO_HIGH.

See also: d346fdca06d0dc66eafcdaf281de352170bcf08c

Signed-off-by: Samuel Just <sjust@redhat.com>

diff --git a/src/osd/PrimaryLogPG.cc b/src/osd/PrimaryLogPG.cc
index 1667781b890333b9681106ed1331b7ffd080876d..ec013eb085ac45b6abd38c6472c7f759fb68546e 100644 (file)
--- a/src/osd/PrimaryLogPG.cc
+++ b/src/osd/PrimaryLogPG.cc
@@ -560,13 +560,13 @@ void PrimaryLogPG::maybe_kick_recovery(
     dout(7) << "object " << soid << " v " << v << ", recovering." << dendl;
     PGBackend::RecoveryHandle *h = pgbackend->open_recovery_op();
     if (is_missing_object(soid)) {
-      recover_missing(soid, v, osd->osd->op_prio_cutoff, h);
+      recover_missing(soid, v, CEPH_MSG_PRIO_HIGH, h);
     } else if (recovery_state.get_missing_loc().is_deleted(soid)) {
       prep_object_replica_deletes(soid, v, h, &work_started);
     } else {
       prep_object_replica_pushes(soid, v, h, &work_started);
     }
-    pgbackend->run_recovery_op(h, osd->osd->op_prio_cutoff);
+    pgbackend->run_recovery_op(h, CEPH_MSG_PRIO_HIGH);
   }
 }