[
https://issues.apache.org/jira/browse/LIVY-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyorgy Gal updated LIVY-773:
----------------------------
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.
> 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
> Fix For: 0.10.0
>
> Time Spent: 50m
> 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.20.10#820010)
