Propagation of config (filesystems, nodes) to a slave manager

Having removed filesystems and a node from the master manager (and having the config in quarkdb), I am surprised that it does not seem to propagate to a slave manager… Is there something to do for that or just wait ?
Thanks JM (EOS version 4.8.40)

Hi JM,

This part of the configuration is not necessarily kept in sync between the master and the slaves as the entire configuration will be reloaded from QDB once a slave is promoted to a master. I believe in some of the newer version this has been improved and things are in sync but we don’t necessarily aim for that.


Thanks Elvin, I decided to simply restart the eos services on he slave manager and it worked.