Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] [Registration Center] The 'Flink Instance' cannot be updated properly #3053

Closed
2 of 3 tasks
leeoo opened this issue Jan 24, 2024 · 1 comment · Fixed by #3070
Closed
2 of 3 tasks

[Bug] [Registration Center] The 'Flink Instance' cannot be updated properly #3053

leeoo opened this issue Jan 24, 2024 · 1 comment · Fixed by #3070
Assignees
Labels
Bug Something isn't working
Milestone

Comments

@leeoo
Copy link
Contributor

leeoo commented Jan 24, 2024

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

Env: Dinky 1.0.0-rc3

There is an old flink-instance with jobManager address 192.168.200.179:8081 (1.18.0 standalone HA) , I update it with new jobManager address 192.168.200.167:8081 (1.18.1 standalone HA), then I see it still show me with the old jobManager address even if after clicking [Heartbeat] button.

4493b5ef8f8d40830c3617cf163d0f9

fcb69ab361f1eaa9a940d74163249e4

34b44475a37577347e18ba6fbba3933

a4f79f2a952eb32b420c3952eab89cc

8e6d1b1a3a4d7dcb0fcb6a891f4cbed

What you expected to happen

The 'Flink Instance' can be updated properly.

How to reproduce

  1. Registration Center -> Cluster -> Flink, create a flink cluster instance with Flink 1.18.0 jobManager HA address (e.g. 192.168.200.179:8081).
  2. Edit above flink cluster instance, update it with Flink 1.18.1 jobManager HA address (e.g. 192.168.200.167:8081).
  3. See the flink cluster instance info, even after clicking [Heartbeat] button.

Note that the two jobManagers above-mentioned are not belong to a flink cluster, they are just two flink clusters with different flink version.

Anything else

No response

Version

1.0.0

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@gaoyan1998
Copy link
Contributor

#3070

@aiwenmo aiwenmo moved this to Done in Dinky Roadmap Mar 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
Archived in project
4 participants