Hi Anton,
On Dec 28, 2006, at 11:02 , Anton V. Goldberg wrote:
A scenario I had in mind looked like this:
2 controllers (2.10.3) on 2 machines
with Appia gossip servers running on each machine (so TCP).
To start with, Sequoia 2.10.3 does not include gossipServer.xml in its
distribution, while Appia seems to want it.
Appia only needs it for very special configurations. The Sequoia team
decided not to include this script file for the moment, but if
everybody starts using it, it can be included.
But if you use always 2 controllers (and always the same controllers)
and you only need failure detection, you can use the CVS distribution
and define a base view. With this you do not need the gossip server
for membership discovery and the controllers work just fine with
those controllers.
I downloaded Appia 3.2.3 and dug up
gossipServer.sh and gossipServer.xml from there.
While I was at it, I verified
the version of Appia distributed with Sequoia 2.10.3
by extracting MANIFEST.MF
from appia.jar. Manifest claimed it to be also 3.2.3, but the sizes
of appia.jar in sequoia distribution are different:
antong.desktop% ls -al appia-3.2.3-bin/appia-3.2.3.jar
-rw-r--r-- 1 antong yyyyy 480478 Oct 19 09:43
appia-3.2.3-bin/appia-3.2.3.jar
antong.desktop% ls -al 2.10.3/lib/appia.jar
-rw-r--r-- 1 antong yyyyy 479628 Dec 13 05:42
2.10.3/lib/appia.jar
Comparison of MANIFEST.MFs:
antong.desktop% diff ./META-INF/MANIFEST.MF
./appia-3.2.3-bin/META-INF/MANIFEST.MF
3c3
< Created-By: 1.4.2_12-b03 (Sun Microsystems Inc.)
---
Created-By: 1.5.0_06-64 ("Apple Computer, Inc.")
Fun!
Hum... yes, I use a MAC :) Is it giving problems to Sequoia? Please
tell me if you see some strange behavior related to this particular
issue.
Then I tried to start gossip servers, as it was advertized
in Sequoia and Appia documentation:
$SEQUOIA_HOME/bin/gossipServer.sh -gossips x.x.x.140,y.y.y.144
Naturally, that doesn't work. GossipServer complains about
"invalid argument" "gossips", the reasons for
which become clear after a look into source code.
Switch "gossip" (notice the lack of "s" at the end)
went through all right and
GossipServer started both client and server.
I configured virtual databases on both machines
(through appia.xml) to connect
to local gossip server via <gossip> element. That possibly worked, but
controllers didn't see each other.
I could not make it work with 2 gossip servers, so I ended
up starting just 1
gossip server with "-solo" switch and
pointing both appia.xml to that ip address.
That is not I really wanted, but it works. Now I
wonder if anybody on the list
would know where's the best place to describe the situation and ask:
1.For myself: an advice on making 2 gossip servers work together.
The gossip server is replicated using also group communication. So,
it creates a group of gossips. To create that group, d the following:
- Start the first gossip server on host A
- Start the second gossip server on host B with the flag -gossip A
- Start more gossip servers with the flag -gossip pointing to an
existing gossip server.
They will all join and make gossip of membership discovery requests
through the gossip group.
Then, start the controllers, with the gossip configurated to the one
that is running in the local machine.
Note: it's better if you use always ip addresses (not localhost or
127.0.0.1) in all configurations.
2.For other people: fixes to the code and documentation.
The documentation is maintained by the sequoia people. I'm sure that
they pay attention to the list and this will be fixed in the next
releases.
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
