Parameters Related to cm_agent

log_dir

Parameter description: Specifies the directory where cm_agent logs are stored. It can be specified as an absolute path, or a path relative to $GAUSSLOG.

Value range: a string You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

Default value: log, indicating that the cm_agent log is generated in the CM directory in $GAUSSLOG.

log_file_size

Parameter description: Specifies the size of a log file. If a log file exceeds the specified size, a new one is created to record log information.

Value range: an integer ranging from 0 to 2047. The unit is MB. You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

Default value: 16 MB

log_min_messages

Parameter description: Specifies which message levels are written to the cm_agent log. Each level covers all the levels following it. The lower the level is, the fewer messages will be written into the log.

Value range: enumerated type. Valid values are debug5, debug1, log, warning, error, and fatal. You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

Default value: warning

incremental_build

Parameter description: Specifies whether a standby DN is incrementally built. If this parameter is enabled, a standby DN is incrementally built.

Value range: Boolean. The value can be on or off. You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

Default value: on

alarm_component

Parameter description: Specifies the location of the alarm component that processes alarms.

Value range: a string You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

  • If --alarm-type in the gs_preinstall script is set to 5, no third-party component is connected and alarms are written into the system_alarm log. In this case, the value of alarm_component is /opt/huawei/snas/bin/snas_cm_cmd.
  • If --alarm-type in the gs_preinstall script is set to 1, a third-party component is connected. In this case, the value of alarm_component is the absolute path of the executable program of the third-party component.

Default value: /opt/huawei/snas/bin/snas_cm_cmd

alarm_report_interval

Parameter description: Specifies the interval at which an alarm is reported. For details about how to modify this parameter, see Table 2.

Value range: a non-negative integer (unit: s)

Default value: 1

alarm_report_max_count

Parameter description: Specifies the maximum number of times an alarm is reported. For details about how to modify this parameter, see Table 2.

Value range: a non-negative integer

Default value: 1

agent_report_interval

Parameter description: Specifies the interval at which cm_agent reports the instance status.

Value range: an integer. The unit is s. You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

Default value: 1

agent_phony_dead_check_interval

Parameter description: Specifies the interval at which cm_agent checks whether the DN process is suspended.

Value range: an integer. The unit is s. You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

Default value: 10

agent_check_interval

Parameter description: Specifies the interval at which cm_agent queries for the status of instances, such as the DNs.

Value range: an integer. The unit is s. You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

Default value: 2

agent_heartbeat_timeout

Parameter description: Specifies the time to wait before the cm_server heartbeat times out.

Value range: an integer ranging from 2 to 231 – 1. The unit is second. You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

Default value: 8

agent_connect_timeout

Parameter description: Specifies the time to wait before the attempt of cm_agent to connect to cm_server times out.

Value range: an integer. The unit is s. You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

Default value: 1

agent_connect_retries

Parameter description: Specifies the number of times cm_agent tries to connect to the cm_server.

Value range: an integer. You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

Default value: 15

agent_kill_instance_timeout

Parameter description: Specifies the interval from the time when cm_agent fails to connect to the primary cm_server to the time when cm_agent kills all instances on the node.

Value range: an integer. You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

Default value: 0, indicating that the operation of killing all instances on the node is not initiated.

security_mode

Parameter description: Specifies whether DNs are started in secure mode. If this parameter is set to on, DNs are started in secure mode. Otherwise, DNs are started in non-secure mode.

Value range: Boolean. The value can be on or off. You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

Default value: off

upgrade_from

Parameter description: Specifies the internal version number of the database before an in-place upgrade. Do not modify the value of this parameter.

Value range: a non-negative integer You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

Default value: 0

process_cpu_affinity

Parameter description: Specifies whether to bind a primary DN process to a CPU core before starting the process. If this parameter is set to 0, core binding will not be performed. If it is set to another value, core binding will be performed, and the number of physical CPU cores is 2n. Restart the database and cm_agent for the modification to take effect. Only ARM is supported. For details about how to modify this parameter, see Table 2.

Value range: an integer ranging from 0 to 2

Default value: 0

log_threshold_check_interval

Parameter description: Specifies the interval for compressing and clearing logs. Logs are compressed and cleared every 1800 seconds.

Value range: an integer ranging from 0 to 2147483647. The unit is s. You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

Default value: 1800

dilatation_shard_count_for_disk_capacity_alarm

Parameter description: Specifies the number of shards to be added in the scale-out scenario. This parameter is used to calculate the threshold for reporting a disk capacity alarm.

NOTE: The parameter value must be the same as the actual number of shards to be added.

Value range: an integer ranging from 0 to 232 – 1. If this parameter is set to 0, the disk scale-out alarm is not reported. If this parameter is set to a value greater than 0, the disk scale-out alarm is reported and the threshold is calculated based on the number of shards specified by this parameter. You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

Default value: 1

log_max_size

Parameter description: Specifies the maximum size of a log file.

Value range: an integer ranging from 0 to 2147483647. The unit is MB. You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

Default value: 10240

log_max_count

Parameter description: Specifies the maximum number of logs that can be stored on hard disks.

Value range: an integer ranging from 0 to 10000. You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

Default value: 10000

log_saved_days

Parameter description: Specifies the number of days for storing logs.

Value range: an integer ranging from 0 to 1000. The unit is day. You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

Default value: 90

enable_log_compress

Parameter description: Specifies whether to enable log compression.

Value range: Boolean You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 2.

  • on indicates that log compression is enabled.
  • off indicates that log compression is disabled.

Default value: on

log_pattern_%s

Parameter description: Specifies the format of compressed logs. It is used when enable_log_compress=on is set. All logs containing the keyword %s are compressed. %s is the name of a server tool.

Value range: values of all parameters in Table 1. For details about how to modify this parameter, see Table 2.

Default value: default values of the parameters in Table 1. The default value cannot be modified.

Table 1

Parameter (log_pattern_%s)

Default Value

log_pattern_cm_ctl

cm_ctl-

log_pattern_gs_clean

gs_clean-

log_pattern_gs_ctl

gs_ctl-

log_pattern_gs_guc

gs_guc-

log_pattern_gs_dump

gs_dump-

log_pattern_gs_dumpall

gs_dumpall-

log_pattern_gs_restore

gs_restore-

log_pattern_gs_initcm

gs_initcm-

log_pattern_gs_initdb

gs_initdb-

log_pattern_gs_initgtm

gs_initgtm-

log_pattern_gtm_ctl

gtm_ctl-

log_pattern_cm_agent

cm_agent-

log_pattern_system_call

system_call-

log_pattern_cm_server

cm_server-

log_pattern_om_monitor

om_monitor-

log_pattern_gs_local

gs_local-

log_pattern_gs_preinstall

gs_preinstall-

log_pattern_gs_install

gs_install-

log_pattern_gs_replace

gs_replace-

log_pattern_gs_uninstall

gs_uninstall-

log_pattern_gs_om

gs_om-

log_pattern_gs_upgradectl

gs_upgradectl-

log_pattern_gs_expand

gs_expand-

log_pattern_gs_shrink

gs_shrink-

log_pattern_gs_postuninstall

gs_postuninstall-

log_pattern_gs_backup

gs_backup-

log_pattern_gs_checkos

gs_checkos-

log_pattern_gs_collector

gs_collector-

log_pattern_GaussReplace

GaussReplace-

log_pattern_GaussOM

GaussOM-

log_pattern_gs_checkperf

gs_checkperf-

log_pattern_gs_check

gs_check-

log_pattern_roach-agent

roach-agent-

log_pattern_roach-controller

roach-controller-

log_pattern_postgresql

postgresql-

log_pattern_gtm

gtm-

log_pattern_sessionstat

sessionstat-

log_pattern_sync

sync-

log_pattern_system_alarm

system_alarm-

log_pattern_pg_perf

pg_perf-

log_pattern_slow_query_log

slow_query_log-

log_pattern_asp

asp-

log_pattern_etcd

etcd-

log_pattern_gs_cgroup

gs_cgroup-

log_pattern_pscp

pscp-

log_pattern_postgresql-query-log

postgresql-query-log-

log_pattern_gs_hotpatch

gs_hotpatch-

log_pattern_pssh

pssh-

agent_backup_open

Parameter description: Specifies the DR database instance settings. After this parameter is enabled, CM runs in DR database instance mode.

Value range: 0 or 1. You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 1.

  • 0: disabled.
  • 1: enabled.

Default value: 0

enable_xc_maintenance_mode

Parameter description: Specifies whether the pgxc_node system catalog can be modified when the database instance is in read-only mode.

Value range: Boolean For details about how to modify this parameter, see Table 1.

  • on indicates that the pgxc_node system catalog can be modified.
  • off indicates that the pgxc_node system catalog cannot be modified.

Default value: on

unix_socket_directory

Parameter description: Specifies the directory location of the Unix socket.

Value range: a string You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 1.

Default value: ''

enable_dcf

Parameter description: Specifies the status of the DCF mode.

Value range: Boolean You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 1.

  • 0: disabled.
  • 1: enabled.

Default value: off

disaster_recovery_type

Parameter description: Specifies the type of the DR relationship between the primary and standby database instances.

Value range: an integer ranging from 0 to 2 You need to restart cm_agent for the modification to take effect. For details about how to modify this parameter, see Table 1.

  • 0 indicates that no DR relationship is established.
  • 1 indicates that the OBS DR relationship is established.
  • 2 indicates that the streaming DR relationship is established.

Default value: 0

Feedback
编组 3备份
    openGauss 2024-05-07 00:46:52
    cancel