[MESOS-9189] Include 'Connection: close' header in master streaming API responses.

• Type: Improvement
• Status: Accepted
• Priority: Major
• Resolution: Unresolved
• Component/s: HTTP API
• Target Version/s: 1.5.4, 1.6.3, 1.7.4
• Assignee: Benjamin Mahler
• Reporter: Benjamin Mahler
• Created: 29/Aug/18 01:11
• Updated: 29/Apr/20 05:01

Description

We've seen some HTTP intermediaries (e.g. ELB) decide to re-use connections to mesos as an optimization to avoid re-connection overhead. As a result, when the end-client of the streaming API disconnects from the intermediary, the intermediary leaves the connection to mesos open in an attempt to re-use the connection for another request once the response completes. Mesos then thinks that the subscriber never disconnected and the intermediary happily continues to read the streaming events even though there's no end-client.

To help indicate to intermediaries that the connection SHOULD NOT be re-used, we can set the 'Connection: close' header for streaming API responses. It may not be respected (since the language seems to be SHOULD NOT), but some intermediaries may respect it and close the connection if the end-client disconnects.

Note that libprocess' http server currently doesn't close the the connection based on a handler setting this header, but it doesn't matter here since the streaming API responses are infinite.

Issue Links

• is blocked by: MESOS-9215 SchedulerSubscribeAfterFailoverTimeout times out.
• is cloned by: MESOS-9209 Include 'Connection: close' header in agent streaming API responses.
• relates to: MESOS-9258 Prevent subscribers to the master's event stream from leaking connections
• links to: RFC 6202: HTTP Streaming