[
https://issues.apache.org/jira/browse/MESOS-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046015#comment-15046015
]
Qian Zhang commented on MESOS-4073:
-----------------------------------
Agree that these parameters should be exposed in a JSON file rather than master
flags, but currently hierarchical allocator is not a module yet, so if we want
it to accept a JSON file like other modules, should we make it an allocator
module first?
> Expose recovery parameters from Hierarchical allocator
> ------------------------------------------------------
>
> Key: MESOS-4073
> URL: https://issues.apache.org/jira/browse/MESOS-4073
> Project: Mesos
> Issue Type: Improvement
> Components: allocation
> Reporter: Alexander Rukletsov
> Assignee: Alexander Rukletsov
> Labels: mesosphere
>
> While implementing recovery in the hierarchical allocator, we introduced some
> internal constants that influence the recovery process:
> {{ALLOCATION_HOLD_OFF_RECOVERY_TIMEOUT}} and {{AGENT_RECOVERY_FACTOR}}. We
> should expose these parameters for operators to configure.
> However, I am a bit reluctant to expose them as master flags, because they
> are implementation specific. It would be nice to combine all hierarchical
> allocator-related flags into one (maybe JSON) file, similar to how we do it
> for modules.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
