[jira] [Commented] (MAPREDUCE-4993) AM thinks it was killed when an error occurs setting up a task container launch context
[ https://issues.apache.org/jira/browse/MAPREDUCE-4993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13594519#comment-13594519 ] Abhishek Kapoor commented on MAPREDUCE-4993: Though I am not sure who is handling the cleanseing of exception handling in AM, but as for now, we can set diagnostics in catch statement of the below code. If some one is dealing with excpetion handling I can take up the task for the same :) Let me know. AM thinks it was killed when an error occurs setting up a task container launch context --- Key: MAPREDUCE-4993 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4993 Project: Hadoop Map/Reduce Issue Type: Bug Components: mr-am Affects Versions: 2.0.3-alpha, 0.23.5 Reporter: Jason Lowe Assignee: Abhishek Kapoor If an IOException occurs while setting up a container launch context for a task then the AM exits with a KILLED status and no diagnostics. The job should be marked as FAILED (or maybe ERROR) with a useful diagnostics message indicating the nature of the error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4993) AM thinks it was killed when an error occurs setting up a task container launch context
[ https://issues.apache.org/jira/browse/MAPREDUCE-4993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595601#comment-13595601 ] Abhishek Kapoor commented on MAPREDUCE-4993: If the jar required for the job gets deleted in the middle while job is running, then job should be failed and AM for the specific job should die, isn't it a expected behaviour? If it is a expected then we can gracefully kill the AM with an appropriate diagnostics. Please correct me if am wrong. AM thinks it was killed when an error occurs setting up a task container launch context --- Key: MAPREDUCE-4993 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4993 Project: Hadoop Map/Reduce Issue Type: Bug Components: mr-am Affects Versions: 2.0.3-alpha, 0.23.5 Reporter: Jason Lowe Assignee: Abhishek Kapoor If an IOException occurs while setting up a container launch context for a task then the AM exits with a KILLED status and no diagnostics. The job should be marked as FAILED (or maybe ERROR) with a useful diagnostics message indicating the nature of the error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4993) AM thinks it was killed when an error occurs setting up a task container launch context
[ https://issues.apache.org/jira/browse/MAPREDUCE-4993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13590290#comment-13590290 ] Abhishek Kapoor commented on MAPREDUCE-4993: Please explain the use case. All I can understand is you wrote MR job which is trying to access some jar in hdfs and if that the respective jar does not exist the MR-AM is dying with above stacktrace? AM thinks it was killed when an error occurs setting up a task container launch context --- Key: MAPREDUCE-4993 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4993 Project: Hadoop Map/Reduce Issue Type: Bug Components: mr-am Affects Versions: 2.0.3-alpha, 0.23.5 Reporter: Jason Lowe If an IOException occurs while setting up a container launch context for a task then the AM exits with a KILLED status and no diagnostics. The job should be marked as FAILED (or maybe ERROR) with a useful diagnostics message indicating the nature of the error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (MAPREDUCE-4993) AM thinks it was killed when an error occurs setting up a task container launch context
[ https://issues.apache.org/jira/browse/MAPREDUCE-4993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kapoor reassigned MAPREDUCE-4993: -- Assignee: Abhishek Kapoor AM thinks it was killed when an error occurs setting up a task container launch context --- Key: MAPREDUCE-4993 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4993 Project: Hadoop Map/Reduce Issue Type: Bug Components: mr-am Affects Versions: 2.0.3-alpha, 0.23.5 Reporter: Jason Lowe Assignee: Abhishek Kapoor If an IOException occurs while setting up a container launch context for a task then the AM exits with a KILLED status and no diagnostics. The job should be marked as FAILED (or maybe ERROR) with a useful diagnostics message indicating the nature of the error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4993) AM thinks it was killed when an error occurs setting up a task container launch context
[
https://issues.apache.org/jira/browse/MAPREDUCE-4993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13590313#comment-13590313
]
Abhishek Kapoor commented on MAPREDUCE-4993:
Though I think the issue is in below code.
Class: TaskAttemptImpl
Function: createCommonContainerLaunchContext
code:
} catch (IOException e) {
throw new YarnException(e);
}
But I need to replicate the issue in-order to fix it.
Could you please suggest the step you are doing, so I can replicate the bug
Thanks
Abhi
AM thinks it was killed when an error occurs setting up a task container
launch context
---
Key: MAPREDUCE-4993
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4993
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: mr-am
Affects Versions: 2.0.3-alpha, 0.23.5
Reporter: Jason Lowe
Assignee: Abhishek Kapoor
If an IOException occurs while setting up a container launch context for a
task then the AM exits with a KILLED status and no diagnostics. The job
should be marked as FAILED (or maybe ERROR) with a useful diagnostics message
indicating the nature of the error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
