You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@livy.apache.org by "Andras Beni (Jira)" <ji...@apache.org> on 2020/06/09 18:58:00 UTC

[jira] [Commented] (LIVY-773) Wrong status code when session creation limit reached

    [ https://issues.apache.org/jira/browse/LIVY-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17129711#comment-17129711 ] 

Andras Beni commented on LIVY-773:
----------------------------------

Pull request:

[https://github.com/apache/incubator-livy/pull/297]

> Wrong status code when session creation limit reached
> -----------------------------------------------------
>
>                 Key: LIVY-773
>                 URL: https://issues.apache.org/jira/browse/LIVY-773
>             Project: Livy
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 0.7.0
>            Reporter: Andras Beni
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When {{livy.server.session.max-creation}} is reached, Livy server responds with HTTP status code [400 Bad Request|https://tools.ietf.org/html/rfc7231#section-6.5.1], which is designed for situations when the request is bad in itself and the sever cannot process it.
>  [503 Server Unavailable|https://tools.ietf.org/html/rfc7231#section-6.6.4] is meant for temporary overload when the server cannot serve the request.
> The latter fits the this case, so I propose to change the response.



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