Hello Friends,

Here with one more topic on.

Fencing Basics - Node Eviction in Oracle RAC || Real Application Cluster:
=============================================================
Why are nodes evicted?
• Evicting (fencing) nodes is a preventive measure (it’s a good thing)!
• Nodes are evicted to prevent consequences of a split brain:
– Shared data must not be written by independently operating nodes
– The easiest way to prevent this is to forcibly remove a node from the cluster

How are nodes evicted? – STONITH
EXAMPLE: Network heartbeat failure
What happens, if CSSD is stuck?
How can nodes be evicted?
EXAMPLE: IPMI based eviction on heartbeat failure
Which node gets evicted?
Cluster members can escalate a kill request
Re-Bootless Node Fencing
EXCEPTIONS
• With Oracle Clusterware 11.2.0.2, re-boots will be seen less, unless…:
– IF the check for a successful kill of the IO processes fails → reboot
– IF CSSD gets killed during the operation → reboot
– IF cssdmonitor (oprocd replacement) is not scheduled → reboot
– IF the stack cannot be shutdown in “short_disk_timeout”-seconds → reboot

#Fencing #NodeEviction #exadata #oracle #oracledatabase #oracledba #rac #database #databaseadministration #databases


Please do follow me and support me on,

LinkedIn: https://www.linkedin.com/in/mallik034
YouTube: https://www.youtube.com/c/mallik034
Fakebook: https://www.facebook.com/mallik034
Blog: https://mallik034.blogspot.com
twitter: https://twitter.com/mallik034
Instagram: https://www.instagram.com/mallik034
FBPage: https://www.facebook.com/mallik034oracledba
Skype: malluramadurg


Regards,
Mallikarjun Ramadurg
Mobile: +966 543796525
WhatsApp: +91 9880616848
Email: [email protected]
LinkedIn: https://www.linkedin.com/in/mallik034
YouTube: https://www.youtube.com/c/mallik034
Fakebook: https://www.facebook.com/mallik034
Blog: https://mallik034.blogspot.com