Chesnay Schepler commented on FLINK-8641:

Yes, that would work as well. However we would need a way to pass in additional 
JVM options as {{getTaskManagerShellCommand()}} also has kerberos-specific 
paths that we ideally get out of there:
//applicable only for YarnMiniCluster secure test run
//krb5.conf file will be available as local resource in JM/TM container
if(hasKrb5) {
        javaOpts += " -Djava.security.krb5.conf=krb5.conf";

> Move BootstrapTools#getTaskManagerShellCommand to flink-yarn
> ------------------------------------------------------------
>                 Key: FLINK-8641
>                 URL: https://issues.apache.org/jira/browse/FLINK-8641
>             Project: Flink
>          Issue Type: Improvement
>          Components: Configuration, YARN
>    Affects Versions: 1.5.0
>            Reporter: Chesnay Schepler
>            Priority: Critical
> 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

Reply via email to