mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bannier (JIRA)" <>
Subject [jira] [Commented] (MESOS-7757) Update master to handle updates to agent total resources
Date Tue, 10 Oct 2017 21:59:00 GMT


Benjamin Bannier commented on MESOS-7757:

Commit: a3faf6cf854cd64271bff7246ace13acfa37e731 [a3faf6c]
Author: Benjamin Bannier
Date: 10 October 2017 at 11:36:48 GMT-7
Committer: Alexander Rukletsov

Reverted 2af9a5b07dc80151154264e974d03f56a1c25838.

The changes from 2af9a5b07dc80151154264e974d03f56a1c25838 introduced a
race between 'CheckpointResourcesMessage' and changes to agent total
resources via 'UpdateSlaveMessage' which needs to be addressed before
this change can go in.


> Update master to handle updates to agent total resources
> --------------------------------------------------------
>                 Key: MESOS-7757
>                 URL:
>             Project: Mesos
>          Issue Type: Task
>          Components: master
>            Reporter: Benjamin Bannier
>            Assignee: Benjamin Bannier
>              Labels: mesosphere, storage
>             Fix For: 1.4.0
> With MESOS-7755 we update the allocator interface to support updating the total resources
on an agent. These allocator invocations are driven by the master when it receives an update
the an agent's total resources.
> We could transport the updates from agents to the master either as update to {{UpdateSlaveMessage}},
e.g., by adding a {{repeated Resource total}} field; in order to distinguish updates to {{oversubscribed}}
to updates to {{total}} we would need to introduce an additional tag field (an empty list
of {{Resource}} has the same representation as an absent list of {{Resource}}). Alternatively
we could introduce a new message transporting just the update to {{total}}; it should be possible
to reuse such a message for external resource providers which we will likely add at a later

This message was sent by Atlassian JIRA

View raw message