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

Vinod Kone updated MESOS-3332:
------------------------------
    Sprint: Twitter Mesos Q3 Sprint 4, Twitter Mesos Q3 Sprint 5  (was: Twitter 
Mesos Q3 Sprint 4)

> Support HTTP Pipelining in libprocess (http::post)
> --------------------------------------------------
>
>                 Key: MESOS-3332
>                 URL: https://issues.apache.org/jira/browse/MESOS-3332
>             Project: Mesos
>          Issue Type: Task
>          Components: libprocess
>            Reporter: Anand Mazumdar
>            Assignee: Benjamin Mahler
>              Labels: twitter
>
> Currently , {{http::post}} in libprocess, does not support HTTP pipelining. 
> Each call as of know sends in the {{Connection: close}} header, thereby, 
> signaling to the server to close the TCP socket after the response.
> We either need to create a new interface for supporting HTTP pipelining , or 
> modify the existing {{http::post}} to do so.
> This is needed for the Scheduler/Executor library implementations to make 
> sure "Calls" are sent in order to the master. Currently, in order to do so, 
> we send in the next request only after we have received a response for an 
> earlier call that results in degraded performance.



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

Reply via email to