Hi Pierre,
The difference is that when killed, the controller socket connections
will be closed with an error. The second controller will then notice
immediately the failure.
Upon cable unplugging, there will be no direct notification, you will
have to wait for tcp timeouts, which generally are ~15min. Note that
even upon timeout detection, the behavior won't be really clean and you
will not be able to keep on going with the cluster.
Then solution is to write a little script that will watch the network on
both controllers. Let's say you take a server or a switch as a
reference: just ping it all the time and upon failure, kill the
controller on which the script runs, it is safer. Then, when you will
plug your cable back, the remaining controller will see the error and
you will be operational again.
Hope these help,
Gilles.
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
