[
https://issues.apache.org/jira/browse/FLINK-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976932#comment-15976932
]
ASF GitHub Bot commented on FLINK-6336:
---------------------------------------
Github user EronWright commented on a diff in the pull request:
https://github.com/apache/flink/pull/3744#discussion_r112487388
--- Diff: docs/setup/mesos.md ---
@@ -222,6 +222,8 @@ When running Flink with Marathon, the whole Flink
cluster including the job mana
`mesos.initial-tasks`: The initial workers to bring up when the master
starts (**DEFAULT**: The number of workers specified at cluster startup).
+`mesos.constraints.hard.hostattribute`: Constraints for task placement on
mesos (**DEFAULT**: None).
--- End diff --
The description seems too generic; I suggest `Constraints for task
placement on mesos based on host attributes`. An inline example would also be
nice, or at least some description of the value format.
> Placement Constraints for Mesos
> -------------------------------
>
> Key: FLINK-6336
> URL: https://issues.apache.org/jira/browse/FLINK-6336
> Project: Flink
> Issue Type: New Feature
> Components: Mesos
> Affects Versions: 1.2.0
> Reporter: Stephen Gran
> Priority: Minor
>
> Fenzo supports placement constraints for tasks, and operators expose agent
> attributes to frameworks in the form of attributes about the agent offer.
> It would be extremely helpful in our multi-tenant cluster to be able to make
> use of this facility.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
