Sylvain,
I wonder how to correctly use the WaitForCompletion settings. We're
running a dual controller setup with the following :
<LoadBalancer>
<RAIDb-1>
<WaitForCompletion policy="all"/>
<RAIDb-1-LeastPendingRequestsFirst/>
</RAIDb-1>
</LoadBalancer>
We understood from previous posts that this was the only supported
algorythm. But, with this setup, when I crash a controller (kill -9 or
power down), I have *all* of my requests locked. Is this the expected
behavior ?
WaitForCompletion is only for the query completion locally to a
controller but has no effect on cross-controller completion.
The fact that your queries are hanging on one controller is due to your
group communication settings that do not properly detect the other
controller failure. The controller will wait until the group
communication either reports a timeout or a failure. Otherwise your
settings are correct.
Hope this helps,
Emmanuel
--
Emmanuel Cecchet
Chief Scientific Officer, Continuent
Blog: http://emanux.blogspot.com/
Open source: http://www.continuent.org
Corporate: http://www.continuent.com
Skype: emmanuel_cecchet
Cell: +33 687 342 685
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
