modify log level

[Wang-Kai]

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.

[volcano-sh-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign shinytang6
You can assign the PR to them by writing /assign @shinytang6 in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• pkg/scheduler/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[volcano-sh-bot]

@Wang-Kai: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.