[
https://issues.apache.org/jira/browse/MESOS-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15145590#comment-15145590
]
Vinod Kone commented on MESOS-4666:
-----------------------------------
{quote}
So we want to send the total resources the slave started off with when it
registered. I do not think it exposes what other frameworks have
launched/reserved
{quote}
My concern is that if a slave has reservations (static/dynamic) for 'roleA' it
doesn't make sense (without some sort of ACLs) to send that information to a
framework that was registered with 'roleB'.
IIUC, you have two slightly orthogonal requirements
1) Two frameworks to launch tasks that are dependent on each other.
2) Needing exclusive access to a slave *dynamically* instead of static
reservations.
For 1) you can simply use dynamic reservations. Framework1 can make a
reservation for a resources required for task1 and task2. It sounds like
Framework1 already knows task2's resources out of band, which is a bit weird
but not too bad.
For 2) Why do you want exclusive access? Is it because the current isolation
(resource and security) in Mesos is not good/compliant enough or something else?
Anyway, the ability to somehow dynamically reserve a *whole* slave is an
interesting use case. For that we might have to expose the total *amount* of
resources, without exposing the reservation information.
> Expose total resources of a slave in offer for scheduling decisions
> -------------------------------------------------------------------
>
> Key: MESOS-4666
> URL: https://issues.apache.org/jira/browse/MESOS-4666
> Project: Mesos
> Issue Type: Improvement
> Components: general
> Affects Versions: 0.25.0
> Reporter: Anindya Sinha
> Assignee: Anindya Sinha
> Priority: Minor
>
> To effectively schedule certain class of tasks, the scheduler might need to
> know not only the available resources (as exposed currently) but also the
> maximum resources available on that slave. This is specifically true for
> clusters having different configurations of the slave nodes in terms of
> resources such as cpu, memory, disk, etc.
> Certain class of tasks might have a need to be scheduled on the same slave
> (esp needing shared persistent volumes, MESOS-3421). Instead of dedicating a
> slave to a framework, the framework can make a very good determination if it
> had exposure to both available as well as total resources.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
