[
https://issues.apache.org/jira/browse/MESOS-5581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328452#comment-15328452
]
Benjamin Mahler commented on MESOS-5581:
----------------------------------------
After some discussion with [~jieyu], I left a TODO to restore the ability for
operators to express the isolator ordering. This will require us to
de-centralize the ordering constraints so that each isolator is responsible for
validating its ordering within the {{--isolation}} flag:
{code}
// TODO(bmahler): De-centralize the ordering enforcement so that
// each isolator is responsible for validating that it is
// ordered correctly within the --isolation flag. This gives the
// operator control over the isolator ordering. If the operator
// specifies an invalid ordering, it will produce an error
// during the creation of an isolator and we will inform the
// operator to adjust the --isolation flag accordingly.
{code}
> Guarantee ordering between Isolators
> ------------------------------------
>
> Key: MESOS-5581
> URL: https://issues.apache.org/jira/browse/MESOS-5581
> Project: Mesos
> Issue Type: Improvement
> Reporter: Kevin Klues
> Assignee: Kevin Klues
> Labels: isolator, mesosphere
> Fix For: 1.0.0
>
>
> Some isolators depend on other isolators. However, we currently do not have a
> generic method of expressing these dependencies. We special case the
> `filesystem/*` isolators to make sure that dependencies on them are
> satisfied, but no other dependencies can be expressed.
>
> Instead, we should use a vector to represent the pairing of isolator name to
> isolator creator function. This way, the relative dependencies between each
> isolator will be implicit in the ordering of the vector. Currently, a hashmap
> is used to hold this pairing, but this is inadequate because hashmaps are
> inherently unordered. The new implementation using a vector will ensure
> everything is processed in the order it is listed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
