<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>In pacemaker 1.1.7-6 with corosync 1.4.1-7 update of attributes works almost online.</div>
<div>Used with SysInfo resource agent and manual commands like "attrd_updater -U 4 -n test".</div>
<div> </div>
<div>In the logfile there is one line</div>
<div>attrd[...] notice: attrd_trigger_update: Sending flush up to all hosts for: ...</div>
<div>and a few milliseconds later</div>
<div>attrd[...] notice: attrd_perform_update: Sent update ...</div>
<div>with the same content.</div>
<div> </div>
<div>After upgrade to version 1.1.8-6 there is always nearly exact one second between trigger and perform.</div>
<div>
<div>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)<br/>
2013-04-11T22:51:56.397+02:00 int2node2 attrd[28370] notice: notice: attrd_perform_update: Sent update 5814: text=81</div>
<div> </div>
<div>And what i found out having several updates running, they have a single queue.</div>
<div>All attrd_updater processes are waiting for the next to be finished, so there cant be more than one update per second any more.</div>
<div> </div>
<div>Has this something to do with</div>
<div>attrd: Have single-shot clients wait for an ack before disconnecting</div>
<div>stated in the Changelog for 1.1.8 ?</div>
<div> </div>
<div>If yes, is it intended to have a single queue ?</div>
<div>And is this 1 second fixed ?</div>
<div>From where does this 1 second come, i dont think that it takes one second to get the ack.</div>
<div> </div>
<div>This can run into heavy delays (and therefore timeouts) for monitor functions of RA performing attribute updates.</div>
<div> </div>
<div>Rainer</div>
</div></div></body></html>