>>> Ken Gaillot <kgail...@redhat.com> schrieb am 09.09.2019 um 17:14 in Nachricht <9e51c562c74e52c3b9e5f85576210bf83144fae7.ca...@redhat.com>: > 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.
But wouldn't it be more appropriate in the status section of the CIB then? Also isn't pacemaker working with CIB digests anyway? And there is the three-number CIB versioning, too. > > 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. My guess is that a crm configure did such a change. Why I care: I'm archiving CIB configuration (but not status) changes (that is the CIBs and the diffs); so I don't like such dummy changes ;-) Regards, Ulrich _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
