[MESOS-3343] Rate Limiting functionality for HTTP Frameworks

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: mesosphere
• Epic Link: Scheduler API v1 improvements
• Story Points: 5
• Assignee: Unassigned
• Reporter: Anand Mazumdar
• Shepherd: Vinod Kone
• Created: 31/Aug/15 20:57
• Updated: 16/Mar/17 01:07

Description

We need to build rate limiting functionality for frameworks connecting via the Scheduler HTTP API similar to the PID based frameworks.

Link to the rate-limiting section from design doc:
https://docs.google.com/document/d/1pnIY_HckimKNvpqhKRhbc9eSItWNFT-priXh_urR-T0/edit#heading=h.kzgdk4d5fmba

• This ticket deals with refactoring the existing PID based framework functionality and extend it for HTTP frameworks.
• The second part of notifying the framework when rate-limiting is active i.e. returning a status of 429 can be undertook as part of MESOS-1664

Issue Links

• relates to: MESOS-1664 Inform framework when rate limiting is active