Sorry to keep replying to myself... Okay, I see the meaning of mapred.userlog.limit.kb is different now: it is a total disk space limit, not a per-log-file limit.
I still seems wrong that my logs don't show up immediately when a map task starts -- this is when logs are most valuable for me because they tell me whether I can stop watching the task. Maybe there is some flushing problem? -Michael On 8/21/07 8:47 AM, "Michael Bieniosek" <[EMAIL PROTECTED]> wrote: > Even worse, now that my logs have appeared, I'm only getting the second half > of the log in the file userlogs/$task/stdout, and no previous segments. It > looks like all the split.idx stuff is gone? > > -1 > > -Michael > > On 8/21/07 8:13 AM, "Michael Bieniosek" <[EMAIL PROTECTED]> wrote: > >> I noticed a problem in hadoop-0.14: >> >> Often when I start a map task, the status will show up in the hadoop ui, but >> when I click on the "Show logs" link, it says, "Failed to retrieve >> syslog..." If I actually log onto the host to hunt for the logs, I see >> empty files (not directories) for userlogs/$task/stdout. >> >> -Michael >> >> On 8/19/07 10:02 PM, "Owen O'Malley" <[EMAIL PROTECTED]> wrote: >> >>> +1 >> >
