trafodion-codereview mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From selvaganesang <...@git.apache.org>
Subject [GitHub] trafodion pull request #1449: RMS infrastructure now reads the configured pi...
Date Fri, 16 Feb 2018 16:02:04 GMT
GitHub user selvaganesang opened a pull request:

    https://github.com/apache/trafodion/pull/1449

    RMS infrastructure now reads the configured pid Max from /proc/sys/ke…

    …rnel/pid_max
    
    but limits it to a maximum of 128K. It can be overridden by "PID_MAX" environment
    variable in ms.env.
    
    If the PID_MAX variable is set to 0, 64K is assumed to be configured pid max.
    If the PID_MAX variable is set to less than 32K, then 32K is assumed to be configured
pid max.
    
    When a SQL process has a pin greater than the configured pid max, an error message
    "Pid , is higher than the configured pid max <configured_pid>" is written to
    the SQL log file and disables RMS for those processes. Node won't be brought down.
    
    "Get Statistics for rms " shows the the configured pid max.
    
    The environment variable to set the size of RMS shared segment size is now
    changed to RMS_SHARED_SEG_SIZE_MB.
    
    genms change for controlling pid_max and rms shared segment size

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/selvaganesang/trafodion trafodion-2963

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafodion/pull/1449.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1449
    
----
commit e7624aaaf8d1cad59186c07686404c652d0eb97b
Author: selvaganesang <selva.govindarajan@...>
Date:   2018-02-16T15:56:48Z

    RMS infrastructure now reads the configured pid Max from /proc/sys/kernel/pid_max
    but limits it to a maximum of 128K. It can be overridden by "PID_MAX" environment
    variable in ms.env.
    
    If the PID_MAX variable is set to 0, 64K is assumed to be configured pid max.
    If the PID_MAX variable is set to less than 32K, then 32K is assumed to be configured
pid max.
    
    When a SQL process has a pin greater than the configured pid max, an error message
    "Pid , is higher than the configured pid max <configured_pid>" is written to
    the SQL log file and disables RMS for those processes. Node won't be brought down.
    
    "Get Statistics for rms " shows the the configured pid max.
    
    The environment variable to set the size of RMS shared segment size is now
    changed to RMS_SHARED_SEG_SIZE_MB.
    
    genms change for controlling pid_max and rms shared segment size

----


---

Mime
View raw message