[Linux-cluster] Networking guidelines for RHCS across datacenters

[brem belguebli]

2009/6/5, Jon Schulz <jschulz at soapstonenetworks.com>:
>
> Yes I would be interested to see what products you are currently using to
> achieve this. In my proposed setup we are actually completely database
> transaction driven. The problem is the people higher up want active database
> <-> database replication which will be problematic I know.


Still we also use DB (Oracle, Sybase) replication mechanisms to address
accidental data corruption, as mirroring being synchonous, if something
happens (someone intentionnaly alters the DB or filesystem corruption) it
will be on both legs of the mirror.



Outside of the data side of the equation, how tolerant is the cluster
> network/heartbeat to latency assuming no packet loss? Or more to the point,
> at what point does everyone in their past experience see the heartbeat
> network become unreliable, latency wise. E.g. anything over 30ms?
>
> Most of my experiences with rhcs and linux-ha have always been with the
> cluster network being within the same LAN :(


It is definitely the best solution in case you cannot rely on your network
infrastructure. This is not completely my case :-)


-----Original Message-----
> From: linux-cluster-bounces at redhat.com [mailto:
> linux-cluster-bounces at redhat.com] On Behalf Of Fajar A. Nugraha
> Sent: Friday, June 05, 2009 5:47 AM
> To: linux clustering
> Subject: Re: [Linux-cluster] Networking guidelines for RHCS across
> datacenters
>
> On Fri, Jun 5, 2009 at 4:22 PM, brem belguebli<brem.belguebli at gmail.com>
> wrote:
> > We are in the same setup, already doing "Geo-cluster" with other technos
> and
> > we are looking at RHCS to provide us the same service level.
>
> Usually the concepts are the same. What solution are you using? How
> does it work, replication or real cluster?
>
> > Let's consider this kind of setup, 2 datacenters far from each other by 1
> ms
> > delay, each hosting a SAN array, each of them connected to 2 SAN fabrics
> > extended between the 2 sites.
> >
> > What reason would prevent us from building Geo-clusters without having to
> > rely on a database replication mechanism, as the setup I would like to
> > implement would also be used to provide NFS services that are disaster
> > recovery proof.
> >
> > Obviously, such setup should rely on LVM mirroring to allow a node
> hosting a
> > service to be able to write to both local and distant SAN LUN's.
>
> Does LVM mirroring work with clustered LVM?
>
> --
> Fajar
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20090605/ed4e745b/attachment.htm>