[
https://issues.apache.org/jira/browse/FLINK-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17202018#comment-17202018
]
Matthias commented on FLINK-5505:
---------------------------------
[~trohrmann] is this still a topic? Or can we close this issue assuming that
majority is anyway switching to Kubernetes?
> Harmonize ZooKeeper configuration parameters
> --------------------------------------------
>
> Key: FLINK-5505
> URL: https://issues.apache.org/jira/browse/FLINK-5505
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Mesos
> Affects Versions: 1.2.0, 1.3.0
> Reporter: Till Rohrmann
> Assignee: vinoyang
> Priority: Trivial
>
> Since Flink users don't necessarily know all of the Mesos terminology and a
> JobManager runs also as a task, I would like to rename some of Flink's Mesos
> configuration parameters. I would propose the following changes:
> {{mesos.initial-tasks}} => {{mesos.initial-taskmanagers}}
> {{mesos.maximum-failed-tasks}} => {{mesos.maximum-failed-taskmanagers}}
> {{mesos.resourcemanager.artifactserver.\*}} => {{mesos.artifactserver.*}}
> {{mesos.resourcemanager.framework.\*}} => {{mesos.framework.*}}
> {{mesos.resourcemanager.tasks.\*}} => {{mesos.taskmanager.*}}
> {{recovery.zookeeper.path.mesos-workers}} =>
> {{mesos.high-availability.zookeeper.path.mesos-workers}}
> What do you think [~eronwright]?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
