aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-199) It's not possible to mix limit and attribute constraints
Date Mon, 10 Feb 2014 02:15:19 GMT

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

Bill Farner commented on AURORA-199:
------------------------------------

Fwiw i believe the current behavior with a host value constraint would be to fit as many tasks
as possible.

> It's not possible to mix limit and attribute constraints
> --------------------------------------------------------
>
>                 Key: AURORA-199
>                 URL: https://issues.apache.org/jira/browse/AURORA-199
>             Project: Aurora
>          Issue Type: Bug
>          Components: Client
>            Reporter: brian wickman
>
> A user had a valid need for the following use-case:
> {noformat}
> constraints = {
>   'host': 'hostname1',
>   'host': 'limit:2'
> }
> {noformat}
> in order to pin 2 instances of a job to the same host.  Pystachio Map is a multimap but
it gets coerced to a Python dictionary when converting to a set of Thrift Constraint objects,
and the 'multi-' part of the mapping is lost.
> We should probably add a new delimiter, e.g. ';' in order to allow for mixes of limit
and attribute constraints, e.g. 'host': 'hostname1;limit:2'



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message