flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Rohrmann (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FLINK-4046) Failing a restarting job can get stuck in JobStatus.FAILING
Date Thu, 09 Jun 2016 13:50:20 GMT
Till Rohrmann created FLINK-4046:

             Summary: Failing a restarting job can get stuck in JobStatus.FAILING
                 Key: FLINK-4046
                 URL: https://issues.apache.org/jira/browse/FLINK-4046
             Project: Flink
          Issue Type: Bug
          Components: Distributed Runtime
    Affects Versions: 1.1.0
            Reporter: Till Rohrmann
             Fix For: 1.1.0

When a job is in state {{RESTARTING}}, then it can happen that all of its {{ExecutionJobVertices}}
are in a final state (if they have not been reset). When calling {{fail}} on this {{ExecutionGraph}}
will transition the state to {{FAILING}} and call cancel on all {{ExecutionJobVertices}}.
The job state {{FAILING}} can only be left iff all {{ExecutionJobVertices}} have reached a
final state. The notification of this final state is only sent to the {{ExecutionGraph}} when
all subtasks of an {{ExecutionJobVertex}} have transitioned to a final state. However, this
won't happen because the {{ExeuctionJobVertices}} are already in a final state. The result
is that a job can get stuck in the state {{FAILING}} if {{fail}} is called on a {{RESTARTING}}

I propose to add a direct transition from {{RESTARTING}} to {{FAILED}} as it is the case for
the {{cancel}} call (transition from {{RESTARTING}} to {{CANCELED}}).

This message was sent by Atlassian JIRA

View raw message