[jira] [Updated] (FLINK-13694) Refactor Flink on YARN configuration with relavent overlay classes to make hadoop user name env configurable
[
https://issues.apache.org/jira/browse/FLINK-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-13694:
---
Priority: Minor (was: Major)
> 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: Minor
> Labels: auto-deprioritized-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
(v8.3.4#803005)
[jira] [Updated] (FLINK-13694) Refactor Flink on YARN configuration with relavent overlay classes to make hadoop user name env configurable
[
https://issues.apache.org/jira/browse/FLINK-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-13694:
---
Labels: auto-deprioritized-major (was: stale-major)
> 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
> Labels: auto-deprioritized-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
(v8.3.4#803005)
[jira] [Updated] (FLINK-13694) Refactor Flink on YARN configuration with relavent overlay classes to make hadoop user name env configurable
[
https://issues.apache.org/jira/browse/FLINK-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-13694:
---
Labels: stale-major (was: )
> 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
> Labels: stale-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
(v8.3.4#803005)
[jira] [Updated] (FLINK-13694) Refactor Flink on YARN configuration with relavent overlay classes to make hadoop user name env configurable
[
https://issues.apache.org/jira/browse/FLINK-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
vinoyang updated FLINK-13694:
-
Summary: Refactor Flink on YARN configuration with relavent overlay classes
to make hadoop user name env configurable (was: Refactor Flink on YARN
configuration with relavent overlay classes)
> 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)
[jira] [Updated] (FLINK-13694) Refactor Flink on YARN configuration with relavent overlay classes
[
https://issues.apache.org/jira/browse/FLINK-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
vinoyang updated FLINK-13694:
-
Description:
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.
was:
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.
> Refactor Flink on YARN configuration with relavent overlay classes
> --
>
> 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)
