-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
ttl: initialize notifyStateCh in ttl job manager (#39956) #39959
ttl: initialize notifyStateCh in ttl job manager (#39956) #39959
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
37a7df8
to
5ce277b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 5ce277b
|
/run-unit-test |
This is an automated cherry-pick of #39956
Signed-off-by: YangKeao yangkeao@chunibyo.icu
What problem does this PR solve?
Issue Number: close #39955
What is changed and how it works?
Initialize the
notifyStateCh
while initializing the job manager. It'll make the recycle of scan worker much faster.Using a channel with bound 1 is good enough, as the scan worker will actually be blocked by
PollTaskResult
. If the manager didn't callPollTaskResult
, it will not be scheduled anything.