Thanks,
When I turn off JGroups debug logs, it looks like both controllers try to
exchange a message and then just hang (if I kill one of them, the other one
will detect it resume action - i.e. go to "listening mode" - sorry my wording
is not accurate). You can see this in the attached logs.
I also tried to swich to appia. Both controllers wait in "ready, listening to
requests" mode. They do not reach the "Checking virtual database configuration"
stage. So I guess they do not see each other.
For both JGroups and Appia, I used the default config files provided with
Sequoia 2.10.2. From the docs, I had gotten the idea that they were good to
use. Did I miss something? Are some settings to be changed?
Thank you in advance,
Lionel
----- Message d'origine ----
De : Nuno Carvalho <[EMAIL PROTECTED]>
À : Sequoia general mailing list <[email protected]>
Envoyé le : Lundi, 11 Décembre 2006, 16h10mn 02s
Objet : Re: [Sequoia] Controllers caught in a loop when "Checking virtual
database configuration" from each other
Hi,
it seems that jgroups is sending messages, but they are not delivered to hedera
in the other controller.
It is not exactly a loop, it is just jgroups exchanging control messages. You
could turn off the jgroups debug and see if hedera is able to exchange
messages. Did you tried using Appia?
Cheers,
nuno
On Dec 11, 2006, at 2:49 , Lionel Capiez wrote:
Hi all,
I have a config with 2 controllers hosting 1 virtual database, set in RAIDb-1
with two backends - one on each controller.
When I start both controllers (#2 is started once #1 is "ready, listening to
requests"), they manage to "see" each other but they get caught in a loop when
"Checking virtual database configuration" from each other.
I read of a similar issue in the list, but with no definite answer:
https://forge.continuent.org/pipermail/sequoia/2006-April/001671.html
I attached an excerpt from the logs from the point where both clusters check
the vdb config until the logs showed the pattern of a loop.
controller #1 is 192.168.137.91 (full_cluster_91.log)
controller #2 is 192.168.137.161 (full_cluster_161.log)
Do you have an idea of what may be going on?
Thank you in advance,
Lionel
Découvrez une nouvelle façon d'obtenir des réponses à toutes
vos questions ! Profitez des connaissances, des opinions et des expériences des
internautes sur Yahoo! Questions/Réponses.<full_cluster_91.log>
<full_cluster_161.log>
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
--
Nuno Carvalho
University of Lisbon, Portugal
http://dialnp.di.fc.ul.pt
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
___________________________________________________________________________
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur
Yahoo! Questions/Réponses
http://fr.answers.yahoo.com_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
