Backport of client: move 'waiting for previous alloc to terminate' log messages to info into release/1.9.x #24809
Conversation
This file contains 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
hc-github-team-nomad-core
force-pushed
the
backport/f-waiting-for-previous-alloc-log-info/gratefully-factual-zebra
branch
from
f70529a to
f503431
Compare
pkazmierczak
approved these changes
Jan 8, 2025
pkazmierczak
deleted the
backport/f-waiting-for-previous-alloc-log-info/gratefully-factual-zebra
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport
This PR is auto-generated from #24804 to be assessed for backporting due to the inclusion of the label backport/1.9.x.
The below text is copied from the body of the original PR.
I'm not a 100% sure if this is the right move, but seeing as some users are hit by bugs that cause allocations to be stuck in
pendingstate, they are forced to run agents withdebuglog levels which is very noisy.On the other hand, having these messages at
infowill significantly increase the noise of that level. I welcome comments and opinions on whether that's the right way to handle this issue.Resolves #24788
Overview of commits