[jira] [Commented] (FLINK-26655) Merge isJobManagerPortReady and isJobManagerServing to check if JM pod can work correctly

["Yang Wang (Jira)" <ji...@apache.org>]

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

Yang Wang commented on FLINK-26655:
-----------------------------------

We might need to rethink the timeout then. Otherwise, it will take too long time when the port is not available.

> Merge isJobManagerPortReady and isJobManagerServing to check if JM pod can work correctly
> -----------------------------------------------------------------------------------------
>
>                 Key: FLINK-26655
>                 URL: https://issues.apache.org/jira/browse/FLINK-26655
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Biao Geng
>            Priority: Major
>
> We now consider that JM pod can have 2 possible states after launching:
>  # JM is launched but port is not ready.
>  # JM is launched, port is ready but rest service is not ready.
> It looks that they can be merged as what we really care is if the JM can serve REST calls correctly, not if the JM port is ready.
> With above observation, we can merge {{isJobManagerPortReady}} and {{isJobManagerServing}} to check if JM pod can serve correctly.



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