[
https://issues.apache.org/jira/browse/FLINK-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746029#comment-15746029
]
Chesnay Schepler edited comment on FLINK-5322 at 12/13/16 7:35 PM:
-------------------------------------------------------------------
yes, we can adjust the configuration documentation.
was (Author: zentol):
yes, we can adjust the configuration.
> Clean up yarn configuration documentation
> -----------------------------------------
>
> Key: FLINK-5322
> URL: https://issues.apache.org/jira/browse/FLINK-5322
> Project: Flink
> Issue Type: Improvement
> Components: Documentation, YARN
> Environment: Flink 1.1.3 on AWS EMR emr-5.2.0 (Hadoop "Amazon 2.7.3")
> Reporter: Shannon Carey
> Assignee: Chesnay Schepler
> Priority: Trivial
> Fix For: 1.1.3
>
>
> The value I specified in flink-conf.yaml
> {code}
> yarn.taskmanager.env:
> MY_ENV: test
> {code}
> is not available in {{System.getenv("MY_ENV")}} from the plan execution
> (execution flow of main method) nor from within execution of a streaming
> operator.
> Interestingly, it does appear within the Flink JobManager Web UI under Job
> Manager -> Configuration.
> --------------------------
> The yarn section of the configuration page should be cleaned up a bit. The
> "yarn.containers.vcores" parameter is listed twice, the example for
> "yarn.application-master.env" is listed as a separate parameter and the
> "yarn.taskmanager.env" description indirectly references another parameter
> ("same as the above") which just isn't maintainable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
