Thu Feb 2 22:12:54 PST 2006
- Previous message: [Slony1-general] Slony susceptible to temporary network outages?
- Next message: [Slony1-general] BUG: [SLONY1] slonik doesn't catch errors properly (ID: 1518) (new)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> I am running slon 1.1 with a "g" factor of 10000. As I understand it (somebody please correct me if I'm wrong), a "g" factor of more than 100 actually impedes "catch up". The code has logic that resets the sync group to 1 whenever the group size "grows" above 100 (slon gradually grows to -g size). If you grep your slony log for "processing", you should see a pattern were the event being synced gradually increases more from the previous until it exceeds 100. Once it hits 100, it likely drops back down to zero. So, try setting '-g 100' and see if the slon eventually makes progress. -Michael
- Previous message: [Slony1-general] Slony susceptible to temporary network outages?
- Next message: [Slony1-general] BUG: [SLONY1] slonik doesn't catch errors properly (ID: 1518) (new)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list