Description
Currently, the AM cannot programmatically determine if the task was killed due to using excessive memory. The NM kills it without passing this information in the container status back to the RM. So the AM cannot take any action here. The jira tracks adding this exit status and passing it from the NM to the RM and then the AM. In general, there may be other such actions taken by YARN that are currently opaque to the AM.
Attachments
Attachments
Issue Links
- is depended upon by
-
TEZ-1069 Support ability to re-size a task attempt when previous attempts fail due to resource constraints
- Open