[ 
https://issues.apache.org/jira/browse/FLINK-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16173649#comment-16173649
 ] 

ASF GitHub Bot commented on FLINK-7486:
---------------------------------------

Github user EronWright commented on a diff in the pull request:

    https://github.com/apache/flink/pull/4628#discussion_r140022455
  
    --- Diff: 
flink-mesos/src/main/java/org/apache/flink/mesos/runtime/clusterframework/LaunchableMesosWorker.java
 ---
    @@ -155,7 +155,7 @@ public int getPorts() {
     
                @Override
                public List<? extends VMTaskFitnessCalculator> 
getSoftConstraints() {
    -                   return null;
    +                   return params.softConstraints();
    --- End diff --
    
    Let's pass the soft constraints to the launchable mesos worker in its 
constructor, rather than fetching them from the params.    The params aren't a 
good vehicle for this information.


> flink-mesos: Support for adding unique attribute / group_by attribute 
> constraints
> ---------------------------------------------------------------------------------
>
>                 Key: FLINK-7486
>                 URL: https://issues.apache.org/jira/browse/FLINK-7486
>             Project: Flink
>          Issue Type: Improvement
>          Components: Mesos
>    Affects Versions: 1.3.2
>            Reporter: Bhumika Bayani
>            Assignee: Bhumika Bayani
>
> In our setup, we have multiple mesos-workers. Inspite of this, flink 
> application master most of the times ends up spawning all task-managers on 
> same mesos-worker.
> We intend to ensure HA of task managers. We would like to make sure each 
> task-manager is running on different mesos-worker as well as such 
> mesos-worker which does not share the AZ attribute with earlier task manager 
> instances.
> Netflix-fenzo supports adding UniqueHostAttribute and BalancedHostAttribute 
> contraints. Flink-mesos should also enable us to add these kind of 
> constraints.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to