CN111371865B - Client connection relation adjusting method, system and node - Google Patents

Client connection relation adjusting method, system and node Download PDF

Info

Publication number
CN111371865B
CN111371865B CN202010119142.5A CN202010119142A CN111371865B CN 111371865 B CN111371865 B CN 111371865B CN 202010119142 A CN202010119142 A CN 202010119142A CN 111371865 B CN111371865 B CN 111371865B
Authority
CN
China
Prior art keywords
node
information
client
connection
database cluster
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
Application number
CN202010119142.5A
Other languages
Chinese (zh)
Other versions
CN111371865A (en
Inventor
王海龙
蔡池池
韩朱忠
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Dameng Database Co Ltd
Original Assignee
Shanghai Dameng Database Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shanghai Dameng Database Co Ltd filed Critical Shanghai Dameng Database Co Ltd
Priority to CN202010119142.5A priority Critical patent/CN111371865B/en
Publication of CN111371865A publication Critical patent/CN111371865A/en
Application granted granted Critical
Publication of CN111371865B publication Critical patent/CN111371865B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/104Peer-to-peer [P2P] networks
    • H04L67/1061Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1001Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004Server selection for load balancing
    • H04L67/1008Server selection for load balancing based on parameters of servers, e.g. available memory or workload
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1001Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1031Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/104Peer-to-peer [P2P] networks
    • H04L67/1044Group management mechanisms 
    • H04L67/1046Joining mechanisms
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/104Peer-to-peer [P2P] networks
    • H04L67/1044Group management mechanisms 
    • H04L67/1048Departure or maintenance mechanisms

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Mathematical Physics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The invention discloses a method, a system and a node for adjusting a client connection relation. Wherein, the method comprises the following steps: any node in the database cluster periodically acquires the connection information and the switching information of all nodes in the database cluster, wherein the connection information is the information of a target node in the database cluster, and the switching information is the information of a client to be adjusted; and the connection relation between any node and the client is adjusted by any node according to the connection information and the switching information. Therefore, even if the load condition on each node changes, any node can dynamically adjust the connection relation between the node and the client based on the acquired latest connection information and switching information, and the load balance of the database cluster is realized.

Description

Client connection relation adjusting method, system and node
Technical Field
The embodiment of the invention relates to a data processing technology, in particular to a method, a system and a node for adjusting a client connection relation.
Background
In the field of implementing database cluster load balancing for application systems, the existing implementation is generally to determine a connection instance when a client creates a connection. Once the connection instance is determined, the instance of the connection is kept unchanged. The allocation of the connection instance is determined according to the load condition of the system when the connection is established, for example, the number of client connections, the memory, the Central Processing Unit (CPU), and the like. If the load condition of each instance changes, for example, the number of connections on each instance is unbalanced due to disconnection of the client, or the load generated by the connections already distributed to the instances is always larger than that on other instances, the connected instances cannot be dynamically adjusted.
Disclosure of Invention
The invention provides a method, a system and a node for adjusting a client connection relation, which can dynamically adjust the connection relation between the node and a client and realize the load balance of a database cluster.
In a first aspect, an embodiment of the present invention provides a method for adjusting a connection relationship between clients, where the method includes:
any node in the database cluster periodically acquires the connection information and the switching information of all nodes in the database cluster, wherein the connection information is the information of a target node in the database cluster, and the switching information is the information of a client to be adjusted;
and any node adjusts the connection relation between any node and the client according to the connection information and the switching information.
In a second aspect, an embodiment of the present invention further provides a client connection relation adjusting system, where the system includes: the system comprises a database cluster formed by at least two nodes and a client connected with the at least two nodes;
the system comprises a database cluster, a client and a server, wherein any node in the database cluster is used for periodically acquiring connection information and switching information of all nodes in the database cluster, the connection information is information of a target node in the database cluster, and the switching information is information of the client to be adjusted;
adjusting the connection relation between any node and the client according to the connection information and the switching information;
the client is used for analyzing the response message and acquiring the connection information and the switching information;
when the client determines that the client needs to switch according to the switching information, the client is used for connecting to a target node according to the connection information and disconnecting the connection relation between the client and any node;
the client is also used for caching the connection information of the client and the connection information of any node when any node is connected for the first time.
In a third aspect, an embodiment of the present invention further provides a node, where the node includes:
a memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor, implement the functionality of any of the nodes as in the embodiments of the invention.
The embodiment of the invention provides a method, a system and nodes for adjusting a client connection relation, and particularly relates to a method, a system and nodes for periodically acquiring connection information and switching information of all nodes in a database cluster by any node in the database cluster, wherein the connection information is information of a target node in the database cluster, and the switching information is information of a client to be adjusted; and the connection relation between any node and the client is adjusted by any node according to the connection information and the switching information. Therefore, even if the load condition of each node changes, any node can dynamically adjust the connection relation between the node and the client based on the latest acquired connection information and switching information, and the load balance of the database cluster is realized.
Drawings
Fig. 1 is a flowchart of a method for adjusting a connection relationship between clients according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a client connection relationship adjustment system according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a node structure in the embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
In addition, in the embodiments of the present invention, words such as "optionally" or "exemplarily" are used for indicating as examples, illustrations or explanations. Any embodiment or design described as "optionally" or "exemplary" in embodiments of the invention is not to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the words "optionally" or "exemplary" etc. are intended to present relevant concepts in a concrete fashion.
Fig. 1 is a diagram of a method for adjusting a connection relationship between clients according to an embodiment of the present invention, which is applied in a data cluster scenario including at least two nodes, and as shown in fig. 1, the method specifically includes:
s101, any node in the database cluster periodically acquires the connection information and the switching information of all nodes in the database cluster.
The connection information in the above steps is information of a target node to be connected in the database cluster, for example, an Internet Protocol Address (IP Address) and a port number of the target node, and the switching information is related information of a client to be switched and adjusted on the node, such as the number to be switched and an interface. The client is a part of the database cluster, and can be specifically understood as an interface and a driver for communication between the application program and the database cluster.
In this embodiment, any node in the database cluster may be a control node or a slave control node, where the control node is configured to determine a target node, and the slave control node is configured to perform client connection relationship adjustment according to information sent by the control node. Of course, the target node may be a control node or a slave node.
And S102, any node adjusts the connection relation between any node and the client according to the connection information and the switching information.
After the connection information and the switching information of all the nodes in the database cluster are acquired through the step S101, any node can adjust the connection relationship between itself and the client according to the connection information and the switching information of all the nodes.
In this embodiment, each node may periodically acquire the latest connection information and switching information of all nodes in the database cluster, so that even if the load condition on each node changes, based on the latest connection information and switching information acquired by the node, the connection relationship between the node and the client may be dynamically adjusted, so as to implement load balancing of the database cluster under the condition of following the Atomicity, consistency, isolation, and persistence (Atomicity, consistency, isolation, dual, ACDI) principles, and at the same time, the implementation method does not need to adjust the application program.
In an example, when any of the nodes is a control node, the implementation manner of step S101 may be that the control node periodically collects load information of all nodes in the database cluster, for example, memory usage, CPU, the number of client connections, and the like of each node, and then determines connection information and switching information of all nodes according to the load information of all nodes.
For example, the control node may determine, according to the load information of all the nodes, connection information and switching information of all the nodes in an implementation manner, that the control node determines, based on a load balancing algorithm, a node with the minimum load in the database cluster as a target node for switching all the nodes in the cluster according to the load information of all the nodes, where information of the target node is the connection information. Furthermore, the control node determines the switching information of each node, such as the number of required switching of each node, interfaces and the like, according to the load information of the target node.
The load balancing algorithm may adopt any algorithm that can implement a corresponding function in the prior art, which is not limited in this embodiment. Certainly, the determined switching information is not that all the clients connected to the nodes except the target node need to be switched, that is, the number of the clients that some nodes need to be switched is 0, and only part of the clients connected to some nodes need to be switched to the target node.
In an example, when any of the nodes is a slave node, the implementation manner of step S101 may be that the slave node periodically receives connection information and switching information of all nodes in the database cluster, which are sent by the control node, where the slave node may be any node in the database cluster except the control node.
In an example, when the connection relationship between any node and the client needs to be adjusted, the implementation manner of step S102 may be that any node switches the client connected to any node to a target node according to the connection information and the switching information, where the target node is any node in other nodes except any node in the database cluster.
For example, after performing the transaction COMMIT or ROLLBACK, any node may carry the acquired connection information and handover information in a response message to send to the client connected to itself in a manner of sending the response message. And assuming that the client connected with the node comprises three clients A, B and C, wherein after receiving the response information, the client C determines that the switching information conforms to the information of the client C, namely the client C on the node needs to be switched to the target node, and then the client C corresponding to the switching information is switched to the target node according to the connection information.
For example, the implementation process of switching the client to the target node may be that the client parses the received response message, obtains the connection information and the switching information, connects to the target node according to the connection information if the client determines that the client needs to switch according to the switching information, disconnects the connection relationship between the client and the previous node after the client successfully connects to the target node, and caches the connection information of the target node. Of course, if the client confirms that the client does not need to perform the switching, no operation is performed.
In an example, when the connection relationship between any node and the client does not need to be adjusted, the implementation manner of step S102 may be that any node keeps the connection relationship between itself and the client unchanged according to the connection information and the handover information, that is, the connection information does not include the relevant information of the client connected to the current node, and then the client connected to the node does not need to perform handover adjustment.
In another example, if any node determines that the node is a target node according to the connection information, the implementation manner of step S102 may be that the target node connects to a corresponding client according to the handover information.
In addition, this embodiment also provides an optional implementation manner, when a client connects to any node for the first time, the client caches connection information of the client (for example, information such as a login account and a login password) and connection information of any node (for example, an IP address and a port number of the node), so that, if the client needs to switch to a target node but does not switch successfully, the client may continue to maintain an original connection with the node based on the cached information, and perform a database related operation on the node.
Fig. 2 is a system for adjusting a connection relationship between clients according to an embodiment of the present invention, and as shown in fig. 2, the system includes: the system comprises a database cluster formed by at least two nodes and a client connected with the at least two nodes;
the system comprises a database cluster, a client and a server, wherein any node in the database cluster is used for periodically acquiring connection information and switching information of all nodes in the database cluster, wherein the connection information is information of a target node in the database cluster, and the switching information is information of the client to be adjusted;
and any node is also used for adjusting the connection relation between the node and the client according to the connection information and the switching information.
In an example, when any of the nodes is a control node, the control node is configured to periodically collect load information of all nodes in the database cluster, and determine connection information and handover information of all nodes according to the load information of all nodes.
In an example, when any of the above nodes is a slave control node, the slave control node is configured to periodically receive the connection information and the handover information of all the nodes in the database cluster, where the connection information and the handover information are sent by the control node, and the slave control node is any node in the database cluster except the control node.
In one example, any node is further configured to switch the client connected to the node to a target node according to the connection information and the switching information, where the target node is any node in other nodes except for any node in the database cluster;
or keeping the connection relation between any node and the client unchanged according to the connection information and the switching information.
In one example, when any node determines itself to be the target node according to the connection information, the target node connects with the corresponding client according to the handover information.
Further, any node can send a response message carrying the connection information and the switching information to a client connected with any node, so that the client corresponding to the switching information is switched to a target node according to the connection information.
The client is used for analyzing the response message and acquiring the connection information and the switching information;
and when the client determines that the client needs to switch according to the switching information, the client is used for connecting to the target node according to the connection information and disconnecting the connection relation between the client and any node.
Further, the client is also used for caching the connection information of the client and the connection information of any node when any node is connected for the first time.
Fig. 3 is a schematic structural diagram of a node according to an embodiment of the present invention, as shown in fig. 3, the node includes a processor 301, a memory 302, an input device 303, and an output device 304; the number of the processors 301 in the node may be one or more, and one processor 301 is taken as an example in fig. 3; the processor 301, the memory 302, the input device 303 and the output device 304 in the node may be connected by a bus or other means, which is exemplified in fig. 3.
The memory 302 is used as a computer-readable storage medium, and can be used to store software programs, computer-executable programs, and modules, such as program instructions corresponding to the functions of the node in the client connection relation adjustment method in the embodiment of the present invention. The processor 301 executes various functional applications and data processing of the node by running software programs, instructions and modules stored in the memory 302, that is, the processor implements related functions of any node in the client connection relation adjustment method.
The memory 302 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the memory 302 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, the memory 302 may further include memory located remotely from the processor 301, which may be connected to a node/terminal/server through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input means 303 may be used to receive entered numeric or character information and to generate key signal inputs relating to user settings and function control of the node. The output device 304 may include a display node such as a display screen.
Embodiments of the present invention also provide a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to implement the functionality of any of the above-described embodiments.
From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly can be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.
It is to be noted that the foregoing description is only exemplary of the invention and that the principles of the technology may be employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in some detail by the above embodiments, the invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the invention, and the scope of the invention is determined by the scope of the appended claims.

Claims (10)

1. A method for adjusting a client connection relationship is characterized by comprising the following steps:
any node in a database cluster periodically acquires connection information and switching information of all nodes in the database cluster, wherein the connection information is information of a target node in the database cluster, and the switching information is information of a client to be adjusted; the information of the client is the number and the interface;
and the connection relation between any node and the client is adjusted by any node according to the connection information and the switching information.
2. The method of claim 1, wherein periodically obtaining connection information and handover information for all nodes in the database cluster by any node in the database cluster comprises:
when any node is a control node, the control node periodically collects load information of all nodes in the database cluster;
and the control node determines the connection information and the switching information of all the nodes according to the load information of all the nodes.
3. The method of claim 1, wherein periodically obtaining load information and handover information for all nodes in the database cluster by any node in the database cluster comprises:
when any node is a slave control node, the slave control node periodically receives connection information and switching information of all nodes in the database cluster, which are sent by the control node;
the slave control node is any node except the control node in the database cluster.
4. The method according to any one of claims 1 to 3, wherein the adjusting, by the any node, the connection relationship between the any node and the client according to the connection information and the handover information includes:
the any node switches the client connected with the any node to a target node according to the connection information and the switching information, wherein the target node is any node in other nodes except the any node in the database cluster;
or the connection relation between any node and the client is kept unchanged by any node according to the connection information and the switching information;
or when any node determines that the node is the target node according to the connection information, the target node is connected with the corresponding client according to the switching information.
5. The method of claim 4, wherein the any node switches the client connected to the any node to the target node according to the connection information and the switching information, and comprises:
the any node sends a response message carrying the connection information and the switching information to a client connected with the any node;
and the client corresponding to the switching information is switched to a target node according to the connection information.
6. The method of claim 5, wherein switching the client corresponding to the switching information to the target node according to the response message comprises:
the client analyzes the response message to acquire the connection information and the switching information;
the client side is connected to the target node according to the connection information when determining that the client side needs to switch according to the switching information;
and the client disconnects the connection relation between the client and any node.
7. The method of claim 1, further comprising:
when the client side is connected with any node for the first time, the client side caches the connection information of the client side and the connection information of any node.
8. The method of claim 7, further comprising:
and when the connection relation between any node and the client is adjusted by any node according to the connection information and the switching information, the client keeps the connection relation with any node unchanged according to the connection information of the client and the connection information of any node.
9. A client connection relationship adjustment system, comprising: the system comprises a database cluster formed by at least two nodes and a client connected with the at least two nodes;
the system comprises a database cluster and a plurality of nodes, wherein any node in the database cluster is used for periodically acquiring connection information and switching information of all nodes in the database cluster, the connection information is information of a target node in the database cluster, and the switching information is information of a client to be adjusted; the information of the client is the number and the interface;
adjusting the connection relation between any node and the client according to the connection information and the switching information;
the client is used for analyzing the response message and acquiring the connection information and the switching information;
when the client determines that the client needs to switch according to the switching information, the client is used for connecting to the target node according to the connection information and disconnecting the connection relation between the client and any node;
the client is also used for caching the connection information of the client and the connection information of any node when any node is connected for the first time.
10. A node comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor, when executing the computer program, implements the functionality of any of the nodes of claims 1-7.
CN202010119142.5A 2020-02-26 2020-02-26 Client connection relation adjusting method, system and node Active CN111371865B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010119142.5A CN111371865B (en) 2020-02-26 2020-02-26 Client connection relation adjusting method, system and node

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010119142.5A CN111371865B (en) 2020-02-26 2020-02-26 Client connection relation adjusting method, system and node

Publications (2)

Publication Number Publication Date
CN111371865A CN111371865A (en) 2020-07-03
CN111371865B true CN111371865B (en) 2023-02-24

Family

ID=71211532

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010119142.5A Active CN111371865B (en) 2020-02-26 2020-02-26 Client connection relation adjusting method, system and node

Country Status (1)

Country Link
CN (1) CN111371865B (en)

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103457967A (en) * 2012-05-30 2013-12-18 腾讯科技(深圳)有限公司 Service node switching method and system
CN104462515A (en) * 2014-12-19 2015-03-25 北京奇虎科技有限公司 Link configuration adjusting method and device
CN104486155A (en) * 2014-12-15 2015-04-01 北京趣拿软件科技有限公司 Database cluster monitoring method and system
CN104579765A (en) * 2014-12-27 2015-04-29 北京奇虎科技有限公司 Disaster tolerance method and device for cluster system
CN105207818A (en) * 2015-09-23 2015-12-30 杭州数梦工场科技有限公司 Node control method and device
CN105511805A (en) * 2015-11-26 2016-04-20 深圳市中博科创信息技术有限公司 Data processing method and device for cluster file system
CN107391633A (en) * 2017-06-30 2017-11-24 北京奇虎科技有限公司 Data-base cluster Automatic Optimal processing method, device and server
CN108055314A (en) * 2017-12-08 2018-05-18 锐捷网络股份有限公司 The management method and group system of a kind of group system
CN109245908A (en) * 2017-07-10 2019-01-18 北京京东尚科信息技术有限公司 A kind of method and apparatus of principal and subordinate's cluster switching
CN109526253A (en) * 2016-06-23 2019-03-26 华为技术有限公司 Access node, control device and method thereof
CN110580198A (en) * 2019-08-29 2019-12-17 上海仪电(集团)有限公司中央研究院 Method and device for adaptively switching OpenStack computing node into control node

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4717788B2 (en) * 2006-11-28 2011-07-06 日本電信電話株式会社 Cluster node and cluster node configuration method
CN108496405B (en) * 2015-11-30 2022-09-09 瑞典爱立信有限公司 Method and device for configuring cluster
CN106603443B (en) * 2016-12-14 2019-09-27 郑州云海信息技术有限公司 A method of carrying out data exchange in aggregated server system
CN109274641A (en) * 2018-08-09 2019-01-25 广东神马搜索科技有限公司 Connection method and device, calculating equipment and storage medium between client and service node

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103457967A (en) * 2012-05-30 2013-12-18 腾讯科技(深圳)有限公司 Service node switching method and system
CN104486155A (en) * 2014-12-15 2015-04-01 北京趣拿软件科技有限公司 Database cluster monitoring method and system
CN104462515A (en) * 2014-12-19 2015-03-25 北京奇虎科技有限公司 Link configuration adjusting method and device
CN104579765A (en) * 2014-12-27 2015-04-29 北京奇虎科技有限公司 Disaster tolerance method and device for cluster system
CN105207818A (en) * 2015-09-23 2015-12-30 杭州数梦工场科技有限公司 Node control method and device
CN105511805A (en) * 2015-11-26 2016-04-20 深圳市中博科创信息技术有限公司 Data processing method and device for cluster file system
CN109526253A (en) * 2016-06-23 2019-03-26 华为技术有限公司 Access node, control device and method thereof
CN107391633A (en) * 2017-06-30 2017-11-24 北京奇虎科技有限公司 Data-base cluster Automatic Optimal processing method, device and server
CN109245908A (en) * 2017-07-10 2019-01-18 北京京东尚科信息技术有限公司 A kind of method and apparatus of principal and subordinate's cluster switching
CN108055314A (en) * 2017-12-08 2018-05-18 锐捷网络股份有限公司 The management method and group system of a kind of group system
CN110580198A (en) * 2019-08-29 2019-12-17 上海仪电(集团)有限公司中央研究院 Method and device for adaptively switching OpenStack computing node into control node

Also Published As

Publication number Publication date
CN111371865A (en) 2020-07-03

Similar Documents

Publication Publication Date Title
US20210337046A1 (en) Intelligent scheduling method, terminal device, edge node cluster and intelligent scheduling system
CN107645529B (en) Heartbeat packet sending method and device
JP7450750B2 (en) Methods, apparatus, electronic devices, systems and storage media for configuring microservices
JP2000276432A (en) Dynamic load distribution system for transaction message
JP2019525604A (en) Network function NF management method and NF management apparatus
KR102565409B1 (en) Method, device, electronic equipment for adjusting the number of instances and readble storage medium
CN111787079A (en) Communication method, device, server, system and medium based on communication group
CN111314416B (en) Data synchronization method, device, system, equipment and storage medium
KR101916799B1 (en) Apparatus And Method For Big Data Server Load Balancing Control
EP3817335A1 (en) System operating using opc ua, communication method using opc ua, and load balancer
CN111371865B (en) Client connection relation adjusting method, system and node
CN113079210A (en) Cross-region data automatic synchronization configuration method, terminal equipment and storage medium
CN109788075B (en) Private network system, data acquisition method and edge server
CN110493095A (en) A kind of processing method of vpn service, device, server and storage medium
CN111162952A (en) Equipment fault tolerance method and device
EP2047373A2 (en) Host posing network device and method thereof
CN113596119A (en) Edge capability distribution method, system, device and computer readable storage medium
CN108696598B (en) Method and device for transparently transmitting message received by stateless service through long connection under micro-service architecture
CN111258739A (en) Server process updating method, device, server and medium
CN112559472A (en) File transmission method and device, computer equipment and storage medium
CN113271326A (en) Network protocol address scheduling method and device and electronic equipment
CN111416852A (en) Method for session synchronization among multiple load balancers and load balancer
CN116055555B (en) Proxy server setting method, proxy server setting device, electronic equipment and readable storage medium
CN106911815B (en) Information processing method, capacity expansion method, manager, controller and DNS (domain name system)
US12009968B1 (en) Managing regional failover via DNS queries

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