Bu sayfa henüz yerel dilinizde mevcut değildir. Daha fazla dil seçeneği eklemek için yoğun bir şekilde çalışıyoruz. Desteğiniz için teşekkür ederiz.

Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
Software Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Parameters Related to cm_agent

Updated on 2024-05-07 GMT+08:00

log_dir

Parameter description: Specifies the directory where cm_agent logs are stored. The value can be an absolute path, or relative to the CM Agent data directory.

Value range: a string. Any modification of this parameter takes effect only after cm_agent is restarted. For details about how to modify this parameter, see Table 2.

Default value: "log", indicating that CM Agent logs are generated in the CM Agent data directory.

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. The modification of this parameter takes effect after reloading. For details about how to modify the 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. The modification of this parameter takes effect after reloading. For details about how to modify the 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. The modification of this parameter takes effect after reloading. For details about how to modify the 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. The modification of this parameter takes effect after reloading. For details about how to modify the 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. The modification of this parameter takes effect after reloading. For details about how to modify the 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. The modification of this parameter takes effect after reloading. For details about how to modify the 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. The modification of this parameter takes effect after reloading. For details about how to modify the 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. The modification of this parameter takes effect after reloading. For details about how to modify the 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. The modification of this parameter takes effect after reloading. For details about how to modify the parameter, see Table 2.

Default value: 2

agent_heartbeat_timeout

Parameter description: Specifies the heartbeat timeout interval for CM Agent to connect to CM Server.

Value range: an integer ranging from 2 to 231 – 1. The unit is second. The modification of this parameter takes effect after reloading. For details about how to modify the 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. The modification of this parameter takes effect after reloading. For details about how to modify the 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. The modification of this parameter takes effect after reloading. For details about how to modify the 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. The modification of this parameter takes effect after reloading. For details about how to modify the 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. The modification of this parameter takes effect after reloading. For details about how to modify the 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. The modification of this parameter takes effect after reloading. For details about how to modify the 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. Only ARM is supported.

Value range: an integer ranging from 0 to 2. The modification of this parameter takes effect only after the database and CM Agent are restarted. For details about how to modify the parameter, see Table 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. The modification of this parameter takes effect after reloading. For details about how to modify the 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. The modification of this parameter takes effect after reloading. For details about how to modify the 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. The modification of this parameter takes effect after reloading. For details about how to modify the 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. The modification of this parameter takes effect after reloading. For details about how to modify the 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. The modification of this parameter takes effect after reloading. For details about how to modify the parameter, see Table 2.

Default value: 90

enable_log_compress

Parameter description: Specifies whether to enable log compression.

Value range: Boolean. The modification of this parameter takes effect after reloading. For details about how to modify the parameter, see Table 2.

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

Default value: on

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. Any modification of this parameter takes effect only after cm_agent is restarted. 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. The modification of this parameter takes effect after reloading. For details about how to modify the parameter, see Table 1.

Default value: ''

enable_dcf

Parameter description: Specifies the status of the DCF mode.

Value range: Boolean. The modification of this parameter takes effect after reloading. For details about how to modify the 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. The modification of this parameter takes effect after reloading. For details about how to modify the 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

Sitemizi ve deneyiminizi iyileştirmek için çerezleri kullanırız. Sitemizde tarama yapmaya devam ederek çerez politikamızı kabul etmiş olursunuz. Daha fazla bilgi edinin

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback