[Pgcluster-general] Failover of PGReplicate

[a.mitani at sra-europe.com]

Hi,

The status (active/standby) of replication server will be changed if
active server was stopped.

When "primary" is up again, it's status become "standby".
(action 4th-5th in following table)
If "secondary" is down, the "primary" status will be changed to "active".
(action 6th in following table)

Action   Cluster DBs      Status of      Status of
num      connect with     Replicator A   Replicator B
----------------------------------------------------------
1       (start-up)        (start-up)     (start-up)
2       Replicator A       active         standby
3       Replicator B      (down)          active
4       Replicator B      (start-up)      active
5       Replicator B       standby        active
6       Replicator A       active        (down)
7       Replicator A       active        (start-up)
8       Replicator A       active         standby

Does that answer you?

Regards,
-------------
At.Mitani


> Sorry, as I see it, the question hasn't been answered. He asked if the
> "secondary" node should detect that the "primary" is up again, and then
> restore the original behavior (i.e. root replication server getting
> active again in the whole replication schema).
>
> Regards,
> --
> Tom;
>
> a.mitani at sra-europe.com escribi�:
>> Hi,
>>
>> The replication server is used for queueing queries.
>> Therefore, all cluster db must connect same replication server.
>>
>> Replication server has not primary / secondary order.
>> It has just active / stand-by mode.
>>
>> Regards,
>> -------------------
>> At.Mitani
>>
>>
>>> Lets say I have 2 nodes, each running PGReplicate and ClusterDB. The
>>> node
>>> running the primary PGReplicate fails and the ClusterDB on the second
>>> node
>>> automatically fails over the PGReplicate of the first node. However,
>>> when
>>> I restart node1, the ClusterDB of node2 seems to remain connected to
>>> PGreplicate of node2, and thus any changes done on node 2 are no longer
>>> reflected on node1, and viceversa.
>>>
>>> Is ClusterDB supposed to realise that the primary replicator has been
>>> restored so that all clusterDBs access the same replicator?
>>>
>>> regards,
>>> Josef
>>>
>>> _______________________________________________
>>> Pgcluster-general mailing list
>>> Pgcluster-general at pgfoundry.org
>>> http://pgfoundry.org/mailman/listinfo/pgcluster-general
>>>
>>>
>>
>> _______________________________________________
>> Pgcluster-general mailing list
>> Pgcluster-general at pgfoundry.org
>> http://pgfoundry.org/mailman/listinfo/pgcluster-general
>>
>
> _______________________________________________
> Pgcluster-general mailing list
> Pgcluster-general at pgfoundry.org
> http://pgfoundry.org/mailman/listinfo/pgcluster-general
>