CN116582527A - Dynamic updating method, device, equipment, medium and product of distributed service - Google Patents
Dynamic updating method, device, equipment, medium and product of distributed service Download PDFInfo
- Publication number
- CN116582527A CN116582527A CN202310629324.0A CN202310629324A CN116582527A CN 116582527 A CN116582527 A CN 116582527A CN 202310629324 A CN202310629324 A CN 202310629324A CN 116582527 A CN116582527 A CN 116582527A
- Authority
- CN
- China
- Prior art keywords
- service
- countdown
- transaction
- determining
- update
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 40
- 230000003068 static effect Effects 0.000 claims abstract description 42
- 230000006855 networking Effects 0.000 claims abstract description 16
- 238000004590 computer program Methods 0.000 claims description 6
- 230000007246 mechanism Effects 0.000 abstract description 9
- 230000001960 triggered effect Effects 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 14
- 238000004891 communication Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 7
- 230000001419 dependent effect Effects 0.000 description 4
- 239000004973 liquid crystal related substance Substances 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 239000003795 chemical substances by application Substances 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/10015—Access to distributed or replicated servers, e.g. using brokers
Abstract
The embodiment of the disclosure discloses a dynamic updating method, a device, equipment, a medium and a product of distributed service, wherein the method comprises the following steps: receiving a service update request sent by equipment in a networking system and starting countdown; determining a status of the service within the countdown; and taking the time point of the service in a static state in the countdown as the starting moment of updating, and dynamically updating the service. According to the technical scheme, the countdown mechanism is introduced, the time point of the service in the static state in the countdown is used as the update starting time, so that the dynamic update of the service is triggered at a proper time, the safety of dynamic configuration is ensured, and the legal and consistent system states before and after the update are ensured.
Description
Technical Field
The disclosure relates to the technical field of intelligent networking, in particular to a dynamic updating method, device, equipment, medium and product of distributed service.
Background
Currently, in a large-scale distributed service system, the reliability, availability, reliability and maintainability of the system gradually become important factors that must be considered by a computer system, especially in some key service application fields such as: financial data processing system, medical service system, remote communication system, telecommunication online charging system, etc. In a distributed system environment like this, real-time decision support or event driven processing is often required, and once the system starts to operate, it must be kept operational all the time, and interruption of the system means a high cost and even endangers the user's life. However, such systems must keep evolving continuously during the life cycle of the software to correct software failures, extend service functions, and improve system performance. There is therefore a need for a corresponding mechanism that can support the system in a continuous operation while evolving and expanding functionality without affecting existing services, i.e. a support mechanism that enables dynamic updates of distributed services.
Disclosure of Invention
In order to solve the problems in the related art, embodiments of the present disclosure provide a method, an apparatus, a device, a medium, and a product for dynamically updating a distributed service.
In a first aspect, an embodiment of the present disclosure provides a method for dynamically updating a distributed service.
Specifically, the dynamic updating method of the distributed service comprises the following steps:
receiving a service update request sent by equipment in a networking system and starting countdown;
determining a status of the service within the countdown;
and taking the time point of the service in a static state in the countdown as the starting moment of updating, and dynamically updating the service.
According to an embodiment of the present disclosure, the determining the status of the service within the countdown includes:
analyzing the dependency relationship of the service to determine the transaction participated by the service;
and determining the state of the service in the countdown according to the execution state of the transaction.
According to an embodiment of the disclosure, the analyzing the dependency relationship of the service to determine the transaction in which the service participates includes:
determining a first transaction participated by the service according to a service instance dependency tree;
determining a second transaction participated by the service according to the root service dependency tree;
and taking the first transaction and the second transaction as the transactions participated in by the service.
According to an embodiment of the present disclosure, the service is in a stationary state during the countdown, comprising:
if the service does not participate in the first transaction and the second transaction, determining that the service is in a static state in the countdown;
if the service only participates in a first transaction and the execution ending time of the first transaction is in the countdown, determining that the service is in a static state in the countdown;
if the service only participates in a second transaction and the execution ending time of the second transaction is in the countdown, determining that the service is in a static state in the countdown;
and if the execution ending time of the first transaction and the second transaction participated by the service are in the countdown, determining that the service is in a static state in the countdown.
According to an embodiment of the present disclosure, the performing the dynamic update of the service includes:
if the service only participates in the first transaction, directly updating to the latest version of the service;
if the service only participates in the second transaction, updating to the latest version of the service on the basis of retaining the existing version of the service.
According to an embodiment of the present disclosure, the performing the dynamic update of the service includes:
configuring an update flag for the service in a stationary state during the countdown;
and dynamically updating the service according to the update mark.
In a second aspect, embodiments of the present disclosure provide a dynamic update apparatus for a distributed service.
Specifically, the dynamic updating device of the distributed service comprises:
the starting module is configured to receive a service update request sent by equipment in the networking system and start countdown;
a determining module configured to determine a status of the service within the countdown;
and the dynamic updating module is configured to take the time point of the service in a static state in the countdown as the starting moment of updating to dynamically update the service.
In a third aspect, an embodiment of the present disclosure provides an electronic device, including a memory and a processor, wherein the memory is configured to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method of any one of the first aspects.
In a fourth aspect, in an embodiment of the present disclosure, there is provided a readable storage medium having stored thereon computer instructions which, when executed by a processor, implement a method according to any of the first aspects.
In a fifth aspect, embodiments of the present disclosure provide a computer program product comprising computer instructions which, when executed by a processor, implement the method steps as described in any of the first aspects.
According to the technical scheme provided by the embodiment of the disclosure, a service update request sent by equipment in a networking system is received and countdown is started; determining a status of the service within the countdown; and taking the time point of the service in a static state in the countdown as the starting moment of updating, and dynamically updating the service. According to the technical scheme, the countdown mechanism is introduced, the time point of the service in the static state in the countdown is used as the update starting time, so that the dynamic update of the service is triggered at a proper time, the safety of dynamic configuration is ensured, and the legal and consistent system states before and after the update are ensured.
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 disclosure.
Drawings
Other features, objects and advantages of the present disclosure will become more apparent from the following detailed description of non-limiting embodiments, taken in conjunction with the accompanying drawings. In the drawings:
fig. 1 illustrates a system architecture diagram of a dynamic update method of a distributed service according to an embodiment of the present disclosure.
Fig. 2 shows a flowchart of a dynamic update method of a distributed service according to an embodiment of the present disclosure.
FIG. 3 illustrates a flow chart of a transaction that analyzes a dependency relationship determination service of a service participation in accordance with an embodiment of the present disclosure.
Fig. 4 illustrates a flow chart for dynamic updating of services according to an embodiment of the present disclosure.
Fig. 5 shows a block diagram of a dynamic update apparatus of a distributed service according to an embodiment of the present disclosure.
Fig. 6 shows a block diagram of the determination module according to an embodiment of the present disclosure.
Fig. 7 shows a schematic block diagram of an electronic device according to an embodiment of the disclosure.
Fig. 8 shows a schematic diagram of a computer system suitable for use in implementing a dynamic update method for distributed services according to an embodiment of the present disclosure.
Detailed Description
Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily implement them. In addition, for the sake of clarity, portions irrelevant to description of the exemplary embodiments are omitted in the drawings.
In this disclosure, it should be understood that terms such as "comprises" or "comprising," etc., are intended to indicate the presence of features, numbers, steps, acts, components, portions, or combinations thereof disclosed in this specification, and are not intended to exclude the possibility that one or more other features, numbers, steps, acts, components, portions, or combinations thereof are present or added.
In addition, it should be noted that, without conflict, the embodiments of the present disclosure and features of the embodiments may be combined with each other. The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
In the present disclosure, the acquisition of user information or user data is an operation that is authorized, confirmed, or actively selected by the user.
Currently, in a large-scale distributed service system, the reliability, availability, reliability and maintainability of the system gradually become important factors that must be considered by a computer system, especially in some key service application fields such as: financial data processing system, medical service system, remote communication system, telecommunication online charging system, etc. In a distributed system environment like this, real-time decision support or event driven processing is often required, and once the system starts to operate, it must be kept operational all the time, and interruption of the system means a high cost and even endangers the user's life. However, such systems must keep evolving continuously during the life cycle of the software to correct software failures, extend service functions, and improve system performance. There is therefore a need for a corresponding mechanism that can support the system in a continuous operation while evolving and expanding functionality without affecting existing services, i.e. a support mechanism that enables dynamic updates of distributed services.
In view of the above problems, in the method for dynamically updating distributed services according to the embodiments of the present disclosure, a service update request sent by a device in a networking system is received, a countdown is started, a state of the service in the countdown is determined, and a time point when the service is in a static state in the countdown is taken as an update start time to dynamically update the service. According to the technical scheme, the countdown mechanism is introduced, the time point of the service in the static state in the countdown is used as the update starting time, so that the dynamic update of the service is triggered at a proper time, the safety of dynamic configuration is ensured, and the legal and consistent system states before and after the update are ensured.
Fig. 1 illustrates a system architecture diagram of a dynamic update method of a distributed service according to an embodiment of the present disclosure. As shown in fig. 1, the system architecture includes a server 101, a plurality of devices to be updated 102, and a network 103. The server 101 may be a server, or include several servers, or be a virtualization platform, or be a cloud computing service center, or may be a device group including servers and databases. The device to be updated 102 may also be a server, or include a plurality of servers, or be a virtualized platform, or be a cloud computing service center, where a distributed service, also called a micro service, is deployed on the device to be updated 102, each service may provide one or more functions, and the services interact with each other through a specified communication protocol, where all the services are integrated to provide a basic element for normal operation of the service. The network 103 is a medium for providing a communication link between the server 101 and several devices 102 to be updated, and the network 103 may comprise various connection types, such as a wired, wireless communication link or a fiber optic cable, etc.
It should be understood that the number of servers, devices to be updated in fig. 1 is merely illustrative. There may be any number of servers, devices to be updated, as desired, and this disclosure is not limited in this regard.
Fig. 2 shows a flowchart of a dynamic update method of a distributed service according to an embodiment of the present disclosure. As shown in fig. 2, the dynamic update method of the distributed service includes steps S201 to S203:
in step S201, a service update request sent by a device in a networking system is received and a countdown is started;
in step S202, determining a status of the service within the countdown;
in step S203, a time point when the service is in a stationary state during the countdown is taken as an update start time, and dynamic update of the service is performed.
The dynamic update method of the distributed service provided by the present disclosure is applied to the server 101 shown in fig. 1, and is schematically described below with reference to fig. 1.
According to an embodiment of the present disclosure, a distributed service (hereinafter also simply referred to as a service) needs to be deployed on different devices, and a set of machines of all deployed services together constitute a business execution environment. The machine deploying the distributed service, such as the device to be updated 102 shown in fig. 1, and the server 101 shown in fig. 1, for example, constitute the networking system of the present disclosure.
According to the embodiment of the disclosure, after receiving a service update request sent by a device to be updated 102 (also referred to as a device) in a networking system, by starting countdown and identifying a state of the service, dynamic update of the service is performed only when the service is identified to be in a static state in the countdown, so that feedback of whether the device to be updated 102 is updated after the period of the countdown is obtained at maximum, long waiting is avoided, and the service is in a static state and is regarded as a security state configured dynamically, i.e. the state update service is secure for the system, thereby ensuring that the system states before and after update are legal and consistent.
According to embodiments of the present disclosure, services are not generally isolated, one service may be implementation that requires reliance on other services, as such a service may in turn be relied upon by other services. The current service-oriented distributed system provides the functional behavior description of the service when the service end registers and registers single service information, and provides the dependent service description of the service at the same time, so that the matched dependent service, possibly the service matched with the local dependence, can be searched according to the description, and the remote service can be accessed transparently through a service agent established locally for accessing the remote service.
According to the embodiment of the present disclosure, the operation of the service is based on transaction control, and the device to be updated 102 is configured with a transaction monitor responsible for transaction operation control, which generates a transaction ID when a first service request of a certain transaction arrives, and records and manages the operation of each service in units of transactions.
According to an embodiment of the disclosure, the determining the status of the service in step S202 includes:
analyzing the dependency relationship of the service and determining the transaction participated by the service;
and determining the state of the service in the countdown according to the execution state of the transaction.
In the method, the dependency relationship of the service is analyzed, the service and the service with the dependency relationship are analyzed, and then the transaction participated by the service is determined, so that the state of the service in the countdown is determined based on the execution state of the transaction, and whether the service is in a static state is further identified.
FIG. 3 illustrates a flow chart of a transaction that analyzes a dependency relationship determination service of a service participation in accordance with an embodiment of the present disclosure. As shown in fig. 3, the analyzing the dependency relationship of the service determines the transaction in which the service participates, including steps S301-S303:
in step S301, determining a first transaction in which the service participates according to a service instance dependency tree;
in step S302, determining a second transaction in which the service participates according to the root service dependency tree;
in step S303, the first transaction and the second transaction are used as transactions in which the service participates.
In the present disclosure, transactions in which a service participates may be classified into two types, one being a transaction that the service initiates itself, and the other being a related transaction that the service initiates as a root service. Thus, identifying that the service is in a stationary state determines the two types of transactions, namely the first transaction and the second transaction. The first transaction, i.e. the transaction started by the service itself, can be determined by the service instance dependency tree. The second transaction, i.e., the related transaction that is initiated as the root service, may be determined by the root service dependency tree. The construction of the service instance dependency tree and the root service dependency tree can refer to the prior art, and are not used as the key points of the application, and are not repeated here. After the first transaction and the second transaction are obtained, the first transaction and the second transaction are taken as the transactions participated in by the service.
According to an embodiment of the present disclosure, the service in step S203 is in a stationary state during the countdown, including:
if the service does not participate in the first transaction and the second transaction, determining that the service is in a static state in the countdown;
if the service only participates in a first transaction and the execution ending time of the first transaction is in the countdown, determining that the service is in a static state in the countdown;
if the service only participates in a second transaction and the execution ending time of the second transaction is in the countdown, determining that the service is in a static state in the countdown;
and if the execution ending time of the first transaction and the second transaction participated by the service are in the countdown, determining that the service is in a static state in the countdown.
Fig. 4 illustrates a flow chart for dynamic updating of services according to an embodiment of the present disclosure. As shown in fig. 4, the dynamic update of the service is performed in step S203, which includes steps S401 to S402:
in step S401, if the service only participates in the first transaction, directly updating to the latest version of the service;
in step S402, if the service participates in only the second transaction, the latest version of the service is updated on the basis of retaining the existing version of the service.
In the method, if the service only participates in the first transaction, the coexistence problem of the new version and the old version is not needed to be considered, and the service is directly updated to the latest version; if the service only participates in the second transaction, taking the fact that the execution time of the second transaction is longer into consideration, an old and new version coexistence strategy is adopted, namely updating to the latest version of the service on the basis of keeping the existing version of the service so as to ensure the consistency of the running states of the old and new versions.
The embodiment of the present disclosure further provides another manner of performing dynamic update of the service in step S203, including:
configuring an update flag for the service in a stationary state during the countdown;
and dynamically updating the service according to the update mark.
In this disclosure, an update flag may be configured for the service in a static state during countdown, and for at least one device to be updated 102 that needs to be updated, the service configured with the same update flag may be updated together, thereby improving efficiency.
Fig. 5 shows a block diagram of a dynamic update apparatus of a distributed service according to an embodiment of the present disclosure. The apparatus may be implemented as part or all of an electronic device by software, hardware, or a combination of both.
As shown in fig. 5, the dynamic update apparatus 500 of a distributed service includes: a startup module 510, a determination module 520, and a dynamic update module 530.
The starting module 510 is configured to receive a service update request sent by a device in the networking system and start countdown;
the determination module 520 is configured to determine a status of the service within the countdown;
the dynamic update module 530 is configured to perform dynamic update of the service using a time point at which the service is in a stationary state during the countdown as an update start time.
According to the dynamic updating device for the distributed service, a countdown mechanism is introduced, and a time point of the service in a static state in the countdown is used as an updating starting time, so that the dynamic updating of the service is triggered at a proper time, the safety of dynamic configuration is ensured, and the legal and consistent system states before and after updating are ensured.
According to an embodiment of the present disclosure, a distributed service (hereinafter also simply referred to as a service) needs to be deployed on different devices, and a set of machines of all deployed services together constitute a business execution environment. The machine deploying the distributed service, such as the device to be updated 102 shown in fig. 1, and the server 101 shown in fig. 1, for example, constitute the networking system of the present disclosure.
According to the embodiment of the disclosure, after receiving a service update request sent by a device to be updated 102 (also referred to as a device) in a networking system, the server 101 identifies the state of the service by starting countdown, and dynamically updates the service only when the service is identified to be in a static state in the countdown, so that feedback of whether the device to be updated 102 is updated after the period of the countdown is obtained at maximum, long waiting is avoided, and the service is in a static state and is regarded as a dynamically configured safe state, i.e. the state update service is safe for the system, thereby ensuring that the system states before and after the update are legal and consistent.
According to embodiments of the present disclosure, services are not generally isolated, one service may be implementation that requires reliance on other services, as such a service may in turn be relied upon by other services. The current service-oriented distributed system provides the functional behavior description of the service when the service end registers and registers single service information, and provides the dependent service description of the service at the same time, so that the matched dependent service, possibly the service matched with the local dependence, can be searched according to the description, and the remote service can be accessed transparently through a service agent established locally for accessing the remote service.
According to the embodiment of the present disclosure, the operation of the service is based on transaction control, and the device to be updated 102 is configured with a transaction monitor responsible for transaction operation control, which generates a transaction ID when a first service request of a certain transaction arrives, and records and manages the operation of each service in units of transactions.
According to an embodiment of the disclosure, the portion of the determining module that determines the status of the service within the countdown is configured to:
analyzing the dependency relationship of the service and determining the transaction participated by the service;
and determining the state of the service in the countdown according to the execution state of the transaction.
In the method, the dependency relationship of the service is analyzed, the service and the service with the dependency relationship are analyzed, and then the transaction participated by the service is determined, so that the state of the service in the countdown is determined based on the execution state of the transaction, and whether the service is in a static state is further identified.
Fig. 6 shows a block diagram of the determination module according to an embodiment of the present disclosure. As shown in fig. 6, the determining module 520 includes:
a first determination submodule 521 configured to determine a first transaction in which the service participates according to the service instance dependency tree;
a second determination submodule 522 configured to determine a second transaction in which the service participates from the root service dependency tree;
a transaction module 523 configured to take the first transaction and the second transaction as the transactions in which the service participates.
In the present disclosure, transactions in which a service participates may be classified into two types, one being a transaction that the service initiates itself, and the other being a related transaction that the service initiates as a root service. Thus, identifying that the service is in a stationary state determines the two types of transactions, namely the first transaction and the second transaction. The first transaction, i.e. the transaction started by the service itself, can be determined by the service instance dependency tree. The second transaction, i.e., the related transaction that is initiated as the root service, may be determined by the root service dependency tree. The construction of the service instance dependency tree and the root service dependency tree can refer to the prior art, and are not used as the key points of the application, and are not repeated here. After the first transaction and the second transaction are obtained, the first transaction and the second transaction are taken as the transactions participated in by the service.
According to an embodiment of the present disclosure, the service is in a stationary state during the countdown, comprising:
if the service does not participate in the first transaction and the second transaction, determining that the service is in a static state in the countdown;
if the service only participates in a first transaction and the execution ending time of the first transaction is in the countdown, determining that the service is in a static state in the countdown;
if the service only participates in a second transaction and the execution ending time of the second transaction is in the countdown, determining that the service is in a static state in the countdown;
and if the execution ending time of the first transaction and the second transaction participated by the service are in the countdown, determining that the service is in a static state in the countdown.
According to an embodiment of the present disclosure, the portion of the dynamic update module that performs the dynamic update of the service is configured to:
if the service only participates in the first transaction, directly updating to the latest version of the service;
if the service only participates in the second transaction, updating to the latest version of the service on the basis of retaining the existing version of the service.
In the method, if the service only participates in the first transaction, the coexistence problem of the new version and the old version is not needed to be considered, and the service is directly updated to the latest version; if the service only participates in the second transaction, taking the fact that the execution time of the second transaction is longer into consideration, an old and new version coexistence strategy is adopted, namely updating to the latest version of the service on the basis of keeping the existing version of the service so as to ensure the consistency of the running states of the old and new versions.
According to an embodiment of the present disclosure, the portion of the dynamic update module that performs the dynamic update of the service is configured to:
configuring an update flag for the service in a stationary state during the countdown;
and dynamically updating the service according to the update mark.
In this disclosure, an update flag may be configured for the service in a static state during countdown, and for at least one device to be updated 102 that needs to be updated, the service configured with the same update flag may be updated together, thereby improving efficiency.
The present disclosure also discloses an electronic device, fig. 7 shows a schematic block diagram of the electronic device according to an embodiment of the present disclosure, and as shown in fig. 7, the electronic device 700 includes a memory 701 and a processor 702; wherein, the liquid crystal display device comprises a liquid crystal display device,
the memory 701 is used to store one or more computer instructions that are executed by the processor 702 to implement any of the methods of the disclosed embodiments.
Receiving a service update request sent by equipment in a networking system and starting countdown;
determining a status of the service within the countdown;
and taking the time point of the service in a static state in the countdown as the starting moment of updating, and dynamically updating the service.
According to the dynamic updating method of the distributed service, a service updating request sent by equipment in a networking system is received, countdown is started, the state of the service in the countdown is determined, and the time point of the service in a static state in the countdown is used as the starting moment of updating to dynamically update the service. According to the technical scheme, the countdown mechanism is introduced, the time point of the service in the static state in the countdown is used as the update starting time, so that the dynamic update of the service is triggered at a proper time, the safety of dynamic configuration is ensured, and the legal and consistent system states before and after the update are ensured.
According to an embodiment of the present disclosure, the determining the status of the service within the countdown includes:
analyzing the dependency relationship of the service to determine the transaction participated by the service;
and determining the state of the service in the countdown according to the execution state of the transaction.
According to an embodiment of the disclosure, the analyzing the dependency relationship of the service to determine the transaction in which the service participates includes:
determining a first transaction participated by the service according to a service instance dependency tree;
determining a second transaction participated by the service according to the root service dependency tree;
and taking the first transaction and the second transaction as the transactions participated in by the service.
According to an embodiment of the present disclosure, the service is in a stationary state during the countdown, comprising:
if the service does not participate in the first transaction and the second transaction, determining that the service is in a static state in the countdown;
if the service only participates in a first transaction and the execution ending time of the first transaction is in the countdown, determining that the service is in a static state in the countdown;
if the service only participates in a second transaction and the execution ending time of the second transaction is in the countdown, determining that the service is in a static state in the countdown;
and if the execution ending time of the first transaction and the second transaction participated by the service are in the countdown, determining that the service is in a static state in the countdown.
According to an embodiment of the present disclosure, the performing the dynamic update of the service includes:
if the service only participates in the first transaction, directly updating to the latest version of the service;
if the service only participates in the second transaction, updating to the latest version of the service on the basis of retaining the existing version of the service.
According to an embodiment of the present disclosure, the performing the dynamic update of the service includes:
configuring an update flag for the service in a stationary state during the countdown;
and dynamically updating the service according to the update mark.
Fig. 8 shows a schematic diagram of a computer system suitable for use in implementing a dynamic update method for distributed services according to an embodiment of the present disclosure.
As shown in fig. 8, the computer system 800 includes a processing unit 801 that can execute various processes in the above-described embodiments according to a program stored in a Read Only Memory (ROM) 802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. In the RAM803, various programs and data required for the operation of the system 800 are also stored. The CPU801, ROM802, and RAM803 are connected to each other by a bus 804. An input/output (I/O) interface 805 is also connected to the bus 804.
The following components are connected to the I/O interface 805: an input portion 806 including a keyboard, mouse, etc.; an output portion 807 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage section 808 including a hard disk or the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. The drive 810 is also connected to the I/O interface 805 as needed. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as needed so that a computer program read out therefrom is mounted into the storage section 808 as needed. The processing unit 801 may be implemented as a processing unit such as CPU, GPU, TPU, FPGA, NPU.
In particular, according to embodiments of the present disclosure, the methods described above may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising computer instructions which, when executed by a processor, implement the method steps described above. In such embodiments, the computer program product may be downloaded and installed from a network via communication portion 809, and/or installed from removable media 811.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units or modules referred to in the embodiments of the present disclosure may be implemented in software or in programmable hardware. The units or modules described may also be provided in a processor, the names of which in some cases do not constitute a limitation of the unit or module itself.
As another aspect, the present disclosure also provides a computer-readable storage medium, which may be a computer-readable storage medium included in the electronic device or the computer system in the above-described embodiments; or may be a computer-readable storage medium, alone, that is not assembled into a device. The computer-readable storage medium stores one or more programs for use by one or more processors in performing the methods described in the present disclosure.
The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by those skilled in the art that the scope of the application referred to in this disclosure is not limited to the specific combination of features described above, but encompasses other embodiments in which any combination of features described above or their equivalents is contemplated without departing from the inventive concepts described. Such as those described above, are mutually substituted with the technical features having similar functions disclosed in the present disclosure (but not limited thereto).
Claims (10)
1. A method for dynamic updating of distributed services, comprising:
receiving a service update request sent by equipment in a networking system and starting countdown;
determining a status of the service within the countdown;
and taking the time point of the service in a static state in the countdown as the starting moment of updating, and dynamically updating the service.
2. The method of claim 1, the determining a status of the service within the countdown comprising:
analyzing the dependency relationship of the service to determine the transaction participated by the service;
and determining the state of the service in the countdown according to the execution state of the transaction.
3. The method of claim 2, the analyzing the dependencies of the service to determine transactions in which the service participates, comprising:
determining a first transaction participated by the service according to a service instance dependency tree;
determining a second transaction participated by the service according to the root service dependency tree;
and taking the first transaction and the second transaction as the transactions participated in by the service.
4. A method according to claim 3, the service being in a stationary state during the countdown, comprising:
if the service does not participate in the first transaction and the second transaction, determining that the service is in a static state in the countdown;
if the service only participates in a first transaction and the execution ending time of the first transaction is in the countdown, determining that the service is in a static state in the countdown;
if the service only participates in a second transaction and the execution ending time of the second transaction is in the countdown, determining that the service is in a static state in the countdown;
and if the execution ending time of the first transaction and the second transaction participated by the service are in the countdown, determining that the service is in a static state in the countdown.
5. The method of claim 3 or 4, the performing a dynamic update of the service comprising:
if the service only participates in the first transaction, directly updating to the latest version of the service;
if the service only participates in the second transaction, updating to the latest version of the service on the basis of retaining the existing version of the service.
6. The method of claim 1, the performing the dynamic update of the service comprising:
configuring an update flag for the service in a stationary state during the countdown;
and dynamically updating the service according to the update mark.
7. A dynamic update apparatus for a distributed service, comprising:
the starting module is configured to receive a service update request sent by equipment in the networking system and start countdown;
a determining module configured to determine a status of the service within the countdown;
and the dynamic updating module is configured to take the time point of the service in a static state in the countdown as the starting moment of updating to dynamically update the service.
8. An electronic device includes a memory and a processor; wherein the memory is for storing one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method steps of any of claims 1-6.
9. A readable storage medium having stored thereon computer instructions, which when executed by a processor, implement the method steps of any of claims 1-6.
10. A computer program product comprising computer instructions which, when executed by a processor, implement the method steps of any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310629324.0A CN116582527A (en) | 2023-05-31 | 2023-05-31 | Dynamic updating method, device, equipment, medium and product of distributed service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310629324.0A CN116582527A (en) | 2023-05-31 | 2023-05-31 | Dynamic updating method, device, equipment, medium and product of distributed service |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116582527A true CN116582527A (en) | 2023-08-11 |
Family
ID=87545162
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310629324.0A Pending CN116582527A (en) | 2023-05-31 | 2023-05-31 | Dynamic updating method, device, equipment, medium and product of distributed service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116582527A (en) |
-
2023
- 2023-05-31 CN CN202310629324.0A patent/CN116582527A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10735345B2 (en) | Orchestrating computing resources between different computing environments | |
| US10891122B2 (en) | Rolling upgrade of a distributed application | |
| US10621651B2 (en) | Automatic recharge system and method, and server | |
| Rankin | The software testing automation framework | |
| CN109783151B (en) | Method and device for rule change | |
| CN114996337A (en) | Multi-cluster database management system and method | |
| CN109445937A (en) | A kind of modularization programming and seamless execution method | |
| CN115167874B (en) | Automatic driving software mirror image deployment method and device, electronic equipment and readable medium | |
| CN115390897B (en) | Micro front end management method, micro front end management device, electronic equipment and storage medium | |
| FR3003365A1 (en) | METHOD AND DEVICE FOR MANAGING SOFTWARE UPDATES OF A SET OF EQUIPMENT OF A SYSTEM SUCH AS A SYSTEM OF AN AIRCRAFT | |
| CN116582527A (en) | Dynamic updating method, device, equipment, medium and product of distributed service | |
| CN116069366A (en) | Client application program updating method and device, storage medium and electronic equipment | |
| CN112559001B (en) | Method and device for updating application | |
| JP4882291B2 (en) | Module update program | |
| CN112636986A (en) | Gateway plug-in updating method and device | |
| US10140155B2 (en) | Dynamically provisioning, managing, and executing tasks | |
| US11907364B2 (en) | Managing incompliances identified at instances of cloud applications | |
| CN111858234A (en) | Task execution method, device, equipment and medium | |
| CN107678840B (en) | System, method and device for running tasks | |
| CN114240265B (en) | Product deployment method and device based on mixed environment | |
| US11977922B2 (en) | Resource reuse for pipeline workloads | |
| US11966723B2 (en) | Automatic management of applications in a containerized environment | |
| CN116820526B (en) | Operating system upgrading method, device, equipment and storage medium | |
| US11086549B2 (en) | Just-in-time data migration in a live system | |
| US20240012631A1 (en) | Remediation engine for updating desired state of inventory data to be replicated across multiple software-defined data centers |
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 |