You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/05/26 23:01:03 UTC
[jira] [Closed] (FLINK-8641) Move
BootstrapTools#getTaskManagerShellCommand to flink-yarn
[ https://issues.apache.org/jira/browse/FLINK-8641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot closed FLINK-8641.
---------------------------------
Resolution: Auto Closed
This issue was labeled "stale-minor" 7 ago and has not received any updates so I have gone ahead and closed it. If you are still affected by this or would like to raise the priority of this ticket please re-open, removing the label "auto-closed" and raise the ticket priority accordingly.
> Move BootstrapTools#getTaskManagerShellCommand to flink-yarn
> ------------------------------------------------------------
>
> Key: FLINK-8641
> URL: https://issues.apache.org/jira/browse/FLINK-8641
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN, Runtime / Configuration
> Affects Versions: 1.5.0
> Reporter: Chesnay Schepler
> Priority: Minor
> Labels: auto-closed
>
> I would like to move {{getTaskManagerShellCommand()}} and {{getStartCommand()}} from {{org.apache.flink.runtime.clusterframework.BootstrapTools}} in flink-runtime to flink-yarn.
> Yarn is the sole user of these methods, and both methods are directly related to the {{YARN_CONTAINER_START_COMMAND_TEMPLATE}} {{ConfigConstants}}
> We can't move this constant to {{YarnOptions}} at this point since the {{YarnOptions}} are in {{flink-yarn}}, but the above methods require the option to be accessible from {{flink-runtime}}.
> [~till.rohrmann] Do you see any problems that this move could cause?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)