Highlighted

Maxuproc not get updated even after reboot

Hi,

Got a update to change the "maxuproc for wt82369 by 1.5 times" , While verifying we make necessary modification on the Global (wt81958).

Normally  there is a relation between max_nprocs value and  maxuproc value.

FYI..

maxuprc = max_nprocs – reserved_procs (default is 5)

 In this case we modified the max_nprocs value from 30000 to 50000

FYI..

[root@wt81958 GLOBAL] /etc # cat /etc/system | grep max_nprocs                                                                                          
set max_nprocs=50000

After the global zone reboot the value is not updated while we hit sysdef

[root@wt81958 GLOBAL] /root # sysdef | grep processes
   30000        maximum number of processes (v.v_proc)
   29995        maximum processes per user id (v.v_maxup)

Can anyone please assist us  if any thing we missed in this to make the necessary changes to replicate.

Awaiting for your valuable suggestions.

 

Thanks,

senthilsam

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Solaris/OS related problem as

Solaris/OS related problem as Marianne mentioned ie: not Storage Foundation related.

... however, the following details from the Solaris Tunable Parameters Reference Manual may assist (Chapter 2 Oracle Solaris Kernel Tunable Parameters - Process Sizing Parameters):

max_nprocs
http://download.oracle.com/docs/cd/E19082-01/819-2724/chapter2-8/index.html

--------------------
Validation
Yes. The value is compared to maxpid and set to maxpid if it is larger. On x86 platforms, an additional check is made against a platform-specific value. max_nprocs is set to the smallest value in the triplet (max_nprocs, maxpid, platform value). Both SPARC and x86 platforms use 65,534 as the platform value.
--------------------

pidmax
http://download.oracle.com/docs/cd/E19082-01/819-2724/chapter2-107/index.html

--------------------
Description
Specifies the value of the largest possible process ID. Valid for Solaris 8 and later releases.
pidmax sets the value for the maxpid variable. Once maxpid is set, pidmax is ignored. maxpid is used elsewhere in the kernel to determine the maximum process ID and for validation checking.
Any attempts to set maxpid by adding an entry to the /etc/system file have no effect.

[...]
Default
30,000

[...]
Implicit
max_nprocs range checking ensures that max_nprocs is always less than or equal to this value.

When to Change
Required to enable support for more than 30,000 processes on a system.
--------------------

see also: Solaris 10 - Increasing Number of Processes Per User
http://blogs.oracle.com/hasham/entry/solaris_10_increasing_number_of

If this is unclear / still have problems updating the values, you should contact Oracle/Solaris support for further details.

View solution in original post

3 Replies
Highlighted

Your problem seems to be

Your problem seems to be OS-related and not Storage Foundation, right?

Highlighted
Accepted Solution!

Solaris/OS related problem as

Solaris/OS related problem as Marianne mentioned ie: not Storage Foundation related.

... however, the following details from the Solaris Tunable Parameters Reference Manual may assist (Chapter 2 Oracle Solaris Kernel Tunable Parameters - Process Sizing Parameters):

max_nprocs
http://download.oracle.com/docs/cd/E19082-01/819-2724/chapter2-8/index.html

--------------------
Validation
Yes. The value is compared to maxpid and set to maxpid if it is larger. On x86 platforms, an additional check is made against a platform-specific value. max_nprocs is set to the smallest value in the triplet (max_nprocs, maxpid, platform value). Both SPARC and x86 platforms use 65,534 as the platform value.
--------------------

pidmax
http://download.oracle.com/docs/cd/E19082-01/819-2724/chapter2-107/index.html

--------------------
Description
Specifies the value of the largest possible process ID. Valid for Solaris 8 and later releases.
pidmax sets the value for the maxpid variable. Once maxpid is set, pidmax is ignored. maxpid is used elsewhere in the kernel to determine the maximum process ID and for validation checking.
Any attempts to set maxpid by adding an entry to the /etc/system file have no effect.

[...]
Default
30,000

[...]
Implicit
max_nprocs range checking ensures that max_nprocs is always less than or equal to this value.

When to Change
Required to enable support for more than 30,000 processes on a system.
--------------------

see also: Solaris 10 - Increasing Number of Processes Per User
http://blogs.oracle.com/hasham/entry/solaris_10_increasing_number_of

If this is unclear / still have problems updating the values, you should contact Oracle/Solaris support for further details.

View solution in original post

Highlighted

Re: Maxuproc not get updated even after reboot

  So, in order to set the max per user processes in this scenario, we were required to make the changes to "pidmax" (upper cap), maxusers, max_nprocs & maxuprc   in /etc/system & reboot the server.

 

set pidmax=60000
set maxusers = 4096
set maxuprc = 50000
set max_nprocs = 50000