[jira] [Updated] (MESOS-4007) Persist non-default weights information to registry

["Yongqiao Wang (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MESOS-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yongqiao Wang updated MESOS-4007:
---------------------------------
       Assignee: Yongqiao Wang  (was: Yongqiao Wang)
    Description: 
To consider the Mesos master recovery and failover case, Mesos master needs to persist the non-default weights information in registry: 
- In the first boot, the first leading master initialize the weights replicated log with the specified by command-line flags(--weights). The flags values are only useful to bootstrap the cluster, after which point the registry becomes the source of truth.

- At runtime, the weights replicated log can only be updated by /weight.

- For Mesos master restart/failover case, if the replicated log for roles/weights has exist, and then it prefers to use the registry values and ignore the flags (--weights), and also log a warning in Mesos master that the flags values are being ignored.

The `--weights` flag is now considered deprecated and will be removed in a future.
version of Mesos.


  was:
To consider the Mesos master recovery and failover case, Mesos master needs to persist the roles and weights information in registry: 
- In the first boot, the first leading master initialize the replicated log with the roles/weights specified by command-line flags(--roles and --weights). The flags values are only useful to bootstrap the cluster, after which point the registry becomes the source of truth.

- At runtime, the replicated log can only be updated to add/remove/update entries by the operator REST API.

- For Mesos master restart/failover case, if the replicated log for roles/weights has exist, and then it prefers to use the registry values and ignore the flags (--roles/--weights), and also log a warning in Mesos master that the flags values are being ignored.

- For the future works, we can educate end users to create the replicated log to initialize the supported roles/weights before Mesos cluster bootstrap, and reset roles/weights configurations by update the replicated log.


        Summary: Persist non-default weights information to registry  (was: Persist role information to registry)

> Persist non-default weights information to registry
> ---------------------------------------------------
>
>                 Key: MESOS-4007
>                 URL: https://issues.apache.org/jira/browse/MESOS-4007
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Yongqiao Wang
>            Assignee: Yongqiao Wang
>
> To consider the Mesos master recovery and failover case, Mesos master needs to persist the non-default weights information in registry: 
> - In the first boot, the first leading master initialize the weights replicated log with the specified by command-line flags(--weights). The flags values are only useful to bootstrap the cluster, after which point the registry becomes the source of truth.
> - At runtime, the weights replicated log can only be updated by /weight.
> - For Mesos master restart/failover case, if the replicated log for roles/weights has exist, and then it prefers to use the registry values and ignore the flags (--weights), and also log a warning in Mesos master that the flags values are being ignored.
> The `--weights` flag is now considered deprecated and will be removed in a future.
> version of Mesos.



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