Yes, or similarly, separate user code output from tasktracker logs. System logs won't be corrupted by user output so they can remain at the INFO level, and the user logs could somehow be propagated back to the user, who may well find them useful.
Yoram -----Original Message----- From: Doug Cutting [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 15, 2006 9:20 AM To: [email protected] Subject: Re: Some queries about stability and reliability Yoram Arnon wrote: > User code data gets written to the tasktracker's log at the INFO level. > We switched to WARNING level when a rogue user program produced a lot of > output to stdout, and it > filled the task trackers' logs with junk. Another approach might be to log warning & fatal messages to a separate log, in addition to the primary log. Both logs could be size limited. That way even if user code overflows the primary log with INFO messages, warnings will not be lost. Doug
