mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anand Mazumdar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-6769) The server does not close it's end of the connection after returning a response to a streaming request.
Date Fri, 09 Dec 2016 20:39:58 GMT

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

Anand Mazumdar updated MESOS-6769:
----------------------------------
    Description: 
Consider this scenario, 
- The client starts to send a streaming request to the agent with the {{Connection: close}}
header set. This means that the client is relying on the server to close it's end of the connection
after sending the response.
- If the request failed on the server i.e., some validation errors. The server sends the response
but does not close it's end of the socket.
- Some client libraries e.g., Python Requests rely on the server to close its end of the socket
after sending the response. Otherwise, the connection just hangs on the client when it has
no more streaming data to send in such cases.

Libprocess should close its end of the connection after sending the response in such cases.

  was:
Consider this scenario, 
- The client starts to send a streaming request to the agent with the {{Connection: close}}
header set. This means that the client is relying on the server to close it's end of the connection
after sending the response.
- If the request failed on the server i.e., some validation errors. The server sends the response
but does not close it's end of the socket.
- Some client libraries e.g., Python Requests rely on the server to close its end of the socket
after sending the response. Otherwise, the connection just hangs on the client when it has
no more streaming data to send in such cases.

Libprocess should close its end of the 


> The server does not close it's end of the connection after returning a response to a
streaming request.
> -------------------------------------------------------------------------------------------------------
>
>                 Key: MESOS-6769
>                 URL: https://issues.apache.org/jira/browse/MESOS-6769
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Anand Mazumdar
>              Labels: libprocess, mesosphere
>
> Consider this scenario, 
> - The client starts to send a streaming request to the agent with the {{Connection: close}}
header set. This means that the client is relying on the server to close it's end of the connection
after sending the response.
> - If the request failed on the server i.e., some validation errors. The server sends
the response but does not close it's end of the socket.
> - Some client libraries e.g., Python Requests rely on the server to close its end of
the socket after sending the response. Otherwise, the connection just hangs on the client
when it has no more streaming data to send in such cases.
> Libprocess should close its end of the connection after sending the response in such
cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message