Hi Vinod,
Thanks for that info :).
Regards,
Sahana
On Thu, Dec 8, 2011 at 3:30 AM, Vinod Kumar Vavilapalli <
vino...@hortonworks.com> wrote:
>
> That is a stale property in log4j.properties that isn't used for anything.
> There are other such things like noKeepSplits, purgeLogSplits etc w
That is a stale property in log4j.properties that isn't used for anything.
There are other such things like noKeepSplits, purgeLogSplits etc which seem to
be stale too.
mapred.userlog.retain.hours should work just fine as Harsh correctly mentioned.
HTH,
+Vinod
On Dec 7, 2011, at 2:48 AM, Sah
I'm using CDH3 here and I do not see that option in my
log4j.properties. Probably something remaining from an older
mechanism?
Good to know the actual property worked for you.
On Wed, Dec 7, 2011 at 4:18 PM, Sahana Bhat wrote:
> Hi Harsh,
>
> Thanks for the reply. I realized that the p
Hi Harsh,
Thanks for the reply. I realized that the property you mentioned
was missing in my mapred-site.xml.
I added the entry and it works just fine.
Was my assumption that "*hadoop.tasklog.logsRetainHours " *in
log4j.properties will do the same wrong? What is this property for in tha
Sahana,
IIRC, "mapred.userlog.retain.hours" (24h default) controls this in my
environment and it seems to work fine on my cluster. Are you sure you
have tasklogs older than 24h lying around? It might even be a bug that
may have been fixed in the subsequent 0.20 releases that went out
recently.
On
