-
Notifications
You must be signed in to change notification settings - Fork 638
Disable coordinator if no ingress tasks #472
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
Disable coordinator if no ingress tasks #472
Conversation
…oordinator-if-no-ingress-tasks_new
…oordinator-if-no-ingress-tasks_new
Note This is an automated comment that will be appended during run. 🔴 linux-x86_64-relwithdebinfo: some tests FAILED for commit 9c859c9.
🔴 linux-x86_64-release-asan: some tests FAILED for commit 9c859c9.
|
@@ -103,6 +103,12 @@ void TCheckpointCoordinator::Handle(NYql::NDqs::TEvReadyState::TPtr& ev) { | |||
AllActorsSet.insert(actorId); | |||
} | |||
|
|||
CC_LOG_I("ActorsToTrigger count: " << ActorsToTrigger.size() << ", ActorsToNotify count: " << ActorsToNotify.size() << ", ActorsToWaitFor count: " << ActorsToWaitFor.size()); |
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.
- Do we need to use info instead of debug in this case? And the same below.
- If we have different sources in the same graph ("PgSource", "S3Source") will it work fine?
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.
- Changed to debug
- I think yes, S3Source just not added to ActorsToTrigger (not tested)
…rdinator-if-no-ingress-tasks_new
@kardymonds Кажется, эти изменения сломали кучу тестов. Если так, откатите, пожалуйста. |
This reverts commit 7c308ff.
Do nothing if there is no one to send barriers,
before this fix log was:
Checkpoint successfully created, going to inject barriers to 0 actor(s)