Updating ulimit settings for Teracloud® Streams

There are several ways to change ulimit settings. The examples in this procedure show one way to change the hard and soft ulimit settings for Teracloud® Streams.

Before you begin

Before you change ulimit settings, contact your system administrator.

Procedure

  1. Update the ulimit settings as user root.

    The following examples show one way to change the hard and soft settings for all users of a Teracloud® Streams resource.

    Notes:
    • If a .conf file in the following examples does not exist on your system, create the file using the same name in the example and then edit the file as shown in the example.

    • For RHEL, the files in the /etc/security/limits.d directory override the properties in the /etc/security/limits.conf configuration file.
      • By default RHEL sets some ulimit values in the limits.d file and a default file in the /etc/security/limits.d directory for the maximum user processes.

      • The filenumber in the file names in the /etc/security/limits.d directory indicates which file takes effect. The values in the file with the highest number in the name of the file are used. For example, if the /etc/security/limits.d directory contains the 21-nofile.conf and 22-nofile.conf files, the values in the 22-nofile.conf file are used.

    Examples:

    To change the open files value, use the procedure for your operating system.

    • On RHEL, add the following line to the /etc/security/limits.d/filenumber-nofile.conf file as shown in the following example:
      * - nofile open-files-value

    To change the max user processes value, use the procedure for your operating system.

    • On RHEL, add the following line to the /etc/security/limits.d/filenumber-nproc.conf file as shown in the following example:
      * - nproc max-user-processes-value

    To set the hard stack and soft stack values, use the procedure for your operating system.

    Note: The soft stack size might be too low for your Teracloud® Streams applications, especially if your applications require a large stack size. If the soft stack size is too low, PE issues can occur. Common symptoms are that the PE starts and then terminates, the PE fails to start, the PE starts but fails to reach a healthy state, or the PE starts and reaches an unknown state.
    • On RHEL, add the following lines to the /etc/security/limits.d/filenumber-stack.conf file as shown in the following example:
      
* hard stack unlimited 
* soft stack 20480

  2. For the changes to take effect:

    • If Teracloud® Streams services and applications are not running, the Teracloud® Streams user logs out and then logs into the system.

    • If Teracloud® Streams services and applications are running, use the procedure for your environment:
      • If running the domain controller service unregistered as non-root:
        1. Stop the domain.
        2. Start the domain.

      • If running the domain controller service as a registered Linux system service, or unregistered as user root:
        1. On each resource in the domain, run the streamtool stopdomainhost command.
        2. Stop the domain.
        3. On each resource in the domain, run the streamtool startdomainhost command. If running the controller unregistered, specify the --unregistered option.
        4. Start the domain.
  3. To verify that the ulimit settings are updated, use the procedure in Reviewing ulimit settings for Teracloud Streams.