You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Mariusz Wojakowski (JIRA)" <ji...@apache.org> on 2017/02/14 18:30:42 UTC

[jira] [Commented] (FLINK-5253) Remove special treatment of "dynamic properties"

    [ https://issues.apache.org/jira/browse/FLINK-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866340#comment-15866340 ] 

Mariusz Wojakowski commented on FLINK-5253:
-------------------------------------------

I have 2 questions:
* should we store these dynamic properties in _flink-conf.yaml_ and completely remove that information from cluster descriptor? (Correct me if I'm wrong)
* do we want to completely remove that special handling? I’m thinking about existing implementation that setup Flink on Yarn (’yarn-sessions’).

> Remove special treatment of "dynamic properties"
> ------------------------------------------------
>
>                 Key: FLINK-5253
>                 URL: https://issues.apache.org/jira/browse/FLINK-5253
>             Project: Flink
>          Issue Type: Sub-task
>          Components: YARN
>         Environment: {{flip-6}} feature branch
>            Reporter: Stephan Ewen
>              Labels: flip-6
>
> The YARN client accepts configuration keys as command line parameters.
> Currently these are send to the AppMaster and TaskManager as "dynamic properties", encoded in a special way via environment variables.
> The mechanism is quite fragile. We should simplify it:
>   - The YARN client takes the local {{flink-conf.yaml}} as the base.
>   - It overwrite config entries with command line properties when preparing the configuration to be shipped to YARN container processes (JM / TM)
>   - No additional handling neccessary



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)