Hello Celso,<br><br>Well, your suggestion might be the solution to the problem, but since I think its a quorum latency problem, would the parameters "cludb -p clumemb%rtp 50" and "cludb -p cluquorumd%rtp 50" help on this this issue?
<br>I was digging into the Cluster Suite documentation and I found these parameters. <br>Would those help on this issue without changing the heartbeat method?<br><br>Also take a look in this Kbase bellow, it has some interesting tunning parameters for Red Hat's Clsuter Suite v3:
<br><a href="http://kbase.redhat.com/faq/FAQ_79_7722.shtm">http://kbase.redhat.com/faq/FAQ_79_7722.shtm</a><br><br>Regards,<br>Filipe Miranda<br><br><br><div><span class="gmail_quote">On 9/7/06, <b class="gmail_sendername">
Celso K. Webber</b> <<a href="mailto:celso@webbertek.com.br">celso@webbertek.com.br</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Filipe!<br><br>I think your case is a little bit different from Jordi's case, since you<br>are using Cluster Suite v3 and he is using v4.<br><br> From my own experience, under CSv3 I had this kind o problem when using<br>
high latency quorum devices. So I had to change from disk tiebraker to<br>network tiebraker. I imagine you're using disk tiebraker, aren't you?<br><br>Please, would someone please confirm that Filipe's case could be solved
<br>by changing the heartbeat method? It worked for me in the past, but I'm<br>not pretty sure that this was the actual solution.<br><br>Thanks,<br><br>Celso.<br><br>Filipe Miranda escreveu:<br>> Hi there,<br>><br>> I'm having the same problem!
<br>> I'm using RHEL3.8 for Itanium and RedHat Cluster Suite U8. The cluster<br>> is composed of 2 HP 4CPUs servers and we are using an EMC ClarionCX700<br>> to hold the quorum partitions and data partitions.<br>
> One more thing that I noticed, eventhough the members are shown ative on<br>> both nodes, any action on the node that shows the active service does<br>> not get propagated to the other member.<br>><br>> I already checked the configuration of the rawdevices, and I also used
<br>> the shutil utility and it reported no problems with the quorum partitions.<br>><br>> Does anybody have any suggestions?<br>><br>> Thank you,<br>><br>><br>> On 9/2/06, *Jordi Prats Català* <
<a href="mailto:jprats@cesca.es">jprats@cesca.es</a><br>> <mailto:<a href="mailto:jprats@cesca.es">jprats@cesca.es</a>> > wrote:<br>><br>> Hi,<br>> I'm getting different outputs of clustat utility on each node:
<br>><br>> node1:<br>> # clustat<br>> Member Status: Quorate<br>><br>> Member Name Status<br>> ------ ---- ------<br>> node1 Online, Local, rgmanager
<br>> node2 Online, rgmanager<br>><br>> Service Name Owner (Last) State<br>> ------- ---- ----- ------ -----
<br>> ptoheczas node2 started<br>> xoqil node2 started<br>> ymsgh node1 started
<br>> vofcvhas node2 started<br>><br>> node2:<br>> # clustat<br>> Member Status: Quorate<br>><br>> Member Name Status
<br>> ------ ---- ------<br>> node1 Online, rgmanager<br>> node2 Online, Local, rgmanager<br>>
<br>><br>> (disappears service's info)<br>><br>> Rebooting disapears this problem (displays same info in both nodes) for<br>> a few weeks. After that it appears again.<br>><br>> Do you know what's going on?
<br>><br>> Thanks,<br>><br>> --<br>> ......................................................................<br>> __<br>> / / Jordi Prats Català<br>> C E / S / C A Departament de Sistemes
<br>> /_/ Centre de Supercomputació de Catalunya<br>><br>> Gran Capità, 2-4 (Edifici Nexus) · 08034 Barcelona<br>> T. 93 205 6464 · F. 93 205 6979 · <a href="mailto:jprats@cesca.es">
jprats@cesca.es</a><br>> <mailto:<a href="mailto:jprats@cesca.es">jprats@cesca.es</a>><br>> ......................................................................<br>><br>> --<br>> Linux-cluster mailing list
<br>> <a href="mailto:Linux-cluster@redhat.com">Linux-cluster@redhat.com</a> <mailto:<a href="mailto:Linux-cluster@redhat.com">Linux-cluster@redhat.com</a>><br>> <a href="https://www.redhat.com/mailman/listinfo/linux-cluster">
https://www.redhat.com/mailman/listinfo/linux-cluster</a><br>> <<a href="https://www.redhat.com/mailman/listinfo/linux-cluster">https://www.redhat.com/mailman/listinfo/linux-cluster</a>><br>><br>><br>>
<br>><br>> --<br>> Esta mensagem foi verificada pelo sistema de antivírus e<br>> acredita-se estar livre de perigo.<br>><br>><br>> ------------------------------------------------------------------------
<br>><br>> --<br>> Linux-cluster mailing list<br>> <a href="mailto:Linux-cluster@redhat.com">Linux-cluster@redhat.com</a><br>> <a href="https://www.redhat.com/mailman/listinfo/linux-cluster">https://www.redhat.com/mailman/listinfo/linux-cluster
</a><br><br>--<br>*Celso Kopp Webber*<br><br><a href="mailto:celso@webbertek.com.br">celso@webbertek.com.br</a> <mailto:<a href="mailto:celso@webbertek.com.br">celso@webbertek.com.br</a>><br><br>*Webbertek - Opensource Knowledge*
<br>(41) 8813-1919<br>(41) 3284-3035<br><br><br>--<br>Esta mensagem foi verificada pelo sistema de antivírus e<br> acredita-se estar livre de perigo.<br><br>--<br>Linux-cluster mailing list<br><a href="mailto:Linux-cluster@redhat.com">
Linux-cluster@redhat.com</a><br><a href="https://www.redhat.com/mailman/listinfo/linux-cluster">https://www.redhat.com/mailman/listinfo/linux-cluster</a><br></blockquote></div><br><br clear="all"><br>-- <br>---<br>Filipe T Miranda
<br>Red Hat Certified Engineer