[
https://issues.apache.org/jira/browse/MESOS-5833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neil Conway updated MESOS-5833:
-------------------------------
Fix Version/s: 1.0.0
> Disable strict registry
> -----------------------
>
> Key: MESOS-5833
> URL: https://issues.apache.org/jira/browse/MESOS-5833
> Project: Mesos
> Issue Type: Improvement
> Components: master
> Reporter: Neil Conway
> Assignee: Neil Conway
> Priority: Blocker
> Labels: mesosphere
> Fix For: 1.0.0
>
>
> I'd like to propose that we disable the {{--registry_strict}} master flag for
> Mesos 1.0.0.
> Rationale:
> * This feature has always been marked as experimental and sparsely documented.
> * The strict registry will no longer be relevant once support for
> partition-aware frameworks is introduced (MESOS-4049).
> * If we can assume that no frameworks are assuming the strict-registry
> behavior, we can simplify the design/implementation of MESOS-4049. It also
> makes the system's current behavior easier to explain, and makes the current
> LOST behavior more similar to the proposed UNREACHABLE behavior in MESOS-4049.
> Note that if we disable the {{--registry_strict}} flag but keep the code (for
> now), we can always re-enable the feature if any users complain. However, a
> recent email to the {{user}} and {{dev}} lists did not result in anyone
> volunteering that they are using the strict registry.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
