Re: [Postgres-xc-general] Move from a single-cluster machine to a multi cluster machine.

[Mason S. <ms...@tr...>]

On Thu, Aug 21, 2014 at 4:32 PM, Joseph Mays <ma...@wi...> wrote:

>   What they are looking for in the end is high-availability and load
> balancing. They want either system to be able to receive read and write
> requests, and for either one to be able to take over all the work if the
> other is down. My understanding is that postgres-xc is capable of this,
> it’s just a matter of getting there from where they are. All of this would
> be easier if their current database server weren’t running on one of the
> machines that needs to be in the two-machine cluster when we’re done.
>
> And yes, minimizing downtime is a priority, too.
>
>

How heavy are the writes? If it is read-mainly, you could be ok. With what
you describe, all tables would have to be designated as replicated, adding
latency. Or, you could define two datanodes, and have a warm standby on
each of the other's portion.

In any event, Postgres-XC does not have automated high availability. You
would have to have something external monitor and decide when to failover.
I have used Corosync/Pacemaker for example.


-- 
Mason Sharp

TransLattice - http://www.translattice.com
Distributed and Clustered Database Solutions