CN112527491A - Micro-service call load balancing method and system - Google Patents
Micro-service call load balancing method and system Download PDFInfo
- Publication number
- CN112527491A CN112527491A CN201910876276.9A CN201910876276A CN112527491A CN 112527491 A CN112527491 A CN 112527491A CN 201910876276 A CN201910876276 A CN 201910876276A CN 112527491 A CN112527491 A CN 112527491A
- Authority
- CN
- China
- Prior art keywords
- service
- load balancing
- strategy
- micro
- data cache
- 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 58
- 230000003068 static effect Effects 0.000 claims abstract description 22
- 230000000694 effects Effects 0.000 claims abstract description 19
- 230000007246 mechanism Effects 0.000 claims description 8
- 230000001360 synchronised effect Effects 0.000 claims description 6
- 230000008569 process Effects 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 6
- 238000004590 computer program Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000013500 data storage Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000003287 optical 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/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
- G06F9/505—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the load
Abstract
The invention discloses a micro-service call load balancing method and a system, relating to the field of micro-services, wherein the method comprises the steps of defining a load balancing strategy in a service description file of the micro-service based on the call requirement of a service provided by the service on the micro-service; defining a load balancing strategy in a configuration center based on the calling requirement of the service provided by the service on the micro service; when the micro service is started, analyzing a service description file of the micro service, caching the analyzed load balancing strategy into a local static data cache, and caching the load balancing strategy in the configuration center into a local dynamic data cache; and when the micro service is called, based on the current service, acquiring a load balancing strategy corresponding to the current service from the local static data cache or the local dynamic data cache, and taking effect. The invention can flexibly select the set load balancing strategy when the micro service is called by the service.
Description
Technical Field
The invention relates to the field of micro-services, in particular to a micro-service call load balancing method and system.
Background
The micro-service is a method for developing a single application program as a set of small-sized services, each application program runs in the own process and communicates with a lightweight mechanism, the micro-service is constructed around business functions, can be independently deployed through a full-automatic deployment mechanism, can be written by using different programming languages, and uses different data storage technologies.
In the field of micro-services, service support horizontal expansion is a basic function, the main purpose of horizontal expansion is to distribute pressure by deploying a plurality of micro-service instances to achieve the purpose of improving the system processing capacity, when a micro-service is deployed by a plurality of instances, a service consumption end must support load balancing when calling the micro-service, the existing system is generally single in supporting load balancing granularity, some systems only support a global strategy, and some systems only support a method-level strategy.
Disclosure of Invention
Aiming at the defects in the prior art, the invention aims to provide a micro-service call load balancing method and system, which can flexibly select the set load balancing strategy when a service calls a micro-service.
In order to achieve the above object, the present invention provides a method for balancing a micro service invocation load, which comprises the following steps:
defining a load balancing strategy in a service description file of the micro service based on the calling requirement of the service provided by the service on the micro service, wherein the load balancing strategy corresponds to the service;
defining a load balancing strategy in a configuration center based on the calling requirement of a service provided by the service on the micro service, wherein the load balancing strategies defined in the service description files of the configuration center and the micro service are the same for the same service;
when the micro service is started, analyzing a service description file of the micro service, caching the analyzed load balancing strategy into a local static data cache, and caching the load balancing strategy in the configuration center into a local dynamic data cache;
and when the micro service is called, based on the current service, acquiring a load balancing strategy corresponding to the current service from the local static data cache or the local dynamic data cache, and taking effect.
On the basis of the technical proposal, the device comprises a shell,
the load balancing strategy comprises a global strategy, a service level strategy and a method level strategy;
the global strategy is suitable for load balancing strategies of all micro services;
the service level policy is applicable to a load balancing policy when a specific micro service is invoked;
the method level policies are applicable to load balancing policies when a particular method of a particular microservice is invoked.
On the basis of the technical proposal, the device comprises a shell,
each service at least corresponds to a load balancing strategy;
when the service corresponds to multiple load balancing strategies and the load balancing strategies take effect, the priority of the global strategy is smaller than that of the service level strategy, and the priority of the service level strategy is smaller than that of the method level strategy.
On the basis of the technical scheme, when the load balancing strategy in the configuration center is modified, the modified load balancing strategy is synchronized to the local dynamic data cache in real time, and when the micro-service is called, if the load balancing strategies corresponding to the current service exist in the local dynamic data cache and the local static data cache, the load balancing strategy in the local dynamic data cache takes effect.
On the basis of the technical scheme, caching the load balancing strategy in the configuration center into a local dynamic data cache specifically comprises the following steps: when the micro-service is started, the load balancing strategy is pulled from the configuration center through the configuration cache component of the micro-service, the pulled load balancing strategy is cached in the local dynamic data cache, and a synchronization mechanism is established between the local dynamic data cache and the configuration center and used for keeping consistency of the local dynamic data cache and the load balancing strategy in the configuration center.
The invention provides a micro-service call load balancing system, which comprises:
the system comprises a first defining module, a second defining module and a third defining module, wherein the first defining module is used for defining a load balancing strategy in a yaml file of a service description file of the micro service based on the calling requirement of the service provided by the service on the micro service, and the load balancing strategy corresponds to the service;
the second definition module is used for defining a load balancing strategy in the configuration center based on the calling requirement of the service provided by the service on the micro service, and for the same service, the load balancing strategies defined in the service description files of the configuration center and the micro service are the same;
the cache module is used for analyzing a service description file of the micro service when the micro service is started, caching the analyzed load balancing strategy into a local static data cache, and caching the load balancing strategy in the configuration center into a local dynamic data cache;
and the obtaining module is used for obtaining the load balancing strategy corresponding to the current service from the local static data cache or the local dynamic data cache based on the current service when the micro service is called, and taking effect.
On the basis of the technical proposal, the device comprises a shell,
the load balancing strategy comprises a global strategy, a service level strategy and a method level strategy;
the global strategy is suitable for load balancing strategies of all micro services;
the service level policy is applicable to a load balancing policy when a specific micro service is invoked;
the method level policies are applicable to load balancing policies when a particular method of a particular microservice is invoked.
On the basis of the technical proposal, the device comprises a shell,
each service at least corresponds to a load balancing strategy;
when the service corresponds to multiple load balancing strategies and the load balancing strategies take effect, the priority of the global strategy is smaller than that of the service level strategy, and the priority of the service level strategy is smaller than that of the method level strategy.
On the basis of the technical scheme, when the load balancing strategy in the configuration center is modified, the modified load balancing strategy is synchronized to the local dynamic data cache in real time, and when the micro-service is called, if the load balancing strategies corresponding to the current service exist in the local dynamic data cache and the local static data cache, the load balancing strategy in the local dynamic data cache takes effect.
On the basis of the technical scheme, the cache module caches the load balancing strategy in the configuration center into the local dynamic data cache, and the specific process is as follows: when the micro-service is started, the load balancing strategy is pulled from the configuration center through the configuration cache component of the micro-service, the pulled load balancing strategy is cached in the local dynamic data cache, and a synchronization mechanism is established between the local dynamic data cache and the configuration center and used for keeping consistency of the local dynamic data cache and the load balancing strategy in the configuration center.
Compared with the prior art, the invention has the advantages that: defining a load balancing strategy in a service description file of the micro service based on the calling requirement of the service provided by the service on the micro service, setting various load balancing strategies, flexibly selecting the set load balancing strategy to meet the service requirement when the service calls the micro service, and defining the load balancing strategy in the configuration center.
Drawings
Fig. 1 is a flowchart of a method for load balancing of micro service invocation in an embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention 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 the like) having computer-usable program code embodied therein.
The embodiment of the invention provides a micro-service call load balancing method, which is used for setting a plurality of load balancing strategies, and flexibly selecting the set load balancing strategies when a service calls a micro-service so as to meet the service requirement. The embodiment of the invention also correspondingly provides a micro-service call load balancing system.
Referring to fig. 1, a method for balancing load of micro service invocation provided by an embodiment of the present invention includes:
s1: defining a load balancing strategy in a service description file of the micro-service based on the calling requirement of the service provided by the service on the micro-service, specifically defining the load balancing strategy in a yaml file, wherein the load balancing strategy corresponds to the service, and when the micro-service is called by the service, the called micro-service is designated and a method in the called micro-service is designated. YAML (YAML Ain't Markup Language) is an intuitive computer-recognizable data serialization format, a programming Language that is readable and easily read by humans, and interacts easily with scripting languages to express material sequences.
In the embodiment of the invention, the load balancing strategy comprises a global strategy, a service level strategy and a method level strategy, wherein the global strategy is suitable for the load balancing strategy of all micro-services, namely the load balancing strategy is used when consumer service calls any provider service; the service level policy is applicable to a load balancing policy when a specific micro service is invoked, i.e. the load balancing policy is used by the consumer service when a specific service provider is invoked; the method level policies are applicable to load balancing policies when a particular method of a particular microservice is invoked, i.e., the consumer service uses the load balancing policies when invoking a particular method of a service provider.
The micro-service call load balancing method is suitable for service scenes when a plurality of micro-services are called, in the same system, the number of the micro-services is multiple, for different services, a service consumer can call a plurality of micro-services, such as A, B, C three micro-services, and the service consumer can use the same load balancing strategy when calling all methods of A, B, C three micro-services; all methods of the micro-service A, B or C can also be called to use different load balancing strategies; methods 1, 2 of microservice a may also be invoked using different load balancing strategies. Therefore, the invention defines the load balancing strategy for the service, and performs load balancing aiming at different methods of different micro-services called by the service so as to flexibly adjust the operation of a plurality of micro-services called by the current service.
In order to ensure the flexibility of load balancing regulation, for the same service, the service can be corresponding to a plurality of load balancing strategies, each service at least corresponds to one load balancing strategy, when the service corresponds to a plurality of load balancing strategies and the load balancing strategies are effective, the priority of the global strategy is smaller than that of the service level strategy, the priority of the service level strategy is smaller than that of the method level strategy, when the service is used for micro service, the load balancing strategies contained in the service are judged, only one load balancing strategy is effective, and the judgment is effective according to the priority of each load balancing strategy.
S2: and defining a load balancing strategy in the configuration center based on the calling requirement of the service provided by the service on the micro service, wherein the load balancing strategies defined in the service description files of the configuration center and the micro service are the same for the same service. And writing a load balancing strategy in the configuration center through a management interface of the configuration center.
S3: when the micro service is started, the service description file of the micro service is analyzed, the analyzed load balancing strategy is cached in the local static data cache, and meanwhile, the load balancing strategy in the configuration center is cached in the local dynamic data cache.
Caching a load balancing strategy in a configuration center into a local dynamic data cache, and the method specifically comprises the following steps: when the micro-service is started, the load balancing strategy is pulled from the configuration center through the configuration cache component of the micro-service, the pulled load balancing strategy is cached in the local dynamic data cache, and a synchronization mechanism is established between the local dynamic data cache and the configuration center and used for keeping consistency of the local dynamic data cache and the load balancing strategy in the configuration center.
S4: and when the micro service is called, based on the current service, acquiring a load balancing strategy corresponding to the current service from the local static data cache or the local dynamic data cache, and taking effect. Because the priority of the load balancing strategy in the local static data cache is smaller than that of the load balancing strategy in the local dynamic data cache, when the load balancing strategies corresponding to the current service exist in both the local static data cache and the local dynamic data cache, the load balancing strategy in the local dynamic data cache takes effect.
In the embodiment of the invention, when the load balancing strategy in the configuration center is modified, the modified load balancing strategy is synchronized to the local dynamic data cache in real time, and when the micro service is called, if the load balancing strategies corresponding to the current service business exist in the local dynamic data cache and the local static data cache, the load balancing strategy in the local dynamic data cache takes effect, the real-time modification is effective in real time, the micro service does not need to be restarted, and the method is convenient and quick.
The micro-service call load balancing method of the embodiment of the invention defines a load balancing strategy in a service description file of the micro-service based on the call requirement of the service provided by the service to the micro-service, sets various load balancing strategies, flexibly selects the set load balancing strategy to meet the service requirement when the service calls the micro-service, and also defines the load balancing strategy in the configuration center.
The micro-service call load balancing system provided by the embodiment of the invention comprises:
the system comprises a first defining module, a second defining module and a third defining module, wherein the first defining module is used for defining a load balancing strategy in a service description file of the micro service based on the calling requirement of the service provided by the service on the micro service, and the load balancing strategy corresponds to the service;
the second definition module is used for defining a load balancing strategy in the configuration center based on the calling requirement of the service provided by the service on the micro service, and for the same service, the load balancing strategies defined in the service description files of the configuration center and the micro service are the same;
the cache module is used for analyzing a service description file of the micro service when the micro service is started, caching the analyzed load balancing strategy into a local static data cache, and caching the load balancing strategy in the configuration center into a local dynamic data cache;
and the obtaining module is used for obtaining the load balancing strategy corresponding to the current service from the local static data cache or the local dynamic data cache based on the current service when the micro service is called, and taking effect.
The load balancing strategy comprises a global strategy, a service level strategy and a method level strategy; the global strategy is applicable to the load balancing strategy of all the microservices; the service level strategy is suitable for a load balancing strategy when a specific micro service is called; the method level policies are applicable to load balancing policies when a particular method of a particular microservice is invoked. Each service at least corresponds to a load balancing strategy; when the service corresponds to multiple load balancing strategies and the load balancing strategies take effect, the priority of the global strategy is smaller than that of the service level strategy, and the priority of the service level strategy is smaller than that of the method level strategy.
When the load balancing strategy in the configuration center is modified, the modified load balancing strategy is synchronized to the local dynamic data cache in real time, and when the micro service is called, if the load balancing strategies corresponding to the current service exist in the local dynamic data cache and the local static data cache, the load balancing strategy in the local dynamic data cache takes effect.
The cache module caches a load balancing strategy in the configuration center into a local dynamic data cache, and the specific process is as follows: when the micro-service is started, the load balancing strategy is pulled from the configuration center through the configuration cache component of the micro-service, the pulled load balancing strategy is cached in the local dynamic data cache, and a synchronization mechanism is established between the local dynamic data cache and the configuration center and used for keeping consistency of the local dynamic data cache and the load balancing strategy in the configuration center.
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.
The present invention is not limited to the above-described embodiments, and it will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the principle of the present invention, and such modifications and improvements are also considered to be within the scope of the present invention. Those not described in detail in this specification are within the skill of the art.
Claims (10)
1. A micro-service call load balancing method is characterized by comprising the following steps:
defining a load balancing strategy in a service description file of the micro service based on the calling requirement of the service provided by the service on the micro service, wherein the load balancing strategy corresponds to the service;
defining a load balancing strategy in a configuration center based on the calling requirement of a service provided by the service on the micro service, wherein the load balancing strategies defined in the service description files of the configuration center and the micro service are the same for the same service;
when the micro service is started, analyzing a service description file of the micro service, caching the analyzed load balancing strategy into a local static data cache, and caching the load balancing strategy in the configuration center into a local dynamic data cache;
and when the micro service is called, based on the current service, acquiring a load balancing strategy corresponding to the current service from the local static data cache or the local dynamic data cache, and taking effect.
2. The method for load balancing of microservice invocations according to claim 1, wherein:
the load balancing strategy comprises a global strategy, a service level strategy and a method level strategy;
the global strategy is suitable for load balancing strategies of all micro services;
the service level policy is applicable to a load balancing policy when a specific micro service is invoked;
the method level policies are applicable to load balancing policies when a particular method of a particular microservice is invoked.
3. The method for load balancing of microservice invocations according to claim 2, wherein:
each service at least corresponds to a load balancing strategy;
when the service corresponds to multiple load balancing strategies and the load balancing strategies take effect, the priority of the global strategy is smaller than that of the service level strategy, and the priority of the service level strategy is smaller than that of the method level strategy.
4. The method of claim 3, wherein the method comprises: when the load balancing strategy in the configuration center is modified, the modified load balancing strategy is synchronized to the local dynamic data cache in real time, and when the micro service is called, if the load balancing strategies corresponding to the current service exist in the local dynamic data cache and the local static data cache, the load balancing strategy in the local dynamic data cache takes effect.
5. The method for load balancing of micro service invocation according to claim 1, wherein the caching of the load balancing policy in the configuration center into the local dynamic data cache comprises the specific steps of: when the micro-service is started, the load balancing strategy is pulled from the configuration center through the configuration cache component of the micro-service, the pulled load balancing strategy is cached in the local dynamic data cache, and a synchronization mechanism is established between the local dynamic data cache and the configuration center and used for keeping consistency of the local dynamic data cache and the load balancing strategy in the configuration center.
6. A microservice call load balancing system, comprising:
the system comprises a first defining module, a second defining module and a third defining module, wherein the first defining module is used for defining a load balancing strategy in a yaml file of a service description file of the micro service based on the calling requirement of the service provided by the service on the micro service, and the load balancing strategy corresponds to the service;
the second definition module is used for defining a load balancing strategy in the configuration center based on the calling requirement of the service provided by the service on the micro service, and for the same service, the load balancing strategies defined in the service description files of the configuration center and the micro service are the same;
the cache module is used for analyzing a service description file of the micro service when the micro service is started, caching the analyzed load balancing strategy into a local static data cache, and caching the load balancing strategy in the configuration center into a local dynamic data cache;
and the obtaining module is used for obtaining the load balancing strategy corresponding to the current service from the local static data cache or the local dynamic data cache based on the current service when the micro service is called, and taking effect.
7. The micro-service invocation load balancing system of claim 6, wherein:
the load balancing strategy comprises a global strategy, a service level strategy and a method level strategy;
the global strategy is suitable for load balancing strategies of all micro services;
the service level policy is applicable to a load balancing policy when a specific micro service is invoked;
the method level policies are applicable to load balancing policies when a particular method of a particular microservice is invoked.
8. The micro-service invocation load balancing system of claim 7, wherein:
each service at least corresponds to a load balancing strategy;
when the service corresponds to multiple load balancing strategies and the load balancing strategies take effect, the priority of the global strategy is smaller than that of the service level strategy, and the priority of the service level strategy is smaller than that of the method level strategy.
9. The micro-service invocation load balancing system of claim 8, wherein: when the load balancing strategy in the configuration center is modified, the modified load balancing strategy is synchronized to the local dynamic data cache in real time, and when the micro service is called, if the load balancing strategies corresponding to the current service exist in the local dynamic data cache and the local static data cache, the load balancing strategy in the local dynamic data cache takes effect.
10. The micro-service invocation load balancing system of claim 6, wherein: the cache module caches a load balancing strategy in the configuration center into a local dynamic data cache, and the specific process is as follows: when the micro-service is started, the load balancing strategy is pulled from the configuration center through the configuration cache component of the micro-service, the pulled load balancing strategy is cached in the local dynamic data cache, and a synchronization mechanism is established between the local dynamic data cache and the configuration center and used for keeping consistency of the local dynamic data cache and the load balancing strategy in the configuration center.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910876276.9A CN112527491A (en) | 2019-09-17 | 2019-09-17 | Micro-service call load balancing method and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910876276.9A CN112527491A (en) | 2019-09-17 | 2019-09-17 | Micro-service call load balancing method and system |
Publications (1)
Publication Number | Publication Date |
---|---|
CN112527491A true CN112527491A (en) | 2021-03-19 |
Family
ID=74974657
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201910876276.9A Pending CN112527491A (en) | 2019-09-17 | 2019-09-17 | Micro-service call load balancing method and system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN112527491A (en) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170364702A1 (en) * | 2015-06-02 | 2017-12-21 | ALTR Solutions, Inc. | Internal controls engine and reporting of events generated by a network or associated applications |
US20180027080A1 (en) * | 2016-07-22 | 2018-01-25 | Cisco Technology, Inc. | Scaling service discovery in a micro-service environment |
CN107911470A (en) * | 2017-11-30 | 2018-04-13 | 掌阅科技股份有限公司 | Distributed dynamic load-balancing method, computing device and computer-readable storage medium |
CN109104483A (en) * | 2018-08-10 | 2018-12-28 | 北京东软望海科技有限公司 | A kind of method and device of the micro services dynamic load leveling based on event notice |
CN109587071A (en) * | 2018-11-30 | 2019-04-05 | 北京工业大学 | Micro services load-balancing method based on SDN |
-
2019
- 2019-09-17 CN CN201910876276.9A patent/CN112527491A/en active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170364702A1 (en) * | 2015-06-02 | 2017-12-21 | ALTR Solutions, Inc. | Internal controls engine and reporting of events generated by a network or associated applications |
US20180027080A1 (en) * | 2016-07-22 | 2018-01-25 | Cisco Technology, Inc. | Scaling service discovery in a micro-service environment |
CN107911470A (en) * | 2017-11-30 | 2018-04-13 | 掌阅科技股份有限公司 | Distributed dynamic load-balancing method, computing device and computer-readable storage medium |
CN109104483A (en) * | 2018-08-10 | 2018-12-28 | 北京东软望海科技有限公司 | A kind of method and device of the micro services dynamic load leveling based on event notice |
CN109587071A (en) * | 2018-11-30 | 2019-04-05 | 北京工业大学 | Micro services load-balancing method based on SDN |
Non-Patent Citations (1)
Title |
---|
天天大傻猫: "SpringCloud服务间调用:负载均衡策略调整", 《HTTPS://WWW.CNBOLGS.COM/BIG-CUT-CAT/P/988841.HTML》, 1 November 2018 (2018-11-01), pages 1 - 2 * |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN107092522B (en) | Real-time data calculation method and device | |
US7962612B2 (en) | Method for connection leak detection and prevention | |
CN107832100B (en) | APK plug-in loading method and terminal thereof | |
US20070220149A1 (en) | Load balance control method and load balance control apparatus in data-processing system | |
CN111966492B (en) | Memory recycling method and device, electronic equipment and computer readable storage medium | |
CN108255708B (en) | Method, device, storage medium and equipment for accessing production file in test environment | |
CN105786603B (en) | Distributed high-concurrency service processing system and method | |
CN110245031B (en) | AI service opening middle platform and method | |
US20150112934A1 (en) | Parallel scanners for log based replication | |
CN112445686A (en) | Memory leak detection method, device and computer-readable storage medium | |
CN111737353A (en) | Metadata synchronization method and device | |
CN110795202B (en) | Resource allocation method and device of virtualized cluster resource management system | |
CN110413395A (en) | Service call pre-heating mean, device, equipment and storage medium | |
CN112527491A (en) | Micro-service call load balancing method and system | |
CN104700255B (en) | Multi-process processing method, device and system | |
CN112416559A (en) | Scheduling policy updating method, service scheduling method, storage medium and related apparatus | |
CN111984448A (en) | Page calling method, device, equipment and storage medium | |
CN102497410A (en) | Method for dynamically partitioning computing resources of cloud computing system | |
CN115562807A (en) | Method and system for mounting dynamic equipment for android container in kubernets environment | |
CN113114731B (en) | Task processing method, device, server and storage medium | |
CN105159619B (en) | The extended method and device of a kind of virtual memory | |
CN114461424A (en) | Inter-unit service discovery method, device and system under unitized deployment architecture | |
CN114356567A (en) | Method, system and equipment for stretching and retracting Slurm cluster | |
CN107786587B (en) | Method for adjusting application resources and cloud controller | |
CN112463312A (en) | Dynamic maintenance system and method for timing task, medium and computing equipment |
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 | ||
RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210319 |
|
RJ01 | Rejection of invention patent application after publication |