crimson/common: apply config changes also on shard.0

Signed-off-by: Yingxin <yingxin.cheng@intel.com>

diff --git a/src/crimson/common/config_proxy.h b/src/crimson/common/config_proxy.h
index 807ca958d5e39b3c0390bf16c62f4230ef2d9ea2..a6016fc10ffcae953341ab8e6eba49e47074e746 100644 (file)
--- a/src/crimson/common/config_proxy.h
+++ b/src/crimson/common/config_proxy.h
@@ -48,6 +48,8 @@ class ConfigProxy : public seastar::peering_sharded_service<ConfigProxy>
       // always apply the new settings synchronously on the owner shard, to
       // avoid racings with other do_change() calls in parallel.
       owner.values.reset(new_values);
+      owner.obs_mgr.apply_changes(owner.values->changed,
+                                  owner, nullptr);
 
       return seastar::parallel_for_each(boost::irange(1u, seastar::smp::count),
                                         [&owner, new_values] (auto cpu) {