You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
What you expected to happen
The 'Flink Instance' can be updated properly.
How to reproduce
Registration Center -> Cluster -> Flink, create a flink cluster instance with Flink 1.18.0 jobManager HA address (e.g. 192.168.200.179:8081).
Edit above flink cluster instance, update it with Flink 1.18.1 jobManager HA address (e.g. 192.168.200.167:8081).
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.
Search before asking
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.
What you expected to happen
The 'Flink Instance' can be updated properly.
How to reproduce
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?
Code of Conduct
The text was updated successfully, but these errors were encountered: