Skip to content
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.

P3 - ApiServer Overload when task number to much #3703

Closed
3 tasks done
yqwang-ms opened this issue Oct 10, 2019 · 3 comments
Closed
3 tasks done

P3 - ApiServer Overload when task number to much #3703

yqwang-ms opened this issue Oct 10, 2019 · 3 comments
Assignees

Comments

@yqwang-ms
Copy link
Member

yqwang-ms commented Oct 10, 2019

What would you like to be added:

Why is this needed:

Without this feature, how does the current module work:

Components that may involve changes:

Potential Solutions:

  1. Tune ApiServer to serve more QPS
    https://github.com/kubernetes/kubernetes/blob/4fb75e2f0d9a36c47edcf65f89bb92f20274ee56/cluster/gce/gci/configure-helper.sh#L1811-L1822

  2. Tune WebPortal, K8S Dashboard, FC and Runtime to send less QPS
    WebPortal control the request concurrency.
    Runtime use downward-api: https://kubernetes.io/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/#the-downward-api
    Runtime use kubelet local web server: https://applatix.com/making-kubernetes-production-ready-part-3/

  3. Cache ApiServer in RestServer

  4. RestServer throttling

Find Culprit Tests:
2000 Tasks

@yqwang-ms
Copy link
Member Author

Cannot reproduce 1k task ApiServer unresponse issue, will tune ApiServer in case future overload.

@yqwang-ms
Copy link
Member Author

Change to low priority due to cannot reproduce

@yqwang-ms yqwang-ms changed the title P0 - ApiServer Overload when task number to much P3 - ApiServer Overload when task number to much Oct 11, 2019
@fanyangCS
Copy link
Contributor

Close it. Feel free to reopen when the issue comes up again.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants