[
https://issues.apache.org/jira/browse/FLINK-13132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16880053#comment-16880053
]
Guowei Ma commented on FLINK-13132:
-----------------------------------
This is a very interesting optimization, but I have two questions.
1）Why do you only change the yarn, according to your description, there should
be more than a yarn in your business system. Have you optimized other systems?
Could you say which systems are you switching between? Such as yarn, mesos, k8s
2） In addition, even if you change to ClassPathJobGraphRetriever, you need to
upload the application and lib jar to the server and regenerate your JobGraph.
Compared with the “client mode”, there is no advantage in time because there is
no optimization of anything, and the user may not feel any difference. Or your
business scenario has a certain speciality, could you make some further
explanations?
> Allow ClusterEntrypoints use user main method to generate job graph
> -------------------------------------------------------------------
>
> Key: FLINK-13132
> URL: https://issues.apache.org/jira/browse/FLINK-13132
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Affects Versions: 1.8.0, 1.8.1
> Reporter: Zhenqiu Huang
> Assignee: Zhenqiu Huang
> Priority: Minor
>
> We are building a service that can transparently deploy a job to different
> cluster management systems, such as Yarn and another internal system. It is
> very cost to download the jar and generate JobGraph in the client side. Thus,
> I want to propose an improvement to make Yarn Entrypoints can be configurable
> to use either FileJobGraphRetriever or ClassPathJobGraphRetriever. It is
> actually a long asking TODO in AbstractionYarnClusterDescriptor in line 834.
> https://github.com/apache/flink/blob/21468e0050dc5f97de5cfe39885e0d3fd648e399/flink-yarn/src/main/java/org/apache/flink/yarn/AbstractYarnClusterDescriptor.java#L834
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
