On 13-12-2011 10:42:40 -0700, Joseph Brower wrote:
On 13-12-2011 10:06:00 -0700, Joseph Brower wrote:
Another concern is that in our installation, we don't see a MonetDB.conf file. I was hoping that we could specify how much RAM we'd like to allow MonetDB to consume. This is to ensure that our memory manager doesn't kill MonetDB, since that's the primary role of this server. Is this a file that we should create? I'm still fairly new to MonetDB and as a result, am still trying to find my way with it. Short answer, you can't. The config files are gone too, infavour of settings managed by monetdbd. Is there any documentation about how to properly manage settings via monetdbd?
See the manpages for monetdbd(1) and monetdb(1): http://www.monetdb.org/Documentation/monetdbd-man-page http://www.monetdb.org/Documentation/monetdb-man-page
There is no notion of a log-level, and MSG and ERR messages can't be separated either. You could locally patch, but I don't think it's worth it. Rotating logs is fairly easy. monetdbd accepts SIGHUP to reopen its logfile, so it's easy to integrate with logrotate.
That's what I figured. :-D I'll make sure we implement the log rotation.
I've done some more research. It appears to be an issue with how our other system is inserting information. We'll be continuing to diagnose this.
You should have not so rapidly growing logs, if you can get clients to use a persistent connection (not making a new connection for every query).