tillrohrmann commented on a change in pull request #7356: 
[FLINK-10868][flink-yarn] Enforce maximum TMs failure rate in ResourceManagers
URL: https://github.com/apache/flink/pull/7356#discussion_r252354300
 
 

 ##########
 File path: docs/_includes/generated/mesos_configuration.html
 ##########
 @@ -27,6 +27,11 @@
             <td style="word-wrap: break-word;">-1</td>
             <td>The maximum number of failed workers before the cluster fails. 
May be set to -1 to disable this feature. This option is ignored unless Flink 
is in <a href="#legacy">legacy mode</a>.</td>
         </tr>
+        <tr>
+            <td><h5>mesos.maximum-failed-workers-per-interval</h5></td>
+            <td style="word-wrap: break-word;">-1</td>
+            <td>Maximum number of workers the system is going to reallocate in 
case of a failure in an interval.</td>
 
 Review comment:
   Is this a Mesos specific configuration? If we want to support that for all 
`ResourceManagers`, then it might be better to use a more generic configuration 
name. E.g. `resourcemanager.maximum-workers-failure-rate`.
   
   Should we combine `maximum-failed-workers-per-interval` and 
`workers-failure-rate-interval` into a `failure-rate` config option which 
defines how many workers can fail per minute or per hour?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to