You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Wencong Liu (Jira)" <ji...@apache.org> on 2023/04/18 08:31:00 UTC

[jira] [Commented] (FLINK-29847) Store/cache JarUploadResponseBody

    [ https://issues.apache.org/jira/browse/FLINK-29847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713475#comment-17713475 ] 

Wencong Liu commented on FLINK-29847:
-------------------------------------

Hello [~darenwkt] , I'm wondering how to identify that two jars are same?

> Store/cache JarUploadResponseBody
> ---------------------------------
>
>                 Key: FLINK-29847
>                 URL: https://issues.apache.org/jira/browse/FLINK-29847
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Daren Wong
>            Priority: Major
>
> Kubernetes operator currently uploadJar always even when the same JAR has been uploaded to JM previously. For example, this occurs during rollback and suspend-run operation.
> To improve the performance, we want to cache the JarUploadResponseBody so that in the next runJar operation, kubernetes operator will check the cache and reuse the jar if it's the same JAR. This "cache" can be as simple as storing the uploaded JarFilePath in the CR Status field.
> Ref: [https://github.com/apache/flink-kubernetes-operator/blob/main/flink-kubernetes-operator/src/main/java/org/apache/flink/kubernetes/operator/service/AbstractFlinkService.java#L188-L199]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)