# Node ct restriction

**URL:** <https://community.openpbs.org/t/node-ct-restriction/3678>\
**Category:** Users/Site Administrators\
**Created:** [October 3, 2023, 8:52pm UTC](https://community.openpbs.org/t/node-ct-restriction/3678 "2023-10-03T20:52:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![krak3nnn](https://avatars.discourse-cdn.com/v4/letter/k/e9c0ed/32.png) [@krak3nnn](https://community.openpbs.org/u/krak3nnn)\
**Post date:** [October 3, 2023, 8:52pm UTC](https://community.openpbs.org/t/node-ct-restriction/3678/1 "2023-10-03T20:52:59Z")

</div>

I have a queue setup with a handful of nodes and I’m trying to set it up in a way where one user can request and execute on a single node. I’ve been able to do this with these queue attributes:

set queue batch resources\_max.nodect = 1  
set queue batch resources\_max.nodes = 1

This seems to work if I request nodes with “-l nodes”. If I select 1, the job goes through, if I select 2, it errors out. However, I’ve noticed that by running “-l select=2”, two nodes are allocated. Is this expected behavior? Any way to limit the “select” attribute?

Thanks!

---

<div class="post-metadata">

**Author:** ![adarsh](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@adarsh](https://community.openpbs.org/u/adarsh)\
**Post date:** [October 6, 2023, 8:08am UTC](https://community.openpbs.org/t/node-ct-restriction/3678/2 "2023-10-06T08:08:14Z")

</div>

- nodect is deprecated.
- nodes is deprecated as well and instead select (chunk statement) is used
- you can write a queue job hook that updates the placement of the job to -l place=pack, so that job always uses one node, even -l select=2 . Also, have some checks where in the job gets rejected if the user is asking more resources than what is available on nodes of your cluster.