CN115250275B - Cluster management method and system - Google Patents
Cluster management method and system Download PDFInfo
- Publication number
- CN115250275B CN115250275B CN202210838951.0A CN202210838951A CN115250275B CN 115250275 B CN115250275 B CN 115250275B CN 202210838951 A CN202210838951 A CN 202210838951A CN 115250275 B CN115250275 B CN 115250275B
- Authority
- CN
- China
- Prior art keywords
- server
- cluster node
- node server
- client
- socket
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 40
- 230000006854 communication Effects 0.000 claims abstract description 28
- 238000004891 communication Methods 0.000 claims abstract description 28
- 238000000034 method Methods 0.000 abstract description 12
- 238000013507 mapping Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 101000643956 Homo sapiens Cytochrome b-c1 complex subunit Rieske, mitochondrial Proteins 0.000 description 1
- 101001099199 Homo sapiens RalA-binding protein 1 Proteins 0.000 description 1
- 101001109145 Homo sapiens Receptor-interacting serine/threonine-protein kinase 1 Proteins 0.000 description 1
- 101001109137 Homo sapiens Receptor-interacting serine/threonine-protein kinase 2 Proteins 0.000 description 1
- 101000733257 Homo sapiens Rho guanine nucleotide exchange factor 28 Proteins 0.000 description 1
- 101710156256 Myosin phosphatase Rho-interacting protein Proteins 0.000 description 1
- 102100022501 Receptor-interacting serine/threonine-protein kinase 1 Human genes 0.000 description 1
- 102100022502 Receptor-interacting serine/threonine-protein kinase 2 Human genes 0.000 description 1
- 102100033729 Receptor-interacting serine/threonine-protein kinase 3 Human genes 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 230000007175 bidirectional communication Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
- H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/163—In-band adaptation of TCP data exchange; In-band control procedures
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention relates to a cluster management method and a system, which relate to the field of server cluster management, wherein the method comprises the steps that a virtual server obtains a communication request of a client; the virtual server selects a cluster node server according to the communication request of the client by using a load balancing algorithm; the cluster node server creates socket channel information according to the cluster node server and the client; the socket channel information comprises the IP information of the socket and the user identification of the socket. The invention can realize cluster management to achieve network load balance.
Description
Technical Field
The present invention relates to the field of server cluster management, and in particular, to a cluster management method and system.
Background
Cluster management is always the issue of server discussion, and a cluster system is a group of loosely coupled servers forming a virtual server providing unified services to client users. For this client, it is typically not aware of which server it is providing its services when accessing the clustered system. The purpose of the cluster is to achieve Load Balancing (Load Balancing), fault Tolerance (Fault Tolerance) and disaster recovery (Failover). To meet the requirements of system availability (High Availability), scalability (Scalability), maintainability.
At present, no method for realizing cluster management to achieve network load balance is utilized.
Disclosure of Invention
The invention aims to provide a cluster management method and system for realizing cluster management to achieve network load balancing.
In order to achieve the above object, the present invention provides the following solutions:
a cluster management method, comprising:
the virtual server acquires a communication request of a client;
the virtual server selects a cluster node server according to the communication request of the client by using a load balancing algorithm;
the cluster node server creates socket channel information according to the cluster node server and the client; the socket channel information comprises the IP information of the socket and the user identification of the socket.
Optionally, the cluster node server creates socket channel information according to the cluster node server and the client, which specifically includes:
the client initiates a link request to the cluster node server;
and the cluster node server creates socket channel information according to the link request.
Optionally, the client is a client of a TCP protocol; the cluster node server is a server end of a TCP protocol.
Optionally, after the cluster node server creates socket channel information according to the cluster node server and the client, the method further includes:
and caching the socket channel information on the cluster node server.
Optionally, after the cluster node server creates socket channel information according to the cluster node server and the client, the method further includes:
and storing the socket channel information to a storage center.
A cluster management system, the cluster management system applying the cluster management method of any one of the above, the cluster management system comprising: a client, a virtual server and a cluster node server;
the virtual server is respectively in communication connection with the client and the cluster node server; the virtual server is used for acquiring the communication request of the client and selecting a cluster node server according to the communication request of the client by utilizing a load balancing algorithm; the cluster node server is used for creating socket channel information according to the cluster node server and the client.
Optionally, the client is a client of a TCP protocol; the cluster node server is a server end of a TCP protocol.
Optionally, the system further comprises a storage center; the storage center is in communication connection with the cluster node server; the storage center is used for storing the socket channel information.
According to the specific embodiment provided by the invention, the invention discloses the following technical effects:
in the invention, a virtual server acquires a communication request of a client; the virtual server selects a cluster node server according to the communication request of the client by using a load balancing algorithm; the cluster node server creates socket channel information according to the cluster node server and the client; the socket channel information comprises the IP information of the socket and the user identification of the socket. According to the invention, the socket channel information between the cluster node server and the client is created through the cluster node server, so that cluster management is realized, and network load balance is achieved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions of the prior art, the drawings that are needed in the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a cluster management method provided by the invention;
FIG. 2 is a schematic diagram of a cluster management system according to the present invention;
FIG. 3 is a flow chart of a service provided by the present invention;
FIG. 4 is a flow chart of a process for initiating a link.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The invention aims to provide a cluster management method and system for realizing cluster management to achieve network load balancing.
LVS: (Linux Virtual Server) Linux virtual server is a virtual server cluster system. The project is established by Zhang Wensong doctor in 5 months of 1998, and is one of the earliest free software projects in China.
Redis: redis is an open source (BSD-licensed) data structure storage system written in ANSI C language, supporting networks, in memory, and can be used as a database, cache, and message middleware that supports multiple types of data mechanisms and provides multiple language APIs.
userId: the user ID in the item is currently the mobile phone number.
Tcp protocol: TCP (Transmission Control Protocol) is a connection-oriented, reliable, byte-stream based transport layer communication protocol, defined by IETF RFC 793. In the simplified OSI model of computer networks, it performs the functions specified by the transport layer four, the User Datagram Protocol (UDP) being another important transport protocol within the same layer. In the internet protocol suite (Internet protocol suite), the TCP layer is an intermediate layer that sits above the IP layer and below the application layer. Reliable, pipe-like connections are often required between application layers of different hosts, but the IP layer does not provide such a streaming mechanism, but rather unreliable packet switching.
MAC address: (Media Access Control Address) is interpreted as a media access control Address, also known as a local area network Address (LAN Address), an Ethernet Address (Ethernet Address) or a Physical Address (Physical Address), which is an Address used to identify the location of a device on the network. In the osi model, the third layer network layer is responsible for IP addresses, and the second layer network link layer is responsible for MAC addresses. The MAC address is used to uniquely identify a network card in the network, and if one or more network cards exist in a device, each network card needs and has a unique MAC address.
socket: two programs on the network implement the exchange of data via a bi-directional communication connection, one end of which is called a socket.
In order that the above-recited objects, features and advantages of the present invention will become more readily apparent, a more particular description of the invention will be rendered by reference to the appended drawings and appended detailed description.
As shown in fig. 1, the cluster management method provided by the present invention includes:
step 101: the virtual server obtains the communication request of the client.
Step 102: and the virtual server selects a cluster node server according to the communication request of the client by using a load balancing algorithm.
Step 103: the cluster node server creates socket channel information according to the cluster node server and the client; the socket channel information comprises the IP information of the socket and the user identification of the socket. In practical application, the cluster node server creates socket channel information according to the cluster node server and the client, and specifically includes: the client initiates a link request to the cluster node server; and the cluster node server creates socket channel information according to the link request. The client is a client of a TCP protocol; the cluster node server is a server end of a TCP protocol.
In an actual application, after the cluster node server creates socket channel information according to the cluster node server and the client, the method further includes: and caching the socket channel information on the cluster node server.
In an actual application, after the cluster node server creates socket channel information according to the cluster node server and the client, the method further includes: and storing the socket channel information to a storage center.
As shown in fig. 2, the present invention provides a cluster management system, where the cluster management system applies the above-mentioned cluster management method, and the cluster management system includes: client, virtual server and cluster node server. The terminal in fig. 2 is a client, and the server is a cluster node server.
The virtual server is respectively in communication connection with the client and the cluster node server; the virtual server is used for acquiring the communication request of the client and selecting a cluster node server according to the communication request of the client by utilizing a load balancing algorithm; the cluster node server is used for creating socket channel information according to the cluster node server and the client.
In practical application, the client is a client of a TCP protocol; the cluster node server is a server end of a TCP protocol.
In practical application, the system also comprises a storage center; the storage center is in communication connection with the cluster node server; the storage center is used for storing the socket channel information.
According to the invention, a LVS (Linux Virtual Server) architecture is adopted to build a plurality of servers, a virtual server IP is provided for a terminal, the terminal adopts a TCP protocol and the virtual server to build long-chain sockets, and the sockets are automatically distributed to each node server after being successfully built, so that the sockets need to be uniformly managed, and the servers can acquire and identify the sockets. And cluster socket management is realized, and the aim of balancing network load is fulfilled. The storage center Redis is used for storing the mapping relation between the IP of all socket channels and userId of the user, the actual socket can only be stored on a specific entity machine (randomly distributed on a certain server), the terminal only interacts with the virtual server, the data stored by the Redis can also be distributed in the memory of each machine by adopting clusters, and the server acquires the data in the Redis through a corresponding interface. Each logged-in user is identified through userId, after logging in, the ip of socket and userId binding relation of the user are stored in redis.
And (3) a terminal: and the user access node carries a unique userId identifier when accessing the virtual server, and creates a client socket.
The generation of the userId is generated by the service logic of the terminal, and each new request socket corresponds to a unique userId.
Virtual server: and responding to the connection request of the terminal, and managing the allocation of the cluster node servers. The server adopts LVS to build a plurality of machines to form a cluster, one server is virtually output, and the IP of the virtual server can be set, so that a cluster system is simply formed. There are three modes of operation of the LVS, here mainly DR (direct routing) mode.
The virtual server and the terminal communicate through the L4 layer TCP socket, and the virtual server is used as a server side of the TCP and receives a connection request of the terminal. And forwarded to the cluster node server through the L3 layer socket.
The virtual server establishes a plurality of L3 sockets to interact messages with the cluster node server through L3 layer socket communication between the virtual server and the cluster node server. The virtual server maintains a list of cluster node servers and locally stores relevant information, including L3 layer socket, keep-alive information, idle state, etc. of the remote cluster server.
The virtual server distributes idle cluster node servers and forwards the request when receiving the terminal access request each time through a load balancing algorithm.
Cluster node server: creating a server socket, managing the mapping relation between the socket and userId, and relevant service logic and Redis storage function.
Service side socket: for the L4 layer socket, the TCP protocol is supported, and all application layer protocols above the TCP protocol are supported, including HTTP, FTP, websocket and the like.
Mapping relationship between socket and userId: the relation between socket and userId is 1 to 1, 1 userId corresponds to 1 socket, and a mapping relation is generated when a terminal initiates a new socket request each time.
Related business logic: maintaining a terminal information table, storing terminal IP addresses, access time, keep-alive information and the like. In the uplink flow, when the terminal message is sent to the node server and the node server replies the message, the message is directly replied through a socket of the uplink message. In the downlink flow, when the node server needs to actively send a message to the terminal, the corresponding terminal socket needs to be queried through the userId of the terminal, and the message is sent. Maintenance of a large number of sockets. When the channel is 10 minutes (time can be set) without any interaction, the server disconnects the socket; when the socket is disconnected abnormally, the server can reserve the resources of the terminal for 5 minutes, so that the server can be conveniently reconnected again, and after 5 minutes, all cache information of the terminal is deleted without reconnection.
When an abnormality or an alarm occurs, disconnecting the socket and deleting all cache information; when one party sends a message, the other party does not respond later, and the socket is disconnected for more than 3 times continuously, and the cache is deleted.
Redis storage function: the cluster node server accesses a storage center Redis node, and related information is stored in the Redis node.
As shown in fig. 3, the first step: the client sends a request, namely web operation, to a target virtual server (VIP for short), the target virtual server LVS receives the message and forwards the message, the virtual server selects an active cluster node server according to a load balancing algorithm, the MAC address of a network card where the IP of the node (cluster node server) is located is used as a target MAC address, and the MAC address is exchanged on a link layer protocol, so that the node server and the client can be directly communicated. The plurality of node servers form a node server cluster, the cluster is established, and the virtual servers are selected for management. After the client initiates the access, if the socket is already built, the socket does not need to be built, otherwise, a new socket is built. And storing the information such as the IP address, the port and the like of the client in the cluster node server to complete the construction of the socket.
And a second step of: after the cluster is established, the terminal can link the cluster node server to create a socket, wherein in the link, the terminal is a TCP client terminal, the cluster node server is a TCP server terminal, and the terminal initiatively initiates a link request. The specific socket is randomly reserved in the cluster node server, and then the cluster node server directly communicates with the terminal. And one terminal can create a plurality of sockets, so that when the user base is large, the sockets consume very large resources. The initiate link procedure is shown in fig. 4, and 192.168.1.13/24 (TCP client) initiates an HTTP request to 192.168.1.100 (virtual server/LVS), where address 192.168.1.100 is a virtual IP address (VIP). The virtual server selects proper nodes as real target server addresses RIP1/RIP2/RIP3 from the following cluster node servers/RS 192.168.1.10/24, 192.168.1.11/24 and 192.168.1.12/24 according to a load balancing algorithm in an intranet. The eth0 port of the LVS communicates with the eth0 port of the RS, and the internal communication IP of the LVS is 192.168.1.2/24 (DIR). The generated socket information is stored in the group node server.
And a third step of: after receiving the new socket, the node server directly extracts the IP of the socket and the userId of the current socket, the two parameter mapping relations are put in a public storage center Redis, and the socket channel information is cached in the local (cluster node server). When the server actively sends a message to a certain terminal, the server only needs to know the userId of the terminal, can obtain the IP information of the socket according to the userId to be redised, and can send the message to the terminal by sending the IP information to the local cache to obtain the channel socket. If the message is the message sent by the terminal, the server directly returns to the original channel.
The invention has the following advantages:
(1) Based on the LVS cluster multi-machine load scheme, cluster socket management is achieved, the LVS is strong in load resistance, and because the LVS works on the 4 th layer, the LVS can perform load balancing on almost all applications, including http, databases, chat rooms and the like. The nginx is a web server, belongs to a lightweight class, and is not suitable for a large number of sockets.
(2) The terminal mainly adopts a tcp link server, the web terminal adopts an http link server, the WebSocket belongs to a typical application layer protocol, and compared with the tcp lock, the method wastes resources.
(3) The communication among the nodes of the server adopts http links, the http is synchronous, the result needs to be returned, the principle of one-to-one answer can be followed, the locktq is asynchronous, and the processing result is not timely.
(4) The invention needs the terminal to log in, after logging in, the binding relation between the ip of the socket and the userId of the user is stored in the redis, and the Session is single.
(5) After the socket is established, the terminal directly communicates with the node server, and in the prior art, the terminal forwards the socket to a server through the nginx, and a large amount of time is consumed for connection verification in each login verification.
In the present specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, and identical and similar parts between the embodiments are all enough to refer to each other. For the system disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section.
The principles and embodiments of the present invention have been described herein with reference to specific examples, the description of which is intended only to assist in understanding the methods of the present invention and the core ideas thereof; also, it is within the scope of the present invention to be modified by those of ordinary skill in the art in light of the present teachings. In view of the foregoing, this description should not be construed as limiting the invention.
Claims (8)
1. A cluster management method, comprising:
the virtual server acquires a communication request of a client;
the virtual server selects a cluster node server according to the communication request of the client by using a load balancing algorithm;
the cluster node server creates socket channel information according to the cluster node server and the client; the socket channel information comprises the IP information of the socket and the user identifier of the socket;
the virtual server and the terminal communicate through an L4 layer TCP socket, and the virtual server is used as a server end of the TCP, receives a connection request of the terminal and forwards the connection request to the cluster node server through the L3 layer socket; the virtual server establishes a plurality of L3 sockets to interact messages with the cluster node server through L3 layer socket communication between the virtual server and the cluster node server.
2. The cluster management method according to claim 1, wherein the cluster node server creates socket channel information according to the cluster node server and the client, specifically comprising:
the client initiates a link request to the cluster node server;
and the cluster node server creates socket channel information according to the link request.
3. The cluster management method according to claim 2, wherein the client is a client of TCP protocol; the cluster node server is a server end of a TCP protocol.
4. The cluster management method according to claim 1, further comprising, after the cluster node server creates socket channel information from the cluster node server and the client:
and caching the socket channel information on the cluster node server.
5. The cluster management method according to claim 1, further comprising, after the cluster node server creates socket channel information from the cluster node server and the client:
and storing the socket channel information to a storage center.
6. A cluster management system, wherein the cluster management system applies the cluster management method of any one of claims 1 to 5, and the cluster management system includes: a client, a virtual server and a cluster node server;
the virtual server is respectively in communication connection with the client and the cluster node server; the virtual server is used for acquiring the communication request of the client and selecting a cluster node server according to the communication request of the client by utilizing a load balancing algorithm; the cluster node server is used for creating socket channel information according to the cluster node server and the client;
the virtual server and the terminal communicate through an L4 layer TCP socket, and the virtual server is used as a server end of the TCP, receives a connection request of the terminal and forwards the connection request to the cluster node server through the L3 layer socket; the virtual server establishes a plurality of L3 sockets to interact messages with the cluster node server through L3 layer socket communication between the virtual server and the cluster node server.
7. The cluster management system of claim 6, wherein the client is a client of TCP protocol; the cluster node server is a server end of a TCP protocol.
8. The cluster management system of claim 6, further comprising a storage center; the storage center is in communication connection with the cluster node server; the storage center is used for storing the socket channel information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210838951.0A CN115250275B (en) | 2022-07-18 | 2022-07-18 | Cluster management method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210838951.0A CN115250275B (en) | 2022-07-18 | 2022-07-18 | Cluster management method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115250275A CN115250275A (en) | 2022-10-28 |
| CN115250275B true CN115250275B (en) | 2024-02-13 |
Family
ID=83699787
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210838951.0A Active CN115250275B (en) | 2022-07-18 | 2022-07-18 | Cluster management method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115250275B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103533080A (en) * | 2013-10-25 | 2014-01-22 | 北京奇虎科技有限公司 | Dispatching method and device for LVS (Linux virtual server) |
| CN108123938A (en) * | 2017-12-14 | 2018-06-05 | 中盈优创资讯科技有限公司 | A kind of AAA service implementing methods and system |
| CN110351246A (en) * | 2019-06-12 | 2019-10-18 | 深圳市奥克多普科技有限公司 | Server cluster system Socket management method and device |
| CN111638957A (en) * | 2020-06-01 | 2020-09-08 | 山东汇贸电子口岸有限公司 | Method for realizing cluster sharing type public cloud load balance |
| CN114448983A (en) * | 2022-03-09 | 2022-05-06 | 南京凌华微电子科技有限公司 | ZooKeeper-based distributed data exchange method |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030014524A1 (en) * | 2001-07-11 | 2003-01-16 | Alexander Tormasov | Balancing shared servers in virtual environments |
| US9268590B2 (en) * | 2012-02-29 | 2016-02-23 | Vmware, Inc. | Provisioning a cluster of distributed computing platform based on placement strategy |
-
2022
- 2022-07-18 CN CN202210838951.0A patent/CN115250275B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103533080A (en) * | 2013-10-25 | 2014-01-22 | 北京奇虎科技有限公司 | Dispatching method and device for LVS (Linux virtual server) |
| CN108123938A (en) * | 2017-12-14 | 2018-06-05 | 中盈优创资讯科技有限公司 | A kind of AAA service implementing methods and system |
| CN110351246A (en) * | 2019-06-12 | 2019-10-18 | 深圳市奥克多普科技有限公司 | Server cluster system Socket management method and device |
| CN111638957A (en) * | 2020-06-01 | 2020-09-08 | 山东汇贸电子口岸有限公司 | Method for realizing cluster sharing type public cloud load balance |
| CN114448983A (en) * | 2022-03-09 | 2022-05-06 | 南京凌华微电子科技有限公司 | ZooKeeper-based distributed data exchange method |
Non-Patent Citations (1)
| Title |
|---|
| 集群信息系统在钢铁企业对标管理中的作用;徐彬;王雪松;薛贵军;张翠坤;;河北理工学院学报(社会科学版)(第03期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115250275A (en) | 2022-10-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4700055B2 (en) | System, network entity, and computer program for configuration management of dynamic host configuration protocol framework | |
| WO2016155300A1 (en) | Remote control system and remote control method for wireless terminal device | |
| US8898268B2 (en) | Method and apparatus for network management | |
| US6397255B1 (en) | Method and apparatus for providing intelligent network services | |
| US20080091812A1 (en) | Automatic proxy registration and discovery in a multi-proxy communication system | |
| US20030088696A1 (en) | Performing multicast communication in computer networks by using overlay routing | |
| CN110351246A (en) | Server cluster system Socket management method and device | |
| US7188175B1 (en) | Method and system for communicating between clients in a computer network | |
| CN102045270A (en) | Chat server system, method for constructing chat server system and chat system | |
| WO2011120256A1 (en) | Method, system and corresponding device for balancing load | |
| US7965630B1 (en) | Load balancing port proxy for dynamically controlling routing of query requests | |
| CN102025799A (en) | Method for discovery and automatic configuration for IP address of device | |
| US20130117308A1 (en) | Apparatus, Method and System for Node Discovering | |
| WO2014014909A1 (en) | Control system for conferencing applications in named-data networks | |
| WO2021169291A1 (en) | Route advertising method, network elements, system, and device | |
| CN112671554A (en) | Node fault processing method and related device | |
| WO2011038639A1 (en) | Realizing method for end-to-end instant messaging, terminal and system for end-to-end instant messaging | |
| CN112073244A (en) | TR069 protocol-based message processing method and system | |
| CN100563263C (en) | In network storage service, realize the method and system of system high-available | |
| US7848258B2 (en) | Dynamically transitioning static network addresses | |
| CN110771117B (en) | Session layer communication using ID-oriented network | |
| CN115250275B (en) | Cluster management method and system | |
| CN115987871B (en) | MQTT-based topological relation preservation method, device and medium | |
| JP5241665B2 (en) | COMMUNICATION DEVICE, COMMUNICATION SYSTEM, AND COMMUNICATION METHOD | |
| EP2591586A1 (en) | Apparatus, method and system for node discovering |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |