Re: Interrupt fencing on Sun

From: Dan Norris <>
Date: Mon, 21 Jan 2008 05:26:11 -0800 (PST)
Message-ID: <>

Sorry I don't have any experiences to share on this one. I have installed several VCS/Sun/RAC clusters, but none as large as you mention. I presume that the size of the cluster you're working on is what led Veritas and Sun to recommend the additional CPU reservations. On smaller (2-3 node) clusters, I haven't seen any issues like what you appear to have encountered.

I'd like to add to your query and/or branch off a new thread: I'd also be interested in knowing if anyone has heard of similar suggestions with respect to Oracle Clusterware. This would certainly be one additional item to add to the Oracle Clustware (only) vs. Third Party Clusterware thread that made the rounds on this list recently.


  • Original Message ---- From: fairlie rego <> To: Oracle-L <> Sent: Monday, January 21, 2008 4:34:04 AM Subject: Interrupt fencing on Sun


  On a 8 node RAC with 128 cpus Sun and Veritas have recommended that the customer set aside 2 cpus on each node for processing network interrupts exclusively.    

  This was suggested after a situation where VCS was unable to process cluster heartbeat messages in a timely manner due to Sun attempting to process the network interrupt thread on the same CPU which was running the cluster communication thread.    

  I would like to know if any other large customers have set aside cpus exclusively to handle network interrupts and if so what percentage of total CPUs    

  Thanks much

          Fairlie Rego
Senior Oracle Consultant
  M: +61 402 792 405             

Make the switch to the world's best email. Get the new Yahoo!7 Mail now.

-- Received on Mon Jan 21 2008 - 07:26:11 CST

Original text of this message