[
https://issues.apache.org/jira/browse/MESOS-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227427#comment-15227427
]
Adam B commented on MESOS-4797:
-------------------------------
Yes, the idea is that `--weights` is now used to bootstrap the cluster weights,
and after the registry has recorded the weights, operators should use the
`/weights` endpoint to update the weights. Continuing to use `--weights` after
the weights have been bootstrapped into the registry will cause a warning to be
printed, and the flag will be ignored. Upgrades should still work fine, since
any existing --weights flags will bootstrap the upgraded cluster's registry.
See http://mesos.apache.org/documentation/latest/weights/
I suppose we could add a separate flag to enable/disable dynamic weights, so
that users can continue to use the deprecated static weights feature, but I
don't know if that's necessary. What do you think?
> Add a couple of registrar tests for /weights endpoint
> -----------------------------------------------------
>
> Key: MESOS-4797
> URL: https://issues.apache.org/jira/browse/MESOS-4797
> Project: Mesos
> Issue Type: Task
> Reporter: Yongqiao Wang
> Assignee: Yongqiao Wang
> Priority: Minor
> Labels: mesosphere
> Fix For: 0.29.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
