System Inspection Content

1. Added the following items to System Inspection:

• 0119 Memory Occupied by Caching on Physical Server

• 0120 Estimated Maximum Memory Usage of Process with Current Configuration

2. Added the following item to System Operation Status:

• 0213 Deployment Method

3. Added the following items to Java VM Check:

• 0802 FineIO Read Memory

• 0903 FineIO Write Memory

1. Added the following items to System Inspection:

• 0121 Memory Resource Check

• 0122 Node Container - Memory Resource Check

• 0123 Node Container - CPU Resource Check

2. Optimized the following items in System Inspection:

• 0108 Core Quantity

• 0109 Memory Size

3. Added the following item to System Operation Status:

• 0214 Nginx Configuration Check

4. Added the following items to Java VM Check:

• 0801 Off-Heap NIO Memory

• 0813 Code Cache Configuration

• 0820 On-Heap Memory

• 0823 Metaspace Configuration

Added the following item to System Operation Status:

• 0215 Inter-Node Time Consistency Check

0101

Operating System Information

Yes

No

It only outputs information.

0102

Server Time

Yes

No

It only outputs information.

0103

Time Zone

Yes

No

It only outputs information.

0104

Glibc/GCC Version

Yes

No

It only outputs information.

0105

Hostname

Yes

No

It only outputs information.

0106

Host File Information

Yes

No

It only outputs information.

0107

CPU Clock Speed

Yes

No

It checks whether the frequency is greater than or equal to 2.4 GHz.

You are advised to ensure that the frequency is greater than or equal to 2.4 GHz.

0108

Core Number

Yes

No

It checks the number of CPU cores.

For the FineBI - Application Node and Engine - Calculation Node components, the recommended maximum number of available CPU cores is at least 8.

For the FineReport, FineDataLink, and Engine - Metadata Node components, the recommended maximum number of available CPU cores is at least 4.

0109

Memory Size

Yes

No

• FineOps-deployed projects:

The recommended upper memory limit for the bi-web, bi-engine-master, and bi-minio containers is at least 6 GB.

The recommended upper memory limit for the worker container is at least 24 GB.

Verify that the upper memory limit for the fr/fdl container is not less than 15.5 GB. Set it to a value greater than 16 GB.

• Projects not deployed via FineOps:

It checks whether the total physical memory of the server hosting the project is greater than or equal to 15.5 GB.

The recommended server physical memory is at least 16 GB.

0110

Swap

Yes

No

It checks if virtual memory is disabled.

It outputs the swap partition size.

Disable virtual memory.

0111

Memory Used

Yes

No

It only outputs information.

0112

Available Memory

Yes

No

It only outputs information.

0113

CPU Information

Yes

No

It only outputs information.

0114

Server Font Encoding

Yes

No

It only outputs information.

0115

Server Font Package

Yes

No

It only outputs information.

It checks if the set heap memory is within the recommended range.

It checks if the median FGC duration in the past week is less than 10 seconds.

If either of the above conditions is not met, CPU performance is considered poor. Increase the number of CPU cores, use a CPU with better performance, or appropriately reduce the maximum heap memory (-Xmx) to avoid excessive Full GC durations that may impact system usability.

This check applies to projects not deployed via FineOps only.

It checks if the value of the Linux kernel parameter vm.panic_on_oom in /proc/sys/vm/panic_on_oom is set to 0.

You are advised to adjust the configuration by running sysctl -w vm.panic_on_oom=0 to prevent the system from panicking on out-of-memory events.

It only outputs information.

It checks the value of ProcessUnpackaged in /etc/abrt/abrt-action-save-package-data.conf.

This check applies to non-FineOps-deployed projects on Linux servers.

It only outputs information.

It only outputs information.

It only outputs information.

• For FineBI - Application Node and Engine - Calculation Node components:

It calculates the total memory usage as: 

Xmx value + Off-heap memory size + CodeCache value + Metaspace size + 3 GB

Ensure that this sum value is not more than the maximum available memory of the container.

• For the Engine - Metadata Node component:

It calculates the total memory usage as: 

Xmx value + Off-heap memory size + CodeCache value + Metaspace size + 2.4 GB

Ensure that this sum value is not more than the maximum available memory of the container.

It outputs the sum of the maximum available memory of all containers on the server.

It outputs the actual available memory of the server.

Ensure that the sum of the maximum available memory of all containers on the server is less than or equal to the available memory of the server. This can be achieved by reducing the maximum available memory of containers or increasing the server memory configuration.

It outputs the sum of the maximum available CPU cores of all containers on the server.

It outputs the actual number of CPU cores on the server.

Ensure that the ratio of the sum of the maximum available CPU cores of containers to the actual server CPU core count is less than or equal to 4.

0201

Startup Duration

Yes

No

It only outputs information, including the time taken for this startup.

0203

Project Startup Path

Yes

No

It only outputs information, including the directory path.

0204

Abnormal Project Folder Size

Yes

No

Note:

Only local folders are inspected. Folders on the file server are not inspected.

Check the size of each folder located in the /WEB-INF path of the project.

Healthy: No folder exceeds 5 GB in size.

Unhealthy: Some folders exceed 5 GB in size.

Suggestion:

You are advised to check and clean up the contents of the folders exceeding 5 GB in size.

0205

Plugin Information

No

No

It only outputs information, including plugin name, version, and whether it is enabled or not.

0206

Registration Authorization Information

No

No

It only outputs information, including whether the project is registered.

0207

web.xml Available Under WEB-INF or Not

No

No

It only outputs information, including Yes/No.

0208

Container Version

Yes

No

It only outputs information.

0209

Project JAR Package Information

No

No

It only outputs information, including versions of various modules in the project and JAR package dates.

0211

Temporary Output Directory

Yes

No

It only outputs information, including the directory path and remaining available space in the directory.

0212

Tomcat Background Running

Yes

No

Check if Tomcat is running in the background using javaw.

Healthy: Tomcat is running in the background using javaw.

Unhealthy: Tomcat is running in the background not using javaw.

Suggestion: You are advised to make Tomcat run in the background using javaw.

It only outputs information.

It outputs FineOps Deployment or Non-FineOps Deployment.

It checks whether the relevant configuration in the nginx.conf file complies with the following recommended settings.

• Passive Health Check

The recommended max_fails value is at least 15.

The recommended fail_timeout value is at most 5 s.

• Active Health Check

The recommended value range of interval is [2000, 60000].

The recommended rise value is at most 3.

The recommended value range of fall is [5, 20].

The recommended value range of timeout is [2000, 5000].

You are advised to configure check_http_send=/webroot/decision/system/health.

You are advised to configure check_http_expect_alive=http_2xx http_3xx.

It checks the current time of all nodes in the project.

Ensure the time difference between nodes is less than 1 s.

1. File path:

The default path is /webapps/webroot/backup.

If the backup folder resides in a custom path, the system will scan the custom path.

2. Purpose:

It stores project backups.

3. Cleanup risk level:

High (caution required)

The displayed files in this path have date-stamped names. You can select and clean files of the required dates.

You are advised to clean up the files older than 3 months.

Files within the last 3 months are not displayed.

1. File path:

/webapps/webroot/WEB-INF/schedule

2. Purpose:

It stores intermediate files generated by scheduled tasks.

3. Cleanable scope:

The system only displays files older than 12 months for cleanup.

4. Cleanup risk level:

Low (cleanup recommended)

The displayed files in this path have date-stamped names. You can select and clean files of the required dates.

You are advised to clean up the files older than 12 months.

Files within the last 12 months are not displayed.

1. File path:

/webapps/webroot/WEB-INF/assets/vcs

2. Purpose:

FineReport template version management file

3. Cleanable scope:

The system only displays files older than 30 days for cleanup.

4. Cleanup risk level:

Low (cleanup recommended)

All historical version files older than 30 days are stored in one folder for easy selection and cleanup.

You are advised to clean up the files older than 30 days.

Files within the last 30 days are not displayed.

1. File path:

/webapps/webroot/WEB-INF/treasures

2. Purpose:

It stores packages of cloud O&M logs.

3. Cleanup risk level:

Low (cleanup recommended)

The displayed files in this path have date-stamped names. You can select and clean files of the required dates.

You are advised to clean up the files older than 12 months.

Files within the last 12 months are not displayed.

1. File path:

Tomcat installation directory/logs/fanruan.log

2. Purpose:

It is the operation log of the FanRuan project.

3. Cleanup risk level:

High (caution required)

1. File path:

The system scans for exported dump files that were not cleaned up in time.

2. Purpose:

Dump file

3. Cleanup risk level:

Low (cleanup recommended)

The displayed files in this path have date-stamped names. You can select and clean files of the required dates.

Clean up the files older than one week.

Files within one week are not displayed.

1. File path:

Tomcat installation directory/logs/Catalina.log

2. Purpose:

Tomcat operation log

3. Cleanup risk level:

High (caution required)

4. Notes

If the log is not configured to roll in Tomcat, do not clean it up. 

The displayed files in this path have date-stamped names. You can select and clean files of the required dates.

Clean up the files older than one week.

Files within one week are not displayed.

1. File path:

Tomcat installation directory\logs\Catalina.out

2. Purpose:

The standard output and error log of Tomcat

3. Cleanup risk level:

High (caution required)

4. Notes

If the log is not configured to roll in Tomcat, do not clean it up.

If the file does not exist on the Windows system, do not clean it up. 

The displayed files in this path have date-stamped names. You can select and clean files of the required dates.

Clean up the files older than one week.

Files within one week are not displayed.

Log in to FineOps as the admin, click a specified project, and choose Business Tool > Resource Cleanup.

Select the file types you want to scan and click Start scanning. You can tick and clean up the redundant files found during the scan.

Log in to the FanRuan system as the admin and choose System Management > Intelligent O&M > Disk O&M > Disk Cleanup.

Select the files/folders to be scanned, and click Start Scanning to immediately start scanning for redundant files eligible for manual cleanup.

In the Windows system, if the project deployed using the Tomcat container is started under window mode instead of background mode, the window may enter the edit and insert state due to accidental clicks, blocking log output and causing the project to become stuck.

For the Windows system, you are advised to start the project deployed using the Tomcat container under background mode.

Modify the default startup mode to javaw first. Prevent repeated startups by adding a script to detect startup commands. Pressing any key can end the script.

1. Modify setclasspath.bat.

Open the setclasspath.bat file in Tomcat installation directory\bin\setclasspath.bat, find set _RUNJAVA, and modify its value:

set _RUNJAVA="%JRE_HOME%\bin\javaw.exe"

2. Modify catalina.bat.

Open the catalina.bat file in Tomcat installation directory\bin\catalina.bat and add the following judgment tips at the end:

set ENV_VAR_VALUE=%_EXECJAVA%
echo %ENV_VAR_VALUE% | findstr /C:"javaw" >nul
if %errorlevel% equ 0 (
   echo Tomcat is running in the background
   pause
)

0301

WebSocket Port

No

No

It only outputs information, including the port number.

0302

Cluster Port

Yes

No

It checks whether the cluster ports are connected.

Healthy: The ports are connected.

Unhealthy: Some ports are disconnected.

Suggestion: The connectivity status of cluster ports is abnormal.

0303

Crash Detection

Yes

No

Inspect:

1. Whether automatic crash detection is enabled.

2. Whether the crashed ports are connected.

Suggestion: You are advised to enable Crash Detection and ensure the ports are available.

Container WebSocket Solution

The container WebSocket solution does not require any user operation. The system can automatically use the WebSocket built into the Web container to connect and reuse the HTTP port.

• As long as your environment meets the validation conditions, the solution will be automatically used.

• If your environment does not meet the validation conditions, you can consider configuring the Socket.IO solution by yourself.

Socket.IO Solution

Projects managed by FineOps

1. Log in to FineOps as the admin, click an O&M project, and choose Availability Statistics > Crash Handling Strategy.

2. Enter the port number in Port Setting. The default port is 12100. Enter a port number between 1024 and 65535.

3. Click Test. A prompt will appear: "The port is available. After saving, the crash handling tool will restart with its port updated to the new one."

4. Click Save to apply the changes.

Projects not managed by FineOps

1. Log in to the FanRuan application as the admin and choose System Management > Intelligent O&M > Downtime Handling > Automatic Downtime Handling Tool.

2. Enter the port number in Port Setting. The default port is 12100. Enter a port number between 1024 and 65535.

3. Click Test. A prompt will appear: "The port is available. After saving, the crash handling tool will restart with its port updated to the new one."

4. Click Save to apply the changes.

0501

Sequential Read

Yes

No

It only outputs information, including the speed of sequential read (display "The rate is less than 100 MB/s." instead of specific values if the speed is below 100 MB/s).

Note:

If the permission is insufficient in the Windows system, you need to use the following command to inspect manually: winsat disk -drive letter-seq -read.

0502

Sequential Write

Yes

No

It only outputs information, including the speed of sequential write (display "The rate is less than 100 MB/s." instead of specific values if the speed is below 100 MB/s).

Note:

If the permission is insufficient in the Windows system, you need to use the following command to inspect manually: winsat disk -drive letter-seq -write.

0504

Small File Creation

Yes

No

It only outputs information, including the number of small files created per second.

0505

Small File Deletion

Yes

No

It only outputs information, including the number of small files deleted per second.

0506

Disk Space

Yes

No

1. For FineReport projects:

Healthy: The total disk space is not less than 100 GB.

Unhealthy: The total disk space is less than 100 GB.

Suggestion: You are advised to use the disk with over 100 GB.

2. For FineBI projects:

Healthy: The total disk space is not less than 400 GB.

Unhealthy: The total disk space is less than 400 GB.

Suggestion: You are advised to use the disk with over 400 GB.

0507

Used Disk Space

Yes

No

It only outputs information, including the size of the used disk space.

0508

Free Disk Space

Yes

No

1. For FineReport projects:

Healthy: The free disk space is greater than 10 GB.

Unhealthy: The free disk space is less than 10 GB.

Suggestions for modification: The available disk space is less than 10 GB. Clean up large disk files to avoid affecting the use.

2. For FineBI projects:

Healthy: The free disk space is greater than 50 GB.

Unhealthy: The free disk space is less than 50 GB.

Suggestions for modification: The available disk space is less than 50 GB. Clean up large disk files to avoid affecting the use.

0509

Sequential Read (Non-buffer Pool)

Yes

No

Healthy: Disk performance > 150 MB/s

Unhealthy: Disk performance < 150 MB/s

Suggestion: The disk performance is poor, which may lead to performance issues. Replace it with a disk offering better performance, such as an SSD.

0510

Sequential Write (Non-buffer Pool)

Yes

No

Healthy: Disk performance > 150 MB/s

Unhealthy: Disk performance < 150 MB/s

Suggestion: The disk performance is poor, which may lead to performance issues. Replace it with a disk offering better performance, such as an SSD.

0601

Process User

Yes

No

It only outputs information, including the user name.

0602

Server Main Folder Permissions

Yes

No

0603

Multi-process Detection

Yes

No

Unhealthy: The sum of the maximum memory required by FanRuan applications and the memory used by other processes is not less than the total physical memory.

Suggestion: You are not advised to make the FanRuan project share the server with other application services, which may cause system crashes.

0604

File Server Solution for Cluster

Yes

No

Healthy: File servers are used for clusters.

Unhealthy: Inter-node synchronization is used for clusters.

Suggestion: You are advised to use file servers instead of inter-node synchronization for clusters. Otherwise, performance issues and file inconsistencies may occur.

vm.max_map_count

Yes

No

Healthy: The value of vm.max_map_count is not less than 262144.

Unhealthy: The value of  vm.max_map_count is less than 262144. 

Suggestion: You are advised to set the vm.max_map_count parameter to 262144.

0702

Maximum Number of Opened Files

Yes

No

1. For FineReport projects:

Healthy: The value of open_files is not less than 65536.

Unhealthy: The value of open_files is less than 65536.

Suggestion: You are advised to set the open_files parameter to greater than 65536.

2. For FineBI projects:

Healthy: The value of open_files is not less than 131070.

Unhealthy: The value of open_files is less than 131070.

Suggestion: You are advised to set the open_files parameter to greater than 131070.

0703

vm.overcommit_memory

Yes

No

Healthy: overcommit_memory＝0

Unhealthy: overcommit_memory ≠ 0

Suggestion: You are advised to set the vm.overcommit_memory parameter to 0.

0704

vm.overcommit_ratio

Yes

No

Healthy: overcommit_ratio = 50

Unhealthy: overcommit_ratio ≠ 50

Suggestion: You are advised to set the vm.overcommit_ratio parameter to 50.

0705

Glibc Memory Leak Configuration

Yes

Yes

It checks whether the export MALLOC_ARENA_MAX parameter is configured.

Healthy: export MALLOC_ARENA_MAX = 1

Unhealthy: not configured or configured to other values

Suggestion: You are advised to configure the export MALLOC_ARENA_MAX parameter to 1.

Healthy: The Redis eviction policy is set to maxmemory-policy noeviction.

Unhealthy: The Redis eviction policy is not set to maxmemory-policy noeviction.

Suggestion: Set the Redis eviction policy to maxmemory-policy noeviction. Failure to do so may result in unpredictable consequences due to unintended key eviction.

Healthy: The maximum process count (nproc) is greater than or equal to 266240.

Unhealthy: The maximum process count (nproc) is less than 266240.

Suggestion: Set the maximum process count (nproc) to a value not less than 266240.

vm.max_map_count is a Linux kernel parameter used to control the maximum number of memory-mapped areas allowed in a process.

If the value of this parameter is too small, memory-mapping errors may occur when you use some applications.

1. Add/Modify the parameter value in /etc/sysctl.conf.

vm.max_map_count=262144

• Run the command sysctl -p for the modification to take effect.

open_files refers to the maximum number of file descriptors that a process can open at the same time.

A file descriptor is the unique identifier used to access files (including pipes, sockets, and other file operations) in Unix systems.

For FineReport projects, you are advised to set the open_files parameter to greater than 65536.

For FineBI projects, you are advised to set the open_files parameter to greater than 131070.

1. Delete system-level restrictions.

Check whether there are statements related to ulimit -n xxx in /etc/profile.

If relevant statements exist, delete those statements and reload the shell environment using the source/etc/profile statement.

2. Modify user-level restrictions.

Open the software and hardware restriction file /etc/security/limits.conf on Linux and add the following code at the end of the file:

* soft nofile 65536
* hard nofile 65536

In the above command, hard represents the system's hard limit, and soft represents the user's soft limit.

On some systems, replacing * with a specific username (for example, root soft nofile 128000) may be required for the changes to take effect.

3. Load the pam_limits.so module.

Open the login file (/etc/pam.d/login) and ensure it contains the following line (typically located in the session section):

If the line does not exist, add it. If it exists but is commented out (starting with #), uncomment it.

session required pam_limits.so

This operation ensures that when a user logs in to the terminal, the system loads the pam_limits.so module, thereby applying the resource limits defined in limits.conf.

4. Restart the project and log in again.

After the configuration is completed, the terminal user logs in again and restarts the Tomcat project to make the configuration effective.

You can use the ulimit -n command to confirm whether the modification is successful based on the returned value.

vm.overcommit_memory is a Linux kernel parameter used to control whether the system allows a process to allocate more memory than is available.

When the parameter value is 0, the kernel will check whether there is enough free memory to satisfy the submitted memory request. If there is enough free memory, the process is allowed to continue allocating memory. Otherwise, the allocation request will fail, and an error will be returned.

1. Add/Modify the parameter value in etc/sysctl.conf.

vm.overcommit_memory=0

2. Run the command sysctl -p for the modification to take effect.

vm.overcommit_ratio is a Linux kernel parameter that specifies the ratio of the system VMware huge page manager (Memory Ballooning) and swap space usage.

When the parameter value is 50, the kernel uses an appropriate space twice the size of the swap partition as another spare space to simulate physical memory.

1. Add/Modify the parameter value in etc/sysctl.conf.

vm.overcommit_ratio=50

2. Run the command sysctl -p for the modification to take effect.

1. Close Tomcat server.

2. Go to Tomcat installation directory/bin and open the startup.sh file.

3. Add/Modify the line at the beginning of the file: export MALLOC_ARENA_MAX = 1.

4. Save the changes to the startup.sh file and close it.

5. Run the startup.sh file in the terminal to restart Tomcat and apply the new environment variable settings.

When the Redis eviction policy is set to noeviction, Redis will not evict any existing data upon the maximum memory limit is reached, and will reject new write operations (such as write commands and data updates).

Using this policy ensures that all data is never automatically deleted, thereby maintaining data integrity and avoiding data loss due to insufficient memory.

Locate the redis.conf configuration file in the Redis installation directory, find maxmemory-policy, and set it to noeviction.

After modification, restart the Redis service to apply the change.

In Linux systems, nproc represents the maximum number of processes that a user can start. This limit is typically set at the system level but can also be configured per user.

If the nproc value is set too low, reaching the limit may prevent applications from starting new processes, affecting user experience or system functionality.

Set the maximum process count (nproc) to a value not less than 266240.

Edit the limits.conf file located in /etc/security/ or /etc/ as the root user.

Add or modify the following lines, where soft is the soft limit, which serves as the default value, and hard is the hard limit, representing the maximum allowed value.

# Set nproc limit for a specific user.
Username soft nproc 266240
Username hard nproc 266240
# Set nproc limit for all users.
* soft nproc 10240
* hard nproc 266240

FineBI - Application Node: 1536 MB ≤ Configuration ≤ 2 GB

Engine - Calculation Node: Configuration ≥ max(6 GB, Xmx value * 0.4 GB)

Engine - Metadata Node: Configuration ≥ 768 MB

FineReport and FineDataLink: Configuration ≤ 2 GB

For the bi6 container, where the minor version of FineBI is V6.0.16 or later: Configuration ≥ (Xmx value * 0.4) GB

For the bi6 container, where the minor version of FineBI is older than V6.0.16: Configuration ≥ 4 GB

1. FineBI - Application Node/FineReport/FineDataLink

Use the ParallelScavenge garbage collector for the JVM.

2. Engine - Calculation Node/Engine - Metadata Node

Use the ParallelScavenge garbage collector for the JVM if JDK 8 is used.

Use the G1GC garbage collector for the JVM if JDK 11 is used.

Healthy: The DisableExplicitGC parameter is not configured.

Unhealthy: The DisableExplicitGC parameter is configured.

Suggestion: Remove the DisableExplicitGC parameter.

FineBI - Application Node/FineReport/FineDataLink: Use JDK8 with a minor version of 202 or later.

Engine - Calculation Node/Engine - Metadata Node: Use JDK11, or JDK8 with a minor version of 202 or later.

Healthy: -Djava.awt.headless=true is configured.

Unhealthy: -Djava.awt.headless=true is not configured.

Suggestion: Configure -Djava.awt.headless=true to enable the headless mode.

Healthy: HeapDumpOnOutOfMemoryError and HeapDumpPath are configured.

Unhealthy: HeapDumpOnOutOfMemoryError and HeapDumpPath are not configured.

Suggestion: Configure HeapDumpOnOutOfMemoryError and HeapDumpPath to ensure the normal dump file exports.

Healthy: -XX:PerBytecodeRecompilationCutoff = -1

Unhealthy: -XX:PerBytecodeRecompilationCutoff ≠ -1

Suggestion: Configure -XX:PerBytecodeRecompilationCutoff = -1.

Healthy: -XX:PerMethodRecompilationCutoff = -1

Unhealthy: -XX:PerMethodRecompilationCutoff ≠ -1

Suggestion: Configure -XX:PerMethodRecompilationCutoff = -1.

Note:

This check applies to FineBI projects only.

Healthy: The project is not deployed using an EXE file.

Unhealthy: The project is deployed using an EXE file.

Suggestion: Use FineOps for deployment.

FineReport/FineDataLink: CodeCacheSize ≥ 512 MB

bi6: -XX:ReservedCodeCacheSize ≥ 1024 MB

FineBI - Application Node:

CodeCacheSize ≥  768 MB

If the container memory limit is between 6 GB and 8 GB, set the CodeCacheSize value to at least 768 MB.

If the container memory limit exceeds 8 GB, set the CodeCacheSize value to at least 1 GB.

Engine - Calculation Node:

CodeCacheSize ≥  768 MB

If the container memory limit is between 32 GB and 64 GB, set CodeCacheSize be to at least 1 GB.

Engine - Metadata Node:

CodeCacheSize ≥  256 MB

If the container memory limit is between 6 GB and 16 GB, set the CodeCacheSize value to at least 256 MB.

If the container memory limit is between 16 GB and 32 GB, set the CodeCacheSize value to at least 512 MB.

If the container memory limit exceeds 32 GB, set the CodeCacheSize value to at least 1 GB.

Healthy: The -Duser.country value is the code of the region where the server is located.

Unhealthy: The -Duser.country value is not the code of the region where the server is located.

Suggestion: Set -Duser.country to the code of the region where the server is located.

Healthy: The -Duser.language value is the language code of the region where the server is located.

Healthy: The -Duser.language value is not the language code of the region where the server is located.

Suggestion: Set -Duser.language to the language code of the region where the server is located.

Healthy: -Dsun.zip.disableMemoryMapping=true

Unhealthy: -Dsun.zip.disableMemoryMapping ≠ true

Suggestion: Configure -Dsun.zip.disableMemoryMapping=true

Healthy: -XX:NewRatio=2

Unhealthy: -XX:NewRatio ≠ 2

Suggestion: Set the ratio of the old generation to the young generation to 2, namely, -XX:NewRatio=2.

Healthy: -Xss value ≤ 1024 KB

Unhealthy: -Xss value > 1024 KB

Suggestion: Set the stack size per thread (Xss value) to no more than 1024 KB.

Healthy: Parameters -agentlib:jdwp and -Xrunjdwp are not configured.

Unhealthy: Parameters -agentlib:jdwp and -Xrunjdwp are configured.

Suggestion: Remove the -agentlib:jdwp and -Xrunjdwp parameters to disable the debug mode.

Healthy:

FineReport/FineDataLink/bi6: Configuration ≤ 32766 MB or ≥ 48 GB

FineBI - Application Node: 6 GB ≤ Configuration ≤ 32766 MB

Engine - Calculation Node:  12800 MB ≤ Configuration ≤ 32766 MB

Engine - Metadata Node: 2420  MB ≤ Configuration ≤ 32766 MB

Suggestion:

To ensure application responsiveness, you are advised to set on-heap memory to 32766 MB or less.

For the bi6 container, you can set it to 48 GB to 64 GB if larger memory is required, provided that the physical machine has sufficient memory. However, this may result in degradation in responsiveness.

Healthy: Xms value = Xmx value

Unhealthy: Xms value ≠ Xmx value

Suggestion: Set the value of Xms to the same as that of Xmx.

FineReport/FineDataLink/bi6:

MaxMetaspaceSize value ≥ 2 GB

FineBI - Application Node:

MaxMetaspaceSize value ≥ 768M

If the container memory limit is between 6 GB and 8 GB, set the MaxMetaspaceSize value to at least 768 MB.

If the container memory limit exceeds 8 GB, set the MaxMetaspaceSize value to at least 1 GB.

Engine - Calculation Node:

MaxMetaspaceSize value ≥ 768M

If the container memory limit is between 32 G and 64 GB, set the MaxMetaspaceSize value to at least 1 GB.

Engine - Metadata Node:

MaxMetaspaceSize value ≥ 256 MB

If the container memory limit is between 6 GB and 16 GB, set the MaxMetaspaceSize value to at least 256 MB.

If the container memory limit is between 16 GB and 32 GB, set the MaxMetaspaceSize value to at least 512 MB.

If the container memory limit exceeds 32 GB, set the MaxMetaspaceSize value to at least 1 GB.

Healthy: Available disk space in the dump output directory > Heap memory * 2

Unhealthy: Available disk space in the dump output directory ≤ Heap memory *2

Suggestion: Free up disk space in the dump output directory and ensure the available space is at least twice the heap memory size for normal dump file exports.

FineBI - Application Node: 1536 MB ≤ Configuration ≤ 2 GB

Engine - Calculation Node: Configuration ≥ max(6 GB, Xmx value * 0.4 GB)

Engine - Metadata Node: Configuration ≥ 768 MB

FineReport

FineDataLink

This parameter is configured for FineOps-deployed projects by default. Normally, you do not need to fix it.

If any exception occurs, log in to FineOps, click the specific project, choose Health Inspection > System Inspection, and click the Quick Fix button.

If Quick Fix is unavailable, modify the project component configuration under Maintenance > Component Management.

Non-FineOps deployed projects

Operating system: Linux

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually configure the setting as follows:

1. Open the setenv.sh file in Tomcat installation directory/bin.

Create a setenv.sh file if the file does not exist.

2. Append the following line to the end:

JAVA_OPTS="$JAVA_OPTS -XX:MaxDirectMemorySize=2g"

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Windows

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually configure the setting as follows:

1. Open the setenv.bat file in Tomcat installation directory/bin.

Create a setenv.bat file if the file does not exist.

2. Append the following line to the end:

set JAVA_OPTS=%JAVA_OPTS% -XX:MaxDirectMemorySize=2g

3. Restart the project to apply the change.

This parameter is configured for bi6/fr/fdl containers of FineOps-deployed projects by default. Normally, you do not need to fix it.

If any exception occurs, log in to FineOps, click the specific project, choose Health Inspection > System Inspection, and click the Quick Fix button.

If Quick Fix is unavailable, modify the project component configuration under Maintenance > Component Management.

Non-FineOps deployed projects

Operating system: Linux

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually configure the setting as follows:

1. Open the setenv.sh file in Tomcat installation directory/bin.

Create a setenv.sh file if the file does not exist.

2. Append the following line to the end:

JAVA_OPTS="$JAVA_OPTS -Dfineio.read_mem_limit=2"

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Windows

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually configure the setting as follows:

1. Open the setenv.bat file in Tomcat installation directory/bin.

Create a setenv.bat file if the file does not exist.

2. Append the following line to the end:

set JAVA_OPTS=%JAVA_OPTS% -Dfineio.read_mem_limit=2

3. Restart the project to apply the change.

This parameter is configured for bi6/fr/fdl containers of FineOps-deployed projects by default. Normally, you do not need to fix it.

If any exception occurs, log in to FineOps, click the specific project, choose Health Inspection > System Inspection, and click the Quick Fix button.

If Quick Fix is unavailable, modify the project component configuration under Maintenance > Component Management.

Non-FineOps deployed projects

Operating system: Linux

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually configure the setting as follows:

1. Open the setenv.sh file in Tomcat installation directory/bin.

Create a setenv.sh file if the file does not exist.

2. Append the following line to the end:

JAVA_OPTS="$JAVA_OPTS -Dfineio.write_mem_limit=1"

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Windows

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually configure the setting as follows:

1. Open the setenv.bat file in Tomcat installation directory/bin.

Create a setenv.bat file if the file does not exist.

2. Append the following line to the end:

set JAVA_OPTS=%JAVA_OPTS% -Dfineio.write_mem_limit=1

3. Restart the project to apply the change.

Use the G1GC garbage collector for the JVM if JDK 11 is used by default.

Use the ParallelScavenge garbage collector for the JVM if JDK 8 is used.

1. Go to the Project mounting directory/fanruanxxx/fr/mount path and open the setenv.sh file.

2. Append the following line to the end or modify it:

JAVA_OPTS="$JAVA_OPTS -XX:+UseParallelGC"

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Linux

Middleware type: Tomcat

1. Open the setenv.sh file in Tomcat installation directory/bin.

Create a setenv.sh file if the file does not exist.

2. Append the following line to the end:

JAVA_OPTS="$JAVA_OPTS -XX:+UseParallelGC"

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Windows

Middleware type: Tomcat

1. Open the setenv.bat file in Tomcat installation directory/bin.

Create a setenv.bat file if the file does not exist.

2. Append the following line to the end:

set JAVA_OPTS=%JAVA_OPTS% -XX:+UseParallelGC

3. Restart the project to apply the change.

This parameter is not configured for FineOps-deployed projects by default. Normally, you do not need to fix it.

If any exception occurs, log in to FineOps, click the specific project, choose Health Inspection > System Inspection, and click the Quick Fix button.

Non-FineOps deployed projects

Operating system: Linux

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually configure the setting as follows:

1. Open the catalina.sh and setenv.sh files in Tomcat installation directory/bin.

2. Delete the XX:+DisableExplicitGC configuration (if any).

3. Save the change and restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Windows

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually configure the setting as follows:

1. Open the catalina.bat and setenv.bat files in Tomcat installation directory/bin.

2. Delete the XX:+DisableExplicitGC configuration (if any).

3. Save the change and restart the project to apply the change.

FineOps-deployed projects

Projects deployed using the server deployment package provided by FanRuan

Command:

java -version

This parameter is configured for bi6/fr/fdl containers of FineOps-deployed projects by default. Normally, you do not need to fix it.

If any exception occurs, log in to FineOps, click the specific project, choose Health Inspection > System Inspection, and click the Quick Fix button.

Non-FineOps deployed projects

Operating system: Linux

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually configure the setting as follows:

1. Open the setenv.sh file in Tomcat installation directory/bin.

Create a setenv.sh file if the file does not exist.

2. Append the following line to the end:

JAVA_OPTS="$JAVA_OPTS -Djava.awt.headless=true"

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Windows

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually configure the setting as follows:

1. Open the setenv.bat file in Tomcat installation directory/bin.

Create a setenv.bat file if the file does not exist.

2. Append the following line to the end:

set JAVA_OPTS=%JAVA_OPTS% -Djava.awt.headless=true

3. Restart the project to apply the change.

1. Go to the Project mounting directory/fanruanxxx/fr/mount path and open the setenv.sh file.

2. Append the following line to the end.

JAVA_OPTS="$JAVA_OPTS -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/Heap dump storage directory"

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Linux

Middleware type: Tomcat

1. Open the setenv.sh file in Tomcat installation directory/bin.

Create a setenv.sh file if the file does not exist.

2. Append the following line to the end.

JAVA_OPTS="$JAVA_OPTS -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/Heap dump storage directory"

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Windows

Middleware type: Tomcat

1. Open the setenv.bat file in Tomcat installation directory/bin.

Create a setenv.bat file if the file does not exist.

2. Append the following line to the end.

set JAVA_OPTS=%JAVA_OPTS% -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/Heap dump storage directory

3. Restart the project to apply the change.

This parameter is configured for bi6/fr/fdl containers of FineOps-deployed projects by default. Normally, you do not need to fix it.

If any exception occurs, log in to FineOps, click the specific project, choose Health Inspection > System Inspection, and click the Quick Fix button.

Non-FineOps deployed projects

Operating system: Linux

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually configure the setting as follows:

1. Open the setenv.sh file in Tomcat installation directory/bin.

Create a setenv.sh file if the file does not exist.

2. Append the following line to the end:

JAVA_OPTS="$JAVA_OPTS -XX:PerMethodRecompilationCutoff=-1 -XX:PerBytecodeRecompilationCutoff=-1"

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Windows

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually configure the setting as follows:

1. Open the setenv.bat file in Tomcat installation directory/bin.

Create a setenv.bat file if the file does not exist.

2. Append the following line to the end:

set JAVA_OPTS=%JAVA_OPTS% -XX:PerMethodRecompilationCutoff=-1 -XX:PerBytecodeRecompilationCutoff=-1

3. Restart the project to apply the change.

If any exception occurs, log in to FineOps, click the specific project, choose Health Inspection > System Inspection, and click the Quick Fix button.

Non-FineOps deployed projects

Operating system: Linux

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually configure the setting as follows:

1. Open the setenv.sh file in Tomcat installation directory/bin.

Create a setenv.sh file if the file does not exist.

2. Append the following line to the end:

JAVA_OPTS="$JAVA_OPTS -XX:ReservedCodeCacheSize=512m"

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Windows

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually configure the setting as follows:

1. Open the setenv.bat file in Tomcat installation directory/bin.

Create a setenv.bat file if the file does not exist.

2. Append the following line to the end:

set JAVA_OPTS=%JAVA_OPTS% -XX:ReservedCodeCacheSize=512m

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Linux

Middleware type: Tomcat

1. Open the setenv.sh file in Tomcat installation directory/bin.

Create a setenv.sh file if the file does not exist.

2. Append the following line to the end:

JAVA_OPTS="$JAVA_OPTS -Duser.country=Country code -Duser.language=Language code"

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Windows

Middleware type: Tomcat

1. Open the setenv.bat file in Tomcat installation directory/bin.

Create a setenv.bat file if the file does not exist.

2. Append the following line to the end:

set JAVA_OPTS=%JAVA_OPTS% -Duser.country=Country code -Duser.language=Language code

3. Restart the project to apply the change.

1. Go to the Project mounting directory/fanruanxxx/fr/mount path and open the setenv.sh file.

2. Add the following code to the file:

JAVA_OPTS="$JAVA_OPTS -Dsun.zip.disableMemoryMapping=true"

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Linux

Middleware type: Tomcat

1. Open the setenv.sh file in Tomcat installation directory/bin.

Create a setenv.sh file if the file does not exist.

2. Append the following line to the end:

JAVA_OPTS="$JAVA_OPTS -Dsun.zip.disableMemoryMapping=true"

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Windows

Middleware type: Tomcat

1. Open the setenv.bat file in Tomcat installation directory/bin.

Create a setenv.bat file if the file does not exist.

2. Append the following line to the end:

set JAVA_OPTS=%JAVA_OPTS% -Dsun.zip.disableMemoryMapping=true

3. Restart the project to apply the change.

1. Go to the Project mounting directory/fanruanxxx/fr/mount path and open the setenv.sh file.

2. Add the NewRatio value in the same location where the -Xmx and -Xms parameters are set. For example:

JAVA_OPTS="$JAVA_OPTS -Xms2048M -Xmx8196M -XX:NewRatio=2"

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Linux

Middleware type: Tomcat

1. Open the setenv.sh file in Tomcat installation directory/bin.

Create a setenv.sh file if the file does not exist.

2. Add the NewRatio value in the same location where the -Xmx and -Xms parameters are set. For example:

JAVA_OPTS="$JAVA_OPTS -Xms2048M -Xmx8196M -XX:NewRatio=2"

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Windows

Middleware type: Tomcat

1. Open the setenv.bat file in Tomcat installation directory/bin.

Create a setenv.bat file if the file does not exist.

2. Add the NewRatio value in the same location where the -Xmx and -Xms parameters are set. For example:

set JAVA_OPTS=%JAVA_OPTS% -Xms512M -Xmx1024M -XX:NewRatio=2

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Linux

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually configure the setting as follows:

1. Open the setenv.sh file in Tomcat installation directory/bin.

Create a setenv.sh file if the file does not exist.

2. Add the -Xss value in the location where the -Xmx and -Xms parameters are set. For example:

JAVA_OPTS="$JAVA_OPTS -Xms2048M -Xmx8196M -Xss1024K"

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Windows

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually configure the setting as follows:

1. Open the setenv.bat file in Tomcat installation directory/bin.

Create a setenv.bat file if the file does not exist.

2. Add the -Xss value in the location where the -Xmx and -Xms parameters are set. For example:

set JAVA_OPTS=%JAVA_OPTS% -Xms512M -Xmx1024M -1024K

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Linux

Middleware type: Tomcat

1. Open the catalina.sh and setenv.sh files in Tomcat installation directory/bin.

2. Remove the relevant configuration of -agentlib:jdwp and -Xrunjdwp parameters (if any).

3. Save the change and restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Windows

Middleware type: Tomcat

1. Open the catalina.bat and setenv.bat files in Tomcat installation directory/bin.

2. Remove the relevant configuration of -agentlib:jdwp and -Xrunjdwp parameters (if any).

3. Save the change and restart the project to apply the change.

Non-FineOps deployed projects

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually modify the memory settings by referring to Modifying Memory Settings.

Non-FineOps deployed projects

Middleware type: Others

Memory Modification for the WebLogic Server

Memory Modification for the WebSphere Server

Memory Modification for the Resin Server

Memory Modification for the JBoss Server

Non-FineOps deployed projects

Operating system: Linux

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually configure the setting as follows:

1. Open the setenv.sh file in Tomcat installation directory/bin.

Create a setenv.sh file if the file does not exist.

2. Append the following line to the end:

JAVA_OPTS="$JAVA_OPTS -XX:MaxMetaspaceSize=2G"

3. Restart the project to apply the change.

Non-FineOps deployed projects

Operating system: Windows

Middleware type: Tomcat

• If the project is managed by FineOps, you are advised to use the Quick Fix button on the System Inspection page of FineOps to resolve the issue.

• If the project is not managed by FineOps, you are advised to log in to the FanRuan application, choose System Management > Intelligent O&M > Health Inspection, and use the Quick Fix button to resolve the issue.

• If you do not have the required permission to create, read, or write files and therefore cannot use Quick Fix, you can manually configure the setting as follows:

1. Open the setenv.bat file in Tomcat installation directory/bin.

Create a setenv.bat file if the file does not exist.

2. Append the following line to the end:

set JAVA_OPTS=%JAVA_OPTS% -XX:MaxMetaspaceSize=2G

3. Restart the project to apply the change.

0901

Redis Connection

Yes

No

It checks whether the project and the redis component are connected.

0902

File Server Connection

Yes

No

It checks whether the project and the file server component are connected.

0903

FineDB Connection

Yes

No

It checks whether the project and the FineDB database are connected.

finedb

No

No

It checks the type of the FineDB database.

Healthy: The FineDB database is migrated to an external database.

Unhealthy: The FineDB database uses the built-in HSQL database.

Suggestion: You are advised to migrate FineDB to a more stable external database.

Log Level

No

No

It checks System Log Level under System Management > Intelligent O&M > Platform Log > Global Setting.

Healthy: The log level is higher than the DEBUG level.

Unhealthy: The log level is the DEBUG level.

Suggestion: You are advised to set the log level to INFO.

Log Cleanup

No

No

It checks the Clearance Frequency under System Management > Intelligent O&M > Platform Log > Global Setting > Auto Cleanup.

Healthy: Auto Cleanup is configured and logs older than three months are automatically cleaned up.

Unhealthy: Auto Cleanup is not configured.

Suggestion: You are advised to enable the automatic cleaning of platform logs and set a cleaning cycle of less than six months.

Limit of Disk Space Occupied by Automatic Backup

No

No

It checks the value of Maximum Disk Space Occupied by Automatic Backup Records Per Module under System Management > Intelligent O&M > Backup & Restoration > Global Setting.

Healthy: The value of Maximum Disk Space Occupied by Automatic Backup Records Per Module is no more than 1024 MB.

Unhealthy: The value of Maximum Disk Space Occupied by Automatic Backup Records Per Module is more than 1024 MB.

Suggestion: You are advised to set the value of Maximum Disk Space Occupied by Automatic Backup Records Per Module to no more than 1024 MB.

Quantity Limit of Automatic Backup Records Retained

No

No

It checks the value of Maximum Number of Successful/Failed Automatic Backup Records Per Module under System Management > Intelligent O&M > Backup & Restoration > Global Setting.

Healthy: The value of Maximum Number of Successful/Failed Automatic Backup Records Per Module is no more than 5 records.

Unhealthy: The value of Maximum Number of Successful/Failed Automatic Backup Records Per Module is more than 5 records.

Suggestion: You are advised to set the value of Maximum Number of Successful/Failed Automatic Backup Records Per Module to no more than 5 records.

Scheduled Task Cleanup Configuration

No

No

It checks the settings of File Processing under Task Schedule > Schedule Object.

Healthy: Retain Only Latest 1 Times or Clear Upon Task End.

Unhealthy: other file processing methods

Suggestion: You are advised to set the scheduling object file processing of scheduled tasks to Retain Only Latest 1 Times.

Row Quantity Limit of Memory Data

No

No

Note:

This item is only inspected for FineBI projects.

It checks the value of the Data Access Volume parameter under System Management > System Setting > BI Parameter > Restriction Parameter.

Healthy: The value of Data Access Volume is no more than 1000000.

Unhealthy: The value of Data Access Volume is more than 1000000.

Suggestion: You are advised to set the value of Data Access Volume to no more than 1000000.

Cell Quantity Limit for Quick Calculation

No

No

Note:

This item is only inspected for FineBI projects.

It checks the value of the spider_fast_compute_limit_unit parameter.

Healthy: The value of the DistributedOptimizationConfig.spiderConfig.spider_fast_compute_limit_unit parameter is no more than 10000000.

Unhealthy: The value of the DistributedOptimizationConfig.spiderConfig.spider_fast_compute_limit_unit parameter is more than 10000000.

Memory Limit for Quick Calculation

No

No

Note:

This item is only inspected for FineBI projects.

It checks the value of the spider_fast_compute_limit_memory parameter.

Healthy: The value of the DistributedOptimizationConfig.spiderConfig.spider_fast_compute_limit_memory parameter is no more than 500000000.

Unhealthy: The value of the DistributedOptimizationConfig.spiderConfig.spider_fast_compute_limit_memory parameter is more than 500000000.

Updated Cell Quantity Limit for Quick Calculation

No

No

Note:

This item is only inspected for FineBI projects.

It checks the value of the spider_update_fast_compute_limit_cell parameter.

Healthy: the value of the DistributedOptimizationConfig.spiderConfig.spider_update_fast_compute_limit_cell parameter is no more than 100000000.

Unhealthy: the value of the DistributedOptimizationConfig.spiderConfig.spider_update_fast_compute_limit_cell parameter is more than 100000000.

Row Quantity Limit for Quick Calculation

No

No

Note:

This item is only inspected for FineBI projects.

Healthy: The value of the DistributedOptimizationConfig.spiderConfig.spider_fast_compute_limit_row parameter is no more than 10000000.

Unhealthy: The value of the DistributedOptimizationConfig.spiderConfig.spider_fast_compute_limit_row parameter is more than 10000000.

Memory Limit of Spark Calculation Result

No

No

Note:

This item is only inspected for FineBI projects.

It checks the value of the spiderConfig.spark_driver_maxResultSize parameter.

Healthy: The value of the DistributedOptimizationConfig.spiderConfig.spark_driver_maxResultSize parameter is no more than 10000000.

Unhealthy: The value of the DistributedOptimizationConfig.spiderConfig.spark_driver_maxResultSize parameter is more than 10000000.

1013

Memory Limit of Spark

No

Yes

Note:

This item is only inspected for FineBI projects.

It checks the value of the spark_memory_fracrtion parameter.

Suggestion: You are advised to set the value of spark_memory_fraction to no more than 0.3 * 1/8 of the on-heap memory and no more than 0.6.

Encoding/Character Set of External Database

No

No

It only outputs information.

It includes the encoding/character set of the FineDB external database.

For details about configuring the external database, see External Database Configuration.

Cluster Parameter Configuration

No

No

It only outputs information.

It checks the values of Internal Forwarding Parameter under System Management > Intelligent O&M > Cluster Configuration > Parameter Configuration.

Unlimited Period Configuration for Resource Update

No

No

Note:

This item is only inspected for FineBI projects.

It only outputs information.

It checks the value of the Update High Performance Time Interval parameter under System Management > System Setting > BI Parameter > Data Update Configuration.

For details about configuring BI parameters, see BI/Spider Parameter.

Second-Level Cache Enabling Status

No

No

It only outputs information.

It checks whether the system is configured with the second-level cache.

For details about enabling and configuring the second-level cache, see Specifying the Ehcache Cache Path.

SQL Execution Period Limit

No

No

It checks the value of SQL Execution Period Limit under System Management > Intelligent O&M > Load Management > Template Limit > General Limit.

Healthy: SQL Execution Period Limit is enabled.

Unhealthy: SQL Execution Period Limit is not enabled.

Suggestion: You are advised to enable SQL Execution Period Limit under System Management > Intelligent O&M > Load Management > Template Limit > General Limit.

Cell Quantity Limit Per Template

No

No

It checks the value of Template Cell Limit under System Management > Intelligent O&M > Load Management > Template Limit > General Limit.

Healthy: Template Cell Limit is enabled.

Unhealthy: Template Cell Limit is not enabled.

Suggestion: You are advised to enable Template Cell Limit under System Management > Intelligent O&M > Load Management > Template Limit > General Limit.

Cell Quantity Limit During Excel Import

No

No

It checks the value of Excel Import Limit under System Management > Intelligent O&M > Load Management > Template Limit > General Limit. 

Healthy: Excel Import Limit is enabled.

Unhealthy: Excel Import Limit is not enabled.

Suggestion: You are advised to enable Excel Import Limit under System Management > Intelligent O&M > Load Management > Template Limit > General Limit.

Row Quantity Limit Per Dataset

No

No

It checks the value of Dataset Row Limit under System Management > Intelligent O&M > Load Management > Template Limit > General Limit.

Healthy: Dataset Row Limit is enabled.

Unhealthy: Dataset Row Limit is not enabled.

Suggestion: You are advised to enable Dataset Row Limit under System Management > Intelligent O&M > Load Management > Template Limit > General Limit.

Load Alert Enabled

No

No

It only outputs information.

It checks whether Intelligent Alert under System Management > Intelligent O&M > Load Management > Load Surveillance is enabled.

Dirty Data Detection

No

No

Note:

This item is only inspected for FineBI projects.

It checks whether there is dirty data.

Healthy: There is 0 piece of dirty data.

Unhealthy: There are x piece(s) of dirty data.

Suggestion: If there are x piece(s) of dirty data, you are advised to choose BI Tool > Detection > Dirty Data to check and clean them up.

Whether to enable cloud operation and maintenance

No

No

It only outputs information.

It checks whether the system enables cloud operation and maintenance.

Password Strength Limit Check

No

No

It checks whether Password Strength Limit under System Management > System Setting > Login is enabled.