[
https://issues.apache.org/jira/browse/MESOS-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180507#comment-15180507
]
Joris Van Remoortere commented on MESOS-4838:
---------------------------------------------
[~klaus1982] I'm not sure why we need to do this.
1. Are you seeing performance issues with the {{allocate(slaveId)}} calls
generated by the maintenance schedule?
2. If this is the case, why wouldn't the general batching proposal for the
allocator cover this case? Why do we need to implement batching in specific API
entry points?
3. If this is being suggested because a maintenance schedule tends to update
many agents simultaneously, then would it make more sense to consider calling
the batch {{allocate()}} function in the allocator after updating all the agent
availabilities?
If you are interested in considering some improvements around maintenance,
let's set up a working group. I know others are also interested in this
feature, and I know [~kaysoky] would love to help guide these discussions.
We should discuss these kinds of larger changes and ideas in terms of their
operational and development consequences before posting patches. (Though if you
just want to try it out to understand the performance implications or what code
would need to be touched that's totally fine; we just may decide to go in a
very different direction).
> Update unavailable in batch to avoid several allocate(slaveId) call
> -------------------------------------------------------------------
>
> Key: MESOS-4838
> URL: https://issues.apache.org/jira/browse/MESOS-4838
> Project: Mesos
> Issue Type: Bug
> Reporter: Klaus Ma
> Assignee: Klaus Ma
>
> In "/machine/schedule", all machines in master will trigger a
> {{allocate(slaveId)}} which will increase the workload of master. The
> proposal of this JIRA is to update unavailable in batch to avoid several
> {{allocate(slaveId)}} call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
