# Scheduler is not using all nodes... bunching/acclimating to common nodes

**URL:** <https://discourse.jupyter.org/t/scheduler-is-not-using-all-nodes-bunching-acclimating-to-common-nodes/14463>\
**Category:** JupyterHub\
**Created:** [June 2, 2022, 4:30pm UTC](https://discourse.jupyter.org/t/scheduler-is-not-using-all-nodes-bunching-acclimating-to-common-nodes/14463 "2022-06-02T16:30:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![malder](https://avatars.discourse-cdn.com/v4/letter/m/91b2a8/32.png) [@malder](https://discourse.jupyter.org/u/malder)\
**Post date:** [June 2, 2022, 4:30pm UTC](https://discourse.jupyter.org/t/scheduler-is-not-using-all-nodes-bunching-acclimating-to-common-nodes/14463/1 "2022-06-02T16:30:56Z")

</div>

We have a 15 node Kubernetes Cluster but we keep running out of resources on a random node as the scheduler is not looking for all available nodes. i.e. there are 4-5 heavily used nodes leaving the others unoccupied. We do not have any tainting set, any guidance or feedback is appreciated.  
Mike - [mike.alder@gm.com](mailto:mike.alder@gm.com)

---

<div class="post-metadata">

**Author:** ![manics](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/manics/32/85_2.png) [@manics](https://discourse.jupyter.org/u/manics)\
**Post date:** [June 2, 2022, 4:42pm UTC](https://discourse.jupyter.org/t/scheduler-is-not-using-all-nodes-bunching-acclimating-to-common-nodes/14463/2 "2022-06-02T16:42:55Z")

</div>

It sounds like the user scheduler is enabled. See [Optimizations — Zero to JupyterHub with Kubernetes documentation](https://zero-to-jupyterhub.readthedocs.io/en/stable/administrator/optimization.html) for the reasons for it, and how to disable it.

---

<div class="post-metadata">

**Author:** ![malder](https://avatars.discourse-cdn.com/v4/letter/m/91b2a8/32.png) [@malder](https://discourse.jupyter.org/u/malder)\
**Post date:** [June 2, 2022, 9:46pm UTC](https://discourse.jupyter.org/t/scheduler-is-not-using-all-nodes-bunching-acclimating-to-common-nodes/14463/3 "2022-06-02T21:46:18Z")

</div>

Thank you for your response. We believe that the scheduler is disabled. Do you know the command we can check on the cluster side to see if there is a configuration that would limit node availability? Any other thoughts on why we would have this behavior. Thank you.

---

<div class="post-metadata">

**Author:** ![minrk](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/minrk/32/13_2.png) [@minrk](https://discourse.jupyter.org/u/minrk)\
**Post date:** [June 3, 2022, 1:38pm UTC](https://discourse.jupyter.org/t/scheduler-is-not-using-all-nodes-bunching-acclimating-to-common-nodes/14463/4 "2022-06-03T13:38:15Z")

</div>

You might inspect a user pod to check if it has any pod/node affinity set.