search

kubernetes-retired / poseidon

[EOL] A Firmament-based Kubernetes scheduler
http://www.firmament.io
Apache License 2.0
410 stars 79 forks source link

A question about how many pods can be scheduled at one time using poseidon. #186

Closed chauncey-77 closed 4 years ago

chauncey-77 commented 4 years ago

Hi, this is my situation: I try to schedule 300 pods at one time, but it likes that poseidon will divide the 300 pods into two part, e.g. 185 pods and 115 pods, and schedule each part alone. I want to know what factors lead to such division, and the possibility of increasing the number of pods scheduled at one time, so I read the code for a long time but have no conclusion. Please give me some tips and help, thanks.

deepak-vij commented 4 years ago

Poseidon has a scheduler loop that starts a Firmament scheduling round upon previous round’s completion. Poseidon/Firmament scheduler runs continuously and picks up however many pods are available in “Pending” state as part of the batch processing. This is all described in the Poseidon design document https://github.com/kubernetes-sigs/poseidon/blob/master/docs/design/README.md.

fejta-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

fejta-bot commented 4 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten

fejta-bot commented 4 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close

k8s-ci-robot commented 4 years ago

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/poseidon/issues/186#issuecomment-706587819): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >Send feedback to sig-testing, kubernetes/test-infra and/or [fejta](https://github.com/fejta). >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.