Home » Server Options » RAC & Failsafe » how to prevent VIP transfer back to it's original node location (11.2.0.3.0)
|
|
|
|
|
|
|
|
|
Re: how to prevent VIP transfer back to it's original node location [message #570542 is a reply to message #570518] |
Mon, 12 November 2012 00:39   |
 |
piotrtal
Messages: 168 Registered: June 2011 Location: Poland/Czestochowa
|
Senior Member |
|
|
mkounalis wrote on Sun, 11 November 2012 23:43The VIP ip address is plumbed on another node so that the client can receive an end of channel signal, and that allows the client to fail over either by using java pool rules or by sqlnet failover. If the VIP ip isn't plumbed on another node, then the tcp/ip timeout would apply, which is usually five minutes. The listeners are only involved in setting up the sqlnet client connection - they are not involved past that. So any session existing on a server won't be effected by anything other than a service change. It is always a good idea to configure services to run on more than a single node for this reason. After a node is brought back up online, the VIP would start on that node, and a listener would then start listening on that VIP ip's address. New sessions would then start on this node. It's usually not necessary to force a session to fail back over, unless the RAC cluster is improperly sized in that their are not enough nodes or horsepower to absorb a failed node. It's always important to size a cluster and tune it to run so that each node is not at 100% capacity and is then capable of absorbing the workload of a failed node.
thanks for this answer (thanks John too). its clear now.
i know that clients could wait for TCPtimeout after VIP dissaperar (and it takes aproximetly couple of minutes), and it reconnection is done quicker if we transfer VIP to another node. but i didn't know that after VIP failover listener doen't reconfigure itself to listen on this VIP. but probably it is done intentionally, because timeout won't appear but clients receive information that there no listener on specified VIP and make connection to another one.
thanks again.
|
|
|
|
Re: how to prevent VIP transfer back to it's original node location [message #571097 is a reply to message #571091] |
Wed, 21 November 2012 01:34  |
mkounalis
Messages: 147 Registered: October 2009 Location: Dallas, TX
|
Senior Member |
|
|
Only the IP address fails over to another node - and again this is ONLY to force open sessions to get immediate notification that their sessions are now dead and to handle them however they have cofigured that situation to be handled. So, if the VIP for RAC1 moves to RAC2, nothing oracle wise is listening on that IP address, so SQLNET connections would only be accomodated b the listener running on RAC2 which is listening to the RAC2 VIP ip. Please read the RAC concepts guides located on docs.oracle.com.
|
|
|
Goto Forum:
Current Time: Wed Jul 16 03:59:59 CDT 2025
|