Re: Configuring failover time with Red Hat Cluster

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I forgot to paste the URL, sorry!

http://people.redhat.com/ccaulfie/docs/CmanYinYang.pdf

Chrissie

On 05/07/11 14:20, Christine Caulfield wrote:
Hiya,

I don't have the URL to have but I'm pretty sure there's something in
the Red Hat knowledge base about calculating failover times. You'll need
to have paid support to get at it.

Failing that here's a document I wrote that talks about configuring the
insider bits of openais and cman. "man 5 openais.conf" is also helpful.

I hope this helps :-)

Chrissie

On 05/07/11 13:43, Parvez Shaikh wrote:
Hello Christine,

Thanks for the link enlisting various documents, I have RHC running over
RHEL 5.5 and has been working fine. However I would greatly appreciate,
some document or pointers which help me in estimate failover time or
adjust it; if that is possible.

I have been through Administration Guide and could not find how I can
adjust it.

Thanks,
Parvez

On Tue, Jul 5, 2011 at 5:58 PM, Christine Caulfield <ccaulfie@xxxxxxxxxx
<mailto:ccaulfie@xxxxxxxxxx>> wrote:

That's a *very* old document. it's from 2003 and refers to RHEL2.1
.. which I sincerely hope you weren't planning to implement.

Before you do anything more I recommend you read the documentation
for the actual version of clustering you are going to install

https://access.redhat.com/__knowledge/docs/Red_Hat___Enterprise_Linux/
<https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_Linux/>

Chrissie


On 05/07/11 12:32, Parvez Shaikh wrote:

Hi all,

I was trying to find out how much time does it take for RHCS to
detect
failure and recover from it. I found the link -
http://www.redhat.com/__whitepapers/rha/RHA___ClusterSuiteWPPDF.pdf
<http://www.redhat.com/whitepapers/rha/RHA_ClusterSuiteWPPDF.pdf>

It says that network polling interval is 2 seconds and 6 retries are
attempted before declaring a node as failed. I want to know can
we tune
this or configure it, say instead of 6 retries I want only 3
retries.
Also reducing network polling time from 2 seconds to say 1
second (can
it be less than 1 second, which I think would consume more CPU)?

Also I have a script resource and I see it invoked with status
argument
after every 30 seconds, can we configure that as well?

Failover also involve fencing, any pointers on how can we control /
configure fencing time would also be useful,I use bladecenter
fencing,
IPMI fencing as well as UCS fencing.

Thanks,
Parvez



--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx <mailto:Linux-cluster@xxxxxxxxxx>
https://www.redhat.com/__mailman/listinfo/linux-cluster
<https://www.redhat.com/mailman/listinfo/linux-cluster>


--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx <mailto:Linux-cluster@xxxxxxxxxx>
https://www.redhat.com/__mailman/listinfo/linux-cluster
<https://www.redhat.com/mailman/listinfo/linux-cluster>




--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster


[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux