Hello,
I was under impression that Backup space understands that the Primary is not available, if it does not receive any signals from Primary for some time. But today we have done a test which makes me wonder...
(1) Start Primary + Backup
(2) Use UNIX command "kill -STOP " to suspend the Primary GSC process.
In the Backup GSC log there is a message "channel lost connection to source", but even after a very long time Backup has not taken over a role of Primary.
(3) Use UNIX command "kill -CONT " to resume the Primary GSC process.
Primary GSC remains primary. In the Backup GSC there is a message "channel reestablished connection to source".
On the other hand, when I really kill the Primary GSC process with the UNIX command "kill -KILL ", the Backup GSC very quickly takes the role of Primary.
My understanding is that when "kill -STOP " is executed, the affected process will not get any CPU time from the OS, so it will not be able to send anything over the network to the Backup GSC, or to respond to any requests from Backup GSC. The question is why in this case Backup GSC does not take over?
I have done this test with XAP 12.0.1 on SunOS 5.11 on x86, if this plays any role.
↧