Overview
You can use FineOps to deploy FineBI 6.1 projects.
This document offers multiple standard deployment schemes for scenarios with different business availability demands, daily active user counts, data volume for analysis, and table quantity. Choose the one that best meets your needs.
Term Definition
High business availability: There are at least two bi-web components, so if one business node crashes, other nodes can complete the tasks instead.
Daily active users (DAU): It refers to the average number of unique users who log into the FineBI system each day.
Maximum rows in an analysis table: It refers to the maximum number of rows in a single self-service dataset used by a single component in a FineBI dashboard.
Number of tables: It refers to the total count of all tables in the FineBI system, including database tables, SQL datasets, Excel datasets, and self-service datasets.
Scheme Applicability
The schemes in this document cater for the server resources of most customers, so in these schemes, some FineBI components and FineOps are deployed on one server. If more servers are available, FineBI and FineOps can be deployed independently to meet disaster recovery and other needs. Contact FanRuan technical support for further assistance.
The schemes in this document are suitable for scenarios primarily involving extracted data. Contact technical support for further assistance if your FineBI project relies entirely on direct-connected data.
These schemes offer resource recommendations based on typical scales of customers’ projects. Contact FanRuan technical support for further assistance if your DAU number, data volume, or the number of tables exceeds the recommended range.
These schemes are suitable for deploying new projects. Contact FanRuan technical support for assistance in capacity expansion if your existing server resources become insufficient as those used by the project grow.
Notes on Project Configuration
The recommended configuration is suitable for completely independently deployed FineOps and FineBI projects. If the FineBI component and FineOps are to be deployed on the same server, the server's configuration should be the combined total of required configurations of the FineBI component server and the FineOps server.
The recommended configuration is for a fresh deployment of all FineBI components. If you have prepared some components, such as the data storage service and the file service, you can lower the corresponding server configurations. For details, see notes of each scheme.
For FineOps-deployed FineBI projects, a master component must be deployed. The bi-web and worker components can only be deployed in a ratio of 1:1 or 1:2. The node number ratio cannot be customized.
To achieve read-write separation, you can only choose between Scheme Three or Scheme Four as it requires highly available services.
Quick Selection Guide
Brief Scheme Introduction
| Scheme | Applicable Condition | Major Component | Server Configuration |
|---|---|---|---|
| Minimum Configuration Scheme | App node: a single business node (not highly available) DAU: 0 to 50 Maximum rows in an analysis table: 0 to 5 million Number of tables: 0 to 500 | One bi-web component, one worker component, one master component, and one bi-minio component | Note: 1. One main application server: 16-core CPU, 64 GB of memory, and 500 GB of disk space It is used to deploy one bi-web component, one worker component, one master component, and one bi-minio component. It is used to deploy the following components: nginx, mysql, elasticsearch, and the cluster component. It is used to deploy all FineOps components. |
| Scheme One | App node: a single business node (not highly available) DAU: 0 to 300 Maximum rows in an analysis table: 0 to 10 million Number of tables: 0 to 2000 | One bi-web component, one worker component, one master component, and one bi-minio component | 1. FineBI main application server: 16-core CPU, 64 GB of memory, and 500 GB of disk space It is used to deploy one bi-web component, one worker component, one master component, and one bi-minio component. 2. Server for FineBI components and FineOps: 8-core CPU, 32 GB of memory, and 500 GB of disk space It is used to deploy the following components: nginx, mysql, elasticsearch, and the cluster component. It is used to deploy all FineOps components. |
| Scheme Two | App node: a single business node (not highly available) DAU: 0 to 600 Maximum rows in an analysis table: 0 to 100 million Number of tables: 0 to 10 thousand | One bi-web component, one worker component, one master component, and one bi-minio component | 1. FineBI main application server: 32-core CPU, 128 GB of memory, and 2 TB of disk space It is used to deploy one bi-web component, one worker component, one master component, and one bi-minio component. 2. Server for FineBI components and FineOps: 16-core CPU, 64 GB of memory, and 500 GB of disk space It is used to deploy the following components: nginx, mysql, elasticsearch, and the cluster component. It is used to deploy all FineOps components. |
| Scheme Three | App node: multiple application nodes (highly available) DAU: 0 to 600 Maximum rows in an analysis table: 0 to 10 million Number of tables: 0 to 2000 | Two bi-web components, two worker components, one master component, and one bi-mino component | 1. FineBI main application server one: 16-core CPU, 64 GB of memory, and 500 GB of disk space It is used to deploy one bi-web component, one worker component, one master component, and one bi-minio component. 2. FineBI main application server two: 16-core CPU, 64 GB of memory, and 200 GB of disk space It is used to deploy one bi-web component and one worker component. 3. Server for FineBI components and FineOps: 8-core CPU, 32 GB of memory, and 500 GB of disk space It is used to deploy the following components: nginx, mysql, elasticsearch, and the cluster component. It is used to deploy all FineOps components. |
| Scheme Four | App node: multiple application nodes (highly available) DAU: 0 to 1200 Maximum rows in an analysis table: 0 to 100 million Number of tables: 0 to 10 thousand | Two bi-web components, two worker components, one master component, and one bi-mino component | 1. FineBI main application server one: 32-core CPU, 128 GB of memory, and 2 TB of disk space It is used to deploy one bi-web component, one worker component, one master component, and one bi-minio component. 2. FineBI main application server two: 32-core CPU, 128 GB of memory, and 500 GB of disk space It is used to deploy one bi-web component and one worker component. 3. Server for FineBI components and FineOps: 16-core CPU, 64 GB of memory, and 500 GB of disk space It is used to deploy the following components: nginx, mysql, elasticsearch, and the cluster component. It is used to deploy all FineOps components. |
Minimum Configuration Scheme
Note:This scheme is intended for customers with little business usage and limited server resources only. All components of FineBI and FineOps are deployed on one server.
Ensure that the number of daily active users ranges from 0 to 50, the maximum number of rows in an analysis table ranges from 0 to 5 million, and the number of tables ranges from 0 to 500.
It includes one main application server with 16-core CPU, 64 GB of memory, and 500 GB of disk space.
It is used to deploy one bi-web component, one worker component, one master component, and one bi-minio component.
It is used to deploy the following components: nginx, mysql, elasticsearch, and the cluster component.
It is used to deploy all FineOps components.
| Configuration | Server | |
|---|---|---|
Component to be installed | It is used to install all components of FineBI and FineOps. 1. For details about the role of FineBI components, see Understanding the Roles of O&M Project Components. Note:1. You are advised to prepare and use the S3 service for data storage. 2. If you use S3 to replace the data storage component bi-minio and the file storage component minio, prepare at least two buckets to store the content of each component separately.
2. For details about the role of FineOps components, see Understanding the Roles of FineOps Components. Note:
| |
| Basic server requirement | Non-VM (Recommended) | Due to the nature of virtual machines, such as competing for resources, unexpected system failures may occur. Therefore, you are not advised to deploy FanRuan applications on virtual machines. |
| Operating system | Operating system type | Linux |
| Operating system architecture | X86_64 | |
| Operating system kernel | Version 3.10 and above | |
| Operating system software | Recommended: Ubuntu 22 Supported: Ubuntu 18.04.4 and later releases (Ubuntu 20.04 is not supported.) CentOS 7.3 to 7.9 Red Hat 7.6 and later releases Rocky Linux 8.8 to 9.4 Note:1. Since CentOS is discontinued, you are advised to use Ubuntu. 2. When using Ubuntu, verify the user privilege (as the default root user is not a super administrator) and confirm that the disk type is XFS. For details, see notes in the following content. | |
| CPU | CPU core quantity | 16 cores |
CPU clock speed | 2.5 GHz and above | |
| Memory | Remaining free physical memory | 64 GB |
| Disk | Remaining free disk space | The server shall have a partition with remaining free space of more than 500 GB. Note:There must be a single partition that meets the condition. |
Disk type | If you have not prepared the data storage component, the bi-minio component must be deployed, and the disk type must be XFS. A non-XFS disk might result in data write failure even with available disk space. Note:1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly. 2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly. 3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution. | |
| Disk performance | The disk read/write speed must be greater than 100 MB/s, meaning the disk can handle at least 100 MB of data per second. The random IOPS (4K) must be greater than 500, meaning the disk can perform at least 500 read/write operations on 4 KB data blocks per second. | |
| Mounting directory | Mounting directory preparation | For details, see FineBI Mounting Directory Preparation. For details, see FineOps Mounting Directory Preparation. Note: |
| File system auto-mounting | Ensure that the file system of the mounting directory is configured to be automatically mounted during a boot. Otherwise, containers may fail to access these directories, leading to data loss or application startup issues. | |
| Non-shared path | The mounting directory cannot be a shared-use path. Sharing the file system may cause performance degradation, file permission issues, and data inconsistency, affecting the reliability and response speed of applications running in the container. | |
| Permission and command | Tar command | Ensure the server has the tar command installed. The tar command is a commonly used tool for packaging and compressing files. FineOps requires this command for file extraction. |
| Sed command | Ensure the server has the sed command installed. The sed command is used for text processing. FineOps requires this command for text processing. | |
| Sudo privilege | The server user responsible for deploying the project must have the necessary sudo privileges. 1. Using the root user (superuser) for project deployment and operation is preferred. 2. To use a non-root user for deployment and operation, see Linux User Privilege Explanation. Note: | |
| Port and network | Intranet latency | Less than 1 ms |
| Server intranet bandwidth (between the application and the business database) | At least 1000 Mbps (125 MB/s) Note: | |
| Server extranet bandwidth (between the project and the client) | At least 20 Mbps (2.5 MB/s) | |
Component-used port and component port interconnection | For details, see FineBI Server Network Confirmation. For details, see FineOps Server Preparation. | |
Scheme One
It includes two servers, namely, a main application server and a component server.
Main application server: 16-core CPU, 64 GB of memory, and 500 GB of disk space, used to deploy one bi-web component, one worker component, one master component, and one bi-minio component
Component server: 8-core CPU, 32 GB of memory, and 500 GB of disk space, used to deploy nginx, mysql, elasticsearch, the cluster component, and all FineOps components
| Configuration | FineBI Main Application Server | Server for FineBI Components and FineOps | |
|---|---|---|---|
Component to be installed | It is used to install the BI business and engine components. For details about the role of components, see Understanding the Roles of O&M Project Components. Note:1. You are advised to prepare and use the S3 service for data storage. 2If you use S3 to replace the data storage component bi-minio and the file storage component minio, prepare at least two buckets to store the content of each component separately.
| 1. It is used to install the BI cluster, log, and configuration components. For details about the role of components, see Understanding the Roles of O&M Project Components.
2. It is used to install FineOps. For details about the role of components, see Understanding the Roles of O&M Project Components. Note:
| |
| Basic server requirement | Time consistency | The time on all servers must be synchronized, with a maximum difference of no more than 5 seconds. Inconsistent server time can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies. | |
Time zone consistency | All servers must be set to the same time zone. Inconsistent server time zones can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies. | ||
| Interconnection with intranet | All servers can communicate with each other on the intranet or have open ports for access. For details about ports, see FineBI Server Network Confirmation. | ||
| Non-VM (Recommended) | Due to the nature of virtual machines, such as competing for resources, unexpected system failures may occur. Therefore, you are not advised to deploy FanRuan applications on virtual machines. | ||
| Operating system | Operating system type | Linux | |
| Operating system architecture | X86_64 | ||
| Operating system kernel | Version 3.10 and above | ||
| Operating system software | Recommended: Ubuntu 22 Supported: Ubuntu 18.04.4 and later releases (Ubuntu 20.04 is not supported.) CentOS 7.3 to 7.9 Red Hat 7.6 and later releases Rocky Linux 8.8 to 9.4 Note:1. Since CentOS is discontinued, you are advised to use Ubuntu. 2. When using Ubuntu, verify the user privilege (as the default root user is not a super administrator) and confirm that the disk type is XFS. For details, see notes in the following content. | ||
| CPU | CPU core quantity | 16 cores | 8 cores |
CPU clock speed | 2.5 GHz and above | ||
| Memory | Remaining free physical memory | 64 GB | 32 GB |
| Disk | Remaining free disk space | The server shall have a partition with remaining free space of more than 500 GB. Note:1. There must be a single partition that meets the condition. 2. The required disk space decreases if you use self-prepared components. For example, if you use a self-provided data storage component, the required remaining free disk space on the server can be reduced by 300 GB (meaning that 200 GB of free disk space on the server is enough). | The server shall have a partition with remaining free space of more than 500 GB. Note:1. There must be a single partition that meets the condition. 2. The required disk space decreases if you use self-prepared components. If you use the self-provided Elasticsearch, the required remaining free disk space on the server can be reduced by 50 GB. If you use the self-provided external database, the required remaining free disk space on the server can be reduced by 50 GB. If you use the self-provided file storage component, the required remaining free disk space on the server can be reduced by 100 GB. |
Disk type | If you have not prepared the data storage component, the bi-minio component must be deployed, and the disk type must be XFS. A non-XFS disk might result in data write failure even with available disk space. Note:1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly. 2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly. 3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution. | If you have not prepared the file service component, the minio component must be deployed, and the disk type must be XFS. Note:1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly. 2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly. 3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution. | |
| Disk performance | The disk should at least be a SATA solid-state drive (SSD). The random IOPS (4K) must be greater than 10,000, meaning the disk can perform at least 10,000 read/write operations on 4 KB data blocks per second. The sequential IOPS (1024K) must be greater than 315.5 MB, meaning the disk can transfer at least 315.5 MB of blocks per second. | Since the configuration database of this project is deployed on the same machine, the disk performance requirements of this server are consistent with the main application server. The disk should at least be a SATA solid-state drive (SSD). The random IOPS (4K) must be greater than 10,000, meaning the disk can perform at least 10,000 read/write operations on 4 KB data blocks per second. The sequential IOPS (1024K) must be greater than 315.5 MB, meaning the disk can transfer at least 315.5 MB of blocks per second. | |
| Mounting directory | Mounting directory preparation | For details, see FineBI Mounting Directory Preparation. Note: | For details, see FineBI Mounting Directory Preparation. For details, see FineOps Mounting Directory Preparation. Note: |
| File system auto-mounting | Ensure that the file system of the mounting directory is configured to be automatically mounted during a boot. Otherwise, containers may fail to access these directories, leading to data loss or application startup issues. | ||
| Non-shared path | The mounting directory cannot be a shared-use path. Sharing the file system may cause performance degradation, file permission issues, and data inconsistency, affecting the reliability and response speed of applications running in the container. | ||
| Permission and command | Tar command | Ensure the server has the tar command installed. The tar command is a commonly used tool for packaging and compressing files. FineOps requires this command for file extraction. | |
| Sed command | Ensure the server has the sed command installed. The sed command is used for text processing. FineOps requires this command for text processing. | ||
| Sudo privilege | The server user responsible for deploying the project must have the necessary sudo privileges. 1. Using the root user (superuser) for project deployment and operation is preferred. 2. To use a non-root user for deployment and operation, see Linux User Privilege Explanation. Note: | ||
| Port and network | Intranet latency | Less than 1 ms | |
| Server intranet bandwidth (between components) | At least 2.5 Gbps (312.5 MB/s) | ||
| Server extranet bandwidth (between projects and clients) | Generally, there are no specific requirements. However, if you have prepared a load-balancing component or wish to access the FineBI application node individually, ensure that the server extranet bandwidth is at least 50Mbps (6.25MB/S). | At least 50 Mbps (6.25 MB/s) | |
Component-used port and component port interconnection | For details, see FineBI Server Network Confirmation. | For details, see FineBI Server Network Confirmation. For details, see FineOps Server Preparation. | |
Scheme Two
It includes two servers, namely, a main application server and a component server.
Main application server: 32-core CPU, 128 GB of memory, and 2 TB of disk space, used to deploy one bi-web component, one worker component, one master component, and one bi-minio component
Component server: 16-core CPU, 64 GB of memory, and 500 GB of disk space, used to deploy nginx, mysql, elasticsearch, the cluster component, and all FineOps components
| Configuration | FineBI Main Application Server | Server for FineBI Components and FineOps | |
|---|---|---|---|
Component to be installed | It is used to install the BI business and engine components. For details about the role of components, see Understanding the Roles of O&M Project Components. Note:1. You are advised to prepare and use the S3 service for data storage. 2If you use S3 to replace the data storage component bi-minio and the file storage component minio, prepare at least two buckets to store the content of each component separately.
| 1. It is used to install the BI cluster, log, and configuration components. For details about the role of components, see Understanding the Roles of O&M Project Components.
2. It is used to install FineOps. For details about the role of components, see Understanding the Roles of FineOps Components. Note:
| |
| Basic server requirement | Time consistency | The time on all servers must be synchronized, with a maximum difference of no more than 5 seconds. Inconsistent server time can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies. | |
Time zone consistency | All servers must be set to the same time zone. Inconsistent server time zones can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies. | ||
| Interconnection with intranet | All servers can communicate with each other on the intranet or have open ports for access. For details about ports, see FineBI Server Network Confirmation. | ||
| Non-VM (Recommended) | Due to the nature of virtual machines, such as competing for resources, unexpected system failures may occur. Therefore, you are not advised to deploy FanRuan applications on virtual machines. | ||
| Operating system | Operating system type | Linux | |
| Operating system architecture | X86_64 | ||
| Operating system kernel | Version 3.10 and above | ||
| Operating system software | Recommended: Ubuntu 22 Supported: Ubuntu 18.04.4 and later releases (Ubuntu 20.04 is not supported.) CentOS 7.3 to 7.9 Red Hat 7.6 and later releases Rocky Linux 8.8 to 9.4 Note:1. Since CentOS is discontinued, you are advised to use Ubuntu. 2. When using Ubuntu, verify the user privilege (as the default root user is not a super administrator) and confirm that the disk type is XFS. For details, see notes in the following content. | ||
| CPU | CPU core quantity | 32 cores | 16 cores |
CPU clock speed | 2.5 GHz and above | ||
| Memory | Remaining free physical memory | 128 GB | 64 GB |
| Disk | Remaining free disk space | The server shall have a partition with remaining free space of more than 2 TB. Note:1. There must be a single partition that meets the condition. 2. The required disk space decreases if you use self-prepared components. For example, if you use a self-provided data storage component, the required remaining free disk space on the server can be reduced by 1.5 TB (meaning that 500 GB of free disk space on the server is enough). | The server shall have a partition with remaining free space of more than 500 GB. Note:1. There must be a single partition that meets the condition. 2. The required disk space decreases if you use self-prepared components. If you use the self-provided Elasticsearch, the required remaining free disk space on the server can be reduced by 50 GB. If you use the self-provided external database, the required remaining free disk space on the server can be reduced by 50 GB. If you use the self-provided file storage component, the required remaining free disk space on the server can be reduced by 100 GB. |
Disk type | If you have not prepared the data storage component, the bi-minio component must be deployed, and the disk type must be XFS. A non-XFS disk might result in data write failure even with available disk space. Note:1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly. 2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly. 3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution. | If you have not prepared the file service component, the minio component must be deployed, and the disk type must be XFS. Note:1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly. 2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly. 3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution. | |
| Disk performance | The disk should at least be a SATA solid-state drive (SSD). The random IOPS (4K) must be greater than 20,000, meaning the disk can perform at least 20,000 read/write operations on 4 KB data blocks per second. The sequential IOPS (1024K) must be greater than 625 MB, meaning the disk can transfer at least 625 MB of blocks per second. | Since the configuration database of this project is deployed on the same machine, the disk performance requirements of this server are consistent with the main application server. The disk should at least be a SATA solid-state drive (SSD). The random IOPS (4K) must be greater than 20,000, meaning the disk can perform at least 20,000 read/write operations on 4 KB data blocks per second. The sequential IOPS (1024K) must be greater than 625 MB, meaning the disk can transfer at least 625 MB of blocks per second. | |
| Mounting directory | Mounting directory preparation | For details, see FineBI Mounting Directory Preparation. Note: | For details, see FineBI Mounting Directory Preparation. For details, see FineOps Mounting Directory Preparation. Note: |
| File system auto-mounting | Ensure that the file system of the mounting directory is configured to be automatically mounted during a boot. Otherwise, containers may fail to access these directories, leading to data loss or application startup issues. | ||
| Non-shared path | The mounting directory cannot be a shared-use path. Sharing the file system may cause performance degradation, file permission issues, and data inconsistency, affecting the reliability and response speed of applications running in the container. | ||
| Permission and command | Tar command | Ensure the server has the tar command installed. The tar command is a commonly used tool for packaging and compressing files. FineOps requires this command for file extraction. | |
| Sed command | Ensure the server has the sed command installed. The sed command is used for text processing. FineOps requires this command for text processing. | ||
| Sudo privilege | The server user responsible for deploying the project must have the necessary sudo privileges. 1. Using the root user (superuser) for project deployment and operation is preferred. 2. To use a non-root user for deployment and operation, see Linux User Privilege Explanation. Note: | ||
| Port and network | Intranet latency | Less than 1 ms | |
| Server intranet bandwidth (between components) | At least 5 Gbps (625 MB/s) | ||
| Server extranet bandwidth (between projects and clients) | Generally, there are no specific requirements. However, if you have prepared a load-balancing component or wish to access the FineBI application node individually, ensure that the server extranet bandwidth is at least 100 Mbps (12.5 MB/s). | At least 100 Mbps (12.5 MB/s) | |
Component-used port and component port interconnection | For details, see FineBI Server Network Confirmation. | For details, see FineBI Server Network Confirmation. For details, see FineOps Server Preparation. | |
Scheme Three
It includes three servers, namely, two main application servers, a component server, and a FineOps server.
Main application server one: 16-core CPU, 64 GB of memory, and 500 GB of disk space, used to deploy one bi-web component, one worker component, one master component, and one bi-minio component
Main application server two: 16-core CPU, 64 GB of memory, and 200 GB of disk space, used to deploy one bi-web component and one worker component
Component server: 8-core CPU, 32 GB of memory, and 500 GB of disk space, used to deploy nginx, mysql, elasticsearch, the cluster component, and all FineOps components
| Configuration | FineBI Main Application Server One | FineBI Main Application Server Two | Server for FineBI Components and FineOps | |
|---|---|---|---|---|
Component to be installed | It is used to install the BI business and engine components. For details about the role of components, see Understanding the Roles of O&M Project Components. Note:1. You are advised to prepare and use the S3 service for data storage. 2If you use S3 to replace the data storage component bi-minio and the file storage component minio, prepare at least two buckets to store the content of each component separately.
| It is used to install the BI business and engine components. For details about the role of components, see Understanding the Roles of O&M Project Components.
| 1. It is used to install the BI cluster, log, and configuration components. For details about the role of components, see Understanding the Roles of O&M Project Components.
2. It is used to install FineOps. For details about the role of components, see Understanding the Roles of FineOps Components. Note;
| |
| Basic server requirement | Time consistency | The time on all servers must be synchronized, with a maximum difference of no more than 5 seconds. Inconsistent server time can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies. | ||
Time zone consistency | All servers must be set to the same time zone. Inconsistent server time zones can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies. | |||
| Interconnection with intranet | All servers can communicate with each other on the intranet or have open ports for access. For details about ports, see FineBI Server Network Confirmation. | |||
| Non-VM (Recommended) | Due to the nature of virtual machines, such as competing for resources, unexpected system failures may occur. Therefore, you are not advised to deploy FanRuan applications on virtual machines. | |||
| Operating system | Operating system type | Linux | ||
| Operating system architecture | X86_64 | |||
| Operating system kernel | Version 3.10 and above | |||
| Operating system software | Recommended: Ubuntu 22 Supported: Ubuntu 18.04.4 and later releases (Ubuntu 20.04 is not supported.) CentOS 7.3 to 7.9 Red Hat 7.6 and later releases Rocky Linux 8.8 to 9.4 Note:1. Since CentOS is discontinued, you are advised to use Ubuntu. 2. When using Ubuntu, verify the user privilege (as the default root user is not a super administrator) and confirm that the disk type is XFS. For details, see notes in the following content. | |||
| CPU | CPU core quantity | 16 cores | 16 cores | 8 cores |
CPU clock speed | 2.5 GHz and above | |||
| Memory | Remaining free physical memory | 64 GB | 64 GB | 32 GB |
| Disk | Remaining free disk space | The server shall have a partition with remaining free space of more than 500 GB. Note:1. There must be a single partition that meets the condition. 2. The required disk space decreases if you use self-prepared components. For example, if you use a self-provided data storage component, the required remaining free disk space on the server can be reduced by 300 GB (meaning that 200 GB of free disk space on the server is enough). | The server shall have a partition with remaining free space of more than 200 GB. Note: | The server shall have a partition with remaining free space of more than 500 GB. Note:1. There must be a single partition that meets the condition. 2. The required disk space decreases if you use self-prepared components. If you use the self-provided Elasticsearch, the required remaining free disk space on the server can be reduced by 50 GB. If you use the self-provided external database, the required remaining free disk space on the server can be reduced by 50 GB. If you use the self-provided file storage component, the required remaining free disk space on the server can be reduced by 100 GB. |
Disk type | If you have not prepared the data storage component, the bi-minio component must be deployed, and the disk type must be XFS. A non-XFS disk might result in data write failure even with available disk space. Note:1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly. 2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly. 3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution. | / | If you have not prepared the file service component, the minio component must be deployed, and the disk type must be XFS. Note:1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly. 2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly. 3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution. | |
| Disk performance | The disk should at least be a SATA solid-state drive (SSD). The random IOPS (4K) must be greater than 10,000, meaning the disk can perform at least 10,000 read/write operations on 4 KB data blocks per second. The sequential IOPS (1024K) must be greater than 315.5 MB, meaning the disk can transfer at least 315.5 MB of blocks per second. | Since the configuration database of this project is deployed on the same machine, the disk performance requirements of this server are consistent with the main application server. The disk should at least be a SATA solid-state drive (SSD). The random IOPS (4K) must be greater than 10,000, meaning the disk can perform at least 10,000 read/write operations on 4 KB data blocks per second. The sequential IOPS (1024K) must be greater than 315.5 MB, meaning the disk can transfer at least 315.5 MB of blocks per second. | ||
| Mounting directory | Mounting directory preparation | For details, see FineBI Mounting Directory Preparation. Note: | For details, see FineBI Mounting Directory Preparation. Note: | For details, see FineBI Mounting Directory Preparation. For details, see FineOps Mounting Directory Preparation. Note: |
| File system auto-mounting | Ensure that the file system of the mounting directory is configured to be automatically mounted during a boot. Otherwise, containers may fail to access these directories, leading to data loss or application startup issues. | |||
| Non-shared path | The mounting directory cannot be a shared-use path. Sharing the file system may cause performance degradation, file permission issues, and data inconsistency, affecting the reliability and response speed of applications running in the container. | |||
| Permission and command | Tar command | Ensure the server has the tar command installed. The tar command is a commonly used tool for packaging and compressing files. FineOps requires this command for file extraction. | ||
| Sed command | Ensure the server has the sed command installed. The sed command is used for text processing. FineOps requires this command for text processing. | |||
| Sudo privilege | The server user responsible for deploying the project must have the necessary sudo privileges. 1. Using the root user (superuser) for project deployment and operation is preferred. 2. To use a non-root user for deployment and operation, see Linux User Privilege Explanation. Note: | |||
| Port and network | Intranet latency | Less than 1 ms | ||
| Server intranet bandwidth (between components) | At least 2.5 Gbps (312.5 MB/s) | |||
| Server extranet bandwidth (between projects and clients) | Generally, there are no specific requirements. However, if you have prepared a load-balancing component or wish to access the FineBI application node individually, ensure that the server extranet bandwidth is at least 100 Mbps (12.5 MB/s). | At least 100 Mbps (12.5 MB/s) | ||
Component-used port and component port interconnection | For details, see FineBI Server Network Confirmation. | For details, see FineBI Server Network Confirmation. | For details, see FineBI Server Network Confirmation. For details, see FineOps Server Preparation. | |
Scheme Four
It includes three servers, namely, two main application servers and a component server.
Main application server one: 32-core CPU, 128 GB of memory, and 2 TB of disk space, used to deploy one bi-web component, one worker component, one master component, and one bi-minio component
Main application server two: 32-core CPU, 128 GB of memory, and 500 GB of disk space, used to deploy one bi-web component and one worker component
Component server: 16-core CPU, 64 GB of memory, and 500 GB of disk space, used to deploy nginx, mysql, elasticsearch, the cluster component, and all FineOps components
| Configuration | FineBI Main Application Server One | FineBI Main Application Server Two | Server for FineBI Components and FineOps | |
|---|---|---|---|---|
Component to be installed | It is used to install the BI business and engine components. For details about the role of components, see Understanding the Roles of O&M Project Components. Note:1. You are advised to prepare and use the S3 service for data storage. 2If you use S3 to replace the data storage component bi-minio and the file storage component minio, prepare at least two buckets to store the content of each component separately.
| It is used to install the BI business and engine components. For details about the role of components, see Understanding the Roles of O&M Project Components.
| 1. It is used to install the BI cluster, log, and configuration components. For details about the role of components, see Understanding the Roles of O&M Project Components.
2. It is used to install FineOps. For details about the role of components, see Understanding the Roles of FineOps Components. Note:
| |
| Basic server requirement | Time consistency | The time on all servers must be synchronized, with a maximum difference of no more than 5 seconds. Inconsistent server time can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies. | ||
Time zone consistency | All servers must be set to the same time zone. Inconsistent server time zones can cause issues such as incorrect execution of scheduled tasks, disorganized log records, and data inconsistencies. | |||
| Interconnection with intranet | All servers can communicate with each other on the intranet or have open ports for access. For details about ports, see FineBI Server Network Confirmation. | |||
| Non-VM (Recommended) | Due to the nature of virtual machines, such as competing for resources, unexpected system failures may occur. Therefore, you are not advised to deploy FanRuan applications on virtual machines. | |||
| Operating system | Operating system type | Linux | ||
| Operating system architecture | X86_64 | |||
| Operating system kernel | Version 3.10 and above | |||
| Operating system software | Recommended: Ubuntu 22 Supported: Ubuntu 18.04.4 and later releases (Ubuntu 20.04 is not supported.) CentOS 7.3 to 7.9 Red Hat 7.6 and later releases Rocky Linux 8.8 to 9.4 Note:1. Since CentOS is discontinued, you are advised to use Ubuntu. 2. When using Ubuntu, verify the user privilege (as the default root user is not a super administrator) and confirm that the disk type is XFS. For details, see notes in the following content. | |||
| CPU | CPU core quantity | 32 cores | 32 cores | 16 cores |
CPU clock speed | 2.5 GHz and above | |||
| Memory | Remaining free physical memory | 128 GB | 128 GB | 64 GB |
| Disk | Remaining free disk space | The server shall have a partition with remaining free space of more than 2 TB. Note:1. There must be a single partition that meets the condition. 2. The required disk space decreases if you use self-prepared components. For example, if you use a self-provided data storage component, the required remaining free disk space on the server can be reduced by 1.5 TB (meaning that 500 GB of free disk space on the server is enough). | The server shall have a partition with remaining free space of more than 500 GB. Note: | The server shall have a partition with remaining free space of more than 500 GB. Note:1. There must be a single partition that meets the condition. 2. The required disk space decreases if you use self-prepared components. If you use the self-provided Elasticsearch, the required remaining free disk space on the server can be reduced by 50 GB. If you use the self-provided external database, the required remaining free disk space on the server can be reduced by 50 GB. If you use the self-provided file storage component, the required remaining free disk space on the server can be reduced by 100 GB. |
Disk type | If you have not prepared the data storage component, the bi-minio component must be deployed, and the disk type must be XFS. A non-XFS disk might result in data write failure even with available disk space. Note:1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly. 2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly. 3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution. | / | If you have not prepared the file service component, the minio component must be deployed, and the disk type must be XFS. Note:1. The default disk type of Ubuntu systems is typically not XFS. Adjust it accordingly. 2. The default disk type of Alibaba Cloud servers is typically not XFS. Adjust it accordingly. 3. This operation may format the disk. FanRuan does not provide related guidance. Follow the instructions from your server vendor and proceed with caution. | |
| Disk performance | The disk should at least be a SATA solid-state drive (SSD). The random IOPS (4K) must be greater than 20,000, meaning the disk can perform at least 20,000 read/write operations on 4 KB data blocks per second. The sequential IOPS (1024K) must be greater than 625 MB, meaning the disk can transfer at least 625 MB of blocks per second. | Since the configuration database of this project is deployed on the same machine, the disk performance requirements of this server are consistent with the main application server. The disk should at least be a SATA solid-state drive (SSD). The random IOPS (4K) must be greater than 20,000, meaning the disk can perform at least 20,000 read/write operations on 4 KB data blocks per second. The sequential IOPS (1024K) must be greater than 625 MB, meaning the disk can transfer at least 625 MB of blocks per second. | ||
| Mounting directory | Mounting directory preparation | For details, see FineBI Mounting Directory Preparation. Note: | For details, see FineBI Mounting Directory Preparation. Note: | For details, see FineBI Mounting Directory Preparation. For details, see FineOps Mounting Directory Preparation. Note: |
| File system auto-mounting | Ensure that the file system of the mounting directory is configured to be automatically mounted during a boot. Otherwise, containers may fail to access these directories, leading to data loss or application startup issues. | |||
| Non-shared path | The mounting directory cannot be a shared-use path. Sharing the file system may cause performance degradation, file permission issues, and data inconsistency, affecting the reliability and response speed of applications running in the container. | |||
| Permission and command | Tar command | Ensure the server has the tar command installed. The tar command is a commonly used tool for packaging and compressing files. FineOps requires this command for file extraction. | ||
| Sed command | Ensure the server has the sed command installed. The sed command is used for text processing. FineOps requires this command for text processing. | |||
| Sudo privilege | The server user responsible for deploying the project must have the necessary sudo privileges. 1. Using the root user (superuser) for project deployment and operation is preferred. 2. To use a non-root user for deployment and operation, see Linux User Privilege Explanation. Note: | |||
| Port and network | Intranet latency | Less than 1 ms | ||
| Server intranet bandwidth (between components) | At least 5 Gbps (625 MB/s) | |||
| Server extranet bandwidth (between projects and clients) | Generally, there are no specific requirements. However, if you have prepared a load-balancing component or wish to access the FineBI application node individually, ensure that the server extranet bandwidth is at least 200 Mbps (25 MB/s). | At least 200 Mbps (25 MB/s) | ||
Component-used port and component port interconnection | For details, see FineBI Server Network Confirmation. | For details, see FineBI Server Network Confirmation. | For details, see FineBI Server Network Confirmation. For details, see FineOps Server Preparation. | |
Annex
FineBI Extraction Performance Report
You can download the FineBI 6.1 extraction performance report. FineBI 6.1 Extraction Performance Report.pdf
Required Resources of FineBI Components
The configuration requirements in the above tables must be met because each component of FineBI projects has minimum operational requirements, as shown in the following table.
Note:1. To prevent resource over-provisioning, a CPU-sharing strategy is used, as the components do not run at full load simultaneously. Therefore, the required number of server CPU cores is not the total number of maximum CPU cores used by each container.
2. The server memory size must be at least the total of the maximum memory used by each container to implement the JAVA memory configuration for each container, including Xmx, off-heap memory, FineIO read/write memory, CodeCache, and Metaspace.
| Component | Maximum CPU Usage | Maximum Memory Usage | Memory Allocation (Xmx) | Disk Space |
|---|---|---|---|---|
bi-web | 16 cores | Server memory/4 64 GB at most | 5/8 Container memory - 2 32766 MB at most | 100 GB |
| bi-engine-worker | 16 cores | Server memory/2/Number of the worker component 64 GB at most | 5/8 Container memory -10/7 32766 MB at most | 100 GB |
| bi-engine-master | 4 cores | Server memory/8 64 GB at most | 3/4 Container memory | 100 GB |
| bi-minio (data storage component) | 2 cores | Server memory/8 64 GB at most | / | 200 GB |
| ops_agent (O&M component) | 1 core | / | 1 GB | / |
| filebeat (O&M component) | 0.1 core | 0.1 GB | / | / |
| elasticsearch (log service) | 1 core | / | 2 GB | 50 GB |
| nginx (internal gateway) | 1 core | / | / | / |
| mysql (configuration database) | 2 cores | / | / | 50 GB |
| redis (state server) | 1 core | / | 4 GB | / |
| minio (file server) | 1 core | / | / | 100 GB |
Previous：Understanding FineBI Deployment Principles