Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPBUGS-13153: Limit the value of GOMAXPROCS on node-exporter. #1996

Merged
merged 1 commit into from Jun 27, 2023

Commits on Jun 20, 2023

  1. OCPBUGS-13153: Limit the value of GOMAXPROCS on node-exporter to 4.

    On nodes with multiple CPU cores, this should help avoid lock contentions
    without having any side effects, see the ticket for more details.
    
    node-exporter versions that have "--runtime.gomaxprocs" can still
    override this: the flag has precedence over this automatic setting.
    
    Make the entrypoint set the env var before runnning the process.
    Get the CPU count from /proc/cpuinfo without taking CPU affinity (via cpuset)
    into account as the container's CPU requests is not an integer, thus no
    affinity is applied.
    
    Signed-off-by: Ayoub Mrini <amrini@redhat.com>
    machine424 committed Jun 20, 2023
    Configuration menu
    Copy the full SHA
    58997b8 View commit details
    Browse the repository at this point in the history