[9.0] fix: disable watchdog wallclock check for remote executions#8180
Merged
fstagni merged 1 commit intoDIRACGrid:integrationfrom Apr 25, 2025
Merged
Conversation
Contributor
Author
|
It seems to work, I can see the following logs in the hotfixed |
fstagni
approved these changes
Apr 25, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For some reason, payloads executed through the
PushJobAgentare quickly killed by theWatchdogs because the CPU consumption is way below the wallclock time, which is expected as the real work is done on a remote worker node.I don't really understand why we didn't have such issues in
v8.0but the following patch should solve the problem, I am going to test it.BEGINRELEASENOTES
*WorkloadManagement
FIX: disable watchdgo wallclock check for remote executions
ENDRELEASENOTES