You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Yan Xu (JIRA)" <ji...@apache.org> on 2014/06/23 23:50:24 UTC
[jira] [Resolved] (MESOS-1350) Initial implementation of framework
API rate limiter, taking the config via master flag
[ https://issues.apache.org/jira/browse/MESOS-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yan Xu resolved MESOS-1350.
---------------------------
Resolution: Fixed
Fix Version/s: 0.20.0
Target Version/s: 0.20.0
Resolving this ticket as all code for it has been checked in. Additional tasks/issues for FW rate limiting are tracked at MESOS-1306.
> Initial implementation of framework API rate limiter, taking the config via master flag
> ---------------------------------------------------------------------------------------
>
> Key: MESOS-1350
> URL: https://issues.apache.org/jira/browse/MESOS-1350
> Project: Mesos
> Issue Type: Story
> Reporter: Yan Xu
> Assignee: Yan Xu
> Fix For: 0.20.0
>
>
> In this iteration:
> - Rate limits are configured via Master flag {{--ratelimits=config.JSON}}
> - The configuration is not persisted.
> - No online tuning for the configuration, reconfiguration is through Master restart with new flags.
> * Create a protobuf for configuration and read through master flags (2)
> * Integrate rate limiter into the master (5)
> * Add new tests for rate limiter (3)
> * Convert all existing tests to use rate limiter (20)
--
This message was sent by Atlassian JIRA
(v6.2#6252)