Bug 2039187 - increasing the thread limits within a pod - PodPidsLimit
Summary: increasing the thread limits within a pod - PodPidsLimit
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.8
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Swarup Ghosh
QA Contact: Sunil Choudhary
URL:
Whiteboard:
Depends On: 1844447
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-11 07:35 UTC by Catherine_H
Modified: 2022-05-05 14:48 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1844447
Environment:
Last Closed: 2022-05-05 14:48:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RFE-2692 0 None None None 2022-04-07 19:36:38 UTC
Red Hat Knowledge Base (Solution) 5366631 0 None None None 2022-03-01 17:02:52 UTC

Comment 5 Dan Seals 2022-03-07 18:35:08 UTC 
I have a case that is hitting this bug as well.
OCP 4.8.21
~~~
 - lastTransitionTime: "2022-02-23T19:37:42Z"
    message: 'Error: invalid PidsLimit -1'
    status: "False"
    type: Failure
~~~
Comment 8 Swarup Ghosh 2022-03-09 09:56:32 UTC 
The PidsLimit in ContainerRuntimeConfig have undergone some changes since 4.8. As a contrary, the value of PidsLimit must be a number greater than 20 [1] for it to be valid. So, using "pidsLimit: -1" is not actually allowed.

However, it also does seem like there is no upper bound on this limit and setting a very high value should suffice the actual use cases in concern.

[1] https://github.com/openshift/machine-config-operator/blob/release-4.7/pkg/controller/container-runtime-config/helpers.go#L437-L439
Note You need to log in before you can comment on or make changes to this bug.