You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Nicholas Jiang (Jira)" <ji...@apache.org> on 2022/04/08 14:59:00 UTC

[jira] [Commented] (FLINK-27141) Improve FlinkService#waitForClusterShutdown logic

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

Nicholas Jiang commented on FLINK-27141:
----------------------------------------

[~gyfora], are you working for this ticket? If no, I will improve the FlinkService#waitForClusterShutdown logic.

> Improve FlinkService#waitForClusterShutdown logic
> -------------------------------------------------
>
>                 Key: FLINK-27141
>                 URL: https://issues.apache.org/jira/browse/FLINK-27141
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Priority: Major
>              Labels: Starter
>             Fix For: kubernetes-operator-1.0.0
>
>
> The current waitForClusterShutdown logic has a hardcoded 60 second timeout and prints a log message after every second.
> We should improve this to make the max timeout configurable and only log a message once every 5-10 seconds to make this more reasonable.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)