CN109218349A - A kind of method and device of management server cluster - Google Patents
A kind of method and device of management server cluster Download PDFInfo
- Publication number
- CN109218349A CN109218349A CN201710520921.4A CN201710520921A CN109218349A CN 109218349 A CN109218349 A CN 109218349A CN 201710520921 A CN201710520921 A CN 201710520921A CN 109218349 A CN109218349 A CN 109218349A
- Authority
- CN
- China
- Prior art keywords
- server
- cluster
- server cluster
- servers
- distributed
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 74
- 238000001514 detection method Methods 0.000 claims abstract description 34
- 238000012544 monitoring process Methods 0.000 claims abstract description 32
- 230000001360 synchronised effect Effects 0.000 claims abstract description 18
- 230000004044 response Effects 0.000 claims description 38
- 230000008569 process Effects 0.000 claims description 14
- 238000005516 engineering process Methods 0.000 abstract description 5
- 238000012935 Averaging Methods 0.000 abstract 1
- 238000004891 communication Methods 0.000 description 13
- 230000002159 abnormal effect Effects 0.000 description 12
- 230000006870 function Effects 0.000 description 8
- 238000012545 processing Methods 0.000 description 7
- 230000005856 abnormality Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000036541 health Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000002547 anomalous effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1029—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers using data related to the state of servers by a load balancer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1031—Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the present invention discloses a kind of method and device of management server cluster, is related to cluster management technology, is capable of the resource utilization of server cluster.The method of the management server cluster includes: the local data base of the server based on distributed push strategy of synchronous averaging after triggering starting is based on the server of distributed push strategy；Whether the server based on distributed push strategy of detection starting is primary server in subordinate server cluster, if the server based on distributed push strategy of starting is primary server, it is provided out service by the synchronous local data base, starting there are multiple primary servers in the server cluster；Pre-set monitoring process is opened, monitors the connection status of other servers in the server cluster, and the connection status obtained according to monitoring updates the corresponding server list of the connection status.The present invention is suitable for being managed the multiple servers using distributed push strategy.
Description
Technical Field
The present invention relates to cluster management technologies, and in particular, to a method and an apparatus for managing a server cluster.
Background
With the continuous development of computer technology and internet communication technology, the content provided by internet pages is more and more abundant, because only one-way communication can be realized in a browser through a hypertext Transfer Protocol (HTTP), the browser needs to continuously send requests to a server to realize quasi-real-time interaction, more bandwidth resources need to be occupied, and as the real-time requirement of a client (browser) on the server is higher and higher, the HTTP mode cannot meet the real-time requirement of a user in some application scenes. In order to improve the real-time experience of a user, a distributed push service based on a WebSocket technology is provided, wherein the WebSocket is a protocol based on HTML5, and full-duplex communication (full-duplex) between a browser and a server can be realized, so that a request is not required to be sent to the server by the browser, the server can actively push the service to the browser, and the distributed push service is suitable for various service functions needing real-time push, for example: chat rooms, page notifications, real-time announcements, dynamic seating charts, etc.
At present, in order to improve the reliability of a server for pushing a service in real time, a server cluster is formed by a plurality of servers based on a distributed pushing strategy, and each server in the server cluster is managed, that is, a master (master) server and one or more slave (slave) servers are arranged in the server cluster, the master server provides the service to the outside, the slave servers monitor the running state of the master servers and keep data synchronization with the master servers, and after the master servers are monitored to be abnormal, one slave server is selected to take over the abnormal master server according to a preset election strategy and is responsible for providing the service to the outside.
However, in the method for managing the servers in the server cluster, one or more slave servers are used as backup servers of the main server, and only when the main server is abnormal, one slave server is selected to take over the main server, so that the resources of the slave servers cannot be effectively utilized, and the resource utilization rate of the server cluster is low; further, when the number of the browsers requiring the push service is large, the response speed or the push speed of the main server may be slow, thereby reducing the service efficiency of the main server.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for managing a server cluster, which can improve a resource utilization rate of the server cluster, so as to solve a problem of a low resource utilization rate of the server cluster caused by that resources of a server are not effectively utilized in an existing method for managing a server cluster based on a distributed push policy.
In a first aspect, an embodiment of the present invention provides a method for managing a server cluster, including:
after triggering and starting a server based on a distributed pushing strategy, synchronously starting a local database of the server based on the distributed pushing strategy;
detecting whether the started server based on the distributed pushing strategy is a main server in a server cluster, if the started server based on the distributed pushing strategy is the main server, providing service to the outside through the synchronous local database, wherein a plurality of main servers are started in the server cluster;
starting a monitoring process preset in the started server based on the distributed pushing strategy, monitoring the connection state of other servers in the server cluster except the started server based on the distributed pushing strategy, and updating a server list corresponding to the connection state according to the monitored connection state.
With reference to the first aspect, in a first implementation manner of the first aspect, the synchronizing initiated local database of the distributed push policy based server includes:
establishing TCP long connections with other running servers in the server cluster except the started server based on the distributed push strategy;
and receiving a database updating message in the server cluster through the TCP long connection, and updating a local database according to the database updating message.
With reference to the first aspect, in a second implementation manner of the first aspect, before synchronizing the local database of the started server based on the distributed push policy after triggering the start of the server based on the distributed push policy, the method further includes:
judging whether the server cluster is registered, if so, executing the synchronous started local database of the server based on the distributed push strategy; if not, sending a joining request to any main server in the server cluster, and if the joining request passes the authentication, executing the step of synchronously starting the local database of the server based on the distributed push strategy.
With reference to the second implementation manner of the first aspect, in a third implementation manner of the first aspect, the sending a join request to any master server in the server cluster, and if the join request passes authentication, includes:
the main server receives the joining request, after the authentication of the joining request is passed, the server information sending the joining request is added to a server list in a local database, the server list adding the server information is carried in the joining request, the joining request is returned to the server sending the joining request, the server information sending the joining request is packaged into database updating information, and the database updating information is broadcasted in the server cluster.
With reference to the first aspect and any one of the first to third implementation manners of the first aspect, in a fourth implementation manner of the first aspect, the detecting whether the server is a master server in a server cluster to which the server belongs includes:
and detecting whether the server is a main server in the server cluster according to the server list in the synchronized local database.
With reference to the first aspect and any one of the first to third implementation manners of the first aspect, in a fifth implementation manner of the first aspect, the monitoring connection states of other servers in the server cluster, and updating the server list corresponding to the connection state according to the monitored connection state includes:
sending ping requests to other servers in the server cluster according to a preset heartbeat cycle;
if the ping request response returned by the server is not received within the preset heartbeat detection time threshold, deleting the server which does not return the ping request response from the server list to obtain an updated server list;
and pushing the updated server list to each server contained in the updated server list.
With reference to the fifth implementation manner of the first aspect, in a sixth implementation manner of the first aspect, before deleting a server that does not return a ping request response from the server list after the server that does not return a ping request response is not received within a preset heartbeat detection time threshold, the method further includes:
and sequentially sending ping requests to servers which do not return ping request responses, and if the number of times of not receiving ping request responses within a preset heartbeat detection time threshold reaches a preset heartbeat detection number threshold, executing the step of deleting the servers which do not return ping request responses from the server list.
With reference to the first aspect or any one of the first to third embodiments of the first aspect, in a seventh embodiment of the first aspect, the method further includes:
if the slave server is detected to be a slave server in the server cluster, synchronizing the local database from the master server which normally operates according to a preset updating period, and electing a slave server by using a preset election strategy to replace the master server which generates the abnormity after the master server is monitored to generate the abnormity.
In a second aspect, an embodiment of the present invention provides an apparatus for managing a server cluster, including: a synchronization module, a detection module, and a process monitoring module, wherein,
the synchronization module is used for synchronizing the started local database of the server based on the distributed pushing strategy after triggering the starting of the server based on the distributed pushing strategy;
the detection module is used for detecting whether the started server based on the distributed pushing strategy is a main server in a server cluster, if the started server based on the distributed pushing strategy is the main server, the service is provided to the outside through the synchronous local database, and a plurality of main servers are started in the server cluster;
and the process monitoring module is used for starting a preset monitoring process in the started server based on the distributed pushing strategy, monitoring the connection state of other servers in the server cluster except the started server based on the distributed pushing strategy, and updating a server list corresponding to the connection state according to the monitored connection state.
With reference to the second aspect, in a first implementation manner of the second aspect, the synchronization module includes: a start unit, a connection unit and a synchronization unit, wherein,
the starting unit is used for informing the linking unit after triggering and starting the server based on the distributed push strategy;
the connection unit is used for constructing TCP long connections with other running servers in the server cluster except the started server based on the distributed push strategy;
and the synchronization unit is used for receiving the database updating message in the server cluster through the TCP long connection and updating a local database according to the database updating message.
According to the method and the device for managing the server cluster, after the server based on the distributed pushing strategy is triggered and started, the local database of the server based on the distributed pushing strategy is synchronously started; detecting whether the started server based on the distributed pushing strategy is a main server in a server cluster, if the started server based on the distributed pushing strategy is the main server, providing service to the outside through the synchronous local database, wherein a plurality of main servers are started in the server cluster; the method comprises the steps of starting a monitoring process preset in a server based on the distributed pushing strategy, monitoring the connection state of other servers in the server cluster except the server based on the distributed pushing strategy, and updating a server list corresponding to the connection state according to the connection state obtained through monitoring.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a method for managing a server cluster according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a method for managing a server cluster according to a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of a device for managing a server cluster according to a third embodiment of the present invention.
Detailed Description
Embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
It should be understood that the described embodiments are only some embodiments of the invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 is a schematic flowchart of a method for managing a server cluster according to an embodiment of the present invention, and as shown in fig. 1, the method according to this embodiment may include:
step 101, after a server based on a distributed push strategy is triggered to start, synchronizing a local database of the server based on the distributed push strategy;
in this embodiment, as an optional embodiment, the synchronously started local database of the server based on the distributed push policy includes:
establishing TCP long connections with other running servers in the server cluster except the started server based on the distributed push strategy;
and receiving a database updating message in the server cluster through the TCP long connection, and updating a local database according to the database updating message.
In this embodiment, as an optional embodiment, the communication protocols between the servers in the server cluster (between the master server and the master server, between the master server and the slave server, and between the slave server and the slave server) adopt TCP long connection, the data type of communication is a binary format, and by adopting the communication mode of the data type, the data packet during communication is smaller, the communication speed is faster, and the communication efficiency is higher.
In this embodiment, as an optional embodiment, the database is located locally in the server, a distributed database is constructed by multiple servers in a TCP long connection manner, and each database stores the same data backup, so that the efficiency of query can be effectively improved.
In this embodiment, as an optional embodiment, after triggering and starting the server based on the distributed push policy, before synchronizing the started local database of the server based on the distributed push policy, the method further includes:
judging whether the server cluster is registered, if so, executing the synchronous started local database of the server based on the distributed push strategy; if not, sending a joining request to any main server in the server cluster, and if the joining request passes the authentication, executing the step of synchronously starting the local database of the server based on the distributed push strategy.
In this embodiment, as an optional embodiment, sending a join request to any main server in the server cluster, and if the join request passes authentication, the sending includes:
the main server receives the joining request, after the authentication of the joining request is passed, the server information sending the joining request is added to a server list in a local database, the server list adding the server information is carried in the joining request, the joining request is returned to the server sending the joining request, the server information sending the joining request is packaged into database updating information, and the database updating information is broadcasted in the server cluster.
In this embodiment, when another server is ready to join the server cluster, a join request, for example, a ping request, may be sent to any master server, and after the master server passes authentication, the master server agrees to join the server, returns a ping request response to the server, and carries an updated server list in the ping request response, and simultaneously, notifies the newly joined server information, for example, the address information of the newly joined server to the other servers already joined in the server cluster, or broadcasts the address information of the newly joined server in the server cluster. In this way, it is ensured that each server in the server cluster can update the server list synchronously.
In this embodiment, as an optional embodiment, the local database is a relational database management system (MySQL) database.
In this embodiment, a MYSQL database is configured on the server that adopts the distributed push policy, the database uses a Structured Query Language (SQL) Language, and the SQL Language is the most common standardized Language for accessing the database.
In this embodiment, as an optional embodiment, the local database is used to store shared resources of the server cluster, and provide services to the outside when the server is the main server.
In this embodiment, as an optional embodiment, the shared resources include but are not limited to: server address information, name of service provided, name of module registered to global by local server, name of global method, global list data and service data. Wherein,
server address information (server name) and a provided service name for identifying an access address of each server and a provided service when a plurality of servers are connected to each other. As an alternative embodiment, in the server cluster, the service names provided by the main servers are the same.
The local server registers global module names and global method names, when the server calls a certain service function, the local server directly fills the global module names and the global method names corresponding to the service function to realize the service function call, searches corresponding server address information according to the global module names and the global method names recorded in the local database, and then remotely calls according to the searched server address information.
In this embodiment, as an optional embodiment, the global module name and the method name in the database may be shared by each server in a TCP long connection manner, and other servers may perform remote access according to the global module name and the method name information of the server, which includes the following specific processes:
when a server joins a server cluster through a master server, a main server in the server cluster can be selected in a random mode to send a pull resource list (get _ resources) request, namely a joining request, after the selected main server receives the pull resource list request and agrees to join, all data (server address information, provided service name, global module name, global method name and global list data) stored in a database are packaged in a pull resource list request response, and the pull resource list request is returned to the server sending the pull resource list request and stored.
When the server calls the module name and the method name, the server address corresponding to the module name and the method name is found from the acquired database, and then the message is directly sent to a remote server. Therefore, the rapid communication among the servers can be more efficiently carried out, and the synchronous communication, the asynchronous communication and the broadcast communication among the servers can be conveniently realized based on the connection mode.
The global list data is a list of blank structures provided to the entire server cluster, and the data stored in the blank structure list is accessible to each server as shared data. In this embodiment, the blank structure list is used as a function to be expanded later, and the global list data is selectable.
The business data is data corresponding to the service pushed outwards.
In this embodiment, as an optional embodiment, in the local database, the module name registered by the local server to the global may map one or more global method names, and a module name registered by the local server to the global and a global method name may map one or more server address information and a provided service name, that is, the module name and the global method name registered by the local server to the global (the module name registered by the local server to the global + the global method name) and the server address information and the provided service name (the server address information + the provided service name) are in one-to-one or one-to-many correspondence, and a module name may be combined with a method name to correspond to a plurality of server address information and a provided service name.
In this embodiment, all the master servers in the server cluster provide the same service to the outside, the master servers and the slave servers mutually synchronize databases, and each server has a complete and identical database.
102, detecting whether the started server based on the distributed pushing strategy is a main server in a server cluster, if the started server based on the distributed pushing strategy is the main server, providing service to the outside through the synchronous local database, wherein a plurality of main servers are started in the server cluster;
in this embodiment, as an optional embodiment, in order to ensure stable operation of the server cluster and reduce catastrophic failure of the server cluster, the number of the primary servers started in the server cluster may be set according to the required stability and the tolerable failure rate, so that by setting and starting a plurality of primary servers, there is no master-slave division between the plurality of primary servers, the configuration of each primary server is the same, the primary servers are responsible for the same things in the server cluster, provide the same function, and play a role of intermediary, so that when adding into the server cluster, other servers can complete the adding process no matter which primary server is connected, and after one or more primary servers fail, other normally operating primary servers can ensure normal operation of the server cluster without re-selecting the primary server through the secondary server, therefore, the service waiting time is effectively reduced, and the service efficiency is improved.
In this embodiment, as an optional embodiment, the detecting whether the server cluster is the master server in the server cluster includes:
and detecting whether the server is a main server in the server cluster according to the server list in the synchronized local database.
In this embodiment, as an optional embodiment, if the server cluster is started, all the main servers in the server cluster may be started, and if the server cluster is synchronously closed after the last operation, when each main server performs data synchronization, the local databases in each main server are the same.
In this embodiment, information on whether the server is the master server is preset in the server list in the local database, and thus, by reading the server list in the local database, it can be determined whether the server is the master server in the server cluster to which the server belongs.
In this embodiment, the server cluster includes one or more servers, including a plurality of master servers and one or more slave servers, where each server may also be referred to as a node.
In the server cluster, a plurality of servers are provided as master servers in advance, and for example, two to five servers are designated as master servers, and the other servers are designated as slave servers. When the server cluster is started, all the main servers are started first, the starting sequence of each main server can be started by adopting a random method, and after all the main servers are started, the corresponding slave servers are started.
In this embodiment, if it is detected that the slave server is a slave server in the server cluster to which the slave server belongs, the local database is synchronized from the master server that operates normally according to a preset update period, and after it is detected that the master server is abnormal, a slave server is selected by using a preset election policy to replace the master server that is abnormal. The master server having the abnormality is used as a slave server after the abnormality is resolved.
In this embodiment, as an optional embodiment, after the master server is started, the service may be provided to the outside through the local database, and since the plurality of master servers (upgrading other slave servers to the master server) are arranged in the server cluster, the service may be provided to the outside through the plurality of master servers, so that resources of the server cluster are effectively utilized, and the resource utilization rate of the server cluster is improved; moreover, under the condition of more service requests or more browsers needing to push services, the services can be distributed to a plurality of main servers through strategies such as load balancing, so that performance indexes such as response speed or push speed of the main servers cannot be reduced, and the service efficiency of the main servers is enhanced.
Step 103, starting a monitoring process preset in the started server based on the distributed pushing policy, monitoring the connection states of other servers in the server cluster except the started server based on the distributed pushing policy, and updating a server list corresponding to the connection states according to the monitored connection states.
In this embodiment, after the master server is started and establishes interconnection and intercommunication with other master servers and other slave servers, a preset monitoring process is started.
In this embodiment, in order to ensure that each server in the server cluster can be constantly in a connected state, the monitoring process in the master server sends a ping request to each server at regular time to perform a check. Therefore, as an optional embodiment, monitoring the connection states of other servers in the server cluster, and updating the server list corresponding to the connection states according to the monitored connection states includes:
a11, sending ping requests to other servers in the server cluster according to a preset heartbeat cycle;
a12, if no ping request response returned by the server is received within the preset heartbeat detection time threshold, deleting the server which does not return the ping request response from the server list to obtain an updated server list;
in this embodiment, as an optional embodiment, the number of times of sending ping requests may be increased to more accurately determine whether the network is abnormal or not, and therefore, before deleting a server that does not return a ping request response from the server list after the ping request response returned by the server is not received within the preset heartbeat detection time threshold, the method further includes:
and sequentially sending ping requests to servers which do not return ping request responses, and if the number of times of not receiving ping request responses within a preset heartbeat detection time threshold reaches a preset heartbeat detection number threshold, executing the step of deleting the servers which do not return ping request responses from the server list.
In this embodiment, after sending a ping request to other servers in the server cluster according to a preset heartbeat cycle, if a ping request response returned by a server is received within a preset heartbeat detection time threshold value; or receiving a ping request response before the heartbeat detection time threshold value, not processing, and continuously waiting for the next heartbeat cycle.
A13, pushing the update server list to each server included in the update server list.
In this embodiment, through the ping request check, if a ping request exceeding a preset threshold number of heartbeat detection times fails (no ping request response is received), for example, if more than five consecutive ping requests fail, the master server removes the server for which the ping request failed, and notifies (broadcasts) other servers in the server cluster to update the server list; or directly notifying the updated server list obtained by processing to each connected server.
In this embodiment, through a health check policy among servers, resources available in a server cluster are managed, and resource allocation is performed, for example, by checking the health state and performance parameters of each server in the server cluster, when a certain main server is abnormal, the abnormal server can be moved out of the server cluster, and a user accessing the main server is switched to another normally operating main server; when the congestion state is caused by too many times of accessing a certain server, the rest access requests can be automatically switched to the server in an idle state, and the maximum resource utilization can be realized, so that the reasonable utilization of a CPU (central processing unit), a memory and network resources and the convenience of performance expansion are realized.
Fig. 2 is a schematic flow chart of a method for managing a server cluster according to a second embodiment of the present invention, and as shown in fig. 2, each server in the server cluster is referred to as a node, and the method according to this embodiment may include:
step 201, starting a local node;
step 202, judging whether the self is a main node, if so, executing step 203, and if not, executing step 211;
step 203, starting a monitoring process;
step 204, sending ping requests to other servers according to a preset heartbeat cycle, judging whether the servers are connected or not, if so, waiting for the next heartbeat cycle, if not, confirming the disconnection, and executing step 205;
step 205, retrying the ping request five times, judging whether the ping request is communicated, if so, waiting for the next heartbeat cycle, if not, confirming the disconnection, and executing step 206;
step 206, deleting the information of the disconnected server from the server list, packaging the information of the disconnected server into a node updating message, and broadcasting in the server cluster;
step 207, the online nodes in the server cluster receive the node update message and update the locally maintained server list;
step 211, sending ping request to main node to request registration, judging whether to connect, if not, confirming to drop line, executing step 212, if yes, executing step 213;
in this embodiment, as an optional embodiment, the join request is a ping request.
Step 212, retrying the ping request for five times, judging whether the ping request is communicated, if so, executing step 213, otherwise, confirming the disconnection, and ending the process;
step 213, registering with the master node;
step 214, receiving a server list returned by the master node;
step 215, calling between nodes, judging whether the calling is normal, if so, executing step 216, and if not, executing step 217;
step 216, executing node calling;
step 217, retrying the node call five times, judging whether the node call is normal or not, if so, executing step 216, otherwise, confirming the abnormality, and executing step 218;
step 218, notify the master node of the anomalous node information.
In this embodiment, after receiving the abnormal node information, the master node broadcasts the abnormal node information in the server cluster.
Fig. 3 is a schematic structural diagram of a device for managing a server cluster according to a third embodiment of the present invention, and as shown in fig. 3, the device according to this embodiment may include: a synchronization module 31, a detection module 32, and a process monitoring module 33, wherein,
the synchronization module 31 is configured to, after triggering and starting a server based on a distributed push policy, synchronize a local database of the started server based on the distributed push policy;
in this embodiment, as an optional embodiment, the synchronization module 31 includes: a start-up unit, a connection unit and a synchronization unit (not shown in the figure), wherein,
the starting unit is used for informing the linking unit after triggering and starting the server based on the distributed push strategy;
the connection unit is used for constructing TCP long connections with other running servers in the server cluster except the started server based on the distributed push strategy;
and the synchronization unit is used for receiving the database updating message in the server cluster through the TCP long connection and updating a local database according to the database updating message.
In this embodiment, as an optional embodiment, the database is located locally in the server, a distributed database is constructed by multiple servers in a TCP long connection manner, and each database stores the same data backup.
In this embodiment, as another optional embodiment, the synchronization module 31 further includes: a judging unit and a registering unit, wherein,
the judging unit is used for receiving the notification of the starting unit and judging whether the server cluster is registered or not, and if so, the connecting unit is notified; if not, notifying a registration unit;
and the registration unit is used for sending a joining request to any main server in the server cluster, and notifying the connection unit if the joining request passes the authentication.
In this embodiment, as an optional embodiment, the sending a join request to any main server in the server cluster, if the join request passes authentication, includes:
the main server receives the joining request, after the authentication of the joining request is passed, the server information sending the joining request is added to a server list in a local database, the server list adding the server information is carried in the joining request, the joining request is returned to the server sending the joining request, the server information sending the joining request is packaged into database updating information, and the database updating information is broadcasted in the server cluster.
In this embodiment, when another server is ready to join the server cluster, a join request, for example, a ping request, may be sent to any master server, and after the master server passes authentication, the master server agrees to join the server, returns a ping request response to the server, and carries an updated server list in the ping request response, and simultaneously, notifies the newly joined server information, for example, the address information of the newly joined server to the other servers already joined in the server cluster, or broadcasts the address information of the newly joined server in the server cluster.
In this embodiment, as an optional embodiment, the local database is a MySQL database, and is used to store shared resources of the server cluster, and provide services to the outside when the server is a main server. Among them, shared resources include but are not limited to: server address information, name of service provided, name of module registered to global by local server, name of global method, global list data and service data.
A detection module 32, configured to detect whether the started server based on the distributed pushing policy is a master server in a server cluster to which the server belongs, and if the started server based on the distributed pushing policy is the master server, provide a service to the outside through the synchronized local database, where multiple master servers are started in the server cluster;
in this embodiment, as an optional embodiment, the detection module 32 is further configured to synchronize the local database from the master server that operates normally according to a preset update period if it is detected that the detection module itself is a slave server in the server cluster to which the detection module itself belongs, and select a slave server by using a preset election policy after it is detected that the master server is abnormal, instead of the master server that is abnormal.
In this embodiment, as an optional embodiment, the detecting module 32 includes: a detection unit, and a service providing unit (not shown), wherein,
the detection unit is used for detecting whether the server is a main server in the server cluster according to the server list in the synchronized local database;
in this embodiment, information on whether the server is the master server is preset in the server list in the local database, and thus, by reading the server list in the local database, it can be determined whether the server is the master server in the server cluster to which the server belongs.
And the service providing unit is used for providing services to the outside through the local database after the detection unit detects that the server is the main server.
A process monitoring module 33, configured to start a monitoring process preset in the started server based on the distributed push policy, monitor connection states of other servers in the server cluster except the started server based on the distributed push policy, and update a server list corresponding to the connection state according to the connection state obtained through monitoring.
In this embodiment, as an optional embodiment, the process monitoring module 33 includes: a monitor process starting unit, a heartbeat detecting unit, a heartbeat processing unit and an update pushing unit (not shown in the figure), wherein,
the monitoring process starting unit is used for starting a preset monitoring process;
the heartbeat detection unit is used for sending ping requests to other servers in the server cluster according to a preset heartbeat period;
the heartbeat processing unit deletes the server which does not return the ping request response from the server list to obtain an updated server list if the server does not receive the ping request response returned by the server within the preset heartbeat detection time threshold;
in this embodiment, as an optional embodiment, the heartbeat processing unit is further configured to sequentially send ping requests to servers that do not return ping request responses after receiving no ping request response returned by the server within a preset heartbeat detection time threshold, and delete a server that does not return ping request responses from the server list if the number of times that no ping request response is received within the preset heartbeat detection time threshold reaches a preset heartbeat detection number threshold.
And the update pushing unit is used for pushing the update server list to each server contained in the update server list.
In this embodiment, through the ping request check, if a ping request exceeding a preset threshold number of heartbeat detection times fails (no ping request response is received), for example, if more than five consecutive ping requests fail, the master server removes the server for which the ping request failed, and notifies (broadcasts) other servers in the server cluster to update the server list; or directly notifying the updated server list obtained by processing to each connected server.
The apparatus of this embodiment may be used to implement the technical solutions of the method embodiments shown in fig. 1 and fig. 2, and the implementation principles and technical effects are similar, which are not described herein again.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments.
In particular, as for the apparatus embodiment, since it is substantially similar to the method embodiment, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof.
In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
For convenience of description, the above devices are described separately in terms of functional division into various units/modules. Of course, the functionality of the units/modules may be implemented in one or more software and/or hardware implementations of the invention.
From the above description of the embodiments, it is clear to those skilled in the art that the present invention can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which may be stored in a storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments or some parts of the embodiments.
The above description is only for the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A method of managing a server cluster, comprising:
after triggering and starting a server based on a distributed pushing strategy, synchronously starting a local database of the server based on the distributed pushing strategy;
detecting whether the started server based on the distributed pushing strategy is a main server in a server cluster, if the started server based on the distributed pushing strategy is the main server, providing service to the outside through the synchronous local database, wherein a plurality of main servers are started in the server cluster;
starting a monitoring process preset in the started server based on the distributed pushing strategy, monitoring the connection state of other servers in the server cluster except the started server based on the distributed pushing strategy, and updating a server list corresponding to the connection state according to the monitored connection state.
2. The method for managing a server cluster according to claim 1, wherein the synchronizing the initiated local database of the distributed push policy based server comprises:
establishing TCP long connections with other running servers in the server cluster except the started server based on the distributed push strategy;
and receiving a database updating message in the server cluster through the TCP long connection, and updating a local database according to the database updating message.
3. The method of claim 1, wherein after triggering the launching of the distributed push policy based server, prior to synchronizing the local database of the launched distributed push policy based server, the method further comprises:
judging whether the server cluster is registered, if so, executing the synchronous started local database of the server based on the distributed push strategy; if not, sending a joining request to any main server in the server cluster, and if the joining request passes the authentication, executing the step of synchronously starting the local database of the server based on the distributed push strategy.
4. The method for managing a server cluster according to claim 3, wherein the sending a join request to any master server in the server cluster, if the join request is authenticated, comprises:
the main server receives the joining request, after the authentication of the joining request is passed, the server information sending the joining request is added to a server list in a local database, the server list adding the server information is carried in the joining request, the joining request is returned to the server sending the joining request, the server information sending the joining request is packaged into database updating information, and the database updating information is broadcasted in the server cluster.
5. The method according to any of claims 1 to 4, wherein the detecting whether the server is a master server in the server cluster comprises:
and detecting whether the server is a main server in the server cluster according to the server list in the synchronized local database.
6. The method for managing a server cluster according to any one of claims 1 to 4, wherein the monitoring the connection states of other servers in the server cluster, and updating the server list corresponding to the connection state according to the monitored connection state includes:
sending ping requests to other servers in the server cluster according to a preset heartbeat cycle;
if the ping request response returned by the server is not received within the preset heartbeat detection time threshold, deleting the server which does not return the ping request response from the server list to obtain an updated server list;
and pushing the updated server list to each server contained in the updated server list.
7. The method for managing a server cluster according to claim 6, wherein before deleting the server which does not return the ping request response from the server list after the ping request response returned by the server is not received within the preset heartbeat detection time threshold, the method further comprises:
and sequentially sending ping requests to servers which do not return ping request responses, and if the number of times of not receiving ping request responses within a preset heartbeat detection time threshold reaches a preset heartbeat detection number threshold, executing the step of deleting the servers which do not return ping request responses from the server list.
8. The method of managing a server cluster according to any of claims 1 to 4, characterized in that the method further comprises:
if the slave server is detected to be a slave server in the server cluster, synchronizing the local database from the master server which normally operates according to a preset updating period, and electing a slave server by using a preset election strategy to replace the master server which generates the abnormity after the master server is monitored to generate the abnormity.
9. An apparatus for managing a server cluster, comprising: a synchronization module, a detection module, and a process monitoring module, wherein,
the synchronization module is used for synchronizing the started local database of the server based on the distributed pushing strategy after triggering the starting of the server based on the distributed pushing strategy;
the detection module is used for detecting whether the started server based on the distributed pushing strategy is a main server in a server cluster, if the started server based on the distributed pushing strategy is the main server, the service is provided to the outside through the synchronous local database, and a plurality of main servers are started in the server cluster;
and the process monitoring module is used for starting a preset monitoring process in the started server based on the distributed pushing strategy, monitoring the connection state of other servers in the server cluster except the started server based on the distributed pushing strategy, and updating a server list corresponding to the connection state according to the monitored connection state.
10. The apparatus for managing a server cluster of claim 9, wherein the synchronization module comprises: a start unit, a connection unit and a synchronization unit, wherein,
the starting unit is used for informing the linking unit after triggering and starting the server based on the distributed push strategy;
the connection unit is used for constructing TCP long connections with other running servers in the server cluster except the started server based on the distributed push strategy;
and the synchronization unit is used for receiving the database updating message in the server cluster through the TCP long connection and updating a local database according to the database updating message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710520921.4A CN109218349A (en) | 2017-06-29 | 2017-06-29 | A kind of method and device of management server cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710520921.4A CN109218349A (en) | 2017-06-29 | 2017-06-29 | A kind of method and device of management server cluster |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109218349A true CN109218349A (en) | 2019-01-15 |
Family
ID=64976703
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710520921.4A Pending CN109218349A (en) | 2017-06-29 | 2017-06-29 | A kind of method and device of management server cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109218349A (en) |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110336884A (en) * | 2019-07-09 | 2019-10-15 | 西安点告网络科技有限公司 | Server cluster update method and device |
| CN111211989A (en) * | 2019-12-24 | 2020-05-29 | 浙江云诺通信科技有限公司 | CDN quality analysis method based on broadband television |
| CN111221557A (en) * | 2020-01-15 | 2020-06-02 | 苏州浪潮智能科技有限公司 | A method and device for batch refreshing server BMC |
| CN111555931A (en) * | 2020-04-23 | 2020-08-18 | 北京奇艺世纪科技有限公司 | Upstream server monitoring processing method, monitor and electronic equipment |
| CN111831455A (en) * | 2020-07-02 | 2020-10-27 | 上海微亿智造科技有限公司 | Distributed transaction processing system and method under industrial Internet of things |
| CN112068939A (en) * | 2020-08-24 | 2020-12-11 | 浙江知水信息技术有限公司 | Method and system for scheduling multiple early warning services |
| CN112564932A (en) * | 2019-09-26 | 2021-03-26 | 北京比特大陆科技有限公司 | Target server offline notification method and device |
| CN112769889A (en) * | 2020-11-18 | 2021-05-07 | 青岛海尔科技有限公司 | Service data pushing method and device, storage medium and electronic device |
| CN113220485A (en) * | 2021-05-25 | 2021-08-06 | 金蝶软件（中国）有限公司 | Processing method and device for remote procedure call service and readable storage medium |
| CN113391759A (en) * | 2020-03-13 | 2021-09-14 | 华为技术有限公司 | Communication method and device |
| CN113407403A (en) * | 2020-03-16 | 2021-09-17 | 顺丰科技有限公司 | Cloud host management method and device, computer equipment and storage medium |
| CN114039976A (en) * | 2021-10-29 | 2022-02-11 | 深圳市科思科技股份有限公司 | Server cluster master-slave machine management method and system |
| WO2022095678A1 (en) * | 2020-11-04 | 2022-05-12 | 华云数据控股集团有限公司 | Message push method and message service system |
| CN115202882A (en) * | 2022-07-26 | 2022-10-18 | 上海中汇亿达金融信息技术有限公司 | Distributed application architecture and execution method of the architecture |
| CN116233137A (en) * | 2023-02-17 | 2023-06-06 | 通明智云(北京)科技有限公司 | Cluster-based load sharing and backup method and device |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101690136A (en) * | 2007-06-26 | 2010-03-31 | 汤姆逊许可证公司 | Real-time protocol stream migration |
| CN103795572A (en) * | 2014-01-24 | 2014-05-14 | 北京京东尚科信息技术有限公司 | Method for switching master server and slave server and monitoring server |
| CN104468777A (en) * | 2014-12-05 | 2015-03-25 | 北京奇虎科技有限公司 | Data operating method and device |
| US9223877B1 (en) * | 2007-03-30 | 2015-12-29 | Google Inc. | Index server architecture using tiered and sharded phrase posting lists |
| EP2919130A4 (en) * | 2012-12-28 | 2015-12-30 | Huawei Tech Co Ltd | Method and system for synchronizing distributed database |
| CN105429799A (en) * | 2015-11-30 | 2016-03-23 | 浙江宇视科技有限公司 | Server backup method and device |
| CN105721200A (en) * | 2016-01-21 | 2016-06-29 | 北京乐动卓越科技有限公司 | Master-slave server system application method and system thereof |
-
2017
- 2017-06-29 CN CN201710520921.4A patent/CN109218349A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9223877B1 (en) * | 2007-03-30 | 2015-12-29 | Google Inc. | Index server architecture using tiered and sharded phrase posting lists |
| CN101690136A (en) * | 2007-06-26 | 2010-03-31 | 汤姆逊许可证公司 | Real-time protocol stream migration |
| EP2919130A4 (en) * | 2012-12-28 | 2015-12-30 | Huawei Tech Co Ltd | Method and system for synchronizing distributed database |
| CN103795572A (en) * | 2014-01-24 | 2014-05-14 | 北京京东尚科信息技术有限公司 | Method for switching master server and slave server and monitoring server |
| CN104468777A (en) * | 2014-12-05 | 2015-03-25 | 北京奇虎科技有限公司 | Data operating method and device |
| CN105429799A (en) * | 2015-11-30 | 2016-03-23 | 浙江宇视科技有限公司 | Server backup method and device |
| CN105721200A (en) * | 2016-01-21 | 2016-06-29 | 北京乐动卓越科技有限公司 | Master-slave server system application method and system thereof |
Cited By (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110336884B (en) * | 2019-07-09 | 2022-03-29 | 西安点告网络科技有限公司 | Server cluster updating method and device |
| CN110336884A (en) * | 2019-07-09 | 2019-10-15 | 西安点告网络科技有限公司 | Server cluster update method and device |
| CN112564932A (en) * | 2019-09-26 | 2021-03-26 | 北京比特大陆科技有限公司 | Target server offline notification method and device |
| CN111211989A (en) * | 2019-12-24 | 2020-05-29 | 浙江云诺通信科技有限公司 | CDN quality analysis method based on broadband television |
| CN111211989B (en) * | 2019-12-24 | 2023-04-07 | 浙江云诺通信科技有限公司 | CDN quality analysis method based on broadband television |
| CN111221557A (en) * | 2020-01-15 | 2020-06-02 | 苏州浪潮智能科技有限公司 | A method and device for batch refreshing server BMC |
| CN113391759A (en) * | 2020-03-13 | 2021-09-14 | 华为技术有限公司 | Communication method and device |
| CN113391759B (en) * | 2020-03-13 | 2024-04-09 | 华为云计算技术有限公司 | Communication method and equipment |
| CN113407403A (en) * | 2020-03-16 | 2021-09-17 | 顺丰科技有限公司 | Cloud host management method and device, computer equipment and storage medium |
| CN113407403B (en) * | 2020-03-16 | 2023-04-25 | 顺丰科技有限公司 | Cloud host management method and device, computer equipment and storage medium |
| CN111555931A (en) * | 2020-04-23 | 2020-08-18 | 北京奇艺世纪科技有限公司 | Upstream server monitoring processing method, monitor and electronic equipment |
| CN111831455A (en) * | 2020-07-02 | 2020-10-27 | 上海微亿智造科技有限公司 | Distributed transaction processing system and method under industrial Internet of things |
| CN112068939A (en) * | 2020-08-24 | 2020-12-11 | 浙江知水信息技术有限公司 | Method and system for scheduling multiple early warning services |
| WO2022095678A1 (en) * | 2020-11-04 | 2022-05-12 | 华云数据控股集团有限公司 | Message push method and message service system |
| CN112769889A (en) * | 2020-11-18 | 2021-05-07 | 青岛海尔科技有限公司 | Service data pushing method and device, storage medium and electronic device |
| CN113220485A (en) * | 2021-05-25 | 2021-08-06 | 金蝶软件（中国）有限公司 | Processing method and device for remote procedure call service and readable storage medium |
| CN114039976A (en) * | 2021-10-29 | 2022-02-11 | 深圳市科思科技股份有限公司 | Server cluster master-slave machine management method and system |
| CN114039976B (en) * | 2021-10-29 | 2024-01-09 | 深圳市科思科技股份有限公司 | Master-slave management method and system for server cluster |
| CN115202882A (en) * | 2022-07-26 | 2022-10-18 | 上海中汇亿达金融信息技术有限公司 | Distributed application architecture and execution method of the architecture |
| CN115202882B (en) * | 2022-07-26 | 2023-11-03 | 上海中汇亿达金融信息技术有限公司 | Distributed application architecture and execution method thereof |
| CN116233137A (en) * | 2023-02-17 | 2023-06-06 | 通明智云(北京)科技有限公司 | Cluster-based load sharing and backup method and device |
| CN116233137B (en) * | 2023-02-17 | 2023-11-17 | 通明智云(北京)科技有限公司 | Cluster-based load sharing and backup method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109218349A (en) | A kind of method and device of management server cluster | |
| US10764369B2 (en) | Data storage method and server applicable to distributed server cluster | |
| CN109542865B (en) | Distributed cluster system configuration file synchronization method, device, system and medium | |
| CN106817387B (en) | Data synchronization method, device and system | |
| CN103117901B (en) | A kind of distributed heartbeat detection method, Apparatus and system | |
| CN100426751C (en) | Method for ensuring accordant configuration information in cluster system | |
| WO2014166265A1 (en) | Method, terminal, cache server and system for updating webpage data | |
| CN103383689A (en) | Service process fault detection method, device and service node | |
| CN113055461B (en) | ZooKeeper-based unmanned cluster distributed cooperative command control method | |
| CN102394914A (en) | Cluster brain-split processing method and device | |
| CN103581276A (en) | Cluster management device and system, service client side and corresponding method | |
| CN102143194A (en) | Data synchronization method and system, immediate data node and terminal data node | |
| CN103036719A (en) | Cross-regional service disaster method and device based on main cluster servers | |
| CN101262369B (en) | Master/slave realization method for dispatching server and dispatching server | |
| US20140310372A1 (en) | Method, terminal, cache server and system for updating webpage data | |
| CN115277379B (en) | Distributed lock disaster recovery processing method and device, electronic equipment and storage medium | |
| CN105610947A (en) | Method, device and system for realizing high-available distributed queue service | |
| JP6434021B2 (en) | Manage data feeds | |
| CN114900449A (en) | Resource information management method, system and device | |
| CN107526652A (en) | A kind of method of data synchronization and storage device | |
| CN109344202B (en) | Data synchronization method and management node | |
| CN112260946A (en) | Link fault processing method and device, terminal equipment and storage medium | |
| CN109005246B (en) | A data synchronization method, device and system | |
| CN111092956A (en) | Resource synchronization method, device, storage medium and equipment | |
| CN110716981A (en) | A method and device for realizing data order synchronization |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190115 |