You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@livy.apache.org by "Saisai Shao (JIRA)" <ji...@apache.org> on 2017/09/18 08:40:00 UTC

[jira] [Assigned] (LIVY-396) Livy does not map YARN app states correctly

     [ https://issues.apache.org/jira/browse/LIVY-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Saisai Shao reassigned LIVY-396:
--------------------------------

    Assignee: Meisam Fathi

> Livy does not map YARN app states correctly
> -------------------------------------------
>
>                 Key: LIVY-396
>                 URL: https://issues.apache.org/jira/browse/LIVY-396
>             Project: Livy
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 0.4
>         Environment: all enironments
>            Reporter: Meisam
>            Assignee: Meisam Fathi
>            Priority: Minor
>             Fix For: 0.5.0
>
>   Original Estimate: 20m
>          Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> If the status of a YARN app is {{KILLED}}, the final status should be {{KILLED}} too, but there is a test case in [{{SparkYarnAppSpec.scala}}|https://github.com/meisam/incubator-livy/blob/master/server/src/test/scala/org/apache/livy/utils/SparkYarnAppSpec.scala#L217] that expect the final status to be {{UNDEFINED}}.
> {code}
>  assert(app.mapYarnState(appId, KILLED, UNDEFINED) == State.KILLED)
> {code}
>  The case that app state is {{KILLED}} and the final status is {{UNDEFINED}} should never happen.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)