CN119166425A - Cooperative management method of multiple copies and related equipment - Google Patents

Abstract

The present application is about a collaborative management method and related equipment for multiple copies, which relates to the field of software technology and is used to unify the copy collaboration mode of different APPs and improve the collaborative management efficiency of multiple copies. The method includes: a first node receives a copy collaboration instruction sent by a scheduling node, and based on the copy collaboration instruction, sends a first modification instruction to at least one second node. Among them, the first node is a node in which a master copy of a target application is deployed among multiple service nodes, the scheduling node is used to manage the operating status of each service node in multiple service nodes, the copy collaboration instruction is used to instruct the synchronization of the target parameter value in the master copy of the target application to the slave copy of the target application, the second node is a node in which a slave copy of the target application is deployed among multiple service nodes, and the first modification instruction is used to instruct the modification of the corresponding parameter value in the slave copy of the target application to the target parameter value.

Description

Multi-copy collaborative management method and related equipment

Technical Field

The application relates to the technical field of software, in particular to a multi-copy collaborative management method and related equipment.

Background

Currently, in a distributed system, in order to improve the availability and redundancy of Application (APP) data, the same APP data may be stored on multiple nodes in a multi-copy cooperative manner, so as to prevent a single point of failure and provide a capability of data recovery when one node fails.

However, when multiple copies of APP data are cooperatively managed, different APPs may have different copy cooperation modes, which increases complexity of the multiple copies of the coordinated management. Therefore, how to unify the copy cooperation modes of different APP and improve the cooperation management efficiency of multiple copies becomes a technical problem to be solved.

Disclosure of Invention

The application provides a multi-copy collaborative management method and related equipment, which are used for unifying copy collaborative modes of different APP and improving the multi-copy collaborative management efficiency.

The technical scheme of the application is as follows:

In a first aspect, the application provides a multi-copy collaborative management method, which is applied to a first node, wherein the first node is a node with a main copy of a target application deployed in a plurality of service nodes, and the method comprises the steps of receiving a copy collaborative instruction sent by a scheduling node. Based on the duplicate cooperative instruction, a first modification instruction is sent to at least one second node. The scheduling node is used for managing the running state of each service node in the plurality of service nodes, the copy cooperative instruction is used for indicating that the target parameter value in the master copy of the target application is synchronized to the slave copy of the target application, the second node is a node where the slave copy of the target application is deployed in the plurality of service nodes, and the first modification instruction is used for indicating that the corresponding parameter value in the slave copy of the target application is modified to the target parameter value.

Optionally, the target parameter value is a copy parameter value corresponding to the first preset type in the primary copy of the target application, or the target parameter value is a copy parameter value different from the historical parameter value in the primary copy of the target application.

Optionally, the multi-copy collaborative management method further comprises the step of acquiring a target event of a main copy of the target application, wherein the target event is used for indicating to modify a copy parameter value of the target application. Based on the target event, a second modification instruction is sent to at least one second node, the second modification instruction being for instructing the slave copy of the target application to execute the target event. In the event that the slave copy of the target application completes the target event in the at least one second node, the target event is executed by the master copy of the target application.

Optionally, the multi-copy collaborative management method further comprises the step of responding to a preset collaborative policy and sending a first modification instruction to at least one second node. The preset collaborative strategy comprises at least one of the following steps that the modification times of the copy parameter values in the main copy of the target application are larger than a preset times threshold, the modified copy parameter values in the main copy of the target application are parameter values corresponding to a second preset type, and the current time is equal to any time in a preset period.

In a second aspect, the present application provides a multi-copy collaborative management method applied to a scheduling node, where the scheduling node is configured to manage an operation state of each service node in a plurality of service nodes, the method including sending a copy collaborative instruction to a first node. The first node is a node in which a master copy of the target application is deployed in a plurality of service nodes, and the copy cooperative instruction is used for indicating that a target parameter value in the master copy of the target application is synchronized to a slave copy of the target application.

Optionally, the target parameter value is a copy parameter value corresponding to the first preset type in the primary copy of the target application, or the target parameter value is a copy parameter value different from the historical parameter value in the primary copy of the target application.

Optionally, the plurality of service nodes includes at least one second node, the second node deployed with a slave copy of the target application, the first node and the at least one second node comprising a multiple copy deployment of the target application. The multi-copy collaborative management method further includes deploying a master copy of the target application in a third node, in response to identifying that the first node is in an abnormal state, the third node being any one of the plurality of service nodes that does not deploy a copy of the target application. And constructing a new multi-copy deployment of the target application by the third node and at least one second node.

Optionally, the first node is in an abnormal state, including at least one of:

the first node is in an abnormal operation state.

The operating environment of the target application in the first node is in an abnormal operating state.

The target application in the first node is in an abnormal running state.

Optionally, the third node is specifically a node that is not deployed with a copy of the target application among the plurality of service nodes and is in an idle state. The idle state comprises at least one of available resources of the central processing unit of the node being greater than a first preset threshold, memory resources of the node being greater than a second preset threshold, and memory resources of the node being greater than a third preset threshold.

Optionally, the multi-copy collaborative management method further comprises the step of acquiring state information of the first node. And sending the state information of the first node to a scheduling application deployed in the management node, wherein the scheduling application is used for determining whether the first node is in an abnormal state or not based on the state information of the first node. And receiving a scheduling instruction sent by a scheduling application in the management node, wherein the scheduling instruction comprises information for indicating that the first node is in an abnormal state.

Optionally, the scheduling instruction further comprises an identification of the third node.

In a third aspect, the present application provides a multi-copy collaborative management apparatus, which is applied to a first node, where the first node is a node where a primary copy of a target application is deployed in a plurality of service nodes. The device comprises a receiving module and a sending module.

And the receiving module is used for receiving the copy cooperative instruction sent by the scheduling node. And the sending module is used for sending the first modification instruction to at least one second node based on the copy cooperative instruction. The scheduling node is used for managing the running state of each service node in the plurality of service nodes, the copy cooperative instruction is used for indicating that the target parameter value in the master copy of the target application is synchronized to the slave copy of the target application, the second node is a node where the slave copy of the target application is deployed in the plurality of service nodes, and the first modification instruction is used for indicating that the corresponding parameter value in the slave copy of the target application is modified to the target parameter value.

Optionally, the target parameter value is a copy parameter value corresponding to the first preset type in the primary copy of the target application, or the target parameter value is a copy parameter value different from the historical parameter value in the primary copy of the target application.

Optionally, the multi-copy collaborative management apparatus may further include a processing module. The receiving module is further used for obtaining a target event of the main copy of the target application, wherein the target event is used for indicating to modify the copy parameter value of the target application. And the sending module is further used for sending a second modification instruction to at least one second node based on the target event, wherein the second modification instruction is used for indicating the slave copy of the target application to execute the target event. And the processing module is used for executing the target event through the master copy of the target application under the condition that the slave copy of the target application completes the target event in at least one second node.

Optionally, the sending module is further configured to send a first modification instruction to at least one second node in response to a preset cooperative policy. The preset collaborative strategy comprises at least one of the following steps that the modification times of the copy parameter values in the main copy of the target application are larger than a preset times threshold, the modified copy parameter values in the main copy of the target application are parameter values corresponding to a second preset type, and the current time is equal to any time in a preset period.

In a fourth aspect, the present application provides a multi-copy collaborative management apparatus, which is applied to a scheduling node, where the scheduling node is configured to manage an operation state of each service node in a plurality of service nodes. The device comprises a sending module.

And the sending module is used for sending the copy cooperative instruction to the first node. The first node is a node in which a master copy of the target application is deployed in a plurality of service nodes, and the copy cooperative instruction is used for indicating that a target parameter value in the master copy of the target application is synchronized to a slave copy of the target application.

Optionally, the target parameter value is a copy parameter value corresponding to the first preset type in the primary copy of the target application, or the target parameter value is a copy parameter value different from the historical parameter value in the primary copy of the target application.

Optionally, the plurality of service nodes includes at least one second node, the second node deployed with a slave copy of the target application, the first node and the at least one second node comprising a multiple copy deployment of the target application. The multi-copy collaborative management apparatus may further include a processing module. And the processing module is used for responding to the recognition that the first node is in an abnormal state, and deploying the main copy of the target application in a third node, wherein the third node is any node which is not deployed with the copy of the target application in a plurality of service nodes. And the processing module is also used for forming a new multi-copy deployment of the target application by the third node and at least one second node.

Optionally, the first node is in an abnormal state, including at least one of:

the first node is in an abnormal operation state.

The operating environment of the target application in the first node is in an abnormal operating state.

The target application in the first node is in an abnormal running state.

Optionally, the third node is specifically a node that is not deployed with a copy of the target application among the plurality of service nodes and is in an idle state. The idle state comprises at least one of available resources of the central processing unit of the node being greater than a first preset threshold, memory resources of the node being greater than a second preset threshold, and memory resources of the node being greater than a third preset threshold.

Optionally, the multi-copy collaborative management apparatus may further include an acquisition module. And the acquisition module is used for acquiring the state information of the first node. The sending module is further configured to send status information of the first node to a scheduling application deployed in the management node, where the scheduling application is configured to determine whether the first node is in an abnormal state based on the status information of the first node. The acquisition module is further used for receiving a scheduling instruction sent by the scheduling application in the management node, wherein the scheduling instruction comprises information for indicating that the first node is in an abnormal state.

Optionally, the scheduling instruction further comprises an identification of the third node.

In a fifth aspect, the present application provides a multi-copy collaborative management apparatus. The apparatus includes a processor, a memory, and a computer program. Wherein the computer program is stored on a memory, which when executed by a processor causes the apparatus to implement a collaborative management method as in any of the first or second aspects.

In a sixth aspect, the present application provides a computer readable storage medium comprising a computer program. The computer program, when executed by an electronic device, causes the electronic device to implement a collaborative management method as in any of the first or second aspects.

In a seventh aspect, the present application provides a computer program product comprising computer readable code, or a non-transitory computer readable storage medium carrying computer readable code, which when run in an electronic device, causes a processor in the electronic device to implement a method of collaborative management of multiple copies of any one of the first or second aspects.

In the above solutions, the technical problems and the technical effects that can be solved by the multi-copy collaborative management apparatus, the device, the computer storage medium, or the computer program product may be referred to the technical problems and the technical effects that can be solved by the first aspect or the second aspect, and are not described herein.

The technical scheme provided by the application has the advantages that the instruction management is carried out on the nodes participating in the multi-copy deployment through the unified upper node so as to realize multi-copy cooperation of the APP. Therefore, the method can be compatible with the copy cooperation requirements of different APP by a unified copy cooperation mode, and improves the cooperation management efficiency of multiple copies.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application as claimed.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application and do not constitute a undue limitation on the application.

Fig. 1 is a schematic diagram of a communication system according to an embodiment of the present application;

fig. 2 is a flow chart of a multi-copy collaborative management method according to an embodiment of the present application;

FIG. 3 is a schematic diagram of an example of consistency synchronization among three copies according to an embodiment of the present application;

FIG. 4 is a flowchart illustrating another multi-copy collaborative management method according to an embodiment of the present application;

FIG. 5 is a schematic illustration of an example of a multi-copy deployment of an application provided by an embodiment of the present application;

FIG. 6 is a schematic illustration of an example of a multi-copy deployment of another application provided by an embodiment of the present application;

fig. 7 is a schematic structural diagram of a multi-copy collaborative management apparatus according to an embodiment of the present application;

FIG. 8 is a schematic structural diagram of another multi-copy collaborative management apparatus according to an embodiment of the present application;

fig. 9 is a schematic hardware structure of a multi-copy collaborative management apparatus according to an embodiment of the present application.

Detailed Description

In order to enable a person skilled in the art to better understand the technical solutions of the present application, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented in sequences other than those illustrated or otherwise described herein. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.

It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, and/or components.

"And/or" is used to describe the association of the associated objects, meaning that three relationships may exist. For example, A and/or B may mean that A alone, both A and B, and B alone are present. The character "/" generally indicates that the context-dependent object is an "or" relationship.

Currently, in a distributed system, in order to improve the availability and redundancy of Application (APP) data, the same APP data may be stored on multiple nodes in a multi-copy cooperative manner, so as to prevent a single point of failure and provide a capability of data recovery when one node fails.

However, when multiple copies of APP data are cooperatively managed, different APPs may have different copy cooperation modes, which increases complexity of the multiple copies of the coordinated management.

That is, there is currently no system provided to automatically implement the APP with high reliability, which is achieved by the APP developer through complex logic and self-implemented coherency protocols. Therefore, the multi-copy implementation is a technology with higher requirements, so that the existing scheme has the defects of steep learning, higher requirements for developers and the like.

Therefore, how to unify the copy cooperation modes of different APP and improve the cooperation management efficiency of multiple copies becomes a technical problem to be solved.

In order to solve the problems, the embodiment of the application provides a multi-copy collaborative management method, which carries out instruction management on nodes participating in multi-copy deployment through a unified upper node so as to realize multi-copy collaborative of APP. Therefore, the method can be compatible with the copy cooperation requirements of different APP by a unified copy cooperation mode, and improves the cooperation management efficiency of multiple copies.

The following describes an implementation environment of an embodiment of the present application.

By way of example, as shown in FIG. 1, a communication system is provided for an embodiment of the present application, where the communication system may include a scheduling node 101 and a plurality of service nodes (e.g., service node 102, service node 103, service node 104, service node 105, service node 106, service node 107, and service node 108), and where the scheduling node 101 may be in wired or wireless communication with the service node 102, service node 103, service node 104, service node 105, service node 106, service node 107, and service node 108.

Wherein, service node 102, service node 103 and service node 104 are each deployed with a copy of application A, constituting three copies of application A. Service node 105 and service node 106 are each deployed with a copy of application B, constituting a two-copy deployment of application B. The service node 107 is deployed with an application C, which constitutes single-copy deployment of the application C, and the application C is a scheduling APP, and may query a change event (i.e., an event that a copy parameter changes in an update) in other service nodes through the scheduling node 101, and perform deployment control on multi-copy collaboration of the application through the scheduling node 101 based on a query result.

That is, the scheduling APP is a consistent scheduling policy extension APP, the scheduling policy can be implemented according to the service requirement, and the copy number can support 0 to n, and the larger n is, the higher the cost of synchronization is.

In an embodiment of the present application, the scheduling node 101 may comprise a scheduling module, and the scheduling module may also be a high availability deployment. Wherein, the functions of the scheduling module may include:

(1) Receiving a scheduling request (which APP is deployed, which data area is deployed, deployment according to several copies, etc.) of the client for the APP;

(2) Monitoring the state of the APP or the state of the operation module, and completing scheduling according to the scheduling strategy when the state change of the APP or the state of the operation module triggers the configured scheduling strategy;

(3) Receiving a query request of a client for a specific APP, and returning to the latest state of the APP;

(4) Receiving a subscription request of a client side for a specific APP, returning a subscription result, and publishing the subscription result to a subscriber when the state of the APP changes;

(5) Receiving a query request of a client for the state of a specific operation module, and returning to the latest state of the operation module;

(6) Receiving a subscription request of a client to a specific operation module, returning a subscription result, and publishing the subscription result to a subscriber when the state of the operation module changes;

it should be noted that, when the APP is deployed, not only a built-in scheduling policy may be used, but also the scheduling APP may be developed through a query or subscription function, so as to implement flexible expansion of the scheduling function.

In addition, service nodes (e.g., service node 102, service node 103, service node 104, service node 105, service node 106, service node 107, and service node 108) may include a status monitoring and control module, an execution module, a consistency synchronization and control module.

The state monitoring and controlling module is responsible for collecting the states of the running module and the APP running therein and reporting the state summary to the scheduling module. Also supported is the reception of active acquisition requests of the state of the dispatch module to complete the acquisition of the state of the running module and the APP running therein. And meanwhile, the method is responsible for executing the dispatching command of the dispatching module or sending the dispatching command to the operation module.

The operation module is an operation engine of the APP, can complete deployment operation of the APP according to the command of the scheduling module, provides a script method for state access and function call among the APPs, and completes automatic consistency synchronization or manual consistency synchronization of the APP states according to parameters configured by APP members. And responding to the request of the deployment sub of the APP to deploy the sub APP, and synchronizing the recursive call to complete the deployment operation of the whole APP tree.

The consistency synchronization and control module can realize parameter synchronization of application copies on different nodes, and the main functions comprise synchronization of consistency logs and control of consistency (election, consistency recovery and the like) according to a consistency protocol.

That is, the present application provides a system that automatically enables the deployment of APP multiple copies and consistency among the multiple copies through configuration. Therefore, by being compatible with the copy cooperation requirements of different APP, the complexity of developing the highly reliable APP is compared with that of the existing method, the development difficulty of the highly reliable APP can be remarkably reduced, the development efficiency of the APP is improved, and the cooperation management efficiency of multiple copies is improved. In addition, through centralized management of the industrial APP, the method and the system are respectively and independently executed, flexible expansion of a scheduling strategy can be supported, and deployment nodes of multiple copies of the application can be flexibly changed, so that abnormal states of part of the nodes are prevented from influencing deployment operation of the multiple copies of the application, and high-reliability deployment operation of the multiple copies of the application is ensured.

Optionally, in the embodiment of the present application, the number of the operation modules, the consistency synchronization modules and the control modules in the service node is not limited. For example, as in service node 108 of FIG. 1, multiple operational modules and multiple coherency synchronization and control modules may be included, with one operational module corresponding to one coherency synchronization and control module, while all operational modules in service node 108 are governed by one state monitoring and control module.

It should be noted that, in the embodiment of the present application, APP is an object of system operation and maintenance, and APP attributes may include a name, an Identity (ID), a member attribute, a function set, a sub APP set, and so on.

The member attributes may include name, whether volatile (volatile is not required to guarantee reliable status, non-volatile is required to be synchronized), whether automatic synchronization (configurable when Non-volatile, automatic real-time synchronization-guaranteed synchronization to other copies before modification, manual synchronization-APP logic calls a synchronization function to complete batch synchronization of status that was not synchronized in the period of time from the previous synchronization to the present period), type, value, and so on.

The function is a functional method and has a return value, a parameter list and a logic code.

It should be noted that the scheduling node and/or the service node may be a terminal or a server.

The server may be a single physical server or may be a server cluster formed by a plurality of servers. Or the server cluster may also be a distributed cluster. Or the server may also be a cloud server. The embodiment of the application does not limit the specific implementation mode of the server.

The terminal may be a mobile phone, a tablet computer, a desktop, a laptop, a handheld computer, a notebook, an ultra-mobile personal computer (UMPC), a netbook, or the like with a transceiver function, and the specific form of the terminal is not particularly limited in the present application. The system can perform man-machine interaction with a user through one or more modes of a keyboard, a touch pad, a touch screen, a remote controller, voice interaction or handwriting equipment and the like.

After the application scenario and the implementation environment of the embodiment of the present application are described, the multi-copy collaborative management method provided by the embodiment of the present application is described in detail below with reference to the implementation environment.

Fig. 2 is a flow chart of a multi-copy collaborative management method according to an embodiment of the present application. As shown in FIG. 2, the collaborative management method for multiple copies may include S201-S202.

S201, the first node receives a copy cooperative instruction sent by the scheduling node.

The first node is a node, in which a main copy of the target application is deployed, in a plurality of service nodes.

Illustratively, in conjunction with the above-described fig. 1, taking the target application as an application a as an example, in the three-copy deployment of the application a, if the service node 102 deploys a master copy of the application a, and the service node 103 and the service node 104 each deploy a slave copy of the application a, the service node 102 is the first node.

In the embodiment of the application, the scheduling node is used for managing the running state of each service node in the plurality of service nodes, and the copy cooperative instruction is used for indicating to synchronize the target parameter value in the master copy of the target application to the slave copy of the target application.

As a possible implementation manner, the first node may report, to the scheduling node, a target event in which a parameter change occurs in a primary copy of the target application, so that the scheduling node issues a copy collaboration instruction to the first node based on the target event reported by the first node, to implement multi-copy collaborative management on the target application.

Wherein the target event is used to indicate modification of the duplicate parameter value of the target application, the target event may include a parameter type of which the parameter change occurred. If the parameter type of the parameter change in the target event is a first preset type (namely a nonvolatile type), the scheduling node needs to issue a copy cooperative instruction to the first node so as to perform multi-copy cooperative management on the target application. If the parameter type of the parameter change in the target event is a third preset type (i.e. volatile type), the scheduling node does not need to perform multi-copy collaborative management on the target application.

As another possible implementation manner, the duplicate cooperative instruction is sent to the first node by the user through the scheduling node, so as to meet the requirement of the user on multi-duplicate cooperative management of the target application.

Illustratively, a user may send a duplicate collaboration instruction to a scheduling node through a scheduling application in the management node. The scheduling node may then forward the user-initiated duplicate co-instruction to the first node.

It should be noted that, in the embodiment of the present application, the target parameter value may be a duplicate parameter value of the parameter change in the target event. Or the target parameter value may be a copy parameter value corresponding to all the first preset types in the main copy of the target application. Or the target parameter value may be a duplicate parameter value that differs from the historical parameter value in the primary duplicate of the target application. The historical parameter value is a copy parameter value of a main copy in the last multi-copy cooperation of the target application.

By way of example, the copy parameter values (i.e., history parameter values) of the primary copy in the last multi-copy collaboration of the target application may include a parameter value of a timer of 11 seconds, a parameter value of a text name of H2L, and a parameter value of a port number of RS2, the copy parameter values of the primary copy of the target application prior to sending the target event may include a parameter value of a timer of 10 seconds, a parameter value of a text name of H3L, and a parameter value of a port number of RS3, the target event may include a parameter value of a timer of 11 seconds, a parameter value of a port number of RS4, and a port number of a nonvolatile type (i.e., a first preset type).

Taking the target parameter value as an example of a duplicate parameter value in which a parameter change occurs in the target event, the target parameter value includes a parameter value of 11 seconds of a timer and a parameter value of RS4 of a port number.

If the target parameter value is taken as an example of the copy parameter values corresponding to all the nonvolatile types in the main copy of the target application, the target parameter value is the parameter value RS4 of the port number.

If the target parameter value is taken as an example of a copy parameter value which is different from the historical parameter value in the main copy of the target application, the target parameter value comprises a parameter value H3L of a text name and a parameter value RS4 of a port number.

That is, by indicating the values of the copy parameters to be synchronized in the copy collaboration instruction, the method can adapt to the collaboration requirements of different applications on different types of parameters in the copy collaboration process, further can be compatible with the copy collaboration requirements of different applications, and realizes a unified copy collaboration mode, so that the collaborative management efficiency of multiple copies can be improved.

S202, the first node sends a first modification instruction to at least one second node based on the copy cooperative instruction.

The second node is a node, in which a slave copy of the target application is deployed in the plurality of service nodes.

Illustratively, in combination with the above example, service node 103 and service node 104 are both second nodes.

In an embodiment of the present application, the first modification instruction is configured to instruct modifying a parameter value corresponding to the slave copy of the target application to the target parameter value.

As a possible implementation manner, after the first node sends the first modification instruction to at least one second node, each second node may respond to the first modification instruction based on the consistency protocol, modify a parameter value corresponding to the target application from the copy into a target parameter value, and complete control of consistency.

The technical scheme provided by the embodiment at least has the following beneficial effects that the nodes participating in multi-copy deployment are subjected to instruction management through the unified upper node so as to realize multi-copy cooperation of the APP. Therefore, the method can be compatible with the copy cooperation requirements of different APP by a unified copy cooperation mode, and improves the cooperation management efficiency of multiple copies.

It should be noted that, the number of copies of the APP that the running module runs may be greater than 1, and the member attribute of the APP is a nonvolatile type, and then the running module may complete synchronization according to the synchronization policy. That is, the first node may not only perform multi-copy collaborative management on the target application based on the scheduling node, but also perform multi-copy collaborative management on the target application by itself.

In some embodiments, the first node may obtain a target event for the primary copy of the target application and send a second modification instruction to the at least one second node based on the target event. The first node may then execute the target event through the master copy of the target application in the event that the slave copy of the target application completes the target event in at least one of the second nodes (i.e., all of the second nodes). Wherein the second modification instruction is for instructing the slave copy of the target application to execute the target event.

That is, the first node may monitor the primary copy of the target application for a parameter change event to occur, and by intercepting the parameter change event of the primary copy, prioritize the secondary copy to respond to the parameter change event, and then, after the secondary copy completes execution of the parameter change event, letting the primary copy respond to the parameter change event. Thus, by automatically synchronizing in real time, the consistency between multiple copies can be ensured by preferentially changing the response parameters from the copies.

Illustratively, when the member value of the APP (i.e., the parameter value of the copy) is modified, the execution module receives the event, and the system automatically synchronizes the modification event to the other copy, and after synchronization is completed, the modification of the value is completed after the local log is written.

Member assignment for non-automatic synchronization is achieved by way of memory access and thus no modification event need be captured, but for automatic real-time synchronization the script compiler will adjust to assignment by means of setter of the member functions where the corresponding variables are modified according to the configuration, processing such assignment event in setter, and then completing consistent synchronization at this point. Thus, the multi-copy automatic synchronization can be realized, and the access performance of the volatile members can not be influenced.

As shown in fig. 3, an example schematic diagram of consistency synchronization between three copies is shown. The application copies deployed by the node 1 are master copies, and the application copies deployed by the node 2 and the node 3 are slave copies. The method comprises the following specific steps:

step one, an operation module in the node 1 intercepts a modification event of a member value.

The execution module may be executed based on the script assignment statement, and may have been converted to a call to setter at compile time, so as to intercept the modification event.

And step two, the operation module in the node 1 writes a consistency log to the consistency synchronization and control module in the node 1.

And thirdly, synchronizing the logs to other copies by the consistency synchronization and control module in the node 1.

Wherein the consistency synchronization and control module in node 1 may synchronize the log to the consistency synchronization and control module in node 2.

Here, only the synchronization to the node 2 is taken as an example, and the synchronization to the node 3 may refer to the synchronization process to the node 2.

And step four, synchronizing the state of the copies in the node 2 after receiving the log.

Wherein the consistency synchronization and control module in node 2 instructs the execution module in node 2 to execute the modification event in the log.

And step five, the copy in the node 2 returns the synchronization result to the master copy.

The running module in the node 2 can feed back a synchronization result to the consistency synchronization and control module in the node 1 through the consistency synchronization and control module in the node 2.

And step six, after confirming the notification, the consistency synchronization and control module in the node 1 writes the local log, and then returns a successful log writing result to the operation module in the node 1.

That is, the consistency synchronization and control module in node 1 instructs the running module of node 1 to continue responding to the modification event after confirming that the response of the modification event is completed from the copy in node 2.

And step seven, the running module in the node 1 modifies the member value, and the script function executes the next statement.

It should be noted that, the first node may not need to respond to the parameter change event of each primary copy, and perform batch collaboration between multiple copies through a preset collaboration policy, so as to improve the collaboration efficiency.

In some embodiments, the first node may send the first modification instruction to the at least one second node in response to a preset cooperative policy.

Wherein the preset synergy policy comprises at least one of the following (1) - (4):

(1) The modification times of the copy parameter values in the main copy of the target application are larger than a preset time threshold;

(2) The modified copy parameter value in the main copy of the target application is a parameter value corresponding to a second preset type;

(3) The current moment is equal to any moment in a preset period;

(4) The script invokes a consistency synchronization function.

That is, the nodes deploying the primary replicas may perform bulk consistency synchronization on multiple replicas where the number of parameter modifications of the primary replicas is relatively frequent, or at specified coordinated times, or where pre-specified parameter types are modified, or where there is a need for consistency synchronization for the target application.

It should be noted that, for the process of sending the first modification instruction to the at least one second node after the first node responds to the preset cooperative policy, reference may be made to the above-mentioned interaction process of consistency synchronization shown in fig. 3.

That is, when the APP logic calls the synchronization function, the operation module synchronizes all the modifications of the values in the period from the previous synchronization to the current synchronization as a synchronization log to other copies, writes the local log after the synchronization is completed, and returns the result of the synchronization returned by the synchronization function.

For manually synchronized members, the run module will store a list of members that have been modified since the last synchronization was summarized, and synchronize the latest value of a member to other copies based on the list at the next synchronization. Another implementation is to synchronize all members of the non-volatile members that are configured for manual synchronization at the time of synchronization, without concern for modification, which is less performance-intensive for situations where the variables are not particularly numerous. The second approach is typically used because no change events need to be captured, nor do the statistics need to be modified.

It can be appreciated that by providing a batch synchronization function, manual triggering of batch-to-batch copy synchronization can be achieved by one call, greatly reducing the cost of developing highly reliable apps.

In the following embodiments, a scheduling node is taken as an execution body as an example, and embodiments of the present application are specifically described with reference to the accompanying drawings. As shown in fig. 4, the collaborative management method for multiple copies further includes S401.

S401, the scheduling node sends a copy cooperative instruction to the first node.

It should be noted that, for the procedure of the scheduling node sending the duplicate cooperative instruction to the first node, reference may be made to the description of S201 in the foregoing embodiment, which is not repeated herein.

It should be noted that, the scheduling node may monitor the running state of each service node to ensure that the multi-copy deployment of the application may run normally.

In some embodiments, the scheduling node may monitor an operational state of the first node, obtain state information of the first node, and in response to identifying that the first node is in an abnormal state, deploy a primary copy of the target application in a third node, with the third node and at least one second node constituting a new multi-copy deployment of the target application.

The third node is any node which is not deployed with a copy of the target application in the plurality of service nodes.

It should be noted that, in the embodiment of the present application, the first node is in an abnormal state, and may include at least one of the following (1) - (3):

The first node is in an abnormal operation state;

the running environment of the target application in the first node is in an abnormal running state;

The target application in the first node is in an abnormal running state.

Illustratively, the status monitoring and control module in the first node returns a result or actively reports to the scheduling module status change in response to a status acquisition command of the scheduling module in the scheduling node. Then, after the state is reported to the scheduling module, the state detection logic in the scheduling module checks the state, and if the configured built-in scheduling strategy is triggered, a scheduling command is sent out. And then, the scheduled state monitoring and control module performs scheduling control and executes scheduling actions.

As shown in fig. 5, an example schematic diagram of a multi-copy deployment of an application is shown. Wherein node 1, node 2, and node 3 constitute three copies of application A, and node 1 can report to node 0 the status of the node, the running module (i.e., the running environment), and the APP. Then, the node 0 can determine whether the node 1 is in an abnormal state through the state checking logic in the scheduling module, and starts scheduling based on the configured built-in scheduling policy under the condition of checking the abnormality, and schedules the APP of the abnormal node/operation module to other operation modules (such as the operation module in the node 4), so that the node 2, the node 3 and the node 4 form three new copies of the application a for deployment.

As one possible implementation, the third node may be specifically a node of the plurality of service nodes that does not deploy a copy of the target application and is in an idle state.

Wherein the idle state includes at least one of the following (1) - (3):

(1) The available resources of the central processing unit of the node are larger than a first preset threshold;

(2) The memory resource of the node is larger than a second preset threshold;

(3) The storage resources of the node are greater than a third preset threshold.

It can be understood that by centrally managing multiple copies of an application, the deployment node of the multiple copies of the application can be flexibly changed, so that the abnormal state of part of nodes is avoided to influence the multiple copy deployment operation of the application, and the multiple copies of the application are ensured to be deployed and operated with high reliability.

In the deployment management process of the multiple copies, manual deployment is performed by a user to ensure the reasonability of deployment.

In some embodiments, the scheduling node may obtain the state information of the first node and send the information of the first state to a scheduling application deployed in the management node. The scheduling node may then receive a scheduling instruction sent by the scheduling application in the management node.

The scheduling application is used for determining whether the first node is in an abnormal state based on the state information of the first node, and the scheduling instruction comprises information for indicating that the first node is in the abnormal state.

Optionally, in a case that the user determines that the first node is in an abnormal state through the scheduling application, the scheduling instruction may further include an identification of the third node.

The state monitoring and control module in the first node returns a result or actively reports a state change to the scheduling module in response to a state acquisition command of the scheduling module. Then, after the state is reported to the scheduling module, the scheduling module sends the state to the scheduling APP (realizing the extended scheduling strategy). Then, the scheduling APP state detection logic checks the state, and if the configured built-in scheduling policy is triggered, a scheduling command is issued. Then, the scheduled state monitoring and control module performs scheduling control to execute scheduling actions.

As shown in fig. 6, an example schematic diagram of a multi-copy deployment of an application is shown. Wherein node 1, node 2, and node 3 constitute three copies of application A, and node 1 can report to node 0 the status of the node, the running module (i.e., the running environment), and the APP. Then, the node 0 may send a status query or a change result to the scheduling application in the node 6, so that the scheduling application in the node 6 expands the scheduling policy check status and performs active scheduling if the scheduling condition is satisfied, i.e., sends a scheduling request to the node 0. Then, node 0 schedules the APP of the abnormal node/execution module to other execution modules (such as the execution modules in node 4) based on the scheduling request, and further, three new copies of application a are deployed with nodes 2, 3 and 4. Or node 0 performs other scheduling actions based on the scheduling request.

The foregoing description of the solution provided by the embodiments of the present application has been presented primarily in terms of a computer device. It will be appreciated that the computer device, in order to carry out the functions described above, comprises corresponding hardware structures and/or software modules that perform the respective functions. Those skilled in the art will readily appreciate that the present application can be implemented in hardware or a combination of hardware and computer software, as example multiple copy collaborative management method steps described in connection with the disclosed embodiments of the application. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The embodiment of the application also provides a multi-copy collaborative management device. The multi-copy collaborative management apparatus may be a computer device, a CPU in the computer device, a processing module for collaborative management of multiple copies in the computer device, or a client for collaborative management of multiple copies in the computer device.

The embodiment of the application can divide the functional modules or functional units of the multi-copy collaborative management device according to the method example, for example, each functional module or functional unit can be divided corresponding to each function, and two or more functions can be integrated in one processing module. The integrated modules may be implemented in hardware, or in software functional modules or functional units. The division of the modules or units in the embodiment of the present application is schematic, which is merely a logic function division, and other division manners may be implemented in practice.

Fig. 7 is a schematic structural diagram of a multi-copy collaborative management apparatus according to an embodiment of the present application. The multi-copy collaborative management device is applied to a first node, wherein the first node is a node with a main copy of a target application deployed in a plurality of service nodes. As shown in fig. 7, the multi-copy collaborative management apparatus 700 may include a receiving module 701 and a transmitting module 702.

The receiving module 701 is configured to receive a duplicate cooperative instruction sent by a scheduling node. The sending module 702 is configured to send a first modification instruction to at least one second node based on the duplicate coordination instruction. The scheduling node is used for managing the running state of each service node in the plurality of service nodes, the copy cooperative instruction is used for indicating that the target parameter value in the master copy of the target application is synchronized to the slave copy of the target application, the second node is a node where the slave copy of the target application is deployed in the plurality of service nodes, and the first modification instruction is used for indicating that the corresponding parameter value in the slave copy of the target application is modified to the target parameter value.

Optionally, the target parameter value is a copy parameter value corresponding to the first preset type in the primary copy of the target application, or the target parameter value is a copy parameter value different from the historical parameter value in the primary copy of the target application.

Optionally, the multi-copy collaborative management apparatus 700 may further include a processing module 703. The receiving module 701 is further configured to obtain a target event of the primary copy of the target application, where the target event is used to indicate modification of a copy parameter value of the target application. The sending module 702 is further configured to send, to at least one second node, a second modification instruction based on the target event, where the second modification instruction is configured to instruct the slave copy of the target application to execute the target event. A processing module 703, configured to execute, in case the slave copy of the target application completes the target event in the at least one second node, the target event through the master copy of the target application.

Optionally, the sending module 702 is further configured to send a first modification instruction to at least one second node in response to a preset cooperative policy. The preset collaborative strategy comprises at least one of the following steps that the modification times of the copy parameter values in the main copy of the target application are larger than a preset times threshold, the modified copy parameter values in the main copy of the target application are parameter values corresponding to a second preset type, and the current time is equal to any time in a preset period.

Fig. 8 is a schematic structural diagram of another multi-copy collaborative management apparatus according to an embodiment of the present application. The multi-copy collaborative management device is applied to a scheduling node, and the scheduling node is used for managing the running state of each service node in a plurality of service nodes. The multi-copy collaborative management apparatus 800 may include a transmission module 801.

A sending module 801, configured to send a duplicate collaboration instruction to a first node. The first node is a node in which a master copy of the target application is deployed in a plurality of service nodes, and the copy cooperative instruction is used for indicating that a target parameter value in the master copy of the target application is synchronized to a slave copy of the target application.

Optionally, the target parameter value is a copy parameter value corresponding to the first preset type in the primary copy of the target application, or the target parameter value is a copy parameter value different from the historical parameter value in the primary copy of the target application.

Optionally, the plurality of service nodes includes at least one second node, the second node deployed with a slave copy of the target application, the first node and the at least one second node comprising a multiple copy deployment of the target application. The multi-copy collaborative management apparatus 800 may also include a processing module 802. A processing module 802 is configured to, in response to identifying that the first node is in an abnormal state, deploy a primary copy of the target application in a third node, where the third node is any node of the plurality of service nodes that does not deploy a copy of the target application. The processing module 802 is further configured to construct a new multi-copy deployment of the target application with the third node and the at least one second node.

Optionally, the first node is in an abnormal state, including at least one of:

the first node is in an abnormal operation state.

The operating environment of the target application in the first node is in an abnormal operating state.

The target application in the first node is in an abnormal running state.

Optionally, the third node is specifically a node that is not deployed with a copy of the target application among the plurality of service nodes and is in an idle state. The idle state comprises at least one of available resources of the central processing unit of the node being greater than a first preset threshold, memory resources of the node being greater than a second preset threshold, and memory resources of the node being greater than a third preset threshold.

Optionally, the multi-copy collaborative management apparatus 800 may further include an acquisition module 803. An obtaining module 803 is configured to obtain status information of the first node. The sending module 801 is further configured to send status information of the first node to a scheduling application deployed in the management node, where the scheduling application is configured to determine whether the first node is in an abnormal state based on the status information of the first node. The obtaining module 803 is further configured to receive a scheduling instruction sent by a scheduling application in the management node, where the scheduling instruction includes information for indicating that the first node is in an abnormal state.

Optionally, the scheduling instruction further comprises an identification of the third node.

From the foregoing description of the embodiments, it will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of functional modules is illustrated, and in practical application, the above-described functional allocation may be implemented by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to implement all or part of the functions described above. The specific working processes of the above-described systems, devices and units may refer to the corresponding processes in the above-described method embodiments, which are not described herein again.

As described above, according to the embodiment of the present application, the functional modules of each execution body involved in the multi-copy collaborative management method may be divided according to the above method example. The integrated modules may be implemented in hardware or in software functional modules. In addition, it should be noted that, in the embodiment of the present application, the division of the modules is schematic, only one logic function is divided, and another division manner may be implemented in actual implementation. For example, each functional module may be divided corresponding to each function, or two or more functions may be integrated in one processing module.

The specific manner in which each module performs the operation and the beneficial effects of the multi-copy collaborative management apparatus in the foregoing embodiment are described in detail in the foregoing method embodiment, and are not described herein again.

The embodiment of the application also provides multi-copy collaborative management equipment, which can be the first node or the scheduling node.

Fig. 9 is a schematic diagram showing a hardware structure of a multi-copy collaborative management apparatus according to an exemplary embodiment. The multi-copy collaborative management apparatus may include a communication interface 901 and a processor 902. The processor 902 is configured to control and manage the actions of the apparatus, e.g., perform various steps in the method flows shown in the method embodiments described above, and/or to perform other processes of the techniques described herein. The communication interface 901 is used to support communication of the multi-copy collaborative management apparatus with other network entities. The multi-copy collaborative management apparatus may further include a memory 903 and a bus 904, the memory 903 for storing program codes and data.

Wherein the processor 902 may implement or perform the various exemplary logic blocks, units, and circuits described in connection with the present disclosure. The processor 902 may be a central processor, general purpose processor, digital signal processor, application specific integrated circuit, field programmable gate array or other programmable logic device, transistor logic device, hardware components, or any combination thereof. Which may implement or perform the various exemplary logic blocks, units and circuits described in connection with this disclosure. The processor 902 may also be a combination that performs computing functions, e.g., including one or more microprocessors, a combination of a DSP and a microprocessor, and the like.

The memory 903 may comprise volatile memory, such as random access memory, or the memory 903 may comprise non-volatile memory, such as read-only memory, flash memory, a hard disk, or a solid state drive, or the memory 903 may comprise a combination of the above types of memory.

Bus 904 may be an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus or the like. The bus 904 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in fig. 9, but not only one bus or one type of bus.

In an exemplary embodiment, the present application also provides a computer-readable storage medium having stored thereon computer program instructions which, when executed by an electronic device, cause the electronic device to implement the method of the above-described embodiment.

Alternatively, the above-described computer-readable storage medium may be a non-transitory computer-readable storage medium, for example, a read-only memory (ROM), a random access memory (random access memory, RAM), a CD-ROM (compact disc read-only memory), a magnetic tape, a floppy disk, an optical data electronic device, and the like.

In an exemplary embodiment, the present application also provides a computer program product comprising computer readable code, or a non-volatile computer readable storage medium carrying computer readable code, which when run in an electronic device, causes a processor in the electronic device to implement a collaborative management method as described above for multiple copies.

Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims (14)

1. A method of collaborative management of multiple copies, applied to a first node, the first node being a node in a plurality of service nodes having a primary copy of a target application deployed, the method comprising:

receiving a copy cooperative instruction sent by a scheduling node;

based on the copy cooperative instruction, sending a first modification instruction to at least one second node;

the scheduling node is used for managing the running state of each service node in the plurality of service nodes, the copy cooperative instruction is used for indicating to synchronize a target parameter value in a master copy of the target application to a slave copy of the target application, the second node is a node, in which the slave copy of the target application is deployed, in the plurality of service nodes, and the first modification instruction is used for indicating to modify a parameter value corresponding to the slave copy of the target application to the target parameter value.

2. The method of claim 1, wherein the target parameter value is a copy parameter value corresponding to a first preset type in a primary copy of the target application, or the target parameter value is a copy parameter value that is different from a historical parameter value in the primary copy of the target application.

3. The method according to claim 1, wherein the method further comprises:

Acquiring a target event of a main copy of the target application, wherein the target event is used for indicating modification of a copy parameter value of the target application;

Based on the target event, sending a second modification instruction to the at least one second node, the second modification instruction being for instructing the slave copy of the target application to execute the target event;

And executing the target event through the master copy of the target application under the condition that the slave copy of the target application completes the target event in the at least one second node.

4. The method according to claim 1, wherein the method further comprises:

Responding to a preset cooperative strategy, and sending the first modification instruction to the at least one second node;

the preset collaborative strategy comprises at least one of the following steps that the number of modification times of the copy parameter value in the main copy of the target application is larger than a preset number threshold, the copy parameter value modified in the main copy of the target application is a parameter value corresponding to a second preset type, and the current moment is equal to any moment in a preset period.

5. A multi-copy collaborative management method, applied to a scheduling node, the scheduling node being configured to manage an operation state of each service node in a plurality of service nodes, the method comprising:

sending a copy collaboration instruction to the first node;

The first node is a node, in which a master copy of a target application is deployed in a plurality of service nodes, and the copy cooperative instruction is used for indicating that a target parameter value in the master copy of the target application is synchronized to a slave copy of the target application.

6. The method of claim 5, wherein the target parameter value is a duplicate parameter value corresponding to a first preset type in a primary duplicate of the target application, or the target parameter value is a duplicate parameter value that differs from a historical parameter value in the primary duplicate of the target application.

7. The method of claim 5, wherein the plurality of service nodes includes at least one second node having a slave copy of the target application deployed, the first node and the at least one second node comprising a multi-copy deployment of the target application, the method further comprising:

in response to identifying that the first node is in an abnormal state, deploying a primary copy of the target application in a third node, the third node being any one of the plurality of service nodes that does not deploy a copy of the target application;

And constructing a new multi-copy deployment of the target application by the third node and the at least one second node.

8. The method of claim 7, wherein the first node is in an abnormal state comprising at least one of:

The first node is in an abnormal operation state;

the running environment of the target application in the first node is in an abnormal running state;

the target application in the first node is in an abnormal operation state.

9. The method according to claim 7, wherein the third node is in particular a node of the plurality of service nodes that is not deploying a copy of the target application and is in an idle state;

The idle state comprises at least one of available resources of a central processing unit of the node being greater than a first preset threshold, memory resources of the node being greater than a second preset threshold, and storage resources of the node being greater than a third preset threshold.

10. The method of claim 7, wherein the method further comprises:

Acquiring state information of the first node;

Transmitting state information of the first node to a scheduling application deployed in a management node, wherein the scheduling application is used for determining whether the first node is in an abnormal state or not based on the state information of the first node;

And receiving a scheduling instruction sent by the scheduling application in the management node, wherein the scheduling instruction comprises information for indicating that the first node is in an abnormal state.

11. The method of claim 10, wherein the scheduling instruction further comprises an identification of the third node.

12. A multi-copy collaborative management apparatus applied to a first node, the first node being a node in a plurality of service nodes having a primary copy of a target application deployed therein, the apparatus comprising:

the receiving module is used for receiving the copy cooperative instruction sent by the scheduling node;

the sending module is used for sending a first modification instruction to at least one second node based on the copy cooperative instruction;

the scheduling node is used for managing the running state of each service node in the plurality of service nodes, the copy cooperative instruction is used for indicating to synchronize a target parameter value in a master copy of the target application to a slave copy of the target application, the second node is a node, in which the slave copy of the target application is deployed, in the plurality of service nodes, and the first modification instruction is used for indicating to modify a parameter value corresponding to the slave copy of the target application to the target parameter value.

13. A multi-copy collaborative management apparatus applied to a scheduling node for managing an operation state of each of a plurality of service nodes, the apparatus comprising:

the sending module is used for sending a copy cooperative instruction to the first node;

The first node is a node, in which a master copy of a target application is deployed in a plurality of service nodes, and the copy cooperative instruction is used for indicating that a target parameter value in the master copy of the target application is synchronized to a slave copy of the target application.

14. A multi-copy collaborative management apparatus comprising a processor, a memory and a computer program, wherein the computer program is stored on the memory, which when executed by the processor, causes the apparatus to implement the method of any of claims 1-11.