RE: Oracle clusterware related question
- From: D'Hooge Freek <Freek.DHooge@xxxxxxxxx>
- To: "martin.a.berger@xxxxxxxxx" <martin.a.berger@xxxxxxxxx>, "Amir.Hameed@xxxxxxxxx" <Amir.Hameed@xxxxxxxxx>
- Date: Tue, 8 May 2012 20:23:10 +0200
Martin,
With 11.2 that is no longer true.
When you have configured a system management board (eg ILO, DRAC, ELOM, ...)
with the clusterware, a node has the possibility to kill a non responsive node
by switching of the power.
Kind regards
Freek D'Hooge
Uptime
Oracle Database Administrator
email: freek.dhooge@xxxxxxxxx
tel +32(0)3 451 23 82
http://www.uptime.be
disclaimer: www.uptime.be/disclaimer
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Martin Berger
Sent: dinsdag 8 mei 2012 20:03
To: Amir.Hameed@xxxxxxxxx
Cc: tim@xxxxxxxxx; Mathias.Zarick@xxxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: Re: Oracle clusterware related question
Amir,
in Oracle Clusterware no node can be evicted by the remote nodes.
The 'others' can only exclude any node and hope this one commits suicide.
The problem here, on your hanging node the clusterware processes are
hanging in IO to logfiles. As your NFS does not disappear, the
filehandles are still open. It seems writing to logfiles is a
synchronous task - so when these hang in file-IO, they can not do
higher priority tasks as killing the node.
You can try to mount your log-directories 'soft' - maybe this solves
the hanging issue. But I don't know which side-effects this might
cause!
I am not sure if crs shows the same behavior in case logfile write
hangs (as on NFS) or log file write fails (as on "mountpoints
disappears as SAN-nwtwork is removed") - Mathias, do you remember the
details? But as they where back in 11.2.0.1, I probably should do the
testcase again.
I second Mathias, grid-logs (and also grid-binaries) should be local!
All others, like rdbms binaries and logs can be on any remote system.
hth
Martin
--
//www.freelists.org/webpage/oracle-l
Other related posts:
