From: Walker, Bruce J <bruce.walker@hp...> - 2003-11-25 23:49:59
NSC certainly had multiple servers running in parallel across the
NSC clusterized not only lo but also all the physical addresses on all
the nodes. What that meant was that a wild card listen on any node was
effectively listening on all addresses on all nodes. To accomplish
this we had to do several things:
1. have a clusterwide unique port space and all requests for a port were
2. all requests to find and endpoint went thru the central registry;
The code to do all this was more invasive into the base than we thought
it was worth, at the time. Perhaps a fresh look at what it would take
and what it would buy is merited.
My guess is that CVIP doesn't just work as a means of doing a single
listen in the cluster and having processes inside the cluster connect to
you (no matter what node you are on). The reason I suspect it doesn't
work is that each node participating in LVS has the CVIP as a local ip
alias (so the LVS redirector can redirect to it and it will accept it).
Consequently if tried to connect to CVIP it would connect locally and
not find the service unless it was running locally.
This is all speculation on my part.
> -----Original Message-----
> From: ssic-linux-users-admin@...=20
> [mailto:ssic-linux-users-admin@...] On=20
> Behalf Of Watson, Brian J.
> Sent: Tuesday, November 25, 2003 12:52 PM
> To: John Hughes
> Cc: ssic-linux-users@...
> Subject: Re: [SSI-users] is "lo" (127.0.0.1) clusrerized? Can=20
> it be? Should it be?
> It used to be clusterized for NSC, but I'm not sure how=20
> useful it would=20
> be for OpenSSI. The primary use for it would be to connect to=20
> some port=20
> on "lo" and be automatically routed to the node where that server is=20
> listening. OpenSSI introduces the notion of multiple servers=20
> running in=20
> parallel across the cluster (I don't think NSC had this),=20
> which makes a=20
> clusterized "lo" ambiguous. If an Apache server is running on=20
> each node=20
> and you connect to port 80 on "lo", which server should you=20
> connect to?
> It might be useful to make CVIP work in this manner. I think OpenSSI=20
> only allows one server in the cluster to listen on a given=20
> port of the=20
> CVIP address. Therefore, any process can connect to this port of the=20
> CVIP and be automatically routed to this one server. It sounds=20
> reasonable in theory, but I don't think it's been implemented.
> My $.02,
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive? Does it
> help you create better code? SHARE THE LOVE, and help us help
> YOU! Click Here: http://sourceforge.net/donate/
> Ssic-linux-users mailing list