[
https://issues.apache.org/jira/browse/FLINK-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861423#comment-15861423
]
ASF GitHub Bot commented on FLINK-5712:
---------------------------------------
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/3267#discussion_r100556946
--- Diff:
flink-mesos/src/main/java/org/apache/flink/mesos/runtime/clusterframework/services/MesosServicesUtils.java
---
@@ -40,9 +41,11 @@ public static MesosServices
createMesosServices(Configuration configuration) thr
return new StandaloneMesosServices();
case ZOOKEEPER:
- final String zkMesosRootPath =
configuration.getString(
+ final String zkMesosRootPath =
ConfigurationUtil.getStringWithDeprecatedKeys(
+ configuration,
ConfigConstants.HA_ZOOKEEPER_MESOS_WORKERS_PATH,
-
ConfigConstants.DEFAULT_ZOOKEEPER_MESOS_WORKERS_PATH);
+
ConfigConstants.DEFAULT_ZOOKEEPER_MESOS_WORKERS_PATH,
+
ConfigConstants.ZOOKEEPER_MESOS_WORKERS_PATH);
--- End diff --
I think it's better if we replace this directly by a `ConfigOption`. There
you can also define deprecated keys. This is the encouraged way to read
configuration values. Take a look at `HighAvailabilityOptions` to see how it is
used.
> update several deprecated configuration options
> ------------------------------------------------
>
> Key: FLINK-5712
> URL: https://issues.apache.org/jira/browse/FLINK-5712
> Project: Flink
> Issue Type: Bug
> Components: Documentation, Mesos
> Affects Versions: 1.2.0, 1.3.0
> Reporter: Yelei Feng
> Priority: Minor
> Labels: configuration, document
> Fix For: 1.3.0
>
>
> 1. We should use 'containerized.heap-cutoff-ratio' and
> 'containerized.heap-cutoff-min' instead of deprecated yarn-specific options
> in configuration doc.
> 2. In mesos mode, we still use deprecated naming convention of zookeeper -
> 'recovery.zookeeper.path.mesos-workers'. We should make it consistent with
> other zookeeper options by using
> 'high-availability.zookeeper.path.mesos-workers'.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
