crimson/osd: Reduce no crimson_cpu_set usage to info

Using a cpu set is yet to prove a distinct impact.
As first time users are likely to use the non cpu_set variant,
let's try to avoid "scary" warnings.

Signed-off-by: Matan Breizman <mbreizma@redhat.com>

diff --git a/src/crimson/osd/osd.cc b/src/crimson/osd/osd.cc
index e368183442c66834e8b402211fbedd9234d0cc3c..f027fba28d07d66452a82fc0e1929df1fc32baac 100644 (file)
--- a/src/crimson/osd/osd.cc
+++ b/src/crimson/osd/osd.cc
@@ -447,7 +447,7 @@ seastar::future<> OSD::start()
   if (auto cpu_cores =
         local_conf().get_val<std::string>("crimson_cpu_set");
       cpu_cores.empty()) {
-    clog->warn() << "for optimal performance please set crimson_cpu_set";
+    clog->info() << "for optimal performance please set crimson_cpu_set";
   }
   startup_time = ceph::mono_clock::now();
   ceph_assert(seastar::this_shard_id() == PRIMARY_CORE);