[
https://issues.apache.org/jira/browse/LIVY-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyorgy Gal updated LIVY-709:
----------------------------
Fix Version/s: 0.10.0
(was: 0.9.0)
This issue has been moved to the 0.10.0 release as part of a bulk update. If
you feel this is moved out inappropriately, feel free to provide justification
and reset the Fix Version to 0.9.0.
> 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
> Fix For: 0.10.0
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
