Anyone faced similar issue or knows what the issue might be?
Thanks in advance.
On Thu, Apr 5, 2012 at 10:52 AM, Prashant Kommireddi <prash1...@gmail.com>wrote:
> Thanks Nitin.
>
> I believe the config key you mentioned controls the task attempts logs
> that go under - ${hadoop.log.dir}/userlogs.
>
> The ones that I mentioned are the job history logs that go under -
> ${hadoop.log.dir}/history
> and are specified by the key "hadoop.job.history.location". Are these
> cleaned up based on "mapred.userlog.retain.hours" too?
>
> Also, this is what I am seeing in history dir
>
> Available Conf files - Mar 3rd - April 5th
> Available Job files - Mar 3rd - April 3rd
>
> There is no job file present after the 3rd of April, but conf files
> continue to be written.
>
> Thanks,
> Prashant
>
>
>
>
> On Thu, Apr 5, 2012 at 3:22 AM, Nitin Khandelwal <
> nitin.khandel...@germinait.com> wrote:
>
>> Hi Prashant,
>>
>> The userlogs for job are deleted after time specified by "*
>> mapred.userlog.retain.hours*" property defined in mapred-site.xml
>> (default
>> is 24 Hrs).
>>
>> Thanks,
>> Nitin
>>
>> On 5 April 2012 14:26, Prashant Kommireddi <prash1...@gmail.com> wrote:
>>
>> > I am noticing something strange with JobTracker history logs on my
>> cluster.
>> > I see configuration files (*_conf.xml) under /logs/history/ but none of
>> the
>> > actual job logs. Anyone has ideas on what might be happening?
>> >
>> > Thanks,
>> >
>>
>>
>>
>> --
>>
>>
>> Nitin Khandelwal
>>
>
>
