CN112905341A - Distributed load balancing service information continuous inheritance method and device - Google Patents
Distributed load balancing service information continuous inheritance method and device Download PDFInfo
- Publication number
- CN112905341A CN112905341A CN202110180542.1A CN202110180542A CN112905341A CN 112905341 A CN112905341 A CN 112905341A CN 202110180542 A CN202110180542 A CN 202110180542A CN 112905341 A CN112905341 A CN 112905341A
- Authority
- CN
- China
- Prior art keywords
- service
- service information
- changed
- load balancing
- distributed load
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 159
- 230000008569 process Effects 0.000 claims abstract description 108
- 230000008859 change Effects 0.000 claims abstract description 71
- 238000012544 monitoring process Methods 0.000 claims abstract description 21
- 230000036541 health Effects 0.000 claims description 17
- 238000004590 computer program Methods 0.000 claims description 13
- 238000012545 processing Methods 0.000 claims description 7
- 230000008901 benefit Effects 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 14
- 238000001514 detection method Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 6
- 230000004044 response Effects 0.000 description 6
- 238000011161 development Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000012827 research and development Methods 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000000750 progressive effect Effects 0.000 description 2
- 108010001267 Protein Subunits Proteins 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 239000007795 chemical reaction product Substances 0.000 description 1
- 238000011217 control strategy Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5083—Techniques for rebalancing the load in a distributed system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Mathematical Physics (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention provides a method and a device for continuously inheriting distributed load balancing service information, which can be applied to the field of finance, and the method comprises the following steps: monitoring a service change instruction sent by an external server or an internal server in real time; stopping the current process and saving the service information which does not need to be changed in the current process into a temporary storage file according to the service change instruction; changing the service information needing to be changed in the current process according to the service change instruction; and initializing the process according to the service information in the temporary storage file. The method and the device have the advantages that the service information which does not need to be updated is stored outside the process, then the service information which needs to be updated is updated, the process is initialized by the service information which does not need to be updated, the service information is updated pertinently instead of all the service information, timely and dynamic updating of the changed service information can be guaranteed, and continuous succession of the service information which does not change is not influenced.
Description
Technical Field
The application belongs to the technical field of agile iterative research and development, and particularly relates to a method and a device for continuously inheriting distributed load balancing service information.
Background
In agile development, a software project is cut into a plurality of small projects, and the small projects are respectively completed, and the software is always in a usable state in the process. The agile development model has the advantages of sensitive market reaction, rapid problem response, high early-stage customer satisfaction and the like, but also brings the problem of how to ensure the stability and continuity of the service while agile iteration is carried out.
Assuming that a service a runs on a specific process α, the service a needs to update part of the content according to the customer's needs. The start-stop mode is usually adopted, i.e. the old process α is stopped and then the new process β is started to load the updated service content. Some methods can achieve the effect that new service content can be loaded without starting and stopping the process, but these methods often cause other problems (such as performance overhead), and once a process failure occurs, service information in the process is lost.
In the conventional service updating method, in the process of stopping an old process α and restarting a new process β (the process β is substantially the process α after completing the service update), the content of the part of the service a that does not need to be updated and the content of other services running on the process α are all reloaded, so that a large amount of unnecessary service interruption is caused, and the risk of influencing the on-the-road service is caused. This risk is not negligible in a large-scale distributed load balancing scenario where frequent content updates are required under agile development models.
Disclosure of Invention
The application provides a method and a device for continuously inheriting distributed load balancing service information, which are used for at least solving the problem that a large amount of contents which do not need to be updated in a process can be reloaded when the service information is updated under a current agile development model.
According to an aspect of the present application, a method for continuously inheriting distributed load balancing service information is provided, including:
monitoring a service change instruction sent by an external server or an internal server in real time;
stopping the current service process after monitoring the service change instruction, and changing the service information needing to be changed in the current service process according to the service change instruction;
and initializing the process of completing the service information change according to the service information which does not need to be changed.
In an embodiment, the distributed load balancing service information continuous inheritance method further includes:
extracting the name of the service to be changed from the service change instruction;
determining services which do not need to be changed in the current process according to the names of the services which need to be changed;
and saving the service information which does not need to be changed into a temporary storage file.
In an embodiment, changing service information that needs to be changed in a current process according to a service change instruction includes:
searching the service needing to be changed from the current process according to the name of the service needing to be changed;
and changing the service information corresponding to the service needing to be changed according to the service change instruction.
In an embodiment, the distributed load balancing service information continuous inheritance method further includes:
and when the service information does not exist in the temporary storage file, initializing the process according to preset initialization service information.
In an embodiment, the distributed load balancing service information continuous inheritance method further includes:
and carrying out health state check on the servers under the distributed load balancing architecture and marking the health state of each server.
According to another aspect of the present application, there is also provided a distributed load balancing service information continuous inheritance device, including:
the monitoring unit is used for monitoring a service change instruction sent by an external server or an internal server in real time;
the service information changing unit is used for stopping the current service process after monitoring the service changing instruction and changing the service information needing to be changed in the current service process according to the service changing instruction;
and the reinitialization unit is used for initializing the process of completing the service information change according to the service information which does not need to be changed.
In one embodiment, the service information changing unit includes:
the extracting module is used for extracting the name of the service needing to be changed from the service changing instruction;
the determining module is used for determining services which do not need to be changed in the current service process according to the names of the services which need to be changed;
and the storage module is used for storing the service information which does not need to be changed into a storage file.
In one embodiment, the service information changing unit further includes:
the searching module is used for searching the service needing to be changed from the current process according to the name of the service needing to be changed;
and the changing module is used for changing the service information corresponding to the service needing to be changed according to the service changing instruction.
In an embodiment, the distributed load balancing service information continuous inheritance device further includes:
and the original initialization processing unit is used for initializing the process according to the preset initialization service information when the service information does not exist in the temporary storage file.
In an embodiment, the distributed load balancing service information continuous inheritance device further includes:
and the health state checking unit is used for carrying out health state checking on the servers under the distributed load balancing architecture and marking the health state of each server.
The method and the device aim to solve the problem that the traditional service updating mode can cause service influence under an agile iterative research and development model. According to the method and the device, the service information which does not need to be updated is stored outside the process, then the service information which needs to be updated is updated, and then the process is initialized by the service information which does not need to be updated, so that the service information is updated pertinently instead of all the service information, timely and dynamic updating of the changed service information can be guaranteed, continuous inheritance of the service information which does not change is guaranteed to be unaffected, and agile, continuous, accurate and stable operation of the distributed load balancing service is guaranteed.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1A is a flowchart of a method for continuously inheriting information of a distributed load balancing service provided by the present application.
Fig. 1B is a flowchart of a method for continuously inheriting service information in an embodiment of the present application.
Fig. 2 is a flowchart of temporarily storing service information that does not need to be changed in the embodiment of the present application.
Fig. 3 is a flowchart illustrating a change of service information according to a service change instruction in an embodiment of the present application.
Fig. 4 is a schematic diagram illustrating a service information change in a conventional mode.
Fig. 5 is a schematic diagram of service information change after the method is applied.
Fig. 6 is a block diagram of a distributed load balancing service information continuous inheritance device provided in the present application.
Fig. 7 is a block diagram of a service information storage unit in the embodiment of the present application.
Fig. 8 is a block diagram showing a configuration of a service information changing unit in the embodiment of the present application.
Fig. 9 is a schematic structural diagram of an electronic device in an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention. The embodiments of the present application can be applied to the financial field, and can also be applied to other fields, and the present application is not limited thereto.
In an agile iterative development mode, in the conventional service updating method, in the process of stopping an old process α and restarting a new process β (the process β is substantially the process α after completing service update), the content of the part of the service a that does not need to be updated and the content of other services running on the process α are all reloaded, so that a large amount of unnecessary service interruption is caused, and the risk of affecting the on-the-way service is caused.
In order to solve the problem of the conventional service update mode, the present application provides a method for continuously inheriting distributed load balancing service information, as shown in fig. 1A, including:
s1: monitoring a service change instruction sent by an external server or an internal server in real time;
s2: stopping the current service process after monitoring a service change instruction, and changing service information needing to be changed in the current service process according to the service change instruction;
s3: and initializing the process of completing the service information change according to the service information which does not need to be changed.
In one embodiment, the method is implemented as shown in fig. 1B:
s101: and monitoring a service change instruction sent by the external server or the internal server in real time.
S102: and stopping the current process and storing the service information which does not need to be changed in the current process into a temporary storage file according to the service change instruction after monitoring the service change instruction.
S103: and changing the service information needing to be changed in the current process according to the service change instruction.
S104: and initializing the process of finishing the service information change according to the service information in the temporary storage file.
Detecting a demand change signal (service change instruction) sent by a certain server or an external server in the distributed load balancing architecture in real time, triggering a process restart flow if the demand change exists, and continuing the current process to provide services if the demand change does not exist. Starting a new process after the initialization task is completed; and stopping the old process after the new process is successfully started. In addition, whether the new process needs to adjust the service information data structure can be judged through the requirement changing signal.
In an embodiment, saving service information that does not need to be changed in a current process to a temporary storage file according to a service change instruction, as shown in fig. 2, includes:
s201: the name of the service to be changed is extracted from the service change instruction.
S202: and determining the services which do not need to be changed in the current process according to the names of the services which need to be changed.
S203: and saving the service information which does not need to be changed into a temporary storage file.
In a specific embodiment, a server a (or a client server outside the distributed load balancing architecture) in the server cluster under the distributed load balancing architecture needs to update the service information Info _ Z4, and the server a sends a signal (a service change instruction), and stops the current process α (a plurality of services are run on one process, and each service is executed by one server) when monitoring the service change instruction. If the service change instruction includes the service information Info _ Z4 that needs to be changed, the service information Info _ a1 … Info _ Z3 that does not need to be changed is saved in the temporary storage file MEMORY _ LAST.
In another embodiment of the present application, the service change instruction initiated by the external server can also be captured in real time from the traffic flow, because in practical application, the service change instruction can be initiated by the server cluster itself or can be given by the external.
In an embodiment, changing the service information that needs to be changed in the current process according to the service change instruction, as shown in fig. 3, includes:
s301: and searching the service needing to be changed from the current process according to the name of the service needing to be changed.
S302: and changing the service information corresponding to the service needing to be changed according to the service change instruction.
In a specific embodiment, the target service information to be changed is Info _ Z4 extracted from the service change instruction, then the Info _ Z4 is searched from the current process α, and the Info _ Z4 is updated to Info _ Z4'.
After the conventional service updating method is changed, a service information diagram in the process is shown in fig. 4:
when the distributed load balancing service process proxy _ worker _ old works, service information info _ A1, info _ A2, info _ A3, info _ A4, info _ B1, info _ B2, info _ B3, info _ B4, … …, info _ Z1, info _ Z2, info _ Z3 and info _ Z4 of many application servers such as server _ A, server _ B … … server _ Z and the like are carried. The service information data structures of the same type of distributed load balancing service provided by the same process are consistent. Due to the change in business requirements, info _ Z4 needs to be updated to info _ Z4'. After the proxy _ worker _ old process is stopped and the proxy _ worker _ new process is started, all information of server _ a is affected to become info _ a1 ', info _ a 2', info _ A3 'and info _ a 4'. All information of server _ B is affected to become info _ B1 ', info _ B2', info _ B3 ', info _ B4'. Other information info _ Z1, info _ Z2, and info _ Z3 that the server _ Z does not need to be changed are also affected, and become info _ Z1 ', info _ Z2 ', and info _ Z3 '.
After the persistent inheritance service information is updated according to the scheme, a service information schematic diagram in a process is shown in fig. 5:
when the distributed load balancing service process proxy _ worker _ old works, service information info _ A1, info _ A2, info _ A3, info _ A4, info _ B1, info _ B2, info _ B3, info _ B4, … …, info _ Z1, info _ Z2, info _ Z3 and info _ Z4 of many application servers such as server _ A, server _ B … … server _ Z and the like are carried. The service information data structures of the same type of distributed load balancing service provided by the same process are consistent. Due to the change in business requirements, info _ Z4 needs to be updated to info _ Z4'. After the proxy _ worker _ old process is stopped and the proxy _ worker _ new process is started, all information of server _ A is not affected and still remains as info _ A1, info _ A2, info _ A3 and info _ A4. All information of server _ B is not affected, and still remains as info _ B1, info _ B2, info _ B3 and info _ B4. The other information info _ Z1, info _ Z2, info _ Z3 of server _ Z that does not need to be changed are also unaffected.
The executing main bodies of the methods shown in fig. 1A, 1B, 2, and 3 may be a PC, a computer, a server, a terminal, and the like, and the service information that does not need to be updated is saved outside the process, the service information that needs to be updated is updated, and the process is initialized by using the service information that does not need to be updated, so that the service information is updated in a targeted manner instead of updating all the service information, which not only ensures that the changed service information is dynamically updated in time, but also ensures that the unchanged service information is continuously inherited without being affected, thereby ensuring that the distributed load balancing service operates agilely, continuously, accurately, and stably.
In an embodiment, the distributed load balancing service information continuous inheritance method further includes:
and when the service information does not exist in the temporary storage file, initializing the process according to preset initialization service information.
In one embodiment, the user customizes the service information data structure and customizes the content in the service information default template. When the temporary storage file MEMORY _ LAST does not have any service information (possibly because MEMORY _ LAST is unavailable or lost due to some uncontrollable factors), the content in the default template is used to initialize the new service process, and the new process is restarted after the initialization is completed and called.
In an embodiment, the distributed load balancing service information continuous inheritance method further includes:
and carrying out health state check on the servers under the distributed load balancing architecture and marking the health state of each server.
In an embodiment, a health check is performed on a server under a distributed load balancing architecture, and first, service information included in a service process includes an identifier in an availability state, and a total of six identifier bits: available, unavailable, becoming available, becoming unavailable, disabled, standby.
a) The server in the available state can receive the service request distributed by the distributed load balancing group;
b) the server in the unavailable state can be subjected to fault isolation, and is not allowed to receive the front-end service request distributed by the distributed load balancing group;
c) the condition that the server is becoming available is that when the distributed load balancing group performs availability detection on each server in the application server group, in order to eliminate the interference of accidental factors, the current state is not changed because 1 detection passes or does not pass, but M times of detection is required (1 < M <5 is generally recommended), if the M times of detection results are consistent and different from the current state, the current availability state is changed, and if a certain server is in an unavailable state, N times of detection results (1 is not more than N < M) are in an available state, the current state is required to be available;
d) if a certain server is in an available state originally, detecting results N times (N is more than or equal to 1 and less than M) to be in an unavailable state, and then the current state is to become unavailable;
e) if a certain server in the application server group is set to be in a forbidden state, the distributed load balancing group does not carry out availability detection on the server, and the server is directly isolated;
f) if a certain server in the application server group is set to be in a standby state, the server indicates that the distributed load balancing group cannot detect the availability of the server when the non-standby servers in the application server group in which the server is located are in an available state, and the server is isolated by default; when the non-standby servers in the application server group where the server is located are all in the unavailable state, the distributed load balancing group can detect the availability of the server, if the detection result is available, the distributed load balancing group is set to be in the available state, and if the detection result is unavailable, the distributed load balancing group is set to be in the unavailable state and isolates the server.
And recording the current performance index service condition of each server in the application server group so as to set an optimal service distribution rule according to different service types and different performance indexes. The performance indexes mainly comprise: CPU utilization rate, memory utilization rate, current connection number, response time and response error reporting number. The invention supports selecting different performance indexes according to different types of services, for example, the computing service generally selects CPU utilization rate as the index, and preferentially distributes the computing request to the available server with the lowest current CPU utilization rate; the read-write service generally selects the memory utilization rate as an index, and preferentially distributes the calculation type request to an available server with the lowest current memory utilization rate; the service type of the long connection generally uses the current connection number as an index, and preferentially distributes the calculation type request to the available server with the minimum current connection number; for services with higher response time requirements, the response time can be selected as an index; for services with higher accuracy requirements, available servers with lower response error reporting numbers should be selected.
And recording the service correlation strategy information corresponding to each server in the application server group so as to provide the optimal service distribution service. The content mainly comprises: security control strategy, priority strategy, mapping relation strategy and cache content strategy. The security control policy means that the distributed load balancing server should follow a formulated security access control rule when forwarding the traffic flow, for example, if an application server has reached a threshold of a tolerable concurrency number, the distributed load balancing server should not forward the traffic flow to the application server. The priority policy means that the distributed load balancing server may distribute traffic according to a certain priority order when forwarding the traffic, for example, if the priority of the a application server is higher than that of the B application server, the traffic should be preferentially distributed to the a application server under the condition that the health check state of the a server is good. The mapping relationship policy means that in some service scenarios, a service logic dependency relationship may exist among the client, the WEB application server, and the APP application server, and the distributed load balancing server should forward the service traffic to the application server having the relevant service logic dependency relationship when forwarding the service traffic. The cache content policy is used for marking whether a certain back-end application server starts a cache mechanism, and the distributed load balancing server can preferentially forward the request to the back-end application server with the cache.
In another embodiment of the present application, other service information types may also be defined according to personalized application requirements, belonging to the reserved extensible field.
Based on the same inventive concept, the embodiment of the present application further provides a device for continuously inheriting distributed load balancing service information, which can be used to implement the method described in the above embodiment, as described in the following embodiment. Because the principle of the distributed load balancing service information continuous inheritance device for solving the problem is similar to that of the distributed load balancing service information continuous inheritance method, the implementation of the distributed load balancing service information continuous inheritance device can refer to the implementation of the distributed load balancing service information continuous inheritance method, and repeated parts are not described again. As used hereinafter, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. While the system described in the embodiments below is preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.
Therefore, the present application further provides a device for continuously inheriting distributed load balancing service information, as shown in fig. 6, including:
a monitoring unit 601, configured to monitor a service change instruction sent by an external server or an internal server in real time;
a service information storage unit 602, configured to stop the current process and store, according to the service change instruction, service information that does not need to be changed in the current process into a temporary storage file after the service change instruction is monitored;
a service information changing unit 603 configured to change service information that needs to be changed in the current process according to the service change instruction;
a reinitialization unit 604, configured to perform initialization processing on the process of completing the service information change according to the service information in the temporary storage file.
In one embodiment, as shown in fig. 7, the service information storage unit 602 includes:
an extracting module 701, configured to extract a name of a service to be changed from the service change instruction;
a determining module 702, configured to determine, according to a name of a service that needs to be changed, a service that does not need to be changed in a current process;
the storage module 703 is configured to store the service information that does not need to be changed in the temporary storage file.
In one embodiment, as shown in fig. 8, the service information changing unit 603 includes:
a searching module 801, configured to search for a service that needs to be changed from a current process according to a name of the service that needs to be changed;
a changing module 802, configured to change service information corresponding to a service that needs to be changed according to a service change instruction.
In an embodiment, the distributed load balancing service information continuous inheritance device further includes:
and the original initialization processing unit is used for initializing the process according to the preset initialization service information when the service information does not exist in the temporary storage file.
In an embodiment, the distributed load balancing service information continuous inheritance device further includes:
and the health state checking unit is used for carrying out health state checking on the servers under the distributed load balancing architecture and marking the health state of each server.
The device for continuously inheriting the distributed load balancing service information under the agile iterative research and development model can ensure that changed service information is dynamically updated in time and ensure that the continuous inheritance of unchanged service information is not influenced. The stability and the agility of the distributed load balancing service are greatly improved.
An embodiment of the present application further provides a specific implementation manner of an electronic device capable of implementing all steps in the method in the foregoing embodiment, and referring to fig. 9, the electronic device specifically includes the following contents:
a processor (processor)901, a memory 902, a communication Interface (Communications Interface)903, a bus 904, and a nonvolatile memory 905;
the processor 901, the memory 902, the communication interface 903 and the nonvolatile memory 905 complete mutual communication through the bus 904;
the processor 901 is configured to call the computer programs in the memory 902 and the nonvolatile memory 905, and when the processor executes the computer programs, the processor implements all the steps in the method in the foregoing embodiments, for example, when the processor executes the computer programs, the processor implements the following steps:
s101: and monitoring a service change instruction sent by the external server or the internal server in real time.
S102: and stopping the current process and storing the service information which does not need to be changed in the current process into a temporary storage file according to the service change instruction after monitoring the service change instruction.
S103: and changing the service information needing to be changed in the current process according to the service change instruction.
S104: and initializing the process of finishing the service information change according to the service information in the temporary storage file.
Embodiments of the present application also provide a computer-readable storage medium capable of implementing all the steps of the method in the above embodiments, where the computer-readable storage medium stores thereon a computer program, and the computer program when executed by a processor implements all the steps of the method in the above embodiments, for example, the processor implements the following steps when executing the computer program:
s101: and monitoring a service change instruction sent by the external server or the internal server in real time.
S102: and stopping the current process and storing the service information which does not need to be changed in the current process into a temporary storage file according to the service change instruction after monitoring the service change instruction.
S103: and changing the service information needing to be changed in the current process according to the service change instruction.
S104: and initializing the process of finishing the service information change according to the service information in the temporary storage file.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the hardware + program class embodiment, since it is substantially similar to the method embodiment, the description is simple, and the relevant points can be referred to the partial description of the method embodiment. Although embodiments of the present description provide method steps as described in embodiments or flowcharts, more or fewer steps may be included based on conventional or non-inventive means. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or end product executes, it may execute sequentially or in parallel (e.g., parallel processors or multi-threaded environments, or even distributed data processing environments) according to the method shown in the embodiment or the figures. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, the presence of additional identical or equivalent elements in a process, method, article, or apparatus that comprises the recited elements is not excluded. For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, in implementing the embodiments of the present description, the functions of each module may be implemented in one or more software and/or hardware, or a module implementing the same function may be implemented by a combination of multiple sub-modules or sub-units, and the like. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form. The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks. As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein. The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment. In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of an embodiment of the specification. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction. The above description is only an example of the embodiments of the present disclosure, and is not intended to limit the embodiments of the present disclosure. Various modifications and variations to the embodiments described herein will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the embodiments of the present specification should be included in the scope of the claims of the embodiments of the present specification.
Claims (12)
1. A method for continuously inheriting distributed load balancing service information is characterized by comprising the following steps:
monitoring a service change instruction sent by an external server or an internal server in real time;
stopping the current service process after monitoring a service change instruction, and changing service information needing to be changed in the current service process according to the service change instruction;
and initializing the process of completing the service information change according to the service information which does not need to be changed.
2. The method for continuous inheritance of distributed load balancing service information according to claim 1, further comprising:
extracting the name of the service needing to be changed from the service change instruction;
determining services which do not need to be changed in the current service process according to the names of the services which need to be changed;
and saving the service information which does not need to be changed into a storage file.
3. The method for continuously inheriting distributed load balancing service information according to claim 2, wherein the changing the service information that needs to be changed in a current process according to the service change instruction includes:
searching the service needing to be changed from the current process according to the name of the service needing to be changed;
and changing the service information corresponding to the service needing to be changed according to the service change instruction.
4. The method for continuous inheritance of distributed load balancing service information according to claim 2, further comprising:
and when the service information does not exist in the storage file, initializing the process according to preset initialization service information.
5. The method for continuous inheritance of distributed load balancing service information according to claim 1, further comprising:
and carrying out health state check on the servers under the distributed load balancing architecture and marking the health state of each server.
6. A distributed load balancing service information continuous inheritance device is characterized by comprising:
the monitoring unit is used for monitoring a service change instruction sent by an external server or an internal server in real time;
the service information changing unit is used for stopping the current service process after monitoring a service changing instruction and changing the service information needing to be changed in the current service process according to the service changing instruction;
and the reinitialization unit is used for initializing the process of completing the service information change according to the service information which does not need to be changed.
7. The apparatus for continuously inheriting distributed load balancing service information according to claim 6, wherein the service information changing unit includes:
the extracting module is used for extracting the name of the service needing to be changed from the service changing instruction;
the determining module is used for determining services which do not need to be changed in the current service process according to the names of the services which need to be changed;
and the storage module is used for storing the service information which does not need to be changed into a storage file.
8. The apparatus for continuously inheriting distributed load balancing service information according to claim 7, wherein the service information changing unit further includes:
the searching module is used for searching the service needing to be changed from the current process according to the name of the service needing to be changed;
and the changing module is used for changing the service information corresponding to the service needing to be changed according to the service changing instruction.
9. The apparatus for continuously inheriting distributed load balancing service information according to claim 7, further comprising:
and the original initialization processing unit is used for initializing the process according to preset initialization service information when the service information does not exist in the storage file.
10. The apparatus for continuously inheriting distributed load balancing service information according to claim 6, further comprising:
and the health state checking unit is used for carrying out health state checking on the servers under the distributed load balancing architecture and marking the health state of each server.
11. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the steps of the distributed load balancing service information inheriting method according to any one of claims 1 to 5 when executing the program.
12. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the distributed load balancing service information inheriting method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110180542.1A CN112905341B (en) | 2021-02-08 | 2021-02-08 | Method and device for continuously inheriting distributed load balancing service information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110180542.1A CN112905341B (en) | 2021-02-08 | 2021-02-08 | Method and device for continuously inheriting distributed load balancing service information |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112905341A true CN112905341A (en) | 2021-06-04 |
| CN112905341B CN112905341B (en) | 2024-02-23 |
Family
ID=76123227
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110180542.1A Active CN112905341B (en) | 2021-02-08 | 2021-02-08 | Method and device for continuously inheriting distributed load balancing service information |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112905341B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114844912A (en) * | 2022-04-22 | 2022-08-02 | 北京志凌海纳科技有限公司 | Data link distribution method and device and distributed block storage system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107911470A (en) * | 2017-11-30 | 2018-04-13 | 掌阅科技股份有限公司 | Distributed dynamic load-balancing method, computing device and computer-readable storage medium |
| CN109101341A (en) * | 2017-06-21 | 2018-12-28 | 阿里巴巴集团控股有限公司 | The distribution method and equipment of distributed lock |
| CN110225078A (en) * | 2019-04-26 | 2019-09-10 | 深圳法大大网络科技有限公司 | A kind of application service update method, system and terminal device |
| CN111914194A (en) * | 2020-07-02 | 2020-11-10 | 网联清算有限公司 | Business system changing method and device, electronic equipment and storage medium |
-
2021
- 2021-02-08 CN CN202110180542.1A patent/CN112905341B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109101341A (en) * | 2017-06-21 | 2018-12-28 | 阿里巴巴集团控股有限公司 | The distribution method and equipment of distributed lock |
| CN107911470A (en) * | 2017-11-30 | 2018-04-13 | 掌阅科技股份有限公司 | Distributed dynamic load-balancing method, computing device and computer-readable storage medium |
| CN110225078A (en) * | 2019-04-26 | 2019-09-10 | 深圳法大大网络科技有限公司 | A kind of application service update method, system and terminal device |
| CN111914194A (en) * | 2020-07-02 | 2020-11-10 | 网联清算有限公司 | Business system changing method and device, electronic equipment and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114844912A (en) * | 2022-04-22 | 2022-08-02 | 北京志凌海纳科技有限公司 | Data link distribution method and device and distributed block storage system |
| CN114844912B (en) * | 2022-04-22 | 2022-12-09 | 北京志凌海纳科技有限公司 | Data link distribution method and device and distributed block storage system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112905341B (en) | 2024-02-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110275722B (en) | Method, apparatus, device and storage medium for upgrading application | |
| US9960963B2 (en) | Dynamic client fail-over during a rolling patch installation based on temporal server conditions | |
| US8006134B2 (en) | Method for analyzing fault caused in virtualized environment, and management server | |
| US10635473B2 (en) | Setting support program, setting support method, and setting support device | |
| CN106575244B (en) | Patching process to ensure high availability of cloud applications | |
| CN107102916B (en) | Replaying jobs at a secondary location of a service | |
| EP2474910B1 (en) | Setting program, workflow creating method, and work flow creating apparatus | |
| US20080052677A1 (en) | System and method for mitigating repeated crashes of an application resulting from supplemental code | |
| US8656126B2 (en) | Managing snapshots of virtual server | |
| CN111124475A (en) | Method for storage management, electronic device and computer-readable storage medium | |
| JP2006031109A (en) | Management system and management method | |
| JP6288275B2 (en) | Virtualization infrastructure management apparatus, virtualization infrastructure management system, virtualization infrastructure management method, and virtualization infrastructure management program | |
| US20120036496A1 (en) | Plug-in based high availability application management framework (amf) | |
| JP2010009411A (en) | Virtual environment operation support system and virtual environment operation support program | |
| US20130086572A1 (en) | Generation apparatus, generation method and computer readable information recording medium | |
| CN116339908A (en) | Virtual machine starting method, device, computer equipment and storage medium | |
| CN112905341B (en) | Method and device for continuously inheriting distributed load balancing service information | |
| US7269722B1 (en) | Preview of UNIX boot process from multi-user level | |
| US20210173698A1 (en) | Hosting virtual machines on a secondary storage system | |
| US20230088318A1 (en) | Remotely healing crashed processes | |
| US20110154349A1 (en) | Resource fault management for partitions | |
| CN115167896A (en) | Method and device for updating software version, storage medium and electronic equipment | |
| CN110297741B (en) | Background task monitoring method and device | |
| JP7552280B2 (en) | Information processing device, arrangement method, and program | |
| 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |