|
Ben Hollingsworth wrote on 4/26/06 11:25 AM:
Subhankar Sengupta wrote:
Active/Active needs concurrent access to the storage device.
Bottleneck of the extended file system is that it does not allow this
type of concurrent access so global file system comes into picture.
You have to configure the shared storage with global file system and
then
you should configure your heartbeat software.
The requirement for shared storage depends entirely on the application
you're clustering. For example, the real servers in a web proxy cluster
are completely autonomous, so no shared storage is necessary.
Red Hat replaced Piranha with Cluster Suite some time ago, as far as I
can tell. I'm just wondering what the differences are between Cluster
Suite and generic LVS so I can decide which route we want to take.
Piranha is still used, but it's only a GUI for managing the config. The
nuts and bolts are still LVS with ipvsadm, and it uses a program called
"pulse" to run the heartbeat services, and "nanny" for node monitoring.
The "Red Hat Cluster Suite" is a conglomeration of services which gets
you both LVS and HA. There's no requirement to use both at once, but
you need to get the cluster suite in order to get Red Hat's supported
LVS packages.
We use Red Hat's LVS in production on two separate clusters which
between them run about 12 different virtual IPs across about 30 back-end
servers at two colo facilities. I can't really tell you much about the
differences between it and a generic LVS though, as I've never seen the
generic version.
--
Dave Miller http://www.justdave.net/
System Administrator, Mozilla Corporation http://www.mozilla.com/
Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/
|
