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 2019/12/19 02:53:00 UTC

[jira] [Resolved] (LIVY-729) Livy should not recover the killed session

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

Saisai Shao resolved LIVY-729.
------------------------------
    Fix Version/s: 0.8.0
         Assignee: runzhiwang
       Resolution: Fixed

Issue resolved by pull request 266
https://github.com/apache/incubator-livy/pull/266

> Livy should not recover the killed session
> ------------------------------------------
>
>                 Key: LIVY-729
>                 URL: https://issues.apache.org/jira/browse/LIVY-729
>             Project: Livy
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 0.6.0
>            Reporter: runzhiwang
>            Assignee: runzhiwang
>            Priority: Major
>             Fix For: 0.8.0
>
>         Attachments: image-2019-12-18-08-56-46-925.png
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Follows are steps to reproduce the problem:
>  # Set livy.server.recovery.mode=recovery, and create a session: session0 in yarn-cluster
>  # kill the yarn application of the session
>  # restart livy
>  # livy try to recover session0, but application has been killed and driver does not exist, so client can not connect to driver, and exception was thrown as the image.
>  # If the ip:port of the driver was reused by session1, client of session0 will try to connect to driver of session1, then driver will throw exception: Unexpected client ID.
>  # Both the exception threw by livy and driver will confused the user, and recover a lot of killed sessions will delay the recover of alive session.
> !image-2019-12-18-08-56-46-925.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)