CN100426751C - Method for ensuring accordant configuration information in cluster system - Google Patents

Abstract

The invention provides a method for ensuring consistency of configuration information in a cluster system, including: a cluster resource backup management module monitors the working conditions of each node server in the cluster system; when the application program information in the node server changes, update the cluster The configuration information stored in the resource backup management module updates the token information in the cluster resource backup management module, and the token information is used to identify the update status of the configuration information; after the cluster resource management module restarts, according to the command The license information updates the configuration information in the cluster resource management module or the cluster resource backup management module. The method provided by the invention effectively ensures the consistency of the configuration information on each node server in the cluster system, improves the survivability and recoverability of the configuration information in a disaster situation, and enhances the reliability of the cluster system.

Description

A method to ensure consistent configuration information in a cluster system

technical field

The invention relates to a computer cluster technology, in particular to a method for ensuring consistency of configuration information in a cluster system.

Background technique

Cluster (Cluster) technology is to manage a group of mutually independent servers as a single system mode in the network to achieve high availability, manageability and superior scalability, to achieve parallel processing of services and load balancing functions , and the fault tolerance and disaster recovery functions of the system. A cluster is a loosely coupled collection of computer nodes. Through the Cluster Administrator (Cluster Administrator): a graphical administrator tool through which maintenance, monitoring, and failover management can be performed, cluster entities (such as nodes, resources, resource groups) and management of the cluster itself. A cluster includes multiple (at least two) servers with shared data storage space. When any server runs an application, the application data is stored in the shared data space, and the operating system and application files of each server are stored in In their respective local storage spaces, each node server in the cluster communicates with each other through an internal local area network. When a node server fails, the applications running on this server will be automatically taken over on another node server. When an application service fails, the application service will be restarted or taken over by another server. FIG. 1 is a schematic diagram of a network structure of a cluster system including two servers with shared data storage space. The main machine and the standby machine back up each other. Normally, the main machine provides application services. When the main machine fails to provide application services normally, the standby machine takes over the work of the main machine. This is called active/standby (active/backup) mode; Part of the process of the program runs on the main machine, and another part of the process runs on the standby machine. When the main machine fails and cannot provide application services normally, the standby machine takes over the work of the main machine, and vice versa. This is called active/active (active/active) model.

In the prior art, no matter in the active/standby or active/active working mode, the main machine and the standby machine are a single individual, and all configuration information is stored separately on each machine, so there are the following defects and deficiencies :

When the configuration information on the A-node server is updated, the configuration information on the B-node server as the backup of the A-node server cannot be updated in time, and the synchronization and consistency of the configuration information cannot be guaranteed. In this way, when providing application services When the A-node server fails, the B-node server cannot correctly take over the service on the A-node server due to the lag of configuration information, and the reliability is low, which brings losses to users.

Contents of the invention

The technical problem to be solved by the present invention is to provide a cluster system and a method for ensuring consistent configuration information in the cluster system in view of the defects and deficiencies in the existing cluster system, so as to ensure the synchronization of configuration information on each node server in the cluster system Consistency and consistency, improve the reliability of the cluster system.

A method for ensuring consistent configuration information in the cluster system of the present invention, the following steps are performed:

Step 1, cluster resource backup management module (Watchman Cluster Server Back, WMCSB) monitors the working conditions of each node server in the cluster system;

Step 2. When the application program information in the node server changes, update the configuration information stored in the cluster resource backup management module, update the token information in the cluster resource backup management module, and the token information is used to identify Updates to configuration information;

Step 3, after the cluster resource management module restarts, update the configuration information in the cluster resource management module (Watchman Cluster Server, WMCS) or the cluster resource backup management module according to the token information.

In the above technical solution, the following operations are performed before the step 1: Token information with the same initial information is respectively set in the cluster resource management module and the cluster resource backup management module, and the token information includes token group identification information and token Update information.

Updating the token update information in the step 2 is to update the token number information, and the size of the token number identifies the update status of the configuration information.

The step 3 includes: step 301, after the cluster resource management module is restarted, establish a connection with the cluster resource backup management module, and obtain token information with the cluster resource backup management module; step 302, the cluster resource management module and The cluster resource backup management module compares whether the token number in the received token information is equal to the token number in the token information saved by itself, if they are equal, execute step 303; otherwise, execute step 305; step 303, Send an alarm message to the management tool; step 304, the user formulates a data source and uses the data source to update the configuration information in the cluster resource management module and the cluster resource backup management module, and then executes step 306; step 305, according to For preset parameters, the cluster resource management module or cluster resource backup management module with a large or small token number updates the configuration information of the other party; step 306, end.

Wherein, between step 301 and step 302 includes: the cluster resource management module and the cluster resource backup management module analyze the token group identification information in the received token information, and determine the token group identification information Whether the token group identifier in is equal to the token group identifier in the token information saved by itself, if yes, execute step 302 accordingly; otherwise, execute step 306. Updating the configuration information of the other party in step 305 includes: the cluster resource management module or the cluster resource backup management module sending configuration information and update request information to the other party; the cluster resource backup management module or the cluster resource The management module uses the received configuration information to update the configuration information saved by itself.

In addition, updating the token update information in step 2 is updating the token update time information. Correspondingly, the step 3 includes: step 311, after the cluster resource management module is restarted, establish a connection with the cluster resource backup management module, and obtain token information with the cluster resource backup management module; step 312, the cluster resource backup management module The management module compares with the cluster resource backup management module whether the token update time in the received token information is equal to the token update time in the token information saved by itself, or whether the difference between the two is less than the preset The specified value, if yes, execute step 313; otherwise, execute step 315; step 313, send an alarm message to the management tool; step 314, the user formulates a data source and uses the data source to monitor the cluster resource management module and the cluster resource The configuration information in the backup management module is updated, and then step 316 is executed; step 315, the cluster resource management module or the cluster resource backup management module whose token update time is late updates the other party's configuration information; step 316, end.

Between step 311 and step 312 includes: the cluster resource management module and the cluster resource backup management module analyze the token group identification information in the received token information, and determine the token group identification information in the token group identification information Whether the token group identifier is equal to the token group identifier in the token information saved by itself, if yes, then execute step 312 accordingly; otherwise, execute step 316.

At the same time, updating the token update information in the step 2 is updating the token number information and token update time information at the same time. Correspondingly, the step 3 includes:

Step 321, after the cluster resource management module is restarted, establish a connection with the cluster resource backup management module, and mutually obtain token information with the cluster resource backup management module; Step 322, the cluster resource management module and the cluster resource backup management module The module analyzes the weight information in the token information received, and judges whether to update the control right by the token number, if yes, execute step 323; otherwise, execute step 325; step 323, the cluster resource management module and the Cluster resource backup management module compares whether the token number in the received token information is equal to the token number in the token information saved by itself, if not equal, execute step 324; otherwise, execute step 327; step 324, according to Pre-set parameters, the cluster resource management module or cluster resource backup management module with a large or small token number updates the configuration information of the other party, and then performs step 329; step 325, the cluster resource management module and the cluster resource backup management module The cluster resource backup management module compares whether the token update time in the received token information is equal to the token update time in the token information it saves, or whether the difference between the two is less than a predetermined value, no , go to step 326; yes, go to step 327; step 326, the cluster resource management module or the cluster resource backup management module whose token update time is later update the configuration information of the other party, and then go to step 329; step 327, report to the management tool Send an alarm message; step 328, the user formulates a data source and uses the data source to update the configuration information in the cluster resource management module and the cluster resource backup management module;

Between step 321 and step 322 includes: the cluster resource management module and the cluster resource backup management module analyze the token group identification information in the token information received, and determine the token group identification information in the token group identification information Whether the token group identifier is equal to the token group identifier in the token information saved by itself, if yes, then execute step 322; otherwise, execute step 329.

In any one of the above methods, updating the configuration information stored in the cluster resource backup management module in the step 2 specifically includes: the cluster resource backup management module updates the cluster resource backup with the changed application update information Configuration information stored in the management module.

In addition, in any one of the above methods, the operation of updating the configuration information in the cluster management agent module (WatchmanCluster Agent, WMCA) is also included. The operation of updating the configuration information in the cluster management agent module is as follows:

When the cluster resource backup management module receives the connection request information sent by the cluster management agent module, it obtains the address information of the cluster management agent module from the connection request information, and extracts the address information from the configuration information stored in the cluster resource backup management module. Information corresponding to the address information, and using the corresponding information to update the configuration information in the cluster management agent module.

Based on the above technical solution, the present invention uses token information to maintain the consistency of configuration information in WMCS and WMCSB, thereby ensuring the consistency and automatic synchronization of configuration information in all WMCA, WMCS and WMCSB in the cluster system, and improving configuration information. Survivability and recoverability in disaster situations enhance system reliability.

The technical solutions of the present invention will be described in further detail below with reference to the accompanying drawings and embodiments.

Description of drawings

FIG. 1 is a schematic diagram of a network structure of a prior art cluster system;

Fig. 2 is a schematic diagram of the physical distribution of a cluster system implementing the method for ensuring consistent configuration information in the cluster system according to the present invention;

Fig. 3 is another schematic diagram of the physical distribution of the cluster system implementing the method for ensuring consistency of configuration information in the cluster system according to the present invention;

Fig. 4 is a flow chart of the method for ensuring consistent configuration information in the cluster system according to the present invention;

Fig. 5 is another flowchart of the method for ensuring consistent configuration information in the cluster system according to the present invention;

Fig. 6 is another flow chart of the method for ensuring consistent configuration information in the cluster system according to the present invention;

FIG. 7 is another flow chart of the method for ensuring consistency of configuration information in a cluster system according to the present invention.

Detailed ways

Since WMCA for managing the local resources on the node server is set on each node server in the cluster system, WMCS for managing the resources of the cluster system is set on one of the node servers, and WMCS is set on the other node server WMCSB that backs up and manages the resources of the cluster system. Under normal circumstances, the present invention manages the resources of the cluster system by WMCS. When the application program information on a node server in the cluster system changes, for example, a user adds a process, deletes a process, or modifies a process in a node server through WMCS. After obtaining the process attribute information, WMCS updates the WMCA on the node server and the configuration information in WMCSB. When WMCS fails, WMCSB replaces WMCS to manage the resources of all node servers in the cluster system. When WMCA restarts due to a fault and establishes a connection with WMCS, WMCS reconfigures the configuration information in WMCA to eliminate the difference in configuration information caused by WMCA being offline.

Referring to FIG. 2, FIG. 2 shows a schematic diagram of the physical distribution of a cluster system implementing the method for ensuring consistent configuration information in the cluster system according to the present invention. The cluster system includes n (n is an integer greater than 1) node servers (not shown in the figure) marked), each node server is respectively equipped with WMCA10, WMCA20, ... WMCAn0 (n is an integer greater than 1) which manages the resources on the node server where it is located, and the two node servers in it are, for example, node server 1 In node server 2, there are WMCS11 for managing resources on all node servers in the cluster, and WMCSB21, WMCS11 and WMCSB21 for backup management of resources on all node servers in the cluster when the cluster resource management module fails communicate with each other, and all communicate with WMCA10, WMCA20, ... WMCAn0. Under normal circumstances, the configuration information in the cluster system is stored in WMCS11, and WMCSB21 performs real-time synchronous backup of the configuration information in WMCS11. Specifically, WMCS11 and WMCSB21 and WMCS11, WMCSB21 and WMCA10, WMCA20, . . . WMCAn0 are connected through TCP/IP communication.

WMCA10, WMCA20, ...WMCAn0 have established connections with WMCS11 and WMCSB21, and WMCSB21 performs real-time synchronous backup of the configuration information in WMCS11, both of which have the same configuration information, so when WMCSB21 and WMCS11 When one of them fails, such as a communication failure caused by a physical failure such as a network card, the resource management of the cluster system can also be realized through the WMCSB21 or WMCS11 that has not failed; Both WMCS11 and WMCS11 are connected, and the probability of WMCSB21 and WMCS11 failure at the same time is very low. Therefore, when WMCA fails to recover, the configuration information can be updated in time by WMCSB21 or WMCS11, ensuring that WMCA10, WMCA20, ... The consistency and automatic synchronization of configuration information in WMCAn0, WMCS11, and WMCSB21 improves the security and reliability of the cluster system, and effectively avoids the configuration information differences between WMCS, WMCSB, and WMCA caused by node server failures.

Figure 3 is a schematic diagram of the physical distribution of another cluster system that implements the method for ensuring consistency of configuration information in the cluster system according to the present invention. On the basis of the cluster system shown in Figure 2, the cluster system also adds a visual management device (Cluster Administrator, CA)0, the CA0 is connected to WMCS11 and WMCSB21 respectively, and is used to manage WMCS11 and WMCSB21, especially when the configuration information of WMCS11 and WMCSB21 conflicts, WMCS11 and WMCSB21 can be managed through CA0, The safety and reliability of the cluster system and the maintenance efficiency of the cluster system are improved.

In order to clarify that the configuration information in WMCS11 or WMCSB21 is relatively new, the present invention sets token information with the same initial information in WMCS11 and WMCSB21, and the token information is used to identify the update of the configuration information of WMCS11 and WMCSB21 in the subsequent process Circumstances, including token group ID and token update information. Since the configuration information in WMCS 11 and WMCSB21 are the same at the same moment when the token information is set, the token information is the same; the token group ID identifies the cluster system, because WMCSB21 is used for the backup of WMCS11, therefore, WMCS11 and WMCSB21 It should belong to the same cluster system, and its token group ID is the same, and once set, it will not change due to the update of configuration information.

In addition, the token update information may be token number information, token update time information or a combination of the two. When the token update information is token number information, the update status of the configuration information is identified by the size of the token number, for example, the initial value of the token number is set to 0, when the configuration information in WMCS11 or WMCSB21 changes every time , then correspondingly add 1 to the token number in its token information, therefore, you can know whether the configuration information in WMCS11 or WMCSB21 is updated last through the size of the token number, that is, the configuration information is the latest, so that the token number is large The corresponding WMCS11 or WMCSB21 has the update control right to update the configuration information of the other party. Similarly, if the token update time information is used to represent the token update information, the token update time is later, that is, the value is larger, indicating that its configuration information is relatively new, and the corresponding WMCS11 or WMCSB21 has the control right to update the configuration information of the other party. If the token update information includes both token number information and token update time information, it is also necessary to set the token number or token update time to determine the weight information of the update control right in the token information, for example, the weight information can be 0 Or 1, when the weight information is 0, it means that the update control right is determined by the token number; when the weight information is 1, it means that the update control right is determined by the token update time.

Fig. 4 shows a specific process of the method for ensuring that the configuration information in the cluster system is consistent in the present invention, and it performs the following steps:

Step 1. When WMCS11 breaks down, WMCSB21 monitors the working condition of each node server in the cluster system.

Under normal circumstances, the resources of the cluster system are managed by WMCS11, there is a Socket (socket interface) connection between WMCSB21 and WMCS11, the configuration information in WMCS11 is synchronously backed up in real time, and the working conditions of WMCS11 are monitored.

Step 2. When the application program information on the node server in the cluster system changes, WMCSB21 uses the changed application program update information to update the configuration information stored on WMCSB21, and at the same time, update the token update information in the token information, for example , add 1 to the token number, or change the token update time to the time for updating the configuration information stored on WMCSB21. A change in the application program information on the node server may be a change in process information caused by adding or deleting a process on the node server, or a change in process attribute information. Step 3. After the failure of WMCS11 is eliminated and restarted, establish a Socket connection with WMCSB21, WMCS11 and WMCSB21 obtain each other’s token information, analyze the token update information, and decide to update the configuration information according to the token update information Who holds the control right? The WMCS11 or WMCSB21 that has obtained the update control right uses its own current configuration information to update the configuration information of the other party, so as to realize the synchronization of configuration information.

The control right to update the configuration information is determined by the token update information, and the old configuration information is replaced by the new configuration information, which ensures the real-time synchronization of the configuration information in WMCSB21 and WMCS11, thus improving the security and reliability of the cluster system and effectively avoiding the The configuration information difference between WMCS and WMCSB is caused by the failure of the node server.

In step 2 of the above embodiment, in addition, if the WMCA on the node server whose application program information changes is WMCAn0, WMCSB21 also uses the application program update information to update the configuration information of WMCAn0. The specific operation of updating the configuration information of WMCAn0 is as follows: WMCSB21 sends the application program update information to WMCAn0, and WMCAn0 uses the application program update information to update its configuration information.

When WMCA restarts due to a fault, it will establish a Socket connection with WMCS21. When WMCSB21 detects that WMCA establishes a Socket connection with it, it will obtain its address information. Configure information, and send the configuration information to WMCA, and reconfigure the configuration information on WMCA, effectively avoiding the difference between WMCA and WMCSB21 configuration information due to failure.

When the content of the token update information in the token information is different, the specific methods for updating the configuration information in WMCS11 and WMCSB21 will also be different. Fig. 5 is a flow chart of another embodiment of the method for ensuring consistent configuration information in the cluster system in the present invention when the token update information is token number information, step 1-step 2 in this embodiment are the same as those in Fig. 4 The shown embodiment is the same, and the operation of step 3 is:

Step 301, when the failure of MCS11 is eliminated, MCS11 establishes a Socket connection with WMCSB21, and then, WMCS11 and WMCSB21 send request information to each other to obtain the token information of the other party;

Step 302, WMCS11 and WMCSB21 analyze the token number information received at the same time, compare whether the token number in the information is equal to the token number in the token information saved by themselves, if yes, execute step 304; otherwise, execute Step 305;

Step 303, WMCS11 and WMCSB21 send alarm information to CA0;

Step 304, the user formulates a data source through CA0, uses the data source to update the configuration information in WMCS11 and WMCSB21, and then executes step 306;

When the update control of WMCS11 and WMCSB21 to the configuration information cannot be determined through the token information, an alarm message can be sent to the user, and the user can formulate the data source, and realize the enforcement of the configuration information in WMCS11 and WMCSB21 through intuitive and graphical management tools Updated to improve the maintenance efficiency of the cluster system.

Step 305, according to the preset parameters, the WMCS11 or WMCSB21 with a larger or smaller token number grasps the control right to update the configuration information, and sends the configuration information to the other party and uses the configuration information to update the configuration information of the receiving party Update instruction information, WMCSB21 or WMCS11 uses the received configuration information to update the configuration information saved by itself;

Step 306, end.

FIG. 6 is a flow chart of another embodiment of the method for ensuring consistent configuration information in the cluster system in the present invention when the token update information is token update time information. Step 1-step 2 in this embodiment are the same as those in FIG. The embodiment shown in 4 is the same, and the operation of step 3 is:

Step 311, when the fault of WMCS11 is eliminated, WMCS11 and WMCSB21 establish a Socket connection, after that, WMCS11 and WMCSB21 send request information to each other to obtain the token information of the other party;

Step 312, WMCS11 and WMCSB21 analyze the received token update time information at the same time, compare whether the token update time in the information is equal to the size of the token update time in the token update time information saved by itself, or both Whether the difference between the two is less than a predetermined value such as 1 minute, yes, execute step 313; otherwise, execute step 315;

Step 313, WMCS11 and WMCSB21 send alarm information to CA0;

Step 314, the user formulates a data source through CA0, uses the data source to update the configuration information in WMCS11 and WMCSB21, and then executes step 316;

Step 315, according to the preset parameters, the WMCS11 or WMCSB21 whose token update time is late, which means that the data at this time is large, grasps the update control right of the configuration information, and sends the configuration information to the other party and uses the configuration information to receive WMCSB21 or WMCS11 uses the received configuration information to update the configuration information saved by itself, and then executes step 316;

Step 316, end.

Fig. 7 is a flowchart of another embodiment of the method for ensuring consistency of configuration information in the cluster system according to the present invention when the token update information includes token number information and token update time information, step 1 in this embodiment -step 3 is the same as the embodiment shown in Figure 4, and the operation of step 3 is:

Step 321, when the failure of WMCS11 is eliminated, WMCS11 and WMCSB21 establish a Socket connection, after that, WMCS11 and WMCSB21 send request information to each other to obtain the token information of the other party;

Step 322, WMCS11 and WMCSB21 analyze the weight information in the received token update information at the same time, and judge whether the update control right is determined by the token number, if yes, go to step 323; otherwise, go to step 325. For example, if it is predetermined that the weight information is 1, the update control right is determined by the token number, and when the weight information is 0, the update control right is determined by the token update time, then WMCS11 and WMCSB21 need to judge whether the weight information is 1;

Step 323, WMCS11 and WMCSB21 further analyze the received token number information, compare whether the token number in the information is equal to the token number in the token information saved by themselves, if no, execute step 324; yes, execute Step 327;

Step 324: According to the preset parameters, the WMCS11 or WMCSB21 with a large or small token number controls the update control of the configuration information, and sends the configuration information to the other party and uses the configuration information to update the configuration information of the receiver To update the instruction information, WMCSB21 or WMCS11 uses the received configuration information to update the configuration information saved by itself, and then perform step 329;

Step 325, WMCS11 and WMCSB21 further analyze the token update time information received, and compare whether the token update time in the information is equal to the token update time in the token update time information saved by itself, or both Whether the difference between the two is less than a predetermined value such as 1 minute, no, execute step 326; yes, execute step 327;

Step 326, according to the preset parameters, the WMCS11 or WMCSB21 whose token update time is late, that is, the data at this time is large, grasps the update control right of the configuration information, and sends the configuration information to the other party and uses the configuration information to receive WMCSB21 or WMCS11 uses the received configuration information to update the configuration information saved by itself, and then executes step 329;

Step 327, WMCS11 and WMCSB21 send alarm information to CA0;

Step 328, the user formulates a data source through CA0, and uses the data source to update the configuration information in WMCS11 and WMCSB21;

Step 329, end.

In the above embodiments, the control right to update the configuration information is effectively determined through the token information, and the party that holds the control right to update the configuration information of the other party updates the configuration information, which further ensures the accuracy of updating the configuration information.

In addition, in order to ensure the accuracy of configuration information updates in the cluster system, before WMCS11 and WMCSB21 analyze the received token update information in the embodiments shown in FIGS. between steps 311 and 312, or between steps 321 and 322, it is also possible to first analyze whether the token group ID in the received token information is consistent with the token group ID in the token information saved by itself Similarly, the specific operations between step 301 and step 302 are:

WMCS11 and WMCSB21 analyze the token information received, and compare whether the token group ID in the information is the same as the token group ID in the token information saved by itself, if yes, then execute step 302 accordingly; otherwise, execute step 306. The operations between step 311 and step 312, and between step 321 and step 322 are the same and will not be repeated here.

It can be seen from the above embodiments that the present invention uses token information to maintain the consistency of configuration information in WMCS and WMCSB, thereby ensuring the consistency and automatic synchronization of configuration information in all WMCAs, WMCS and WMCSB in the cluster system, and improving configuration information. The survivability and recoverability of information in disaster situations enhance the reliability of the system.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention without limitation. Although the present invention has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that the technical solutions of the present invention can be The scheme shall be modified or equivalently replaced without departing from the spirit and scope of the technical scheme of the present invention.

Claims (15)

1. A method for ensuring consistent configuration information in a cluster system, characterized in that the following steps are performed: Step 1, the cluster resource backup management module monitors the working conditions of each node server in the cluster system; Step 2. When the application program information in the node server changes, update the configuration information stored in the cluster resource backup management module, update the token information in the cluster resource backup management module, and the token information is used to identify Updates to configuration information; Step 3: After the cluster resource management module is restarted, the configuration information in the cluster resource management module or the cluster resource backup management module is updated according to the token information. 2. The method according to claim 1, characterized in that, before the step 1, the following operations are performed: respectively setting token information with the same initial information in the cluster resource management module and the cluster resource backup management module, the token The information includes token group identification information and token update information. 3. The method according to claim 2, characterized in that updating the token update information in the step 2 is updating the token number information, and the size of the token number identifies the update of the configuration information Condition. 4. The method according to claim 3, characterized in that the step 3 comprises: Step 301, after the cluster resource management module is restarted, establish a connection with the cluster resource backup management module, and mutually obtain token information with the cluster resource backup management module; Step 302, the cluster resource management module compares with the cluster resource backup management module whether the token number in the received token information is equal to the token number in the token information saved by itself, and if they are equal, execute step 303 ; Otherwise, execute step 305; Step 303, sending an alarm message to the management tool; Step 304, the user formulates a data source and uses the data source to update the configuration information in the cluster resource management module and the cluster resource backup management module, and then executes step 306; Step 305, according to preset parameters, the cluster resource management module or the cluster resource backup management module with a large or small token number updates the configuration information of the other party; Step 306, end. 5. The method according to claim 4, further comprising: between step 301 and step 302: The cluster resource management module and the cluster resource backup management module analyze the token group identification information in the received token information, and judge whether the token group identification in the token group identification information is consistent with the If the token group identifiers in the card information are equal, if yes, execute step 302 accordingly; otherwise, execute step 306. 6. The method according to claim 4, wherein updating the configuration information of the other party in step 305 includes: The cluster resource management module or the cluster resource backup management module sends configuration information and update request information to the other party; The cluster resource backup management module or the cluster resource management module uses the received configuration information to update the configuration information saved by itself. 7. The method according to claim 1, characterized in that updating the token update information in the step 2 is updating the token update time information. 8. The method according to claim 7, wherein said step 3 comprises: Step 311, after the cluster resource management module is restarted, establish a connection with the cluster resource backup management module, and mutually obtain token information with the cluster resource backup management module; Step 312, the cluster resource management module compares with the cluster resource backup management module whether the token update time in the received token information is equal to the token update time in the token information saved by itself, or both Whether the difference between them is less than a predetermined value, if yes, go to step 313; otherwise, go to step 315; Step 313, sending an alarm message to the management tool; Step 314, the user formulates a data source and uses the data source to update the configuration information in the cluster resource management module and the cluster resource backup management module, and then executes step 316; Step 315, the cluster resource management module or the cluster resource backup management module whose token update time is late updates the other party's configuration information; Step 316, end. 9. The method according to claim 8, further comprising: between step 311 and step 312: The cluster resource management module and the cluster resource backup management module analyze the token group identification information in the received token information, and judge whether the token group identification in the token group identification information is consistent with the If the token group identifiers in the card information are equal, if yes, execute step 312 accordingly; otherwise, execute step 316. 10. The method according to claim 1, characterized in that updating the token update information in step 2 is updating the token number information and token update time information at the same time. 11. The method according to claim 10, characterized in that the step 3 comprises: Step 321, after the cluster resource management module is restarted, establish a connection with the cluster resource backup management module, and mutually obtain token information with the cluster resource backup management module; Step 322, the cluster resource management module and the cluster resource backup management module analyze the weight information in the received token information, and judge whether the token number determines whether to update the control right, if yes, execute step 323; otherwise, Execute step 325; Step 323: The cluster resource management module compares with the cluster resource backup management module whether the token number in the received token information is equal to the token number in the token information saved by itself, and if not, execute step 324; otherwise, execute step 327; Step 324: According to preset parameters, the cluster resource management module or cluster resource backup management module with a large or small token number updates the configuration information of the other party, and then executes Step 329; Step 325: The cluster resource management module compares with the cluster resource backup management module whether the token update time in the received token information is equal to the token update time in the token information saved by itself, or both Whether the difference between them is less than a predetermined value, no, execute step 326; yes, execute step 327; Step 326, the cluster resource management module or the cluster resource backup management module whose token update time is later updates the configuration information of the other party, and then executes step 329; Step 327, sending an alarm message to the management tool; Step 328, the user formulates a data source and uses the data source to update the configuration information in the cluster resource management module and the cluster resource backup management module; Step 329, end. 12. The method according to claim 11, further comprising: between step 321 and step 322: The cluster resource management module and the cluster resource backup management module analyze the token group identification information in the received token information, and judge whether the token group identification in the token group identification information is consistent with the If the token group identifiers in the card information are equal, if yes, execute step 322 accordingly; otherwise, execute step 329. 13. The method according to any one of claims 1 to 12, wherein updating the configuration information stored in the cluster resource backup management module in the step 2 is specifically: the cluster resource backup management module utilizes The changed application update information updates the configuration information stored in the cluster resource backup management module. 14. The method according to any one of claims 1 to 12, further comprising an operation of updating configuration information in the cluster management agent module. 15. The method according to claim 14, wherein the operation of updating the configuration information in the cluster management agent module is specifically: When the cluster resource backup management module receives the connection request information sent by the cluster management agent module, it obtains the address information of the cluster management agent module from the connection request information, and extracts the address information from the configuration information stored in the cluster resource backup management module. Information corresponding to the address information, and using the corresponding information to update the configuration information in the cluster management agent module.

Images