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

[Fix-16793] WorkerGroupChangeNotifier may can not detect cluster's first time change #16796

Merged
merged 6 commits into from
Nov 14, 2024

Conversation

reele
Copy link
Contributor

@reele reele commented Nov 13, 2024

Fix #16793
-- i created a new branch, the old is broken. @SbloodyS

Brief change log

  1. add all groups to new listener when new listener added.

  2. delete DEFAULT_REFRESH_WORKER_INTERVAL , add startScheduleThread() to get the parameter from MasterConfig.

  3. add manual call startScheduleThread() in ClusterManager.start()

Verify this pull request

Pull Request Notice

Pull Request Notice

@SbloodyS SbloodyS added this to the 3.3.0 milestone Nov 13, 2024
@SbloodyS SbloodyS added the bug Something isn't working label Nov 13, 2024
Copy link
Member

@ruanwenjun ruanwenjun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, I left some comments.

@ruanwenjun
Copy link
Member

Since we use a daemon thread to detect the worker group changed, so there will always exist delay, but this delay does have a serious effect. We can broadcast a worker group changed event to all masters once the api receive a worker group changed event.

reele and others added 3 commits November 13, 2024 14:37
…ler/server/master/cluster/WorkerGroupChangeNotifier.java

Co-authored-by: Wenjun Ruan <[email protected]>
…ler/server/master/cluster/WorkerGroupChangeNotifier.java

Co-authored-by: Wenjun Ruan <[email protected]>
…ler/server/master/cluster/ClusterManager.java

Co-authored-by: Wenjun Ruan <[email protected]>
ruanwenjun
ruanwenjun previously approved these changes Nov 13, 2024
Copy link
Member

@ruanwenjun ruanwenjun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@SbloodyS SbloodyS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please run mvn spotless:apply to format the code.

@reele
Copy link
Contributor Author

reele commented Nov 13, 2024

formatted

Copy link

sonarcloud bot commented Nov 13, 2024

Copy link
Member

@SbloodyS SbloodyS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Copy link
Member

@ruanwenjun ruanwenjun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ruanwenjun ruanwenjun merged commit d07a2ed into apache:dev Nov 14, 2024
68 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.3.0 backend bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] [WorkerGroupChangeNotifier] work group listeners may can not be triggered when cluster changed
3 participants