Hi Pierre,
Which group communications are you using and how is it configured?
These two cases are at the opposite ends of network failures. For
example, when using TCP/IP you get the following failure semantics:
1.) Process crash. Network listener goes away and TCP/IP stack
reports a broken connection back to all client. This occurs close to
instantaneously.
2.) Network link down. In this case there is nobody at the other
end. TCP/IP will keep retrying until it times out, which depending
on network settings can be a long time. Strangely enough the
easiest failure to simulate turns out to be among the harder ones to
handle effectively.
Cheers, Robert
Robert Hodges, CTO, Continuent, Inc.
Email: [EMAIL PROTECTED]
Mobile: +1-510-501-3728 Skype: hodgesrm
On Sep 4, 2007, at 10:20 AM, BESSON-DEBLON, Pierre ((SOGETI HIGH
TECH)) wrote:
Hi,
I have 2 controllers, each on different server. Set to RAIDb1 like
that
<RequestManager>
<RequestScheduler>
<RAIDb-1Scheduler level="passThrough"/>
</RequestScheduler>
<LoadBalancer>
<RAIDb-1>
<WaitForCompletion policy="all"/>
<RAIDb-1-LeastPendingRequestsFirst/>
</RAIDb-1>
</LoadBalancer>
1) When a controller crash (ctrl+C), the other one detect this
failure.
2) But when I unplugged network between the two servers, no detection.
On that moment, SQL updates don't answer, my software wait
indefinitely request end. The first controller did the job but
apparently wait for second controller reply...
I don't understand where the difference is between the two case.
Does anyone have a beginning (and maybe an end :) ) of explanation ?
Thanks in advance
Pierre Besson-Deblon
This e-mail is intended only for the above addressee. It may
contain privileged information.
If you are not the addressee you must not copy, distribute,
disclose or use any of the information in it.
If you have received it in error please delete it and immediately
notify the sender.
Security Notice: all e-mail, sent to or from this address, may be
accessed by someone other than the recipient, for system management
and security reasons. This access is controlled under Regulation of
security reasons.
This access is controlled under Regulation of Investigatory Powers
Act 2000, Lawful Business Practises.
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
