You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2015/08/14 20:44:46 UTC

[jira] [Created] (TEZ-2720) Task user code exceptions may show up as TaskTerminationCause.FRAMEWORK_ERROR

Bikas Saha created TEZ-2720:
-------------------------------

             Summary: Task user code exceptions may show up as TaskTerminationCause.FRAMEWORK_ERROR
                 Key: TEZ-2720
                 URL: https://issues.apache.org/jira/browse/TEZ-2720
             Project: Apache Tez
          Issue Type: Bug
            Reporter: Bikas Saha


The main run() method ends up calling
{code}  private void sendFailure(Throwable t, String message) throws IOException, TezException {
    if (!fatalErrorSent.getAndSet(true)) {
      task.setFatalError(t, message);
      task.setFrameworkCounters();
      try {
        taskReporter.taskFailed(task.getTaskAttemptID(), t, message, null);{code}
The last null gives no indication of the source of the failure. This ends up sending the task failed event with the sourceMeta as SYSTEM.
{code}        TezEvent taskAttemptFailedEvent = new TezEvent(new TaskAttemptFailedEvent(diagnostics),
            srcMeta == null ? updateEventMetadata : srcMeta);
        return !heartbeat(Lists.newArrayList(statusUpdateEvent, taskAttemptFailedEvent)).shouldDie;
{code}
In the AM that ends up marking the attempt failure as FRAMEWORK_ERROR instead of APPLICATION_ERROR.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)