[ 
https://issues.apache.org/jira/browse/FLINK-29847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daren Wong updated FLINK-29847:
-------------------------------
    Description: 
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]

  was:
Kubernetes operator currently uploadJar always even when the same JAR has been 
uploaded to JM previously. For example, this occurs during rollback or suspend 
and 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]


> 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
>             Fix For: kubernetes-operator-1.3.0
>
>
> 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)

Reply via email to