Process Control Configuration

Use the configuration parameters in create_config.py to configure the MATRIXX process behavior, including NFS monitoring, service start up and shut down timeouts, heartbeat timeout, and the number of attempts to try restarting a server after it fails.

MATRIXX Process Configuration Parameters lists the information required to configure the MATRIXX processes and the server response behavior.

For more information about the MATRIXX environment variables, see the discussion about container directories and environment variables in MATRIXX Installation and Upgrade.

Table 1. MATRIXX Process Configuration Parameters
Parameter Description Default Value
Process Controller Priority To receive all the MATRIXX process heartbeats, the Process Controller must run at a higher priority. Otherwise, a heartbeat might be missed due to process scheduling. MATRIXX Support recommends that you answer y.

create_config.info question: Do you want "process control" to run at a higher priority (y/n)?

y
Service Start-up Timeout The number of seconds to wait for a MATRIXX process to start before restarting the blade.

create_config.info question: What is the service startup timeout in seconds?

180
Service Shutdown Timeout The number of seconds to wait for a MATRIXX process to shutdown before forcing it to shutdown.

create_config.info question: What is the service shutdown timeout in seconds?

30
Service Heartbeat Timeout The number of seconds to wait for a MATRIXX process heartbeat before considering it a failure and stopping the MATRIXX blade.

create_config.info question: What is the service heartbeat timeout in seconds?

 2
Maximum Number of Retry Attempts The maximum number of times to attempt restarting a server after it fails.

create_config.info question: What is the maximum number of times you want retry restarting the engine after a failure?

 0
Maximum Amount of Time Between Restart Attempts The maximum amount of time, in seconds, to wait between restart attempts after a server fails.

create_config.info question: What is the maximum number of seconds you want to retry restarting the engine after a failure?

 180
Minimum Amount of Time Between Reboot Attempts The minimum number of time, in seconds, to wait between operating system reboot attempts after a server in a MATRIXX Engine has failed.

create_config.info question: What is the minimum number of seconds you want between blade reboots?

 0
Process Controller Resource Agent The resource agent quarantines corrupt data that caused a seg fault on a blade, which prohibits the data from propagating across the cluster and causing the engine to fail. This also prohibits the peer cluster from getting corrupted with the toxic data, resulting in a complete system failure.

create_config.info question: What is the name of the resource agent to be used by process control?

 ${MTX_BIN_DIR}/resource_agent.d/process_ctrl_agent
Process Controller Advanced Options If you answer yes, the script asks whether you want to make the following configuration options:
  • Set any MATRIXX processes not to run, for example, SNMP.
  • Specify extra runtime options for any MATRIXX processes.

create_config.info question: Do you want to specify process control advanced options (y/n)?

 n
Default Input Queue Sizes Do not change the input queue sizes for all MATRIXX processes unless a MATRIXX configuration expert instructs you to do so. Wrong values can affect the operation of the system. For more information, see the discussion about default input queue sizes.

create_config.info questions:

  • Do you want to use the default input queue sizes (y/n)?
  • Do you want to use the default input queue sizes for the camel_gateway (y/n)? (only if Network Enabler is installed).
  • Do you want to use the default input queue sizes for the charging_server (y/n)?
  • Do you want to use the default input queue sizes for the cluster_manager (y/n)?
  • Do you want to use the default input queue sizes for the diameter_gateway (y/n)?
  • Do you want to use the default input queue sizes for the event_loader (y/n)?
  • Do you want to use the default input queue sizes for the mdc_gateway (y/n)?
  • Do you want to use the default input queue sizes for the price_loader_app (y/n)?
  • Do you want to use the default input queue sizes for the task_manager (y/n)?
  • Do you want to use the default input queue sizes for the test_app (y/n)?
  • Do you want to use the default input queue sizes for the transaction_server (y/n)?
 y
Default Number of Threads The default number of threads to use for each service task. For the Charging Server, only the upgrade task can have multiple threads. For more information, see the discussion about the default number of threads.
create_config.info question:
  1. Do you want to use the default number of threads (y/n)?
    To change the number of threads used by a service task, answer n (no) to this question, and then answer y when asked to change the number of threads for the service.
    Note: Some messages involve multiple transactions, and each transaction is treated separately. The following configuration questions ensure that each transaction in a message is protected.
    If the answer to question #1 yes (default), questions #2 through #5 use their defaults.
  2. Do you want to use the default number of threads for the charging_server (y/n)?

    If the answer is yes (default), questions #3 through #5 use their defaults.

  3. Service charging_server:Task upgrade_task:How many threads do you want for this task?

    This must be a positive integer and the default is 10.

  4. Service charging_server:Task upgrade_task:How many unresponsive threads may be quarantined?

    This can be an absolute number from 0-N, where N is the answer to #3. Or it can be a percentage (0%-100%) of N, rounded up (not rounded to the nearest - so 2.1 rounds up to 3). The default is 25%. An amount of 0 (or 0%) disables this feature.

  5. Service charging_server:Task upgrade_task:How many milliseconds before quarantining an unresponsive thread?

    The default is 10000ms (10 seconds). An amount of 0 disables this feature.