[Pgcluster-general] PGcluster recovery error with -R option

Pedro Delgado pdelgado at iten.es
Fri Jul 3 07:00:01 UTC 2009


Thanks, I'll try with 3 db cluster and i'll tell you what happends.

Regards.

----- Mensaje original -----
De: mitani at sraw.co.jp
Para: pgcluster-general at pgfoundry.org
Enviados: Viernes, 3 de Julio 2009 3:18:39 GMT +01:00 Amsterdam / Berlín / Berna / Roma / Estocolmo / Viena
Asunto: Re: [Pgcluster-general] PGcluster recovery error with -R option

Hi Pedro,

First of all, at least three cluster db and load balancer are required 
in order to finish recovery with -R option successfully.

The recovery follows the following actions,
1. All db data were copied to the target DB from the master DB as 1st rsync.
2. Sessions were brocked to the master DB and the target DB at load balancer.
3. All db data were copied to target DB from master DB as 2nd rsync.
   During 2nd rsync, these DB servers have to keep rsync only.

   During 2nd rsync, all sessions are executed at the 3rd cluster DB, 
   and the data write queries (like INSERT, UPDATE) are put into queue files in the replication server.

4. Send stored queries to the master db and the target db from the replication server. 
 
Got it?

Regards,
--------------------
At.Mitani
 
-- original message --
From: Pedro Delgado<pdelgado at iten.es>
To: PGCluster<pgcluster-general at pgfoundry.org>
Sent: Thu, 2 Jul 2009 10:17:24 +0200 (CEST)
Subject: [Pgcluster-general] PGcluster recovery error with -R option

>Hi, I configured pgcluster with 2 data base servers.
>All it works fine, but when I start a database in recovery mode con -R option and I make a lot of insert/update in the other database, I lost some rows in the process.
>This problem it's so stragne because a big number of rows are correctly replicated when the data base it's in recovery mode, but a few number no. 
>I tryed tu insert 100 rows in the started database when one data base it's recoveryng with -R. When the process ended i checked the content of two databases. The first (active) have the 100 rows, the second (recover) have 96 rows, it lost four rows.
>This fail it's critical because the database cluster it's inconsistent.
>Some one know about this problem? it's that a problem o a configuration error? 
>In my configuration all the features works fine (cluster, load balancer, replication server) and i think that it's a bug of pgcluster, but I'm not sure.
>If some one can help me I'll be very agreed.
>Greetings.
>_______________________________________________
>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


More information about the Pgcluster-general mailing list