Github user EronWright commented on the issue:
https://github.com/apache/flink/pull/3356
@StephanEwen I agree that the YARN AM/TM has no need for dynamic properties
since the entire config file is generated per container. But there's a case
to be made that dynamic properties on the CLI makes sense for some cluster
managers. Imagine a Kubernetes deployment using a docker image with Flink
pre-installed & (mostly) pre-configured. It would make sense to pass the JM
RPC port (which Kubernetes generates on-the-fly) as a dynamic property, e.g:
```
bin/flink-jobmanager.sh -Djobmanager.rpc.port=$PORT0
```
The mesos jobmanager and taskmanager use this approach for similar reasons.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
