[
https://issues.apache.org/jira/browse/FLINK-16547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17057792#comment-17057792
]
Kostas Kloudas commented on FLINK-16547:
----------------------------------------
Thanks for reporting this [~felixzheng]. I agree that this works only because
we use the default values and we do not advertise the config option. But do we
expect this to change and let the user specify custom file names? From the name
of the config option "internal.jobgraph-path" I can tell that the intention was
to not let the user play with it.
WDYT?
> Correct the order to write temporary files in
> YarnClusterDescriptor#startAppMaster
> ----------------------------------------------------------------------------------
>
> Key: FLINK-16547
> URL: https://issues.apache.org/jira/browse/FLINK-16547
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Reporter: Canbin Zheng
> Priority: Minor
> Fix For: 1.11.0
>
>
> Currently, in {{YarnClusterDescriptor#startAppMaster}}, we first write out
> and upload the Flink Configuration file, then start to write out the JobGraph
> file and set its name into the Flink Configuration object, the afterward
> setting is not written into the Flink Configuration file so that it does not
> take effect in the cluster side.
> Since in the client-side we name the JobGraph file with the default value of
> FileJobGraphRetriever.JOB_GRAPH_FILE_PATH option, the cluster side could
> succeed in retrieving that file.
> This ticket proposes to write out the JobGraph file before the Configuration
> file to ensure that the setting of FileJobGraphRetriever.JOB_GRAPH_FILE_PATH
> is delivered to the cluster side.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
