> Just for clarification, Appia exists some time ago (since 1998). The
> novelty about Appia is that it started to be distributed under the
> Apache 2.0 open source license and hosted by the continuent.org Forge
oohh... :)
> Does this happen during the dump?
> Can you turn on the DEBUG mode on hedera channel and gms and post it
> (also) to the Appia mailing list?
I will do so. Which Debug-mode do you mean? The one in the
Administration-Console? Or do you mean to enable log4j? sorry for this
stupid question ;)
> Yes, this would also help to see what is happening.
Which config-Data would be helpful for you? The one from the
virtualdatabases and from the appia-config or is the second one enough?
thx for your fast reply
Christopher
Nuno Carvalho schrieb:
Hi,
On Feb 21, 2007, at 10:50 , Christopher Hartung wrote:
In the near future we want to use sequoia as a productive solution. To
look ahead to have a "update to date" solution we plan to use Sequoia
3. When i was testing Sequoia 2 i used jgroups for group-communication
and it works fine. For version 3 we use the new implemented
appia-group-communication-protocol. The configuration of the cluster
was easy and works fine.
Just for clarification, Appia exists some time ago (since 1998). The
novelty about Appia is that it started to be distributed under the
Apache 2.0 open source license and hosted by the continuent.org Forge :-)
controllers which information is right. But if i create a dump of
"DB-Node 1" after few minutes the first Controller throw this
error/info-messages (i replaced the ip with the nicknames above):
2007-02-19 09:43:47,593 INFO continuent.hedera.gms
Member(address=/DB-Node-2:32790, uid=DB-Node-2:32790) failed in
Group(gid=xstamm)
2007-02-19 09:43:47,593 INFO continuent.hedera.gms
Member(address=/DB-Node-2:32790, uid=DB-Node-2:32790) failed in
Group(gid=xstamm)
2007-02-19 09:43:47,607 WARN controller.virtualdatabase.xstamm Unable
to find remote controller name for member
Member(address=/DB-Node-2:32790, uid=DB-Node-2:32790) in list
{Member(address=/DB-Node-1:32790, uid=DB-Node-1:32790)=DB-Node-1:1090}
2007-02-19 09:43:47,608 INFO controller.virtualdatabase.xstamm 1
requests were waiting responses from Member(address=/DB-Node-2:32790,
uid=DB-Node-2:32790)
So for my opinion the seconde DB-Node is leaving the Cluster. When the
Dump-creation is finished the DB-Node 2 isn't joinig the cluster again.
Does this happen during the dump?
Can you turn on the DEBUG mode on hedera channel and gms and post it
(also) to the Appia mailing list?
Do you know this problem? Did you know a solution? Maybe i can post my
config-data to find my problem! :)
Yes, this would also help to see what is happening.
Thanks for your feedback,
--
Nuno Carvalho
University of Lisbon, Portugal
http://dialnp.di.fc.ul.pt
------------------------------------------------------------------------
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
