[
https://issues.apache.org/jira/browse/FLINK-16547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17059349#comment-17059349
]
Canbin Zheng commented on FLINK-16547:
--------------------------------------
Hi [~kkl0u]. I agree that we don't expose this config option to the users.
Actually in the native k8s per-job deployment, internally we set the
"internal.jobgraph-path" to the absolute path of the file in Pod instead of
using the default value.
For the case of YARN deployment, the default value works quite well. But would
it be good to respect the config option on the cluster side for long-term
maintenance?
It‘s not a necessary improvement for me and of course, we could close this
ticket to remain what it is.
> 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)
