You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Bhumika Bayani (JIRA)" <ji...@apache.org> on 2017/07/28 10:34:00 UTC

[jira] [Commented] (FLINK-6336) Placement Constraints for Mesos

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

Bhumika Bayani commented on FLINK-6336:
---------------------------------------

Is it possible to have constraints such as  hostname:UNIQUE or az:UNIQUE?

I my case, scheduler tries to launch all the task managers on same mesos-agent in-spite of us having multiple available agents.



> 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
>            Assignee: Stephen Gran
>            Priority: Minor
>             Fix For: 1.3.0
>
>
> 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.4.14#64029)