Hi,
It seems that after recent commit which introduces staggered probes
running 'crm_resource --cleanup' (without --resource) leads to cluster
to finish recheck too long after cleanup was done. What I see: cluster
fires probes for the first batch of resources, receives their status,
writes it to CIB, and then sleep until cluster-recheck-interval lapses.
After that next batch is reprobed and so on.
This looks like a regression to me.
Should I file bug for that or that can be fixed quite fast? IMHO this is
major enough to be fixed in 1.1.15.
Best,
Vladislav
_______________________________________________
Users mailing list: [email protected]
http://clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
