You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Jeff Zhang (JIRA)" <ji...@apache.org> on 2015/06/02 08:43:17 UTC
[jira] [Updated] (TEZ-2511) Add exitCode to diagnostics when
container fails
[ https://issues.apache.org/jira/browse/TEZ-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Zhang updated TEZ-2511:
----------------------------
Description:
Currently we only support for PREEMPTED/DISKS_FAILED, that means except for these 2 cases, there would be no clear diagnostic message for other cases.
Although we can do that for other ContainerExitStatus, but it would cause incompability issue ( ContainerExitStatus of hadoop-2.2 support less exit code than that of hadoop-2.6).
So I think maybe could use tez's own ContainerExitStatus since all the memebers are integer, so that we could keep updated with yarn's support of ContainerExitStatus and also won't break the compatibility.
But this would require shimming to correctly handle more and more failure scenarios reported by YARN across different versions. Create this ticket here as backlog if it is necessary in the future.
was:
Currently we only support for PREEMPTED/DISKS_FAILED, that means except for these 2 cases, there would be no clear diagnostic message for other cases.
Although we can do that for other ContainerExitStatus, but it would cause incompability issue ( ContainerExitStatus of hadoop-2.2 support less exit code than that of hadoop-2.6).
So I think maybe could use tez's own ContainerExitStatus since all the memebers are integer, so that we could keep updated with yarn's support of ContainerExitStatus and also won't break the compatibility.
But this would cause require the shimming to correctly handle more and more failure scenarios reported by YARN across different versions. Create this ticket here as backlog if it is necessary in the future.
> Add exitCode to diagnostics when container fails
> ------------------------------------------------
>
> Key: TEZ-2511
> URL: https://issues.apache.org/jira/browse/TEZ-2511
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Jeff Zhang
> Assignee: Jeff Zhang
>
> Currently we only support for PREEMPTED/DISKS_FAILED, that means except for these 2 cases, there would be no clear diagnostic message for other cases.
> Although we can do that for other ContainerExitStatus, but it would cause incompability issue ( ContainerExitStatus of hadoop-2.2 support less exit code than that of hadoop-2.6).
> So I think maybe could use tez's own ContainerExitStatus since all the memebers are integer, so that we could keep updated with yarn's support of ContainerExitStatus and also won't break the compatibility.
> But this would require shimming to correctly handle more and more failure scenarios reported by YARN across different versions. Create this ticket here as backlog if it is necessary in the future.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)