[
https://issues.apache.org/jira/browse/HADOOP-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675868#action_12675868
]
Amar Kamat commented on HADOOP-5272:
------------------------------------
Result of test-patch :
{code}
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] -1 tests included. The patch doesn't appear to include any new
or modified tests.
[exec] Please justify why no tests are needed for
this patch.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath
integrity.
[exec]
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
{code}
> JobTracker does not log TIP start information after restart
> -----------------------------------------------------------
>
> Key: HADOOP-5272
> URL: https://issues.apache.org/jira/browse/HADOOP-5272
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Amar Kamat
> Priority: Critical
> Attachments: HADOOP-5272-v1.0.patch
>
>
> In case of JobTracker restart, attempt_0123456789_0001_m_000000_0 might not
> be the first attempt to get scheduled as the attempt id offset changes after
> every restart. For example,
> upon first restart the new attempt id will be
> attempt_0123456789_0001_m_000000_1000. Hence TIP start line never gets logged
> to the job history after the restart, TaskInProgress.isFirstAttempt() always
> returns *false*.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
