In pacemaker 1.1.7-6 with corosync 1.4.1-7 update of attributes works almost online.
Used with SysInfo resource agent and manual commands like "attrd_updater -U 4 -n test".
In the logfile there is one line
attrd[...] notice: attrd_trigger_update: Sending flush up to all hosts for: ...
and a few milliseconds later
attrd[...] notice: attrd_perform_update: Sent update ...
with the same content.
After upgrade to version 1.1.8-6 there is always nearly exact one second between trigger and perform.
2013-04-11T22:51:55.389+02:00 int2node2 attrd[28370] notice: notice: attrd_trigger_update: Sending flush op to all hosts for: text (81)
2013-04-11T22:51:56.397+02:00 int2node2 attrd[28370] notice: notice: attrd_perform_update: Sent update 5814: text=81
2013-04-11T22:51:56.397+02:00 int2node2 attrd[28370] notice: notice: attrd_perform_update: Sent update 5814: text=81
And what i found out having several updates running, they have a single queue.
All attrd_updater processes are waiting for the next to be finished, so there cant be more than one update per second any more.
Has this something to do with
attrd: Have single-shot clients wait for an ack before disconnecting
stated in the Changelog for 1.1.8 ?
If yes, is it intended to have a single queue ?
And is this 1 second fixed ?
From where does this 1 second come, i dont think that it takes one second to get the ack.
This can run into heavy delays (and therefore timeouts) for monitor functions of RA performing attribute updates.
Rainer
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
