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

Adam B commented on MESOS-4189:
-------------------------------

I spoke to [~jvanremoortere] about committing dynamic weights in time for Mesos 
0.28, and his biggest concern was the lack of tests for the registry changes 
(MESOS-4797), since the registry is a critical and complex piece of Mesos.
Additional TODOs from my conversation with Joris:
- MESOS-4316: He'd prefer to see a GET for /weights in the same release as the 
PUT/POST. We can't change what's displayed in /roles without going through a 
deprecation cycle, but we can show the weights in both places for now.
- (no JIRA yet): Rescind all outstanding offers, to facilitate satisfying the 
updated weights. Since the current behavior requires restarting the master, all 
outstanding offers would be rescinded anyway. This can be done in a new patch. 
See how quota handles rescinding offers after updating the allocator: 
https://github.com/apache/mesos/blob/0.28.0-rc1/src/master/quota_handler.cpp#L319
- MESOS-3945: Update docs to reference the change for 0.29 instead of 0.28. The 
0.28.0-rc1 has already been cut, so any non-critical fixes/features have to 
wait until 0.29, which should only be a month away.

That said, I'll review the current patches soon so we can get them committed 
for 0.29 and work on landing the registry tests and rescind behavior asap.

> Dynamic weights
> ---------------
>
>                 Key: MESOS-4189
>                 URL: https://issues.apache.org/jira/browse/MESOS-4189
>             Project: Mesos
>          Issue Type: Epic
>            Reporter: Yongqiao Wang
>            Assignee: Yongqiao Wang
>
> Mesos current uses a static list of weights that are configured when the 
> master startup(via the --weights flag), this place some limitation about 
> change the resource allocation priority for a role/frameworks(changing the 
> set of weights requires restarting all the masters). 
> This JIRA will add a new endpoint /weight to update/show weight of a role 
> with the authorized principles, and the non-default weights will be persisted 
> in registry.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to