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]: High available service should not curator client before LeaderLatch closing #3132

Closed
2 tasks done
Tracked by #3123
nicochen opened this issue Aug 23, 2024 · 0 comments · Fixed by #3133
Closed
2 tasks done
Tracked by #3123

[Bug]: High available service should not curator client before LeaderLatch closing #3132

nicochen opened this issue Aug 23, 2024 · 0 comments · Fixed by #3133
Labels
type:bug Something isn't working

Comments

@nicochen
Copy link
Contributor

What happened?

It obvious that leader latch should not close after curator client closing when releasing resources.
image

Affects Versions

master

What table formats are you seeing the problem on?

No response

What engines are you seeing the problem on?

No response

How to reproduce

No response

Relevant log output

No response

Anything else

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

  • I agree to follow this project's Code of Conduct
@nicochen nicochen added the type:bug Something isn't working label Aug 23, 2024
@tcodehuber tcodehuber changed the title [Bug]: Highavailable service should not curator client before LeaderLatch closing [Bug]: High available service should not curator client before LeaderLatch closing Aug 23, 2024
nicochen added a commit to nicochen/arctic that referenced this issue Aug 23, 2024
czy006 pushed a commit that referenced this issue Aug 27, 2024
…fore LeaderLatch closing (#3133)

[AMORO-3132][Bug]:High available service should not curator client before LeaderLatch closing #3132
@klion26 klion26 mentioned this issue Sep 20, 2024
28 tasks
zhoujinsong pushed a commit that referenced this issue Oct 11, 2024
…fore LeaderLatch closing (#3133)

[AMORO-3132][Bug]:High available service should not curator client before LeaderLatch closing #3132

(cherry picked from commit 79f1bea)
Signed-off-by: zhoujinsong <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
1 participant