Gyula Fora created FLINK-34947:
----------------------------------

             Summary: Do not scale down JM in Orphan deletion propagation and 
reduce timeout
                 Key: FLINK-34947
                 URL: https://issues.apache.org/jira/browse/FLINK-34947
             Project: Flink
          Issue Type: Improvement
          Components: Kubernetes Operator
    Affects Versions: kubernetes-operator-1.8.0
            Reporter: Gyula Fora
            Assignee: Gyula Fora
             Fix For: kubernetes-operator-1.9.0


We introduced a logic to scale down the JobManager before the task managers are 
killed to have a more graceful shutdown sequence.

Currently this is always done in native mode, but it does not make sense during 
orphan deletion propagation when the intention is to delete the FlinkDeployment 
but not the underlying resources.

Furthermore instead of using the entire deletion timeout we should reduce this 
to only use a portion of it as it's an optional step and we should always have 
keep enough time for the TM shutdown.



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

Reply via email to