You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@livy.apache.org by "Viacheslav Tradunsky (Jira)" <ji...@apache.org> on 2019/11/08 11:23:00 UTC

[jira] [Updated] (LIVY-709) Livy doesn't return the exact error when session is dead

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

Viacheslav Tradunsky updated LIVY-709:
--------------------------------------
    Attachment: livy server error.log
                livy client error.log

> Livy doesn't return the exact error when session is dead
> --------------------------------------------------------
>
>                 Key: LIVY-709
>                 URL: https://issues.apache.org/jira/browse/LIVY-709
>             Project: Livy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.5.0, 0.6.0
>            Reporter: Viacheslav Tradunsky
>            Priority: Major
>         Attachments: livy client error.log, livy server error.log
>
>
> When livy client requests for new session livy starts to setup env for that session, it may happen that artifactory is unavailable or the file system permission issue caused session to be shutting_down/dead. However, livy client is silent about this, it only terminates after timeout with error java.net.SocketTimeoutException: Read timed out.[^livy server error.log]



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