[Pgcluster-general] PgCluster recover with -U and lost rows

[mitani at sraw.co.jp]

Hi,

If you want to operate INSERT/UPDATE query during recovery action,
I recomend to use three or more cluster db in your system.
It is a requirement specification of dynamic recovery.

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

-- original message --
From: Lia Domide<lia.domide at codemart.ro>
To: <pgcluster-general at pgfoundry.org>
Sent: Wed, 16 Apr 2008 11:22:34 +0300
Subject: [Pgcluster-general] PgCluster recover with -U and lost  rows

>Hello everybody,
>
> 
>
>I am currently testing pgCluster1.9rc5 with Ubuntu 7.04, and I encounter the
>following problem:
>
> 
>
>I have 2 nodes, each having LB, DB and REP installed.
>
>One DB service is down, and one is still operating, taking INSERTs/SELECTs
>through LoadBalancers.
>
>I try to restart the second DB node with -U option. 
>
>This gives me a desired behavior: no blocking on the master DB, but in the
>same time, if a JDBC client is operating some INSERTS on the master
>database, missing rows are encounter.
>
> More exactly: LadBalancer says: 
>
> 
>
>2008-04-16 11:14:06 [7312] DEBUG:set_recovery():received no:1
>2008-04-16 11:14:06 [7312] DEBUG:set_recovery():add_db host:pg3 port:5432
>max:103
>2008-04-16 11:14:06 [7312] DEBUG:PGRset_status_on_cluster_tbl():host:pg3
>port:5432 max:32 use:2 status3
>2008-04-16 11:14:22 [7312] DEBUG:set_recovery():received no:3
>2008-04-16 11:14:22 [7312] DEBUG:set_recovery():stop_db host:pg2 port:5432
>max:103
>2008-04-16 11:14:22 [7312] DEBUG:PGRset_status_on_cluster_tbl():host:pg2
>port:5432 max:32 use:2 status3
>2008-04-16 11:14:41 [7312] DEBUG:set_recovery():received no:11
>2008-04-16 11:14:41 [7312] DEBUG:set_recovery():start_db host:pg2 port:5432
>max:103
>2008-04-16 11:14:41 [7312] DEBUG:PGRset_status_on_cluster_tbl():host:pg2
>port:5432 max:32 use:3 status1
>2008-04-16 11:14:56 [7312] DEBUG:set_recovery():received no:11
>2008-04-16 11:14:56 [7312] DEBUG:set_recovery():start_db host:pg3 port:5432
>max:103
>2008-04-16 11:14:56 [7312] DEBUG:PGRset_status_on_cluster_tbl():host:pg3
>port:5432 max:32 use:3 status1
>
> 
>
>Anything inserted between 2008-04-16 11:14:41 and 2008-04-16 11:14:56 is not
>synchronized on the second DB node.
>
>More than that, between 2008-04-16 11:14:22 and 2008-04-16 11:14:41, even
>the master DB node is locked, for any insert/select.
>
>Is this a bug in pgcluster or is the default behaviour for the cluster, to
>have the DB locked by the time the synchronization is done?
>
> 
>
>                              Have a nice day,
>
>                                   Lia Domide
>
>
>_______________________________________________
>Pgcluster-general mailing list
>Pgcluster-general at pgfoundry.org
>http://pgfoundry.org/mailman/listinfo/pgcluster-general
>