Fri May 4 07:11:23 PDT 2007
- Previous message: [Slony1-general] Re: Using monit to keep slony running
- Next message: [Slony1-general] How to reduce st_lag_time ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, I'm running a simple replication between a master and a slave. The slave is planned as a switchover host in case of big troubles on the server (ie: slave can be stopped but not the master). My environnment: Postgres: 7.4 Slony: 1.2.6 It seems that my replication is no more active and the tables sl_log_1/2 are now very big (sl_log_1 is around 6GB and 3.3e+06 tuples). Value st_lag_time is very important. I have tried to restart the slon (master and slave) but the st_last_received_event_ts is not changing (or only once for 3 sec). On the master slon log, I have (1 is master, 2 is slave). 2007-05-04 15:54:31 CEST DEBUG2 remoteListenThread_2: queue event 2,712628 SYNC 2007-05-04 15:54:31 CEST DEBUG2 remoteListenThread_2: UNLISTEN 2007-05-04 15:54:31 CEST DEBUG2 remoteWorkerThread_2: Received event 2,712628 SYNC 2007-05-04 15:54:31 CEST DEBUG3 calc sync size - last time: 1 last length: 10166 ideal: 5 proposed size: 3 2007-05-04 15:54:31 CEST DEBUG2 remoteWorkerThread_2: SYNC 712628 processing 2007-05-04 15:54:31 CEST DEBUG2 remoteWorkerThread_2: no sets need syncing for this event 2007-05-04 15:54:32 CEST DEBUG2 localListenThread: Received event 1,1553949 SYNC 2007-05-04 15:54:32 CEST DEBUG2 syncThread: new sl_action_seq 6356493 - SYNC 1553950 So, I'm seeing line with 'no sets need syncing for this event'. Can someone help me understanding what's wrong ? Thanks in advance, Alain.
- Previous message: [Slony1-general] Re: Using monit to keep slony running
- Next message: [Slony1-general] How to reduce st_lag_time ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list