CN112511359B - Method, system and computer readable storage medium for configuration change in service system - Google Patents
Method, system and computer readable storage medium for configuration change in service system Download PDFInfo
- Publication number
- CN112511359B CN112511359B CN202110150713.6A CN202110150713A CN112511359B CN 112511359 B CN112511359 B CN 112511359B CN 202110150713 A CN202110150713 A CN 202110150713A CN 112511359 B CN112511359 B CN 112511359B
- Authority
- CN
- China
- Prior art keywords
- configuration change
- coordinator
- key value
- confirmation information
- participant
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the application discloses a configuration change method, a system and a computer readable storage medium in a service system, wherein the method comprises the following steps: the coordinator receives the configuration change request, generates a global serial number, and adopts a key value pair to persist the configuration change request and the global serial number to a key value database; the method comprises the following steps that a participant subscribes a key value database, calculates a first task table according to current resources and sends first confirmation information to a coordinator; after determining that all participants send first confirmation information, the coordinator persists the first-stage confirmation information; after obtaining the confirmation information of the first stage, the participant calculates a second task schedule according to the locked resources and sends the second confirmation information to the coordinator when the two task schedules are the same; and after determining that all the participants send the second confirmation information, the coordinator persists the two-stage confirmation information to indicate the participants to complete the configuration change requested by the configuration change request. To address consistency of configuration changes in the service system.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and a system for configuration change in a service system, and a computer-readable storage medium.
Background
At present, in a scenario of solving a consistent configuration change of each micro service component in a micro service system or each service node in a distributed service system, the following three technologies are mainly used for realizing the consistent configuration change: a two-phase commit protocol, a three-phase commit protocol, and a consensus algorithm.
The two-phase submission protocol is implemented by two roles: the method comprises the following specific implementation processes of a coordinator and a plurality of participants: the coordinator sends an offer to all participants, such as a specific configuration change offer; the participant replies to the coordinator with an acknowledgement message, which may be an agreement/disagreement with the configuration change, and locks the resource if the configuration change is agreed to. If the coordinator receives a confirmation message that all participants agree to the configuration change, a submission message is sent to all the participants; otherwise, an abort message is sent to all participants. The participant receives the commit/abort message, performs the commit or abort of the configuration change, and releases the locked resource. However, the following problems exist in the implementation of the two-phase commit protocol: (1) and the coordinator sends the proposal to all the participants, and needs all the participants to lock corresponding resources in the service system so as to ensure that the resource states of the participants are consistent, and if the resource locking time is too long, the external service of the system is influenced, and the user experience is influenced. (2) When any participant exits abnormally in the two-stage submission process, the whole process is blocked, the locked resources cannot be released for a long time, and the utilization rate of the resources is reduced. (3) The coordinator has a single point of failure problem.
The three-phase submission protocol is similar to the two-phase submission protocol, and the specific implementation process is as follows: the coordinator sends an offer to all participants, such as a specific configuration change offer; the participant receives the offer and replies to the coordinator with a prepare acknowledge message, which may be an agreement/disagreement with the configuration change. If the coordinator receives a preparation confirmation message that all the participants agree to the configuration change, a preparation submission message is sent to all the participants; otherwise, an abort message is sent to all participants. The participant replies to the coordinator confirmation message after receiving the prepare commit message, which may be an agreement/disagreement with the configuration change, and locks the resource. If the coordinator receives a confirmation message that all participants agree to the configuration change, a submission message is sent to all the participants; otherwise, an abort message is sent to all participants. The participant receives the commit/abort message, performs the commit or abort of the configuration change, and releases the locked resource. However, the following problems exist in the implementation of the three-phase commit protocol: (1) when the coordinator sends a submit message to all participants, if the network partition occurs, part of the participants receive the submit message and execute the submission of the configuration change, and the other part of the participants stop the submission of the configuration change because the network partition does not receive the submit message, so that the configuration change is inconsistent among the participants when the network is recovered. (2) The coordinator has a single point of failure problem.
The consensus algorithm is different from a two-stage/three-stage submission protocol, is a consistency algorithm based on message transfer and with high fault tolerance, and takes the consensus algorithm as a Paxos algorithm as an example, the implementation of the Paxos algorithm includes two types of roles: the proposal message comprises a series of sequence numbers and a proposal content, and the specific implementation flow is as follows: the proposer selects a series of serial numbers n and sends the proposed content to all receivers; after the receiver receives the proposal message, if the sequence number n is the maximum sequence number currently received by the receiver, the receiver carries the sequence number m of the last reply confirmation message in the confirmation message to reply to the presenter, and ensures that other proposal messages smaller than the sequence number n are not received any more. When the proposer receives the acknowledgement message sent by the majority of receivers, the proposer sends a submit message to the majority of receivers, including the sequence number n and the maximum sequence number m returned by the receivers. After the receiver receives the submit message, the proposed configuration change is agreed to and completed without violating the premise of ensuring that no more than n other proposed messages are received. However, the following problems exist in the implementation of the consensus algorithm: the algorithm is complex and difficult to understand, and the implementation cost is high. (2) And only the fault node with the fault can be tolerated, and the malicious node of the flow realized by the malicious tampering consensus algorithm cannot be tolerated.
Therefore, there is a need to propose a method that better enables consistent configuration changes in a service system.
Disclosure of Invention
The embodiment of the application provides a configuration change method in a micro service system, which can ensure the consistency and the safety of the configuration change of all micro service components in the service system.
In a first aspect, a method for changing configuration in a service system is provided, which is applied to a service system including a coordinator and at least one participant, and includes:
the coordinator receives a configuration change request from a user, generates a global serial number n for the configuration change request, and persists the global serial number n and the configuration change request to a key value database in a key value pair mode, wherein the configuration change request carries configuration information and at least one participant related to configuration;
after determining that all participants in the configuration change request corresponding to the global sequence number n send first-stage confirmation information, the coordinator stores first-stage confirmation information in a key value database in a key value pair mode, wherein the first-stage confirmation information is used for indicating that all the participants agree with the configuration change request and lock corresponding resources in the service system, the first-stage confirmation information is sent after the participants calculate a first task schedule after configuration change according to current resources of the participants, and the first-stage confirmation information carries the first task schedule and the global sequence number n;
after determining that all participants in the configuration change request corresponding to the global sequence number n send second confirmation information, the coordinator stores two-stage confirmation information in the key value database in a key value pair mode, wherein the two-stage confirmation information is used for indicating all the participants to release the locked resources and finish the service configuration change requested by the configuration change request, the second confirmation information is sent after the participants determine that the first task schedule and the second task schedule are the same, and the second task schedule is a task schedule obtained after the participants calculate and obtain the configuration change according to the locked resources.
Optionally, the step of determining, by the coordinator, that all the participants in the configuration change request corresponding to the global sequence number n have sent the first-time confirmation information includes:
the coordinator receives the first-time confirmation information sent by each participant respectively and stores the received first-time confirmation information into the key value database respectively in a key value pair mode;
the coordinator determines whether the first-time confirmation information sent by all the participants is received by referring to key value pairs in the key value database.
Optionally, the step of determining, by the coordinator, that all the participants in the configuration change request corresponding to the global sequence number n have sent the second-time confirmation information includes:
the coordinator receives the second confirmation information sent by each participant respectively and stores the received second confirmation information into the key value database respectively in a key value pair mode;
and the coordinator determines whether the second confirmation information sent by all the participants is received or not by referring to the key value pairs in the key value database.
Optionally, after the coordinator persists the global sequence number n and the configuration change request in a key-value pair form in a key-value database, the method further includes:
when the coordinator determines that any participant in the configuration change request corresponding to the global sequence number n does not send the first-time confirmation information or does not receive the first-time confirmation information sent by any participant within a preset time length, storing first-stage suspension information in a key value pair mode in the key value database;
wherein the one-phase abort information is to indicate that the participant does not agree with the configuration change request.
Optionally, after the coordinator persists the global sequence number n and the configuration change request in a key-value pair form in a key-value database, the method further includes:
when the coordinator determines that any participant in the configuration change request corresponding to the global sequence number n does not send the second confirmation information or does not receive the second confirmation information sent by any participant within a preset time length, storing two-stage suspension information in a key value pair mode in the key value database;
wherein the two-stage abort information is to indicate that the participant does not agree with the configuration change request.
Optionally, the method further includes:
and the coordinator returns configuration failure information to the user, wherein the configuration failure information is used for notifying the service configuration change failure requested by the configuration change request.
Optionally, the method further includes:
the coordinator receives configuration completion information sent by each participant respectively and stores the received configuration completion information into the key value database respectively in a key value pair mode, wherein the configuration completion information is sent after the participant subscribes to the two-stage confirmation information to complete the service configuration change requested by the configuration change request;
and the coordinator executes a recovery mechanism and deletes all key value pairs associated with the configuration change request in the key value database when determining that all the participants in the configuration change request corresponding to the global sequence number n send the configuration completion information or the configuration completion information sent by at least one participant is not received within a preset time length.
Optionally, if the number of the configuration change requests is multiple, the coordinator supports to process multiple configuration change requests simultaneously in a parallel manner.
Optionally, the coordinator includes a master coordinator and a slave coordinator, and when the master coordinator is abnormal, the slave coordinator subscribes to the key value database and replaces the master coordinator to continue to complete the service configuration change requested by the configuration change request.
In a second aspect, there is provided another method for changing a configuration in a service system, which is applied to a service system including a coordinator and at least one participant, and includes:
the participants subscribe a key value database, determine themselves as the participants of the service configuration change, and obtain a configuration change request and a global serial number n corresponding to the service configuration change, wherein the configuration change request carries the configuration information and at least one participant related to the configuration, and the key value database stores the global serial number n and the configuration change request in a key value pair mode;
the participant calculates a first task schedule after configuration change according to the current resources and the configuration information, and sends first confirmation information to the coordinator, wherein the first confirmation information carries the first task schedule and the global sequence number n, and the first confirmation information is used for indicating the participant to approve the configuration change request;
the participants subscribe the key value database, lock corresponding resources in the service system after obtaining one-stage confirmation information corresponding to the global serial number n, and calculate a second task schedule after configuration change again according to the locked resources and the configuration information, wherein the one-stage confirmation information is information stored in the key value database in a key value pair form after the coordinator determines that all the participants corresponding to the global serial number n send the first confirmation information;
and when the first task schedule is the same as the second task schedule, the participant sends second confirmation information to the coordinator, wherein the second confirmation information carries the global sequence number n and is used for indicating that the participant agrees to the configuration change request.
Optionally, after the participant recalculates the second task schedule after configuration change according to the locked resource and the configuration information, the method further includes:
and when the participant confirms that the first task schedule is different from the second task schedule, sending confirmation failure information to the coordinator, wherein the confirmation failure information is used for informing the coordinator that the first task schedule is different from the second task schedule, and the participant does not agree with the configuration change request.
Optionally, after the participant sends the second confirmation information to the coordinator, the method further includes:
the participant subscribes the key value database, releases the locked resource after obtaining the two-stage confirmation information corresponding to the global serial number n, and executes the second task schedule to complete the service configuration change requested by the configuration change request;
the second-stage confirmation information is information which is stored in the key value database in a key value pair mode after the coordinator determines that all the participants in the configuration change request corresponding to the global serial number n send the second confirmation information.
In a third aspect, a service system is provided, which includes a coordinator and at least one participant, and the coordinator may perform the method in the first aspect or any optional implementation manner of the first aspect. The participant may perform the method of the second aspect or any one of the alternative embodiments of the second aspect described above. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more units corresponding to the above functions. The unit may be software and/or hardware.
In a fourth aspect, a service system is provided, where the service system includes a coordinator and at least one participant, the coordinator is configured to perform the method for changing configuration in the service system described in the first aspect, and the participant is configured to perform the method for changing configuration in the service system described in the second aspect.
In a fifth aspect, a computer program product is provided, which when run on a computer, causes the computer to perform the method for consistent configuration change in a service system as described in the first or second aspect above.
In a sixth aspect, a chip product is provided, which performs the method for consistent configuration change in the service system described in the first aspect or the second aspect.
In a seventh aspect, a computer-readable storage medium is provided, which has instructions stored therein, and when the instructions are executed on a computer, the instructions cause the computer to perform the method for consistent configuration change in a service system described in the above first aspect or second aspect.
Drawings
Fig. 1 is a schematic flowchart of a configuration change method in a service system according to an embodiment of the present application.
Fig. 2 is a flowchart illustrating another configuration changing method in a service system according to an embodiment of the present application.
Fig. 3 is a schematic structural diagram of a service system according to an embodiment of the present application.
Detailed Description
Specific embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
Fig. 1 is a schematic flow chart illustrating a configuration changing method in a service system according to an embodiment of the present application. The method as shown in fig. 1 comprises the following implementation steps:
s101, the user sends a configuration change request to the coordinator. Accordingly, the coordinator receives a configuration change request from the user. The configuration change request is used for requesting to perform consistent configuration change on a service provided by a corresponding participant (for example, a micro service component provided by the participant in the micro service system or a service node corresponding to the participant in the distributed service system). The configuration change request carries configuration information and at least one participant involved in the configuration.
In the present application, the user may initiate a service configuration change and specify a service (e.g., services A, B and C) related to the configuration change, that is, specify a participant corresponding to the service. After the participant is designated, a corresponding configuration change request may be generated and sent to the coordinator.
It should be noted that the configuration change request related in the present application may be a request for performing consistent configuration change on each micro service component in the micro service system, or may also be a request for performing consistent configuration change on each service node in the distributed service system, and for convenience of describing that the present application is uniformly described as a configuration change request for performing consistent configuration change on a corresponding service in the service system, details are not described below.
S102, the coordinator generates a global serial number n for the configuration change request, and persists the global serial number n, the configuration information, the participants and other information to a key value database in a key value pair mode.
The coordinator can automatically generate a unique global serial number n after receiving the configuration change request, and further persist the global serial number n and the configuration information, participants and other information in the configuration change request into a key value database in a key value pair mode. For example, the information of the key-value pair is specifically as follows: the global sequence number is n, the involved participants are A, B, C and the like, and the configuration change specifically includes: configuration change time is 1 point, and so on. Wherein n may be an integer not less than 1.
S103, the participants subscribe the key value database, determine that the participants are the participants of the service configuration change, and obtain the configuration change request and the global serial number n corresponding to the service configuration change.
The method comprises the steps that participants subscribe a key value database, whether the participants are the participants of the current service configuration change is judged by analyzing key value pairs in the key value database, if the participants of the current service configuration change are the participants of the current configuration change, the subsequent process is continued, and otherwise, the current service configuration change is ignored. After determining that the participant is the participant of the current configuration change, the participant acquires information such as a configuration change request (namely, configuration information and at least one participant involved in configuration) and a global serial number n corresponding to the current configuration change from the key value database.
It should be noted that, in the embodiment of the present application, only one participant is taken as an example to describe in detail a specific implementation of the participant in the service configuration change process, and all participants in the at least one participant can refer to the specific implementation of the one participant to complete the consistency of the service configuration change.
And S104, after confirming that the participant agrees to the service configuration change requested by the configuration change request according to the current resource of the participant, sending first confirmation information to the coordinator, wherein the first confirmation information is used for indicating that the participant agrees to the service configuration change requested by the configuration change request. Correspondingly, the coordinator receives the first confirmation information sent by the participants.
The specific implementation manner of the participant confirming the agreement of the service configuration change requested by the configuration change request according to the current resource of the participant in the application is as follows: the participator calculates a first task schedule after configuration change according to the current resource and configuration information, and sends first confirmation information to the coordinator after the first task schedule is calculated, wherein the first confirmation information carries the first task schedule and a global serial number n and indicates that the participator agrees the service configuration change requested by the configuration change request at one stage.
Correspondingly, after receiving the first-time confirmation information sent by the participants, the coordinator can persist the first-time confirmation information into the key value database in a key value pair mode. Here, the key-value pair corresponding to the first-time confirmation information may be, for example: global sequence number n, participant a, whether to agree to a stage of configuration change: the first task schedule of the change is: etc.
And S105, after determining that all participants in the configuration change request corresponding to the global sequence number n send first confirmation information, the coordinator stores the first confirmation information in a key value database in a key value pair mode, wherein the first confirmation information is used for indicating all participants to lock resources.
The coordinator inquires key value pairs in a key value database, and stores first-stage confirmation information in the key value database in a key value pair mode when determining that all participants in a configuration change request corresponding to a global serial number n send first-time confirmation information. If any participant does not send the first confirmation information, or sends a stage of not agreeing with the service configuration change requested by the configuration change request, or does not receive the first confirmation information sent by any participant within a time-out period (namely within a preset time period), storing a stage of suspension information in a key value pair mode in a key value database, wherein the stage of suspension information is used for indicating that all participants disagree with the service configuration change requested by the configuration change request. Optionally, at this time, configuration failure information may be sent to the user for notifying that the service configuration change requested by the configuration change request fails.
S106, the participant subscribes to the key value database, locks the resource after obtaining the first-stage confirmation information corresponding to the global sequence number n, and confirms the service configuration change requested by the configuration change request approved by the participant in two stages according to the locked resource again, and then sends second-time confirmation information to the coordinator, wherein the second-time confirmation information carries the global sequence number n and is used for indicating the participant to approve the service configuration change requested by the configuration change request in two stages. The coordinator receives the second acknowledgement information accordingly.
The method includes the steps that participants subscribe key value pairs in a key value database, analyze the key value pairs to obtain one-stage confirmation information corresponding to a global serial number n, and then start to lock own resources according to the indication of the information. And then calculating a second task schedule after configuration change according to the locked resources, if the second task schedule is different from the first task schedule, releasing the locked resources, returning two-stage confirmation failure information to the coordinator, and carrying a configuration failure reason: due to different resource states of participants, the task schedule is calculated for two times and fails to change the configuration. To notify the configuration change request that the requested service configuration change failed. And if the second task schedule is the same as the first task schedule, the participant sends second confirmation information to the coordinator, wherein the second confirmation information carries a global sequence number n and is used for indicating that the participant agrees the service configuration change requested by the configuration change request in two stages.
Correspondingly, after receiving the second confirmation information sent by the participants, the coordinator can persist the second confirmation information into the key value database in a key value pair mode. Here, the key-value pair corresponding to the second confirmation information may be, for example: global sequence number n, participants A, B and C, whether two-phase configuration changes are warranted: the second task schedule to be changed is: etc. Optionally, if the participant subscribes to the one-stage suspension information in the key value database, the configuration change may be ignored.
And S107, after determining that all participants in the configuration change request corresponding to the global sequence number n send second confirmation information, the coordinator stores two-stage confirmation information in a key value database in a key value pair mode, wherein the two-stage confirmation information is used for indicating all the participants to release the locked resources and completing the service configuration change requested by the configuration change request.
The coordinator inquires the key value pair in the key value database, and after determining that all participants in the configuration change request corresponding to the global serial number n send second confirmation information, the coordinator stores the second-stage confirmation information in the key value database in a key value pair mode. If any participant does not send the second confirmation information, or sends the second confirmation information that the second time does not agree with the service configuration change requested by the configuration change request, or does not receive the second confirmation information sent by any participant within the time-out (namely within the preset time length), storing the second-stage suspension information in a key value database in a key value pair mode, wherein the second-stage suspension information is used for indicating that all participants do not agree with the service configuration change requested by the configuration change request. Optionally, at this time, configuration failure information may be sent to the user for notifying that the service configuration change requested by the configuration change request fails.
S108, the participants subscribe the key value database, and after obtaining the two-stage confirmation message corresponding to the global sequence number n, the locked resources are released, and the service configuration change requested by the configuration change request is completed.
And S109, after completing the configuration change, the participant sends configuration completion information to the coordinator, wherein the configuration completion information is used for informing that the participant has completed the service configuration change requested by the configuration change request currently. And correspondingly, the coordinator receives the configuration completion information.
The method includes the steps that a participant subscribes a key value pair in a key value database, analyzes the key value pair to obtain two-stage confirmation information corresponding to a global sequence number n, and then releases a locked resource according to the indication of the information. And the participator submits a second task schedule and a configuration change request, and executes the second task schedule to complete the service configuration change requested by the configuration change request. Further participants may send configuration completion information to the coordinator, the configuration completion information carrying the global sequence number n. The participants continue to provide normal service to the outside.
Correspondingly, the coordinator receives the configuration completion information sent by the participants and persists the configuration completion information to the key value database in a key value pair mode. Optionally, if the participant subscribes to the two-stage suspension information in the key-value database, the configuration change is ignored.
S110, if it is determined that all participants in the configuration change request corresponding to the global sequence number n have sent configuration completion information, or the coordinator does not receive the configuration completion information sent by any participant after time out (i.e. within a preset time), executing a recycling mechanism, and deleting all key value pairs related to the configuration change request in the key value database.
The coordinator queries the key value pairs in the key value database, analyzes the key value pairs and determines whether configuration completion information sent by all participants is received. If the coordinator receives the configuration completion information sent by all participants or does not receive the configuration completion information sent by any one or more participants after overtime, the coordinator considers that the influence of the unresponsive participants on the service system is eliminated, and at the moment, a recovery mechanism can be executed to delete all key value pairs related to the configuration change request in the key value database so as to save the memory space.
Optionally, to clear a coordinator single point fault, the coordinator may adopt master-slave deployment. That is, the coordinator includes a master coordinator and a slave coordinator, and the number of the slave coordinators is not less than one, and may be a plurality of, without limitation. When the primary coordinator fails or exits abnormally, the secondary coordinator can subscribe the key value database to continue to complete the service configuration change requested by the configuration change request, namely, continue to complete the related flow of the configuration change.
Optionally, a daemon or a high-availability program is deployed in the participant, and after the participant exits abnormally, the participant can be restarted through the daemon/high-availability program, and still can continue to complete the service configuration change requested by the configuration change request before the abnormal exit through the key-value database.
Optionally, the coordinator may provide services for configuration change requests of different service systems at the same time. Specifically, the coordinator can generate a unique global sequence number n for each configuration change request, and when the coordinator and the participants subscribe to the key value database, different configuration change requests can be distinguished through the global sequence number n, so that the coordinator has the capability of providing parallel processing of a plurality of configuration change requests. That is, when there are a plurality of configuration change requests, the coordinator can process the plurality of configuration change requests simultaneously in a parallel manner.
By implementing the application, the method for solving the problem of the consistency configuration change in the service system has the following beneficial effects:
(1) and reducing the resource locking time. The method and the system have the advantages that the consistent configuration change is carried out based on a three-stage submission protocol, the participants can be enabled to lock the resources after the same configuration change is confirmed in one stage, if any participant cannot agree with the configuration change due to own resources, the confirmation is probably failed in one stage, the resources of all the participants cannot be locked under the condition, the locking time of the system resources is reduced, and the stability and the throughput of the system to external services are improved.
(2) And the problem of single point failure of the coordinator is avoided. According to the method and the device, a key value database persistent configuration change process is adopted, and the method and the device do not depend on memory data of a coordinator. When the coordinator exits abnormally, the daemon can still subscribe the key value database after restarting, and the configuration change before the abnormal exit is continuously completed. Or, the redundant slave coordinator is deployed, and the slave coordinator continues to work after the master coordinator is abnormal, so that the whole configuration change process is completed.
(3) The problem of single point of failure of the participants is avoided. According to the method and the device, the key value database persistent configuration change process is adopted, and when the participant exits abnormally, the participant can still subscribe the key value database to continuously complete the configuration change process after being restarted. When the participator exits abnormally and can not be restarted, the coordinator can determine that the current configuration change is stopped after overtime, and the consistency of the configuration change is maintained.
(4) And the automatic recovery mechanism reduces the operation and maintenance burden. When the configuration change process is abnormal, the coordinator confirms whether the influence of the current configuration change is eliminated or not according to the current process state (the default is overtime, for example, the influence can be eliminated within 24 hours), and if the influence is not eliminated, all information related to the configuration change request, such as configuration information and the like, is deleted without manual repair.
(5) Different configuration change processes can be executed concurrently. The configuration change processes are identified by the unique global serial number n, different configuration change processes can generate different global serial numbers through a coordinator, and the configuration change processes are parallel and do not disturb each other.
(6) And the engineering realization cost is lower. Compared with the consensus algorithm, the configuration change process is simple, easy to understand, low in development cost, low in risk of defects, easy to maintain later and easy to increase new characteristics.
For ease of understanding, a detailed description is provided below with respect to a specific scenario. In a micro service system, a task scheduling service is often used, which is responsible for scheduling and executing each timing task in the system, and displaying an executed task schedule to a user. The timing task can be daily routing inspection, timing backup, shorthand test and the like. Different task types use the same global configuration, for example, the services A, B and C currently having task orchestration are respectively responsible for timing tasks of different system areas, and all tasks are orchestrated according to the global configuration. The global configuration may include configuration information such as a maximum concurrent number of tasks, an operation and maintenance time period during which the tasks may be executed, and a maximum execution time of the tasks. When the global configuration changes, the services A, B and C need to generate a new task schedule according to the new configuration information and feed back to the user for confirmation. After the user confirms approval of the new mission schedule, the services A, B and C update the configuration changes at the same time, and subsequently perform subsequent tasks using the new mission schedule. The flow of consistent configuration change related to different services can be specifically shown in fig. 2. Specifically, fig. 2 is a schematic flowchart of another configuration changing method in a service system according to an embodiment of the present application. The method as shown in fig. 2 comprises the following steps:
s201, the user starts initiating configuration change, specifies at least one service related to the configuration change (specifically, may be a participant who provides the service), and generates a configuration change request. The user sends the configuration change request to the coordinator. The coordinator receives the configuration change request accordingly. The configuration change request carries configuration information and at least one participant involved in the configuration.
S202, the coordinator generates a unique global serial number n for the configuration change request, and information such as the global serial number n, configuration information in the configuration change request and at least one participant is persisted to a key value database in a key value pair mode.
S203, the participants subscribe the key value pairs in the key value database to obtain the configuration change request (namely, new configuration change exists), confirm that the configuration change request relates to the service of the participants, and obtain the information carried in the configuration change request and the global serial number n.
And S204, the participant calculates the first task schedule after the configuration is changed according to the current resource and the configuration information of the participant, and the resource is not locked at the moment.
S205, the participant sends first-time confirmation information to the coordinator, wherein the first-time confirmation information carries a first task schedule and a global serial number so as to reply the first task schedule to the coordinator. Correspondingly, the coordinator receives the first confirmation information and persists the first confirmation information into the key value database in a key value pair mode.
S206, the coordinator consults the key value pairs in the key value database, and after confirming that all the participants send the first confirmation information, the coordinator collects the first task schedules of all the participants and merges all the first task schedules into a new task schedule.
And S207, the coordinator sends the merged new task schedule to the user. The user receives the new task schedule accordingly.
And S208, the user views the new task schedule and feeds back viewing results to the coordinator. The coordinator receives the viewing results.
S209, if the checking result is used for indicating that the user agrees to the service configuration change requested by the configuration change request, the coordinator persists the stage confirmation information to a key value database in a key value pair mode. A phase one acknowledgement message is used to indicate that all participants agree to the service configuration change requested by the configuration change request.
Optionally, if the viewing result indicates that the user does not agree with the service configuration change requested by the configuration change request, the coordinator persists a stage suspension message in a key-value pair form in the key-value database. A phase abort message indicates that all participants do not intend the service configuration change requested by the configuration change request.
S210, after the participants subscribe the key value pairs in the key value database to obtain the first-stage confirmation information, locking the resources, and recalculating the second task schedule after configuration change according to the locked resources and the configuration information.
Optionally, after the participant subscribes the key value pair in the key value database to obtain the termination information of a stage, the configuration change can be finished; otherwise, continuing the subsequent configuration change process.
And S211, if the second task schedule is different from the first task schedule, the participant sends a failure confirmation message to the coordinator to inform that the second task schedule is different from the first task schedule (namely, the two task schedules are calculated differently), and the configuration change fails. The coordinator receives the acknowledgement failure information accordingly.
S212, the coordinator sends configuration failure information to the user, wherein the configuration failure information is used for notifying the service configuration change failure requested by the broken configuration change request. And the user receives and checks the configuration failure information to acquire the failure of the configuration change.
And S213, if the second task schedule is the same as the first task schedule, the participant sends second confirmation information to the coordinator, wherein the second confirmation information carries a global sequence number n and is used for informing the participant of two-stage agreement of the service configuration change requested by the configuration change request. Correspondingly, the coordinator receives the second confirmation information sent by the participants and persists the second confirmation information to the key value database in a key value pair mode.
S214, after the coordinator queries the key value pairs in the key value data chain to confirm that the second confirmation information sent by all participants is received, the key value pairs are adopted to persist the two-stage confirmation information in the key value database. Otherwise, if the coordinator confirms that the second confirmation information sent by any participant in all the participants is not received or the second confirmation information sent by any participant is not received within time, the two-stage suspension information is persisted into the key value database in a key value pair mode.
S215, the participant subscribes the key value pair in the key value database to obtain two-stage confirmation information, which indicates that the task schedules calculated by the participant twice are the same, the new task schedule confirmed by the user is still valid, the participant starts to submit a second task schedule and a configuration change request, executes the second task schedule to complete the service configuration change requested by the configuration change request, and releases the self-locked resources.
Optionally, after the participant subscribes the key value pair in the key value database to obtain the two-stage suspension information, the locked resource can be released, the configuration change is stopped, and normal service is continuously provided for the outside.
And S216, after the configuration change is completed, sending configuration completion information to the coordinator, wherein the configuration completion information carries a global serial number n and is used for informing the participant that the configuration change is completed and normal external services can be continuously provided. Correspondingly, the coordinator receives the configuration completion information, and persists the configuration completion information to the key value database by using the information of the key value pairs.
S217, when the coordinator queries the key value pairs in the key value database to confirm that the configuration completion information sent by all participants is received, or the configuration completion information sent by any participant in all participants is not received within time, a recovery mechanism can be immediately executed to delete all the key value pairs related to the configuration change. For the content that is not described in the embodiment of the present application, reference may be made to the related description in the embodiment described in fig. 1, and further description of the present application is omitted.
By adopting the embodiment of the application, the following beneficial effects are achieved:
(1) and the invalid resource locking time caused by the fact that the user does not approve the new task schedule can be greatly reduced. When the participator returns to the user's schedule in one stage, the participator does not lock the resource of itself and does not influence the normal service function. After the user confirms the schedule, the participant locks the resources of the participant in two stages, the time of the participant is close to the time of the first stage, the task schedule calculated in the two stages does not change in a large probability, and the configuration change can be successfully submitted and the resources are locked. The task schedule of the two-stage calculation under the small-probability scene is different from that of the one-stage calculation, the current configuration change can be stopped through the coordinator, and the configuration changes of all participants are guaranteed to be consistent.
(2) And the coordinator clears the single point fault. And the coordinator adopts master-slave deployment and synchronizes the whole configuration change process to the key value database. And when the master coordinator exits abnormally, the slave coordinator can re-subscribe the key value database and continue to complete the subsequent configuration change process.
(3) And the participant clears the single point of failure. The participator obtains the configuration change process through the subscription key value database, and can still obtain the current process information after the participator is abnormally restarted, and the configuration change is continuously completed. If the participant does not respond for a long time, the coordinator sets the overtime time, and does not receive the information sent by the participant after overtime, the confirmation failure at the stage is judged, and the confirmation failure information is fed back to the coordinator and is persisted to the key value database. And other participants acquire the confirmation failure information of the configuration change through the subscription key value database and interrupt the configuration change in time.
(4) The coordinator can provide services for the configuration change processes of different service systems at the same time. Since each configuration change request is matched with the unique global serial number n generated by the coordinator, the coordinator and the participants distinguish different configuration change requests through the global serial number n when subscribing. Whereby the coordinator has the ability to provide multiple configuration change flow parallel services.
(5) And the development and maintenance cost is low. The scheme has the advantages of convenient understanding of the configuration change process, short development period and realization of any editing language. The key value database has wide selectivity, the master-slave deployment mode of the coordinator is also widely applied, and operation and maintenance personnel can quickly find related resources to be familiar with the deployment process, thereby being beneficial to reducing the later maintenance cost.
Referring to fig. 3, a service system provided in an embodiment of the present application includes a coordinator and at least one server. Wherein,
the coordinator is configured to receive a configuration change request from a user, generate a global sequence number n for the configuration change request, and persist the global sequence number n and the configuration change request in a key value pair form to a key value database, where the configuration change request carries configuration information and at least one of the participants involved in configuration;
the participants are used for subscribing the key value database, determining the participants as the participants of the service configuration change, and obtaining a configuration change request and a global serial number n corresponding to the service configuration change; calculating a first task schedule after configuration change according to the current resources and the configuration information, and sending first-time confirmation information to the coordinator, wherein the first-time confirmation information carries the first task schedule and the global sequence number n, and the first-time confirmation information is used for indicating that the participant agrees to the service configuration change requested by the configuration change request;
the coordinator is further configured to store, in the key value database, one-stage confirmation information in a key value pair manner after it is determined that all the participants in the configuration change request corresponding to the global sequence number n send first confirmation information, where the one-stage confirmation information is used to indicate that all the participants agree with the service configuration change requested by the configuration change request and lock resources;
the participant is also used for subscribing the key value database, locking the resource after obtaining the one-stage confirmation information corresponding to the global serial number n, and recalculating the second task schedule after configuration change according to the locked resource and the configuration information; when the first task schedule is the same as the second task schedule, sending second confirmation information to the coordinator, wherein the second confirmation information carries the global sequence number n and is used for indicating that the participant agrees to the service configuration change requested by the configuration change request;
the coordinator is further configured to, after determining that all the participants in the configuration change request corresponding to the global sequence number n send second-time confirmation information, store two-stage confirmation information in the key value database in a key value-pair manner, where the two-stage confirmation information is used to indicate that all the participants release the locked resource and complete the service configuration change requested by the configuration change request;
the participant is further configured to subscribe to the key value database, release the locked resource after obtaining the two-stage confirmation information corresponding to the global sequence number n, and execute the second task schedule to complete the service configuration change requested by the configuration change request.
Optionally, before determining that all the participants in the configuration change request corresponding to the global sequence number n send the first acknowledgement information, the method further includes:
the coordinator is further configured to receive the first acknowledgement information sent by each of all the participants, and store the first acknowledgement information in the key value database in a key value pair manner, where the first acknowledgement information carries the first task schedule and the global serial number n;
the coordinator is further configured to subscribe to the key value database, and determine whether the first-time acknowledgement information sent by all the participants is received through key value pairs in the key value database.
Optionally, before determining that all the participants in the configuration change request corresponding to the global sequence number n send the second confirmation information, the method further includes:
the coordinator is also used for receiving second confirmation information sent by all the participants respectively and storing the second confirmation information into the key value database in a key value pair mode;
the coordinator is further configured to subscribe to the key value database, and determine whether to receive the second acknowledgment information sent by all the participants through key value pairs in the key value database.
Optionally, after persisting the global sequence number n and the configuration change request in a key-value pair form to a key-value database, the method further includes:
the coordinator is further configured to store the first-stage suspension information in the key value database in a key value pair manner after determining that any one of the participants in the configuration change request corresponding to the global sequence number n does not send the first-stage confirmation information or does not receive the first-stage confirmation information sent by any one of the participants within a preset time length;
wherein the one-phase abort message indicates that the participant does not agree with the service configuration change requested by the configuration change request.
Optionally, after persisting the global sequence number n and the configuration change request in a key-value pair form to a key-value database, the method further includes:
the coordinator is further configured to store the second-stage suspension information in the key value database in a key value pair manner after determining that any one of the participants in the configuration change request corresponding to the global sequence number n does not send the second acknowledgment information, or after determining that the second acknowledgment information sent by any one of the participants is not received within a preset time period;
wherein the two-stage abort information is used to indicate that the participant does not agree with the service configuration change requested by the configuration change request.
Optionally, the coordinator is further configured to return configuration failure information to the user, where the configuration failure information is used to notify that the service configuration requested by the configuration change request fails to be changed.
Optionally, the participant is further configured to send configuration completion information to the coordinator, where the configuration completion information is sent after the participant subscribes to the second-stage confirmation information and completes the service configuration change indicated by the configuration information;
the coordinator is further configured to receive configuration completion information sent by all the participants, and store the configuration completion information in the key value database in a key value pair manner, where the configuration completion information is sent after the participants subscribe to the two-stage confirmation information and complete the service configuration change indicated by the configuration information; and executing a recovery mechanism and deleting all key value pairs associated with the configuration change request in the key value database when determining that all the participants in the configuration change request corresponding to the global sequence number n send the configuration completion information or the configuration completion information sent by at least one participant is not received within a preset time length.
Optionally, the participant is further configured to send a failure confirmation message to the coordinator when the first task schedule is different from the second task schedule, where the failure confirmation message is used to notify that the first task schedule is different from the second task schedule, and the participant does not agree with the service configuration change requested by the configuration change request.
Optionally, if the number of the configuration change requests is multiple, the coordinator supports to process the multiple configuration change requests simultaneously in a parallel manner.
Optionally, the coordinator includes a master coordinator and a slave coordinator, and when the master coordinator is abnormal, the slave coordinator subscribes to the key-value database to continue to complete the service configuration change requested by the configuration change request.
By implementing the method, the consistency configuration change method in the service system is provided, the consistency of the configuration change can be ensured, the resource locking time can be reduced, the problem of single-point faults of a coordinator and a participant can be solved, and the consistency, the safety and the robustness of the configuration change can be improved.
Based on the same inventive concept, the principle of solving the problem by the service system provided in the embodiment of the present application is similar to that of solving the problem by the service system in the embodiment of the method of the present application, so that the implementation of each device may refer to the implementation of the method, and is not described herein again for brevity.
It should be noted that, in the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to relevant descriptions of other embodiments for parts that are not described in detail in a certain embodiment.
The steps in the method of the embodiment of the invention can be sequentially adjusted, combined and deleted according to actual needs.
The modules in the service system of the embodiment of the invention can be merged, divided and deleted according to actual needs.
Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.
Claims (12)
1. A configuration change method in a service system is applied to the service system comprising a coordinator and at least one participant, and comprises the following steps:
the coordinator receives a configuration change request from a user, generates a global serial number n for the configuration change request, and persists the global serial number n and the configuration change request to a key value database in a key value pair mode, wherein the configuration change request carries configuration information and at least one participant related to configuration;
after determining that all participants in the configuration change request corresponding to the global sequence number n send first-stage confirmation information, the coordinator stores first-stage confirmation information in a key value database in a key value pair mode, wherein the first-stage confirmation information is used for indicating that all the participants agree with the configuration change request and lock corresponding resources in the service system, the first-stage confirmation information is sent after the participants calculate a first task schedule after configuration change according to current resources of the participants, and the first-stage confirmation information carries the first task schedule and the global sequence number n;
after determining that all participants in the configuration change request corresponding to the global sequence number n send second confirmation information, the coordinator stores two-stage confirmation information in the key value database in a key value pair mode, wherein the two-stage confirmation information is used for indicating all the participants to release the locked resources and finish the service configuration change requested by the configuration change request, the second confirmation information is sent after the participants determine that the first task schedule and the second task schedule are the same, and the second task schedule is a task schedule obtained after the participants calculate and obtain the configuration change according to the locked resources.
2. The method according to claim 1, wherein the step of the coordinator determining that all the participants in the configuration change request corresponding to the global sequence number n have sent first-time confirmation information comprises:
the coordinator receives the first-time confirmation information sent by each participant respectively and stores the received first-time confirmation information into the key value database respectively in a key value pair mode;
the coordinator determines whether the first-time confirmation information sent by all the participants is received by referring to key value pairs in the key value database.
3. The method according to claim 1, wherein the step of the coordinator determining that all the participants in the configuration change request corresponding to the global sequence number n have sent the second confirmation information comprises:
the coordinator receives the second confirmation information sent by each participant respectively and stores the received second confirmation information into the key value database respectively in a key value pair mode;
and the coordinator determines whether the second confirmation information sent by all the participants is received or not by referring to the key value pairs in the key value database.
4. The method of configuration change in a service system according to claim 1, further comprising, after the coordinator persists the global sequence number n and the configuration change request in a key-value pair form in a key-value database:
when the coordinator determines that any participant in the configuration change request corresponding to the global sequence number n does not send the first-time confirmation information or does not receive the first-time confirmation information sent by any participant within a preset time length, storing first-stage suspension information in a key value pair mode in the key value database;
wherein the one-phase abort information is to indicate that the participant does not agree with the configuration change request.
5. The method of configuration change in a service system according to claim 1, further comprising, after the coordinator persists the global sequence number n and the configuration change request in a key-value pair form in a key-value database:
when the coordinator determines that any participant in the configuration change request corresponding to the global sequence number n does not send the second confirmation information or does not receive the second confirmation information sent by any participant within a preset time length, storing two-stage suspension information in a key value pair mode in the key value database;
wherein the two-stage abort information is to indicate that the participant does not agree with the configuration change request.
6. The method of configuration change in a service system according to claim 4 or 5, further comprising:
and the coordinator returns configuration failure information to the user, wherein the configuration failure information is used for notifying the service configuration change failure requested by the configuration change request.
7. The method of configuration change in a service system according to any of claims 1-5, further comprising:
the coordinator receives configuration completion information sent by each participant respectively and stores the received configuration completion information into the key value database respectively in a key value pair mode, wherein the configuration completion information is sent after the participant subscribes to the two-stage confirmation information to complete the service configuration change requested by the configuration change request;
and the coordinator executes a recovery mechanism and deletes all key value pairs associated with the configuration change request in the key value database when determining that all the participants in the configuration change request corresponding to the global sequence number n send the configuration completion information or the configuration completion information sent by at least one participant is not received within a preset time length.
8. The method according to any of claims 1-5, wherein if the number of the configuration change requests is multiple, the coordinator supports processing multiple configuration change requests simultaneously in a parallel manner.
9. The method of any one of claims 1 to 5, wherein the coordinator comprises a master coordinator and a slave coordinator, and when the master coordinator is abnormal, the slave coordinator subscribes to the key-value database and replaces the master coordinator to continue completing the service configuration change requested by the configuration change request.
10. A configuration change method in a service system is applied to the service system comprising a coordinator and at least one participant, and comprises the following steps:
the participants subscribe a key value database, determine themselves as the participants of the service configuration change, and obtain a configuration change request and a global serial number n corresponding to the service configuration change, wherein the configuration change request carries configuration information and at least one participant related to configuration, and the key value database stores the global serial number n and the configuration change request in a key value pair mode;
the participant calculates a first task schedule after configuration change according to the current resources and the configuration information, and sends first confirmation information to the coordinator, wherein the first confirmation information carries the first task schedule and the global sequence number n, and the first confirmation information is used for indicating the participant to approve the configuration change request;
the participants subscribe the key value database, lock corresponding resources in the service system after obtaining one-stage confirmation information corresponding to the global serial number n, and calculate a second task schedule after configuration change again according to the locked resources and the configuration information, wherein the one-stage confirmation information is information stored in the key value database in a key value pair form after the coordinator determines that all the participants corresponding to the global serial number n send the first confirmation information;
when the first task schedule is the same as the second task schedule, the participant sends second confirmation information to the coordinator, wherein the second confirmation information carries the global sequence number n and is used for indicating that the participant agrees to the configuration change request;
the participant subscribes the key value database, releases the locked resource after obtaining the two-stage confirmation information corresponding to the global serial number n, and executes the second task schedule to complete the service configuration change requested by the configuration change request;
the second-stage confirmation information is information which is stored in the key value database in a key value pair mode after the coordinator determines that all the participants in the configuration change request corresponding to the global serial number n send the second confirmation information.
11. The method of claim 10, further comprising, after the participant recalculates the second mission schedule after the configuration change based on the locked resource and the configuration information:
and when the participant confirms that the first task schedule is different from the second task schedule, sending confirmation failure information to the coordinator, wherein the confirmation failure information is used for informing the coordinator that the first task schedule is different from the second task schedule, and the participant does not agree with the configuration change request.
12. A computer-readable storage medium having stored therein instructions which, when run on a computer, cause the computer to execute the method of configuration change in a service system according to any one of claims 1 to 9 or 10 to 11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110150713.6A CN112511359B (en) | 2021-02-04 | 2021-02-04 | Method, system and computer readable storage medium for configuration change in service system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110150713.6A CN112511359B (en) | 2021-02-04 | 2021-02-04 | Method, system and computer readable storage medium for configuration change in service system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112511359A CN112511359A (en) | 2021-03-16 |
| CN112511359B true CN112511359B (en) | 2021-05-07 |
Family
ID=74952879
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110150713.6A Active CN112511359B (en) | 2021-02-04 | 2021-02-04 | Method, system and computer readable storage medium for configuration change in service system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112511359B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114860304A (en) * | 2022-04-24 | 2022-08-05 | 网易（杭州）网络有限公司 | Configuration information processing method and device, storage medium and electronic device |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104573428A (en) * | 2013-10-12 | 2015-04-29 | 方正宽带网络服务股份有限公司 | Method and system for improving resource effectiveness of server cluster |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105991720B (en) * | 2015-02-13 | 2019-06-18 | 阿里巴巴集团控股有限公司 | Configuration change method, equipment and system |
| CN110601868B (en) * | 2018-06-13 | 2022-06-21 | 阿里巴巴集团控股有限公司 | Distributed system and method for distributing configuration information in real time and electronic equipment |
| CN111930758A (en) * | 2020-07-14 | 2020-11-13 | 广西东信互联科技有限公司 | Micro-service configuration data real-time updating method based on Paxos algorithm |
-
2021
- 2021-02-04 CN CN202110150713.6A patent/CN112511359B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104573428A (en) * | 2013-10-12 | 2015-04-29 | 方正宽带网络服务股份有限公司 | Method and system for improving resource effectiveness of server cluster |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112511359A (en) | 2021-03-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6748451B2 (en) | Distributed computing environment using real-time scheduling logic and time deterministic architecture | |
| EP1084470B1 (en) | Distributed computing environment using real-time scheduling logic and time deterministic architecture | |
| US8169856B2 (en) | Time synchronization in cluster systems | |
| CN109753364A (en) | A kind of implementation method, equipment and the medium of network-based distributed lock | |
| US5551047A (en) | Method for distributed redundant execution of program modules | |
| CA2413615C (en) | Conflict resolution for collaborative work system | |
| Keidar et al. | Moshe: A group membership service for WANs | |
| WO2023029519A1 (en) | Data synchronization method and apparatus, computer device, and storage medium | |
| CN107153660B (en) | Fault detection processing method and system for distributed database system | |
| CN113064950B (en) | Data synchronization method, device, equipment and storage medium | |
| CN109669821B (en) | Cluster part fault recovery method of message middleware, server and storage medium | |
| CN112000444B (en) | Database transaction processing method and device, storage medium and electronic equipment | |
| US20250227037A1 (en) | Node election voting methods and apparatuses based on consensus system | |
| EP4293513A1 (en) | Distributed transaction processing method and system, and related device | |
| CN112182103A (en) | Distributed database and method for realizing cross-node transaction strong consistency | |
| GB2367667A (en) | Serialising replicated transactions of a distributed computing environment | |
| CN114625489B (en) | Access request response method, device and distributed system | |
| CN107153595B (en) | Fault detection method and system for distributed database system | |
| CN111190707B (en) | Data processing method and device | |
| CN112511359B (en) | Method, system and computer readable storage medium for configuration change in service system | |
| CN111352704A (en) | Distributed global transaction processing system and method based on policy management | |
| EP4529080A1 (en) | Blockchain consensus method and apparatus | |
| CN115396296A (en) | Service processing method and device, electronic equipment and computer readable storage medium | |
| CN114500416A (en) | Delivery method and delivery system for at most one message delivery | |
| CN116107706A (en) | Transaction processing method and device of distributed database, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |