[MESOS-3570] Make Scheduler Library use HTTP Pipelining Abstraction in Libprocess

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.28.0
• Labels: mesosphere newbie
• Epic Link: Scheduler API v1 improvements
• Sprint: Mesosphere Sprint 27, Mesosphere Sprint 28, Mesosphere Sprint 29
• Story Points: 8
• Assignee: Anand Mazumdar
• Reporter: Anand Mazumdar
• Shepherd: Vinod Kone
• Created: 01/Oct/15 16:54
• Updated: 26/Nov/18 12:20
• Resolved: 26/Nov/18 12:20

Description

Currently, the scheduler library sends calls in order by chaining them and sending them only when it has received a response for the earlier call. This was done because there was no HTTP Pipelining abstraction in Libprocess process::post.

However once MESOS-3332 is resolved, we should be now able to use the new abstraction.

Issue Links

• blocks: MESOS-4686 Implement master failover tests for the scheduler library.
• is related to: MESOS-4858 Make changes to executor v1 library around managing connections.