mesos git commit: Updated framework-rate-limiting.md

[ya...@apache.org]

Repository: mesos
Updated Branches:
  refs/heads/master 6ae0f80b3 -> 3b7a6b840


Updated framework-rate-limiting.md

The configuration parameter for rate limits should be --rate_limts
rather than --rate-limits.

Review: https://reviews.apache.org/r/38256


Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/3b7a6b84
Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/3b7a6b84
Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/3b7a6b84

Branch: refs/heads/master
Commit: 3b7a6b8400dedd797e15728fc48d179ff571bec8
Parents: 6ae0f80
Author: Guangya Liu <gy...@gmail.com>
Authored: Thu Sep 10 14:17:06 2015 -0700
Committer: Jiang Yan Xu <ya...@jxu.me>
Committed: Thu Sep 10 14:17:06 2015 -0700

----------------------------------------------------------------------
 docs/framework-rate-limiting.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/mesos/blob/3b7a6b84/docs/framework-rate-limiting.md
----------------------------------------------------------------------
diff --git a/docs/framework-rate-limiting.md b/docs/framework-rate-limiting.md
index cb0bbb7..a238af1 100644
--- a/docs/framework-rate-limiting.md
+++ b/docs/framework-rate-limiting.md
@@ -11,7 +11,7 @@ In a multi-framework environment, this feature aims to protect the throughput of
 To throttle messages from a framework, the Mesos cluster operator sets a `qps` (queries per seconds) value for each framework identified by its principal (You can also throttle a group of frameworks together but we'll assume individual frameworks in this doc unless otherwise stated; see the `RateLimits` [ProtoBuf definition](https://github.com/apache/mesos/blob/master/include/mesos/mesos.proto) and the configuration notes below). The master then promises not to process messages from that framework at a rate above `qps`. The outstanding messages are stored in memory on the master.
 
 ## Rate Limits Configuration
-The following is a sample config file (in JSON format) which could be specified with the `--rate-limits` master flag.
+The following is a sample config file (in JSON format) which could be specified with the `--rate_limits` master flag.
 
     {
       "limits": [
@@ -70,4 +70,4 @@ When a framework **exceeds the capacity**, a FrameworkErrorMessage is sent back
 
 After version 0.20.0 we are going to iterate on this feature by having the master send an early alert when the message queue for this framework **starts to build up** ([MESOS-1664](https://issues.apache.org/jira/browse/MESOS-1664), consider it a "soft limit"). The scheduler can react by throttling itself (to avoid the error message) or ignoring this alert if it's a temporary burst by design.
 
-Before the early alerting is implemented we **don't recommend using the rate limiting feature to throttle production frameworks** for now unless you are sure about the consequences of the error message. Of course it's OK to use it to protect production frameworks by throttling other frameworks and it doesn't have any effect on the master if it's not explicitly enabled.
\ No newline at end of file
+Before the early alerting is implemented we **don't recommend using the rate limiting feature to throttle production frameworks** for now unless you are sure about the consequences of the error message. Of course it's OK to use it to protect production frameworks by throttling other frameworks and it doesn't have any effect on the master if it's not explicitly enabled.