Thu Jan 7 15:13:11 PST 2016
- Previous message: [Slony1-general] Slony-I: log switch to sl_log_2 still in progress - sl_log_1 not truncated
- Next message: [Slony1-general] log insert/update query executed on subscriber
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Jan 7, 2016 at 2:59 PM, Steve Singer <steve at ssinger.info> wrote: > On Thu, 7 Jan 2016, Tory M Blue wrote: > > Bump sync_group_maxsize to be much bigger, I'm not saying that will >> solve the problem but it might help(max >> allowed is 10,000). I'm also suspect when you say your have a >> sync_interval of 5 minutes, since I thought 60 >> seconds was the largest allowed. >> >> My apologies >> >> cleanup_interval="5 minutes" >> >> my interval is 1000ms >> >> And sync, group cites 100 is the max >> >> # Range: [0,100], default: 6 >> >> sync_group_maxsize=50 >> > > Where does that come from? > http://www.slony.info/documentation/2.2/slon-config-interval.html > > says the max is 10,000 and the code looks like it agrees. Try it and see > if you start to catch up. Also an analyze on your sl_log_1 and sl_log_2 > can't hurt. > > With a sync_group_size of 20 slon will select the data for at most 20 > SYNC's at once and apply them (using a select from sl_log_1 ... union > select from sl_log_2 ...) > > With a sync_group_size of 10,000 it can in theory select 10,000 sync's at > once (but I think it takes a while to work up to that point). > > If your bottleneck is the master then it is possible that the selecting > from sl_log is causing the problem. > > Thanks Steve, I had that in my slon.conf, it may have been left over from many years 10+ of using slon and a much earlier version :) I'll keep incrementing it and see what happens. Analyze was quick, but I think you are on to something when you cited that it may be taking a bit to grab from sl_log1 and thus the snowball.. Can't say I've ever had this many records backed up, but the idea of dropping node 2, when i know I'll be in the same situation bothers me :) 2016-01-07 15:10:29 PST clsdb postgres [local] 16066 2016-01-07 15:10:29.128 PSTLOG: duration: 2096.165 ms statement: analyze _cls.sl_log_2; 2016-01-07 15:10:36 PST aclsdb postgres [local] 16066 2016-01-07 15:10:36.162 PSTLOG: duration: 2426.762 ms statement: analyze _cls.sl_log_1 Tory -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20160107/41df5853/attachment-0001.htm
- Previous message: [Slony1-general] Slony-I: log switch to sl_log_2 still in progress - sl_log_1 not truncated
- Next message: [Slony1-general] log insert/update query executed on subscriber
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list