[FLINK-26655] Improve the observe logic in SessionObserver

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Labels: pull-request-available
• Assignee: Biao Geng
• Reporter: Biao Geng
• Created: 15/Mar/22 14:51
• Updated: 19/Mar/22 08:14
• Resolved: 19/Mar/22 08:14

Description

We now consider that JM pod can have 2 possible states after launching:

1. JM is launched but port is not ready.
2. 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.

 

Following the discussion in PR 62, we currently discard isJobManagerServing and use the isJobManagerPortReady together with a call to `flinkService.listJobs()`to make sure job manager can serve rest call correctly. The original question of this jira is solved.
Now I adjust this jira to track the improvement of the observe logic in SessionObserver due to the review comments.

Issue Links

• links to: GitHub Pull Request #82