[
https://issues.apache.org/jira/browse/FLINK-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16908028#comment-16908028
]
vinoyang commented on FLINK-13694:
----------------------------------
[~till.rohrmann] Done. Although I want to make {{HADOOP_USER_NAME}}
configurable, that is just a reason I found {{HadoopUserOverlay}}. My goal is
still to refactor the configuration with {{ContainerOverlay}}, so I did not
mention the {{HADOOP_USER_NAME}} in the description. It would be better either
to use a unified abstract or to move {{ContainerOverlay}} into Flink on Mesos
module.
> Refactor Flink on YARN configuration with relavent overlay classes to make
> hadoop user name env configurable
> ------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-13694
> URL: https://issues.apache.org/jira/browse/FLINK-13694
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Reporter: vinoyang
> Priority: Major
>
> Our platform needs to provide a centralized submitter. We need to provide a
> customized env variable {{HADOOP_USER_NAME}}, it is hardcoded in
> {{ApplicationYarnClusterDescriptor}} :
> {code:java}
> appMasterEnv.put(YarnConfigKeys.ENV_HADOOP_USER_NAME,
> UserGroupInformation.getCurrentUser().getUserName());
> {code}
>
> There is an abstract layer beyond special deployment named
> {{ContainerOverlay}}.
> However, currently, only Flink on Mesos used this mechanism. Flink on YARN
> still used some trivial configuration items in
> {{AbstractYarnClusterDescriptor}}. IMO we need to use container overlay to
> refactor Flink on YARN related implementation.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
