flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chesnay Schepler (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-5322) Clean up yarn configuration documentation
Date Tue, 23 Jan 2018 17:05:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chesnay Schepler updated FLINK-5322:
------------------------------------
    Fix Version/s:     (was: 1.1.5)

> 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
>    Affects Versions: 1.2.0, 1.1.3
>         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
>
> 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; instead it should be described similarly
as the application-master entry.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message