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.
Modify the log level to
5
for the case when no feasible node is found.Failure to find a matching node is a very common problem. When the cluster is large enough and the number of pods is large enough, this log will be printed frequently and even drown out other valid logs. The current scheduler does not have a delay queue, and some tasks will keep printing similar logs. The default installation and deployment scheduler log level is 3. For such common scenarios, practical experience shows that level 5 is sufficient.