pod-update-performance

[molei20021]

If there are thousands of pending pods in cluster, pod status update may become performance bottleneck of the whole system. I add PodStatusRateLimit config including minIntervalSec, minPodNum, enable. When the pod num of cluster is greater than minPodNum(default 10000), the times of pod status update will be limited by minIntervalSec(default 60s). If the pod unscheduleable status is updated minIntervalSec ago, we will ignore status update this time until after minIntervalSec.

[volcano-sh-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: To complete the pull request process, please assign k82cn You can assign the PR to them by writing /assign @k82cn 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

[lowang-bh]

Is there a backgroup for this PR? Actually, pod will not be updated if there are no changes.

[molei20021]

Is there a backgroup for this PR? Actually, pod will not be updated if there are no changes.

Our

minIntervalSec

For example, one of the pod unscheduable reason is like "Pod %s/%s can possibly be assigned to %s" this may often change.

[volcano-sh-bot]

@molei20021: 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[bot]]

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.