Thanks. It seems that something else is going on -
Here is the content of log.index -
ajay-srivastava:userlogs ajay.srivastava$ cat job_201307222115_0188/attempt_201307222115_0188_r_000000_0/log.index
Looks like that the log.index is pointing to another attempt directory.
Is it doing some kind of optimization ? What is purpose of log.index ?
On 24-Jul-2013, at 11:09 AM, Vinod Kumar Vavilapalli wrote:
> It could either mean that all those task-attempts are crashing before the process itself is getting spawned (check TT logs) or those logs are getting deleted after the fact. Suspect the earlier.
> On Jul 23, 2013, at 9:33 AM, Ajay Srivastava wrote:
>> I see that most of the tasks have only log.index created in /opt/hadoop/logs/userlogs/jobId/task_attempt directory.
>> When does this happen ?
>> Is there a config setting for this OR this is a bug ?
>> Ajay Srivastava