Fri Feb 22 10:37:23 PST 2008
- Previous message: [Slony1-general] Slave died, no access till next week, master logs filling up. What should I do
- Next message: [Slony1-general] Slave died, no access till next week, master logs filling up. What should I do
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, 2008-02-22 at 13:32 -0500, Andrew Sullivan wrote: > On Sat, Feb 23, 2008 at 02:23:20AM +0800, Ow Mun Heng wrote: > > > > And yesterday, I just created a job to manually force the log_switch to > > occur. So, right now, I'm at a loss as to what i can do. > Add more disk? What is the harm in the log filling up? I wish I could. The so-called server is just a celeron box w/ 4 IDE disks (on master) 1x80G OS, 2x500G Raid1, 1x500G slony logs When the logs start to fill up >2G, I will see the dreaded fetch 100 from log and it takes upwards to 500++ seconds for it to get the 1st row and thus replication will fall behind _way_way_ much.
- Previous message: [Slony1-general] Slave died, no access till next week, master logs filling up. What should I do
- Next message: [Slony1-general] Slave died, no access till next week, master logs filling up. What should I do
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list