Hi, I have 2 servers with a sequoia controller on each. Controllers are configured as Raidb1-waitforall.
When a server crashes, the other controller does not see the failure instantanously. If an update query is send to virtualdatabase, query is executed on the alive controller which wait for crashed controller answer. During my tests controller waited during approximately 2 minutes. 1) Is this timeout customizable ? After 2 minutes, controller store a quit group checkpoint. At this time Task (update query) did not end, then we have a checkpoint quit group with the same log_id than last request (our update query) recovery entry. 2) Is that coherent with sequoia design ? (my problem is that after a crash we resynchronize controllers to replay request after this quit group checkpoint :( ) 3) Does the Task have the status Executing on quit group checkpoint ? (it may be a solution to resolve our problem) Thanks in advance Pierre 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
