Cart
Latest Announcements (6)
2026 (7th) China Internet Basic Resources Conference | 西部数码 became one of the first member units of the Domain Name Industry Information Sharing Work Promotion GroupAnnouncement by 西部数码 on the Reservation Deadline Adjustment and Price Increase for .COM/.NET Domain Names"刺猬响站" has officially launched, making corporate website building easier.西部数码 officially launches premium domain name reservation service, helping enterprises secure high-quality digital assets.西部数码 AI security scan/repair feature launched西部数码 DNS resolution statistics function officially launched.View All Announcements
Sign Up Bonus

[Step 1] Load Balancing EasySLB Activation Management Process

Published: 2015-01-22

```html


Load Balancing NginxSLB Advantages Compared with EasySLB: 

               1.Supports independent SSL deployment, one-click deployment in the backend, no configuration required on the web server

               2.Supports independent multi-site deployment, multiple load balancing sites can be added independently in the backend

               3.Backend web servers do not need separate setup, no need to set the origin gateway address on the web server, web servers are not required to be in the same data center (same data center recommended)

               4.Supports multiple load balancing groups; different backend load balancing groups can be assigned to different domains, enabling diversified functions

               5.nginx-based extended configuration is more flexible, no remote load server is required, graphical operations in the backend, easier for beginners to configure


Our company's load balancing architecture has EasySLB architecture and nginxSLB architecture, for nginxSLB mode please refer to the tutorial Load Balancing nginxSLB Activation and Management Process    .

Below is the EasySLB architecture tutorial description


Load Balancing EasySLB Architecture: one front-end scheduler, three or more backend web servers, and one file server (the file server stores web and database files). Note: All servers must be activated in the same data center and same cluster.

Recommended server configuration: 1. Front-end scheduler (one): 4-core CPU, 4G memory, 20M bandwidth, 50G hard disk. (All bandwidth used by load balancing is on the scheduler, so the scheduler needs sufficient bandwidth. Other servers only need to guarantee at least 1M bandwidth; it can be increased at any time later based on usage.)

                2. Web servers (three or more): 4-core CPU, 4G memory, 1M bandwidth (uses internal IP for data exchange, so 1M bandwidth is sufficient), 100G hard disk

                3. File server (one): 4-core CPU, 4G memory, 1M bandwidth (uses internal IP for data exchange, so 1M bandwidth is sufficient), 100G hard disk (SSD; hard disk size depends on data)

Load Balancing EasySLB Operating Principle: Our company's Load Balancing EasySLB uses NAT mode. The domain resolves to the scheduler IP. When a user enters the domain to visit, the request first goes to the scheduler >> then the scheduler distributes it to the backend web server for processing >> the web server calls the web files and database content on the file server >> after processing, the data is fed back to the user through the scheduler. Therefore all bandwidth is on the scheduler. Communication from the scheduler to the web server and from the web server to the file server all uses the internal network.


  1. First, these servers need to be activated. Web servers and file servers can be activated normally according to requirements at http://www.west.cn/services/CloudHost/. When activating the front-end scheduler, you need to select the "Load Balancing EasySLB" template for activation. Please see the screenshot.

    1.png

     



Note: After these servers are activated, they need to be added to the virtual switch and the internal network must be configured, Virtual Switch VPC Configuration Instructions (Elastic Cloud Internal Network Communication)  



2. Log in to the Management Center >> Business Management >> Independent IP Host Management. The server with tu.jpg this icon is the scheduler server. Click Manage next to it to enter 2.jpg


3. After entering, the basic information is the scheduler server, and the backend servers are web processing servers. Follow the prompts to add the three web servers activated earlier.tianjia.png

Use all default values. The system automatically detects the IP:80 port status. If the status is incorrect, the system automatically stops. In addition, note that a Windows system web server needs to bind an empty host header to the created site so that detection works properly.

It is recommended to use TCP mode to detect port 80

blob.png


blob.png

After adding, the management interface is as follows:

blob.png

Paused status indicates that port 80 detection failed and the system automatically stopped; Active indicates that everything is normal.

Note: The file server does not need to be added to load balancing; only add web servers here.


After the above operations are completed, the user needs to manually perform the following three steps:

1. Set up file sharing.

2. Create a site on the web server.

3. Set the Load Balancing EasySLB backend server gateway.

Appendix: Load Balancing EasySLB FAQ


Cluster System Optimization Reminder:

1. If the WEB server is Linux, it is recommended to increase the file descriptor limit to 655350; the default 4096 may become a bottleneck

2. If the database system uses MYSQL, the innodb storage engine must be used, and the value of innodb_flush_log_trx_commit should be changed to 2


```