FineOps Version
Functional Change
V1.5.5
V1.5.6
1. Added the following items to System Inspection:
0113 CPU Information
0114 Server Font Encoding
0115 Server Font Package
2. Added the following item to Business Inspection:
1025 Whether to enable Cloud O&M
3. Added the following item to Non-Containerized Deployment Information:
0603 Multi-process Detection
4. Added the following item to Java VM Inspection:
0822 JDK Path
V1.5.9
1. Added the following items to Disk Inspection:
0509 Sequential Read (Non-buffer Pool)
0510 Sequential Write (Non-buffer Pool)
2. Deleted the following item in Disk Inspection:
0503 Random Read
3. Displayed "The rate is less than 100 MB/s." instead of specific values if the disk read/write speed was below 100 MB/s.
V1.8.0
Added the following item to Business Inspection:
1026 Password Strength Limit Detection
V1.9.0
1. Supported Quick Fix for the following item of Environment Inspection:
0705 Glibc Memory Leak Configuration
2. Supported Quick Fix for the following items of Java VM Inspection:
0807 Headless Mode
0809 BytecodeRecompilationCutoff Configuration
0810 PerMethodRecompilationCutoff Configuration
0813 Code Cache Configuration
0816 ZIP-Related Configuration - Dsun.zip.disableMemoryMapping
3. Added the following item to Java VM Inspection:
0823 Metadata Space Configuration
V1.10.0
Added the following item to System Operation Status:
0212 Tomcat Background Running
V2.7.0
1. Added the following item to Non-Containerized Deployment Information:
0604 File Server Solution for Cluster
2. Added the following item to Java VM Inspection:
0824 Disk Space Required for Dump Output
3. Added the following items to Business Inspection:
1027 Limit on Submitted Record Quantity
1028 Data Export Volume Limit Per Chart
1029 Template Limit Relaxation
1030 Enable Extracted Data Cache
1031 Cache Space Limit
1032 Enable Parallel Dashboard Calculation
1033 Enable Crash Handling Tool
1034 Automatic Stack Export of Auto Carsh Handling Tool
1035 Lifecycle Setting
1036 Spark Memory Ratio
1037 Update Relevant Configuration
1038 Update SQL Complexity Limit
FanRuan applications have certain system configuration requirements. If the requirements are not met, there may be risks of abnormal usage or crashes. Therefore, you need to regularly inspect the environments and configurations to ensure the healthy operation of the applications.
Meanwhile, the admin needs to monitor the application's operating status and use O&M methods to mitigate risks or locate and resolve issues in time after they occur to ensure the continuous high availability of applications.
Items of System Inspection include:
Inspection Item Number
Inspection Item
Whether Cluster Nodes Are Checked Separately
Whether Quick Fix Is Supported
Health Standards and Suggestions for Modification
0101
Operating System Information
Yes
No
It only outputs information.
0102
Server Time
0103
Time Zone
0104
Glibc/GCC Version
0105
Hostname
0106
Host File Information
0107
CPU Clock Speed
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
It checks whether the number of CPU cores is greater than four.
You are advised to ensure that the number of CPU cores is greater than four.
0109
Memory Size
It checks whether the memory is not less than 15.5 GB.
You are advised to ensure that the physical memory is not less than 16 GB.
0110
Swap
It checks whether the swap configuration is disabled.
It outputs the size of the swap partition.
You are advised to disable the swap configuration.
0111
Memory Used
0112
Available Memory
0113
CPU Information
0114
Server Font Encoding
0115
Server Font Package
Linux Server
1. Log in to the host machine.
Use an appropriate authentication method (such as SSH or Console) to log in to the host machine where the container is running.
2. Check whether the swap partition is enabled in the current system.
Use the following command to view the information of the started swap partition in the system:
sudo swapon -s
If the output result is empty, it means that the swap partition is not started currently.
3. Disable the swap partition.
Use the following command to disable the swap partition:
sudo swapoff -a
This command disables all started swap partitions.
4. Disable the swap partition permanently.
To prevent the swap partition from being automatically enabled during the next system startup, you need to modify the system configuration file correspondingly.
Taking Ubuntu as an example, you can follow these steps:
Comment out or delete the line containing swap in the fstab file of the /etc directory.
Execute the following command to update the grub bootloader:
sudo update-grub
5. Verify whether the swap partition has been disabled.
After restarting the system, you can execute the sudo swapon -s command again to see if there is a started swap partition.
If the output result is empty, it means that the swap partition has been disabled successfully.
Windows Server
1. Log in to the server and choose System Properties > Advanced > Performance> Settings.
2. Click Change under Advanced > Virtual Memory.
3. Deselect Automatically manage paging file size of all drivers.
4. Select Custom Size and set the initial size and maximum size.
Items of System Operation Status Inspection include:
Health Standard
0201
Startup Duration
It only outputs information, including the time taken for this startup.
0203
Project Startup Path
It only outputs information, including directory path.
0204
Abnormal Project Folder Size
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
It only outputs information, including plugin name, version, and enabled or not.
0206
Registration Authorization Information
It only outputs information, including whether the project is registered.
0207
web.xml Available Under WEB-INF or Not
It only outputs information, including Yes/No.
0208
Container Version
0209
Project JAR Package Information
It only outputs information, including versions of various modules in the project and JAR package dates.
0211
Temporary Output Directory
It only outputs information, including directory path and remaining available space in the directory.
0212
Tomcat Background Running
For projects in Windows systems using the Tomcat container:
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.
The Contents Under WEB-INF
FineBI: Structure of FineBI Installation Directory
The Cleanable Folders/Files
Folders/Files
Manual Cleanup
1. Path:
%BI_HOME%\webapps\webroot\WEB-INF\schedule
2. Usage:
It stores intermediate files generated by scheduled tasks.
3. Cleanable scope:
Keep the files generated within one year and clean up the rest files.
4. Cleanup level:
You are advised to clean up its content.
Automatic cleanup is not supported.
Specific dates (accurate to the day) are directly displayed under the file hierarchy. You can manually select the time range and clean up the files.
You are advised to clean up files generated more than 12 months ago.
The files generated within 12 months will not be displayed.
treasure
%BI_HOME%\webapps\webroot\WEB-INF\treasures
It stores packages of cloud O&M logs.
3. Cleanup level:
Keep the files generated within 12 months and clean up the rest files.
Cleanup Method
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.
Cause Analysis:
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.
Procedure:
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 %Tomcat_HOME%\bin\setclasspath.bat, find set _RUNJAVA, and modify its value:
set _RUNJAVA="%JRE_HOME%\bin\javaw.exe"
2. Modify catalina.bat
Open %Tomcat_HOME%\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
)
Items of Port Inspection include:
0301
WebSocket Port
It only outputs information, including port number.
0302
Cluster Port
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
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.
WebSocket is mainly used to refresh tokens, check users being kicked out, display platform messages, memory, and CPU, check the number of current system online users in the platform log, and determine data connection editing status.
Disabling WebSocket will affect the socket communication and may result in abnormal access disconnection.
You can choose the appropriate WebSocket port configuration methods according to project situations. For details, see the following table.
Solution
Scenario
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
Configure WebSocket port in a stand-alone environment.
Configure WebSocket port in a cluster environment.
Configure WebSocket port in an HTTPS environment.
Only one port is open to the outside world.
Log in to a FanRuan application as the admin, and choose System Management > Intelligent O&M > Cluster Configuration.
You can view the ports of each node in the cluster. The nodes that cannot be used will be highlighted in red.
The node ports are editable. You can hover the cursor over a specific node to make the Edit button appear.
Log in to FineOps as the admin, click a project, and choose Crash > Crash Handling Strategy.
You can view the port used by Auto Crash Handling Tool. The default port number is 12100.
The port number is editable. Click Test to check the port availability and click Save.
Check whether the communication between the file server, external database, state server, and application is normal, whether they can be pinged, and whether there are any packet losses.
Items of Disk Inspection include:
0501
Sequential Read
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).
0502
Sequential Write
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).
0504
Small File Creation
It only outputs information, including the number of small files created per second.
0505
Small File Deletion
It only outputs information, including the number of small files deleted per second.
0506
Disk Space
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
It only outputs information, including the size of the used disk space.
0508
Free Disk Space
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.
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)
It only outputs information, including the speed of sequential read in the non-buffer pool (display "The rate is less than 100 MB/s." instead of specific values if the speed is below 100 MB/s).
0510
Sequential Write (Non-buffer Pool)
It only outputs information, including the speed of sequential write in the non-buffer pool (display "The rate is less than 100 MB/s." instead of specific values if the speed is below 100 MB/s).
Items of Non-Containerized Deployment Information Inspection include:
0601
Process User
It only outputs information, including user name.
0602
Server Main Folder Permissions
It only outputs information, including cache folder, resources, assets, assit, and finedb permissions.
0603
Multi-process Detection
Healthy: The sum of Maximum memory required by FanRuan applications and Memory used by other processes is less than Total physical memory.
Unhealthy: The sum of Maximum memory required by FanRuan applications and Memory used by other processes is not less than 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
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 inconsistency may occur.
Items of Environment Inspection include:
vm.max_map_count
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
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.
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
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
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
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.
Parameter Introduction
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.
Recommended Configuration
You are advised to configure the vm.max_map_count parameter to 262144.
Modification Method
Add/Modify the parameter value vm.max_map_count = 262144 in the /etc/sysctl.conf file.
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.
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.
Delete system-level restrictions.
Check whether there are statements related to ulimit -n xxx in the /etc/profile file.
If relevant statements exist, delete those statements and reload the shell environment using the source/etc/profile statement.
Modify user-level restrictions.
Open the software and hardware restriction file /etc/security/limits.conf on Linux and add the following codes 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.
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.
You are advised to set the vm.overcommit_memory parameter to 0.
Add/Modify the parameter value vm.overcommit_memory = 0 in the etc/sysctl.conf file.
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.
You are advised to set the vm.overcommit_ratio parameter to 50.
Add/Modify the parameter value vm.overcommit_ratio = 50 in the etc/sysctl.conf file.
To prevent memory leaks in glibc, you can limit the amount of heap space glibc uses when it allocates and releases dynamic memory by setting the MALLOC_ARENA_MAX environment variable.
You are advised to configure the export MALLOC_ARENA_MAX parameter to 1.
Close Tomcat server.
Go to the %Tomcat_HOME%/bin directory and open the startup.sh file.
Add/Modify the line at the beginning of the file: export MALLOC_ARENA_MAX = 1.
Save the changes to the startup.sh file and close it.
Run the startup.sh file in the terminal to restart Tomcat and apply the new environment variable settings.
Items of Java VM Inspection include:
0801
Off-Heap NIO Memory
For FineReport projects: You are advised to set the value of off-heap memory that can be occupied by JVM NIO to 2 GB.
For FineBI projects: You are advised to set the value of off-heap memory that can be occupied by JVM NIO to 4 GB.
0802
Off-Heap Memory Occupied by FineIO Reading
You are advised to set the value of off-heap memory that can be occupied by JVM FineIO Reading to 2 GB.
0803
Off-Heap Memory Occupied by FineIO Writing
You are advised to set the value of off-heap memory that can be occupied by JVM FineIO Writing to 1 GB.
0804
Garbage Collector Type
You are advised to set the Garbage Collector Type to ParallelScavenge for JVM.
0805
DisableExplicitGC Parameter
Healthy: The DisableExplicitGC parameter is not configured.
Unhealthy: The DisableExplicitGC parameter is configured.
Suggestion: You are advised to cancel the DisableExplicitGC parameter configuration.
0806
JDK Version
Healthy: The current version is higher than the built-in JAVA version of FanRuan applications (typically 1.8.202 and above versions).
Unhealthy: The current version is lower than the built-in JAVA version of FanRuan applications.
Suggestion: You are advised to use JDK 1.8.202 and above versions.
0807
Headless Mode
Healthy: -Djava.awt.headless = true is configured.
Unhealthy: -Djava.awt.headless = true is not configured.
Suggestion: You are advised to configure -Djava.awt.headless = true to enable the headless mode.
0808
Dump Export
Healthy: HeapDumpOnOutOfMemoryError and HeapDumpPath are configured.
Unhealthy: HeapDumpOnOutOfMemoryError and HeapDumpPath are not configured.
Suggestion: You are advised to configure HeapDumpOnOutOfMemoryError and HeapDumpPath to ensure the normal exporting of dump files.
0809
BytecodeRecompilationCutoff Configuration
Healthy: -XX:PerBytecodeRecompilationCutoff = -1
Unhealthy: -XX:PerBytecodeRecompilationCutoff ≠ -1
Suggestion: You are advised to configure -XX:PerBytecodeRecompilationCutoff = -1.
0810
PerMethodRecompilationCutoff Configuration
Healthy: -XX:PerMethodRecompilationCutoff = -1
Unhealthy: -XX:PerMethodRecompilationCutoff ≠ -1
Suggestion: You are advised to configure -XX:PerMethodRecompilationCutoff = -1.
0811
Installation Package Deployment
Healthy: The project is not deployed using an EXE file.
Unhealthy: The project is deployed using an EXE file.
Suggestion: You are advised to use a web container for deployment. For details, see Selecting a Project Deployment Solution.
0813
Code Cache Configuration
For FineReport projects:
Healthy: -XX:ReservedCodeCacheSize is set to a value not less than 512 MB.
Unhealthy: -XX:ReservedCodeCacheSize is set to a value less than 512 MB.
Suggestion: You are advised to configure -XX: ReservedCodeCacheSize = 512 MB.
For FineBI projects:
Healthy: -XX:ReservedCodeCacheSize is set to a value not less than 1024 MB.
Unhealthy: -XX:ReservedCodeCacheSize is set to a value less than 1024 MB.
Suggestion: You are advised to configure -XX: ReservedCodeCacheSize = 1024 MB.
0816
ZIP-Related Configuration - Dsun.zip.disableMemoryMapping
Healthy: -Dsun.zip.disableMemoryMapping = true
Unhealthy: -Dsun.zip.disableMemoryMapping ≠ true
Suggestion: You are advised to configure -Dsun.zip.disableMemoryMapping = true.
0817
Ratio of Old Generation to Young Generation
Healthy: -XX:NewRatio = 2
Unhealthy: -XX:NewRatio ≠ 2
Suggestion: You are advised to set the ratio of the old generation to the new generation to 2, namely, -XX:NewRatio = 2.
0818
Stack Space
Healthy: -Xss is set to a value not greater than 1024 KB.
Unhealthy: -Xss is set to a value greater than 1024 KB.
Suggestion: You are advised to set the -Xss parameter (stack space per thread) to a value not greater than 1024 KB.
0819
Debug Mode
Healthy: Parameters -agentlib:jdwp and -Xrunjdwp are not configured.
Unhealthy: Parameters -agentlib:jdwp and -Xrunjdwp are configured.
Suggestion: You are advised to disable the Debug Mode and delete -agentlib:jdwp and -Xrunjdwp parameters.
0820
On-Heap Memory
Healthy: A range of the on-heap memory size that meets the health standards is calculated based on the actual system conditions. The value of the current on-heap memory is within the range.
Unhealthy: The value of the current on-heap memory is beyond the range. Suggestion: To ensure the application response performance, you are advised to set the value of On-Heap Memory to X GB.
Additional reminder for FineBI projects: If more memory is needed, you can also set it to a value between 48 GB and 64 GB when sufficient memory is ensured for the physical machine, but it may compromise the response performance.
0821
XMS Configuration
Healthy: Xms = Xmx
Unhealthy: Xms ≠ Xmx
Suggestion: You are advised to set the size of Xms to the same as that of Xmx.
0822
JDK Path
0823
Metadata Space Configuration
Healthy: -XX:MaxMetaspaceSize is set to a value not less than 2 GB.
Unhealthy: -XX:MaxMetaspaceSize is set to a value less than 2 GB or not configured.
Suggestion: You are advised to set the value of the maximum metadata space to 2 GB.
0824
Disk Space Required for Dump Output
Healthy: The remaining disk space of the dump output directory is greater than Heap memory * 2.
Unhealthy: The remaining disk space of the dump output directory is not greater than Heap memory * 2.
Suggestion: You are advised to clean the disk space of the dump output directory and ensure a free space of twice the size of heap memory to export the dump file normally.
Recommended Value
NIO is controlled by the -XX:MaxDirectMemorySize parameter. Choose the modification method according to your project deployment methods.
Deployment Method
FineOps-Deployed Projects
The -XX:MaxDirectMemorySize parameter is configured for bi 6/fr/fdl components 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, and click the Quick Fix button under Health Inspection > System Inspection.
Non-FineOps Deployed Projects
Operating System: Linux
Middleware Type: Tomcat
Priority is given to using the Quick Fix function under Health Inspection > System Inspection to fix it.
If you do not have the permission to create, read, or write files, you can follow these steps and configure the parameter manually:
1. Go to the %Tomcat_HOME%/bin path and find the setenv.sh file.
Create a setenv.sh file if the file does not exist.
2. Add the following code to the file:
JAVA_OPTS="$JAVA_OPTS -XX:MaxDirectMemorySize=4g"
3. Restart the project for the configuration to take effect.
Operating System: Windows
1. Go to the %Tomcat_HOME%/bin path and find the setenv.bat file.
Create a setenv.bat file if the file does not exist.
set JAVA_OPTS=%JAVA_OPTS% -XX:MaxDirectMemorySize=4g
FineIO Read Memory is controlled by the -Dfineio.read_mem_limit parameter. Choose the modification method according to your project deployment methods.
The default unit of read memory is GB. Using decimals is supported, while using units like g and m is not supported. You are advised to set the size of the read memory to two to three times that of the write memory and set the size of the cache to the same as that of the write memory.
JAVA_OPTS="$JAVA_OPTS -Dfineio.read_mem_limit=2"
set JAVA_OPTS=%JAVA_OPTS% -Dfineio.read_mem_limit=2
FineIO write memory is controlled by the -Dfineio.write_mem_limit parameter. Choose the modification method according to your project deployment methods.
The default unit of write memory is GB. Using decimals is supported, while using units like g and m is not supported. You are advised to set the size of the read memory to two to three times that of the write memory and set the size of the cache to the same as that of the write memory.
JAVA_OPTS="$JAVA_OPTS -Dfineio.write_mem_limit=1"
set JAVA_OPTS=%JAVA_OPTS% -Dfineio.write_mem_limit=1
This section introduces how to set the Garbage Collector Type to ParallelScavenge.
1. Go to the Project mounting directory/fanruanxxx/fr/mount path and find the setenv.sh file.
2. Add/Modify the following code in the file:
JAVA_OPTS="$JAVA_OPTS -XX:+UseParallelGC"
set JAVA_OPTS=%JAVA_OPTS% -XX:+UseParallelGC
The function of the -XX:+DisableExplicitGC parameter is to disable the System.gc() method. System.gc() is a protection mechanism. For example, it recycles objects to make the memory they occupy available when the off-heap memory runs out.
You are advised not to configure the DisableExplicitGC parameter. Configuring it may disable System.gc() and reduce system stability.
This section introduces how to delete the DisableExplicitGC parameter.
The DisableExplicitGC parameter is not configured for FineOps-deployed projects by default. Normally, you do not need to fix it.
If you do not have the permission to read or write files, you can follow these steps and configure the parameter manually:
1. Go to the %Tomcat_HOME%/bin path and find catalina.sh and setenv.sh files.
2. If XX:+DisableExplicitGC exists in the files, delete the relevant configuration.
3. Save the changes and restart the project for the modification to take effect.
1. Go to the %Tomcat_HOME%/bin directory and find the catalina.bat and setenv.bat files.
You are advised to use JDK8 1.8.0_181 and above versions.
Inspection Method
This section only introduces how to check the JDK version. If your version does not meet the requirements, refer to the documents of relevant products to upgrade/reinstall the JDK product.
Projects Deployed Using FanRuan Server Deployment Package
The built-in JDK version meets the requirements, and requires no checking.
Projects Deployed Using Self-Prepared JDK
Command: java -version
The headless mode is a working mode of the system. If the system property java.awt.headless is set to true, the headless toolkit will be used.
You are advised to configure -Djava.awt.headless = true to enable the headless mode.
This section introduces the steps of enabling the headless mode.
JAVA_OPTS="$JAVA_OPTS -Djava.awt.headless=true"
set JAVA_OPTS=%JAVA_OPTS% -Djava.awt.headless=true
You are advised to configure HeapDumpOnOutOfMemoryError and HeapDumpPath to ensure the normal exporting of dump files.
The -XX:+HeapDumpOnOutOfMemoryError parameter indicates that a dump file is automatically generated when an OOM occurs in the JVM.
The -XX:HeapDumpPath=${Directory} parameter indicates the path of the generated dump file. You can also specify the file name, for example, -XX:HeapDumpPath=${Directory}/java_heapdump.hprof.
If the file name is not specified, the default name is java_<Pid>_<Date>_<Time>_heapDump.hprof.
This section introduces how to configure and export dump files.
2. Add the following code to the file.
JAVA_OPTS="$JAVA_OPTS -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/Heap dump storage directory"
set JAVA_OPTS=%JAVA_OPTS% -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/Heap dump storage directory
It is modified together with 0810 PerMethodRecompilationCutoff Configuration. For details, see the next section.
Not configuring the RecompilationCutoff parameter or setting it to an excessively small value may cause the spider engine data to be slowly updated.
You are advised to set recompilationCutoff-related parameters to -1.
This section introduces how to configure the recompilationCutoff parameter.
JAVA_OPTS="$JAVA_OPTS -XX:PerMethodRecompilationCutoff=-1 -XX:PerBytecodeRecompilationCutoff=-1"
set JAVA_OPTS=%JAVA_OPTS% -XX:PerMethodRecompilationCutoff=-1 -XX:PerBytecodeRecompilationCutoff=-1
This item is only inspected for FineBI projects.
Priority is given to deploying FineBI projects via FineOps.
If you do not use FineOps for deployment, ensure FineBI projects are at least deployed using a Web container. For details, see Tomcat Package Deployment in Linux.
The ReservedCodeCacheSize parameter is used for adjusting the memory size. The value may affect the size of Code Cache.
If the space of Code Cache is insufficient, the JVM may not run properly, resulting in a continuous decrease in performance.
You are advised to configure -XX: ReservedCodeCacheSize = 512 MB.
This section introduces how to modify the ReservedCodeCacheSize parameter.
JAVA_OPTS="$JAVA_OPTS -XX:ReservedCodeCacheSize=512m"
set JAVA_OPTS=%JAVA_OPTS% -XX:ReservedCodeCacheSize=512m
Configuring this parameter can prevent JVM crashes.
You are advised to configure -Dsun.zip.disableMemoryMapping = true.
JAVA_OPTS="$JAVA_OPTS -Dsun.zip.disableMemoryMapping=true"
set JAVA_OPTS=%JAVA_OPTS% -Dsun.zip.disableMemoryMapping=true
The recommended ratio of the old generation to the new generation is 2. (-XX:NewRatio defaults to 2 for JVM.) The parameter setting can only take effect when the size of the new generation is unlimited.
Add the configuration of -XX:NewRatio where the -Xmx and -Xms parameters are located. This section introduces how to configure -XX:NewRatio.
2. Add the configuration of -XX:NewRatio where the -Xmx and -Xms parameters are located. For example:
JAVA_OPTS="$JAVA_OPTS -Xms2048M -Xmx8196M -XX:NewRatio=2"
set JAVA_OPTS=%JAVA_OPTS% -Xms512M -Xmx1024M -XX:NewRatio=2
You are advised to set the value of stack space per thread (-Xss) to not greater than 1024 KB.
Add the value of -Xss where the -Xmx and -Xms parameters are configured. This section introduces how to configure -Xss.
Log in to FineOps, click the specific project, and click the Quick Fix button under Health Inspection > System Inspection.
2. Add the value of -Xss where the -Xmx and -Xms parameters are configured. For example:
JAVA_OPTS="$JAVA_OPTS -Xms2048M -Xmx8196M -Xss1024K"
set JAVA_OPTS=%JAVA_OPTS% -Xms512M -Xmx1024M -1024K
The debug mode is controlled by -agentlib:jdwp and -Xrunjdwp parameters. Deleting these two parameters can disable the debug mode.
You are advised to disable the debug mode.
This section introduces how to disable the debug mode.
The -agentlib:jdwp and -Xrunjdwp parameters are not configured for FineOps-deployed projects by default. Normally, you do not need to fix it.
2. If -agentlib:jdwp and -Xrunjdwp parameters exist in the files, delete the relevant configuration.
非运维平台部署的项目
操作系统为Windows
中间件类型为Tomcat
It is modified together with 0821 XMS Configuration. For details, see the next section.
-Xmx parameter: the maximum on-heap memory
-Xms parameter: the initial memory size
2. You are advised to configure Xms = Xmx to prevent memory expansion failure.
If you do not have the permission to create, read, or write files, you can configure the parameter manually.
Middleware Type: Others
Modify the WebLogic server configuration.
Modify the WebSphere server configuration.
Modify the Resin server memory.
Modify the JBoss server memory.
Metaspace is the area used by the Java Virtual Machine (JVM) to store class metadata. In the JVM, metadata includes class structure information, method information, and field information.
The MaxMetaspaceSize parameter is used to set the maximum size of the metadata space. When the size of the metadata space exceeds this limit, the JVM will perform garbage collection to release metadata that is no longer in use.
You are advised to configure the MaxMetaspaceSize parameter to 2 GB.
This section introduces how to configure the MaxMetaspaceSize parameter.
JAVA_OPTS="$JAVA_OPTS -XX:MaxMetaspaceSize=2G"
set JAVA_OPTS=%JAVA_OPTS% -XX:MaxMetaspaceSize=2G
Items of Service Connection Inspection include:
0901
Redis Connection
It checks whether the project and the redis component are connected.
0902
File Server Connection
It checks whether the project and the file server component are connected.
0903
FineDB Connection
It checks whether the project and the FineDB database are connected.
Items of Business Inspection include:
finedb
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
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
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
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
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
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
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 During Quick Analysis
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 Size Limit During Quick Analysis
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.
Quantity Limit of Updated Cell During Quick Analysis
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 During Quick Analysis
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 Size Limit of Spark Calculation Result
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 Size Limit of Spark
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
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
It checks the values of Internal Forwarding Parameter under System Management > Intelligent O&M > Cluster Configuration > Parameter Configuration.
Unlimited Period Configuration for Resource Update
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
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
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
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
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
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
It checks whether Intelligent Alert under System Management > Intelligent O&M > Load Management > Load Surveillance is enabled.
Dirty Data Detection
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
It checks whether the system enables cloud operation and maintenance.
Password Strength Limit Detection
It checks whether Password Strength Limit under System Management > System Setting > Login is enabled.
Healthy: Password Strength Limit is enabled.
Unhealthy: Password Strength Limit is not enabled.
Suggestion: Password Strength Limit is not enabled, which may cause your account to be vulnerable to attack due to weak password strength and incur security problems. You are advised to enable Password Strength Limit under System Management > System Setting > Login.
1027
Limit on Submitted Record Quantity
It checks whether Record Submission Limit under System Management > Intelligent O&M > Load Management > Template Limit is enabled.
Healthy: Record Submission Limit is enabled.
Unhealthy: Record Submission Limit is not enabled.
Suggestion: You are advised to enable Record Submission Limit under System Management > Intelligent O&M > Load Management > Template Limit > General Limit.
1028
Data Export Volume Limit Per Chart
It checks whether Data Export Volume Limit Per Chart under System Management > Intelligent O&M > Load Management > Template Limit is enabled.
Healthy: Data Export Volume Limit Per Chart is enabled.
Unhealthy: Data Export Volume Limit Per Chart is not enabled.
Suggestion: You are advised to enable Data Export Volume Limit Per Chart under System Management > Intelligent O&M > Load Management > Template Limit > General Limit.
1029
Template Limit Relaxation
It checks whether Limit Relaxation under System Management > Intelligent O&M > Load Management > Template Limit is configured.
Healthy: No individual limit is relaxed.
Unhealthy: Limits are relaxed for some templates.
Suggestion: You are not advised to relax the limit on templates as they may take up excessive system resources and cause crashes.
1030
Enable Extracted Data Cache
It checks whether Enable Cache is turned on under System Management > Extracted Data Cache.
Healthy: Enable Cache is turned on.
Unhealthy: Enable Cache is not turned on.
Suggestion: You are advised to turn on Enable Cache under System Management > Extracted Data Cache.
1031
Cache Space Limit
It will be checked only after Extracted Data Cache mentioned in the previous step is enabled.
It checks the value of Cache Memory Limit under System Management > Extracted Data Cache.
1032
Enable Parallel Dashboard Calculation
It checks whether Parallel Calculation of Report Block under System Management > System Setting > General is enabled.
Healthy: Parallel Calculation of Report Block is enabled.
Unhealthy: Parallel Calculation of Report Block is not enabled.
Suggestion: You are advised to enable Parallel Calculation of Report Block under System Management > System Setting > General > Global Setting of Dashboard Calculation.
1033
Enable Crash Handling Tool
It checks whether Auto Crash Handling under System Management > Intelligent O&M > Crash Handling > Auto Crash Handling Tool is enabled.
Healthy: Auto Crash Handling is enabled.
Unhealthy: Auto Crash Handling is not enabled.
Suggestion: You are advised to enable Auto Crash Handling under System Management > Intelligent O&M > Crash Handling > Auto Crash Handling Tool.
1034
Automatic Stack Export of Auto Carsh Handling Tool
It checks whether Auto Memory Stack Export under System Management > Intelligent O&M > Crash Handling > Auto Crash Handling Tool is enabled.
Healthy: Auto Memory Stack Export is enabled.
Unhealthy: Auto Memory Stack Export is not enabled.
Suggestion: You are advised to enable Auto Memory Stack Export under System Management > Intelligent O&M > Crash Handling > Auto Crash Handling Tool.
1035
Lifecycle Setting
1036
Spark Memory Ratio
It checks the value of the following parameter in the system:
DistributedOptimizationConfig.spiderConfig.spark_memory_fraction.
1037
Update Relevant Configuration
It checks the value of the following parameters in the system:
SystemOptimizationConfig.spiderConfig.threadPoolStrategy
SystemOptimizationConfig.tableLoadThreadPoolNum
DistributedOptimizationConfig.spiderConfig.spider_high_performance_resource_time
SystemOptimizationConfig.baseTableLoadDynamicThreadCoreSizeStr
SystemOptimizationConfig.fastTableLoadDynamicThreadCoreSizeStr
1038
Update SQL Complexity Limit
systemOptimizationConfig.optimizeSqlMaxComplexity.
Log in to a FanRuan application as the admin, and choose System Management > System Setting > General > External Database to migrate the FineDB database to a more stable external database.
For details about migrating to the external database, see External Database Configuration.
Log in to a FanRuan application as the admin, and choose System Management > Intelligent O&M > Platform Log > Global Setting.
Select INFO from the drop-down list under System Log Level and click Save
Enable Auto Cleanup under Log Cleanup and configure Clearance Frequency to less than 6 Months.
Log in to a FanRuan application as the admin, and choose System Management > Intelligent O&M > Backup & Restoration > Global Setting.
You are advised to set the value of Maximum Disk Space Occupied by Automatic Backup Records Per Module under Auto Backup to no more than 1024 MB. For details, see Backup and Restoration.
You are advised to set the value of Maximum Number of Successful/Failed Automatic Backup Records Per Module under Auto Backup to no more than 5 Record(s). For details, see Backup and Restoration.
Log in to a FanRuan application as the admin, choose System Management > Task Schedule > Schedule Object, and select Retain Only Latest 1 Times under File Processing.
For details, see Task Schedule Setting.
Log in to a FanRuan application as the admin, and choose System Management > System Setting > BI Parameter.
You are advised to set the value of Data Access Volume to no more than 1000000. For details about configuring BI parameters, see BI/Spider Parameter.
Configuration information of Cell Quantity Limit During Quick Analysis is recorded in the fine_conf_entity table of the FineDB database.
Configure the value of the DistributedOptimizationConfig.spiderConfig.spider_fast_compute_limit_unit parameter to no more than 10000000 through the FINE_CONF_ENTITY Visualization Configuration plugin.
Click Save and restart the FineBI project for the configuration to take effect.
Configuration information of Memory Size Limit During Quick Analysis is recorded in the fine_conf_entity table of the FineDB database.
Configure the value of the DistributedOptimizationConfig.spiderConfig.spider_fast_compute_limit_memory parameter to no more than 500000000 through the FINE_CONF_ENTITY Visualization Configuration plugin.
Configuration information of Quantity Limit of Updated Cell During Quick Analysis is recorded in the fine_conf_entity table of the FineDB database.
Configure the value of the DistributedOptimizationConfig.spiderConfig.spider_update_fast_compute_limit_cell parameter to no more than 100000000 through the FINE_CONF_ENTITY Visualization Configuration plugin.
Configure the value of the DistributedOptimizationConfig.spiderConfig.spider_fast_compute_limit_row parameter to no more than 10000000 through the FINE_CONF_ENTITY Visualization Configuration plugin.
Configuration information of Memory Size Limit of Spark Calculation Result is recorded in the fine_conf_entity table of the FineDB database.
Configure the value of the DistributedOptimizationConfig.spiderConfig.spark_driver_maxResultSize parameter to no more than 10000000 through the FINE_CONF_ENTITY Visualization Configuration plugin.
Log in to a FanRuan application as the admin, and choose System Management > Intelligent O&M > Load Management > Template Limit > General Limit.
You are advised to enable SQL Execution Period Limit. For details, see Template Limit.
You are advised to enable Template Cell Limit. For details, see Template Limit.
You are advised to enable Excel Import Limit. For details, see Template Limit.
You are advised to enable Dataset Row Limit. For details, see Template Limit.
Log in to a FanRuan application as the admin, and choose BI Tool > Detection > Dirty Data.
Detect, check, and clean up the dirty data in the system.
Log in to a FanRuan application as the admin, and choose System Management > System Setting > Login.
You are advised to enable Password Strength Limit under Password Policy Setting and customize the password strength.
Log in to a FanRuan application as the admin, and choose System Management > Intelligent O&M > Load Management.
You are advised to enable Record Submission Limit under Template Limit.
For details, see Template Limit.
You are advised to enable Data Export Volume Limit Per Chart under Template Limit.
You are not advised to enable Limit Relaxation under Template Limit for some templates.
Log in to a FanRuan application as the admin, and choose System Management > Extracted Data Cache. You are advised to turn on Enable Cache.
For details, see Extracted Data Cache.
Log in to a FanRuan application as the admin, and choose System Management > System Setting.
You are advised to enable Parallel Calculation of Report Block under General.
Log in to a FanRuan application as the admin, and choose System Management > Intelligent O&M > Crash Handling.
You are advised to enable Auto Crash Handling under Automatic Crash Handling Tool.
For details, see Downtime Handling.
You are advised to enable Auto Export Memory Stack under Automatic Crash Handling Tool.