On 05/23/12 06:42 PM, Quanah Gibson-Mount wrote:
Or it just means that the accesslog is receiving a significant number of changes and that the time configured for how often to delete the accesslog DB is too small. It will certainly grow
To the tune of 16+G of VM (only 4.7G resident) on a 512G accesslog DB and 2G main DB, though? I've tried setting the logpurge to kill > 15min entries every 30min, and it doesn't seem to be making a difference.
I'll try to see if I can generate a pile of entries not using our local schemas and reproduce the problem.
I suppose I can also try switching accesslog over to mdb and see if it still occurs.