Scaling Components for Cluster Projects

Convert a standalone application to a cluster.

Application scenario:

You need to convert a FineBI 6.0, FineReport 11.0, or FineDataLink 4.1 project from a single-node application to a multi-node cluster.

Note:

This scenario does not apply to FineBI 6.1 or later because its minimum architecture is a cluster. For FineBI 6.1 projects, refer to the "Scale existing components in a cluster" scenario instead.

Solution overview:

1. First, switch the standalone application to a single-node cluster. For details, see Converting a Containerized Standalone to a Cluster. 

Install cluster components such as Nginx, MinIO, and Redis.

2. Then scale the single-node cluster to a multi-node cluster based on this document. 

Install business components such as FineBI - Application Node, FineReport, and FineDataLink.

Application scenario:

Some components may not have been deployed during the initial project deployment, and you later need to use them. For example:

• If you did not select Nginx during standalone deployment, you must add Nginx to configure SSL.

• If you did not select Elasticsearch during standalone deployment, you must add Elasticsearch to replace Swift (LogDB) for log storage.

Solution overview:

Use the Add Component function to add these components to the project. For details, see Adding Components to O&M Projects.

Note:

Only Nginx is automatically connected to the project after it is added. You need to manually connect other components after they have been deployed. Adding other components is usually used when you convert a standalone application to a cluster. See the first scenario.

Application scenario:

• As business usage grows, the existing cluster configuration may no longer support service needs. You need to add business nodes or compute workers, such as scaling a two-node cluster to a three-node cluster.

• For security reasons, you may need to scale an existing single-node internal gateway to two nodes to ensure high availability.

Solution overview:

Refer to this document.

• Add main application nodes to increase the number of business component instances, such as bi-web, bi6, fr, and fdl.

• Increase the number of bi-engine-worker instances. They can be deployed on existing main application nodes.

• Scale the internal gateway from one node to two nodes. It can be deployed on existing main application nodes or component nodes.

• Scale AI components to build high-availability AI services.

The project must have been deployed via FineOps.

The operations in this document do not apply to non-FineOps-deployed projects.

Before scaling business components such as FineBI - Application Node (bi6), FineReport, and FineDataLink, ensure that the project has been deployed and connected to the state server and file server.

For standalone projects, first switch the project to a single-node cluster. For details, see Converting a Containerized Standalone to a Cluster. 

The image of the component to be scaled must exist in Maintenance Center > Image Management. If the image is missing, the container cannot be created.

If no related image is available, FineOps must be able to pull images from the cloud. For details, see Ensuring Access to FanRuan Cloud Repository.

The node passes validation when its available resources reach 7/8 of the estimated required resources of the component.

For example, if the component is estimated to require 8 GB of memory, deployment is allowed when the node has 7 GB of available memory. 

Note:

The 7/8 rule does not remove the need for runtime monitoring. After deployment, keep monitoring node CPU, memory, and component status, and increase node resources if resource pressure persists.