On Mon, 2019-09-09 at 11:06 +0200, Ulrich Windl wrote: > Hi! > > In recent pacemaker I see that last-lrm-refresh is included in the > CIB config (crm_config/cluster_property_set), so CIBs are "different" > when they are actually the same. > > Example diff: > - <nvpair id="cib-bootstrap-options-last-lrm-refresh" > name="last-lrm-refresh" value="1566194010"/> > + <nvpair id="cib-bootstrap-options-last-lrm-refresh" > name="last-lrm-refresh" value="1567945827"/> > > I don't see a reason for having that. Can someone explain? > > Regards, > Ulrich
New transitions (re-calculation of cluster status) are triggered by changes in the CIB. last-lrm-refresh isn't really special in any way, it's just a value that can be changed arbitrarily to trigger a new transition when nothing "real" is changing. I'm not sure what would actually be setting it these days; its use has almost vanished in recent code. I think it was used more commonly for clean-ups in the past. -- Ken Gaillot <kgail...@redhat.com> _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/