Modifying Component Configuration- FineOps Help Document

Last update: 2024-05-30

Overview

Version

FineOps Version	Functional Change
V1.5.5	/
V2.1.0	Since there is a correlation between various memory configurations, the configuration modification operation is optimized to ensure reasonable adjustments.

Application Scenario

Scenario 1: Demand for a reasonable allocation of CPU and memory for components

You have deployed a containerized project on the server, but found that the performance of the elasticsearch component was poor as the fr component has occupied all of the CPU resources, resulting in insufficient memory allocated to the elasticsearch component.

Scenario 2: Demand for rapid modification of component configuration on the page

After deploying a project, you need to regularly maintain the FR/BI components, external MySQL database, load balancer Nginx, and state server Redis, including operations such as Redis cache cleanup, and JVM memory adjustment.

Performing these operations requires writing commands or modifying configuration files, which is troublesome.

Function Description

FineOps provides the Modify Configuration function for you to quickly adjust and modify the project configuration.

Procedure

Prerequisite

This function is only valid for FineOps-deployed projects.

This function is valid for components in a running status. If the component is stopped, start the component.

013(1).png

Modifying the Configuration

Click the Modify Configuration button of the target component to access the configuration modification page.

017(1).png

Modify the configuration and click OK.

015(1).png

The configuration items are described in the following table.

Note: This document does not cover the modification of SSL configuration. For details, see: Enabling SSL for O&M Project

Component	Configuration Available for Modification	Description
bi6 fr fdl	CPU	The default value is the minimum size of CPU required for component running, and the recommended value is twice the minimum value. Enter a number greater than zero. The container CPU size cannot exceed the server CPU size.
	Memory	When the memory reaches its limit, components will be automatically restarted. Refrain from imposing restrictions on components with continuous business requirements. The default value is the minimum size of memory required for component running, and the recommended value is twice the minimum value. Enter a number greater than zero. The container memory size cannot exceed the server memory size. For the bi6 component, the container memory size must meet the current JAVA memory configuration, that is, it must be greater than or equal to the sum of values of Xmx, Off-heap Memory, FineIO Read Memory, FineIO Write Memory, CodeCache Configuration, Metaspace memory, adding 5 GB. For fr and fdl components, the container memory size must meet the current JAVA memory configuration, that is, it must be greater than or equal to the sum of values of Xmx, Off-heap Memory, FineIO Read Memory, FineIO Write Memory, CodeCache Configuration, and Metaspace Memory.
	Xmx	Enter a number greater than zero. Use the System Inspection function in Health Inspection to view the recommended values. Modifying these values will trigger a validation of the memory setting.
	Xms
	Off-heap Memory
	FineIO Read Memory
	FineIO Write Memory
	CodeCache Configuration
	Metaspace Memory
	HTTP Maximum Thread Pool	Enter a number greater than zero. Use the System Inspection function in Health Inspection to view the recommended values.
	HTTP Queuing Thread Pool
	Chart Maximum Thread Pool
mysql	CPU	The default value is the minimum size of CPU required for component running, and the recommended value is twice the minimum value. Enter a number greater than zero. The container CPU size cannot exceed the server CPU size.
	Memory	When the memory reaches its limit, components will be automatically restarted. Refrain from imposing restrictions on components with continuous business requirements. The default value is the minimum size of memory required for component running, and the recommended value is twice the minimum value. Enter a number greater than zero. The container memory size cannot exceed the server memory size.
	character_set_server	The encoding of the database server (mysqld), for example, utf8mb4. It needs to be modified together with collation-server.
	collation-server	The default sorting oder of the database server, for example, utf8mb4_bin. It needs to be modified together with character_set_server.
	max_allowed_packet	The maximum data size that the client or the database server can accept, for example, 128 MB.
	Write Timeout	Modify the value of net_write_timeout, for example, 1000 (unit: ms).
	Maximum Connection Timeout Count	Modify the value of global max_connect_errors, for example, 1000.
redis	CPU	The default value is the minimum size of CPU required for component running, and the recommended value is twice the minimum value. Enter a number greater than zero. The container CPU size cannot exceed the server CPU size.
	Memory	When the memory reaches its limit, components will be automatically restarted. Refrain from imposing restrictions on components with continuous business requirements. The default value is the minimum size of memory required for component running, and the recommended value is twice the minimum value. Enter a number greater than zero. The container memory size cannot exceed the server memory size. The container memory size must satisfy the current memory configuration, that is, it must be greater than or equal to 1.5 times the value of maxmemory.
	maxmemory-policy	Modify the Redis memory policy, for example, volatile-lru.
	maxmemory	Modify the Redis memory (unit: GB). Modifying these values will trigger a validation of the Redis memory setting.
	stop-writes-on-bgsave-error	Set whether to stop data writes in case of Redis snapshot failure. Option: yes, and no.
nginx	CPU	The default value is the minimum size of CPU required for component running, and the recommended value is twice the minimum value. Enter a number greater than zero. The container CPU size cannot exceed the server CPU size.
	Memory	When the memory reaches its limit, components will be automatically restarted. Refrain from imposing restrictions on components with continuous business requirements. The default value is the minimum size of memory required for component running, and the recommended value is twice the minimum value. Enter a number greater than zero. The container memory size cannot exceed the server memory size.
	client_max_body_size	Set the maximum size of data that can be uploaded by users according to business requirements. The default value is 100 MB.
	proxy_buffer_size	Set the size of the buffer, for example, 64 KB.
	proxy_buffers	Set the number and size of buffers for each connection in a format of number size, for example, 32 64 KB.
	proxy_busy_buffers_size	When buffering response is enabled, nginx will always send responses to the customer if the buffer size reaches a certain threshold before the entire response is read. The response will only stop when the buffer size decreases below this value, for example, 64 KB.
	proxy_connect_timeout	Set the timeout duration for the nginx component connecting to the backend server. It is the duration of establishing a connection, not the duration of waiting for a response from the backend. For example, set it to 60 s.
	proxy_read_timeout	Set the read timeout duration, which defaults to 60 s. If the server does not receive the data within the period, it is considered as timeout. If no large data calculations or exported templates exist, a timeout duration of no more than 100 s is recommended. If large data calculations and exported templates exist, set this value based on the longest template time.
	proxy_send_timeout	Set the write timeout duration, which defaults to 60 s. If the server does not receive the data within the period, it is considered as timeout. If no large data calculations or exported templates exist, a timeout duration of no more than 100 s is recommended. If large data calculations and exported templates exist, set this value based on the longest template time.
elasticsearch	CPU	After successfully modifying the elasticsearch component configuration, the component will automatically restart for the changes to take effect. Restarting components may affect the normal operation of the project. Do not perform any operations while the system is in use. The default value is the minimum size of CPU required for component running, and the recommended value is twice the minimum value. Enter a number greater than zero. The container CPU size cannot exceed the server CPU size.
	Memory	After successfully modifying the elasticsearch component configuration, the component will automatically restart for the changes to take effect. Restarting components may affect the normal operation of the project. Do not perform any operations while the system is in use. If the memory reaches its limit, components will automatically restart. Refrain from imposing restrictions on components with continuous business requirements. The default value is the minimum size of memory required for component running, and the recommended value is twice the minimum value. Enter a number greater than zero. The container memory size cannot exceed the server memory size. The container memory size must satisfy the current memory configuration, that is, it must be greater than or equal to 1.5 times the value of Xmx.
	Xmx	After successfully modifying the elasticsearch component configuration, the component will automatically restart for the changes to take effect. Restarting components may affect the normal operation of the project. Do not perform any operations while the system is in use. Enter a number greater than zero. Modifying these values will trigger validation of the elasticsearch memory setting.
Other Components	CPU	The default value is the minimum size of CPU required for component running, and the recommended value is twice the minimum value. Enter a number greater than zero. The container CPU size cannot exceed the server CPU size.
Other Components	Memory	If the memory reaches its limit, components will automatically restart. Refrain from imposing restrictions on components with continuous business requirements. The default value is the minimum size of memory required for component running, and the recommended value is twice the minimum value. Enter a number greater than zero. The container memory size cannot exceed the server memory size.

Restarting the Component

The component will automatically restart if the configuration of the elasticsearch component has been modified. Other configuration changes require you to restart the component manually.

Restarting components may affect the normal operation of the project. Do not perform any operations while the system is in use.

Modify the configuration as the admin, return to the Component Management page, and click the Restart button of the corresponding component.

010_副本(1).png