CN115964171A - Systematic micro-service resource scheduling method and device and electronic equipment - Google Patents
Systematic micro-service resource scheduling method and device and electronic equipment Download PDFInfo
- Publication number
- CN115964171A CN115964171A CN202211664640.3A CN202211664640A CN115964171A CN 115964171 A CN115964171 A CN 115964171A CN 202211664640 A CN202211664640 A CN 202211664640A CN 115964171 A CN115964171 A CN 115964171A
- Authority
- CN
- China
- Prior art keywords
- service
- server
- load
- service request
- service node
- 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
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Computer And Data Communications (AREA)
Abstract
Some embodiments of the present application provide a systematic micro-service resource scheduling method, apparatus and electronic device, where the method includes: acquiring response time of a service request of a client; comparing the response time with a preset threshold value to obtain a calling result of the service request; and determining whether a target server for providing service needs to be selected for the service request or not based on the calling result. Some embodiments of the application can realize effective scheduling of service resources and guarantee normal operation of services.
Description
Technical Field
The present application relates to the technical field of service scheduling, and in particular, to a systematic micro-service resource scheduling method, apparatus and electronic device.
Background
With the continuous development of the internet, service cluster resources are widely applied to various industries.
At present, the traffic scale is gradually enlarged, and the pressure of service resources is also increased. When dealing with traffic emergencies, thousands or even tens of thousands of service machines are often needed to improve the performance to meet the needs of the system. However, the problem of frequent abnormal service node caused by more service cluster nodes is also brought while the capacity of the server resources is expanded, so that the available service resources are easily affected by various objective factors, and further the service capabilities of the nodes are greatly different.
Therefore, how to provide an effective technical solution of a systematic micro-service resource scheduling method becomes a technical problem which needs to be solved urgently.
Disclosure of Invention
Some embodiments of the present application aim to provide a systematic method and apparatus for scheduling micro service resources, and an electronic device.
In a first aspect, some embodiments of the present application provide a systematic micro service resource scheduling method, including: acquiring response time of a service request of a client; comparing the response time with a preset threshold value to obtain a calling result of the service request; and determining whether a target server for providing service needs to be selected for the service request or not based on the calling result.
According to some embodiments of the application, by comparing the response time of the service request of the client with the preset threshold, whether the service request is successfully responded or not can be confirmed, so that whether the target server is selected or not can be confirmed, the service resource can be effectively scheduled, the service request can be timely responded and processed, the efficiency is high, and the customer experience is improved.
In some embodiments, the comparing the response time with a preset threshold to obtain the invoking result of the service request includes: if the response time does not exceed the preset threshold, the calling result is successful; the determining whether a target server providing service needs to be selected for the service request based on the calling result includes: and when the calling result is successful, determining that a target server providing service does not need to be selected for the service request.
Some embodiments of the application may confirm that the service request is allocated by confirming that the call result is successful, which may ensure normal processing of the service and avoid long waiting time of the client.
In some embodiments, the comparing the response time with a preset threshold to obtain a calling result of the service request includes: if the response time exceeds the preset threshold, the calling result is failure; the determining whether a target server providing service needs to be selected for the service request based on the calling result includes: and when the calling result is failure, determining a target server for providing service for the service request.
According to some embodiments of the application, when the scheduling result of the service request is determined to be failure, the target server is selected for the client, so that normal processing of the service can be ensured, the client is prevented from waiting for a long time, and the customer experience is improved.
In some embodiments, after the determining selects a target server to serve the service request, the method further comprises: acquiring each service node load of each server in a server cluster; calculating the load rate of each service node of each server based on the load of each service node; and determining the target server according to the load rate of each service node.
Some embodiments of the application determine the target server through the service node load rate of the server, have high reliability, and can ensure service efficiency.
In some embodiments, said calculating, based on the respective service node loads, respective service node load ratios for the respective servers includes: acquiring a load threshold value of each service node of each server; and solving the ratio of the load of each service node to the load threshold of each service node to obtain the load rate of each service node.
According to some embodiments of the application, the service node load rate is obtained through the service node load threshold and the service node load, and the reliability is good.
In some embodiments, the determining the target server according to the load rate of each service node includes: and taking the server corresponding to the minimum value in the load rates of the service nodes as the target server.
Some embodiments of the application can quickly select a server provided for a service request by selecting the smallest load rate of the service nodes as a target server, and the efficiency is high.
In some embodiments, the determining the target server according to the load rate of each service node includes: screening out at least one server which is less than or equal to a preset load threshold value from the load rate of each service node; any one of the at least one server is taken as the target server.
According to some embodiments of the application, one of the at least one server meeting the preset load threshold is selected to serve, so that the server provided for the service request can be quickly selected, and the efficiency is high.
In a second aspect, some embodiments of the present application provide a systematic micro service resource scheduling apparatus, including: the acquisition module is configured to acquire response time of a service request of a client; the comparison module is configured to compare the response time with a preset threshold value to obtain a calling result of the service request; and the selection module is configured to determine whether a target server providing service needs to be selected for the service request or not based on the calling result.
In some embodiments, the comparison module is configured to determine that the calling result is successful if the response time does not exceed the preset threshold; and the selection module is configured to determine that a target server providing service does not need to be selected for the service request when the calling result is successful.
In some embodiments, the comparison module is configured to determine that the calling result is a failure if the response time exceeds the preset threshold; and the selection module is configured to determine a target server for selecting and providing service for the service request when the calling result is failure.
In some embodiments, the selection module is configured to obtain each service node load of each server in the server cluster; calculating the load rate of each service node of each server based on the load of each service node; and determining the target server according to the load rate of each service node.
In some embodiments, the selection module is configured to obtain a respective service node load threshold for the respective server; and solving the ratio of the load of each service node to the load threshold of each service node to obtain the load rate of each service node.
In some embodiments, the selection module is configured to take the server corresponding to the minimum value of the load ratios of the service nodes as the target server.
In some embodiments, the selection module is configured to screen out at least one server from the load rates of the service nodes, where the at least one server is smaller than or equal to a preset load threshold; any one of the at least one server is taken as the target server.
In a third aspect, some embodiments of the present application provide a computer-readable storage medium on which a computer program is stored, which when executed by a processor, may implement the method according to any of the embodiments of the first aspect.
In a fourth aspect, some embodiments of the present application provide an electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor, when executing the program, may implement the method according to any of the embodiments of the first aspect.
In a fifth aspect, some embodiments of the present application provide a computer program product comprising a computer program, wherein the computer program, when executed by a processor, implements the method according to any of the embodiments of the first aspect.
Drawings
In order to more clearly illustrate the technical solutions of some embodiments of the present application, the drawings that are required to be used in some embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that for those skilled in the art, other related drawings may also be obtained on the basis of these drawings without inventive effort.
Fig. 1 is a diagram of a systematic micro-service resource scheduling system according to some embodiments of the present application;
fig. 2 is a flowchart of a systematic micro service resource scheduling method according to some embodiments of the present application;
fig. 3 is a second flowchart of a systematic micro-service resource scheduling method according to some embodiments of the present application;
fig. 4 is a block diagram of a systematic micro-service resource scheduling apparatus according to some embodiments of the present application;
fig. 5 is a schematic diagram of an electronic device according to some embodiments of the present application.
Detailed Description
The technical solutions in some embodiments of the present application will be described below with reference to the accompanying drawings in some embodiments of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined or explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
In the related art, the service resource system always encounters special conditions in the daily use process due to certain objective factors. For example, in the case of a calling system, when a request from a client comes in, the service resource system needs to dispatch the request to a corresponding service node. During peak periods, the outbound system may cause a concurrent sudden increase of the service node in case of instantaneous traffic increase, and the service node may delay or even block the service due to traffic pressure, and may also be down in severe cases. In the prior art, in order to avoid long-time resource occupation, conversation with a client is generally selected to be abandoned, but normal processing of services is not utilized. As can be seen from the foregoing related arts, the service resource scheduling method in the prior art has low reliability and poor customer experience.
In view of this, some embodiments of the present application provide a systematic method for scheduling micro service resources, which may determine whether to select a target server providing a service for a service request based on a monitoring result (i.e., a call result) in time by monitoring a response time of the service request of a client. Some embodiments of the application can monitor the service request in real time, provide effective service resource scheduling for the service request, ensure normal processing flow and processing efficiency of the service, and improve customer experience.
The following describes an exemplary configuration of a systematic micro service resource scheduling system provided by some embodiments of the present application with reference to fig. 1.
As shown in fig. 1, some embodiments of the present application provide a systematic micro-service resource scheduling system. The systematized micro-service resource scheduling system comprises: a client 100 and a server 200. The server 200 is connected to a plurality of servers (server 1 to server n). The client 100 may send a service request to the server 200 to enable a session with the client. The server 200 distributes the service request to any one of several servers, so that any one responds to the service request and provides the service for the client 100. The server 200 may monitor a response time to the service request, and after confirming a relationship between the response time and a preset threshold, may determine whether to select a suitable target server for providing a service for the service request from among the plurality of servers. Some embodiments of the present application can provide effective service resource scheduling for the client 100, ensure that the service request of the client 100 is processed normally and orderly, have high reliability, and improve the customer experience.
In some embodiments of the present application, the client 100 may be disposed in a portable terminal or a non-portable computer terminal, and the present application is not limited thereto. The server 200 may be one server with a function of managing a service cluster among a plurality of servers, or may be a service terminal with a function of managing a service cluster independent of a plurality of servers, and may be set according to actual situations, which is not limited to this embodiment of the present application.
The following describes, with reference to fig. 2, an implementation process of systematic micro service resource scheduling performed by the server 200 according to some embodiments of the present application.
Referring to fig. 2, fig. 2 is a flowchart of a systematic micro service resource scheduling method according to some embodiments of the present application, where the systematic micro service resource scheduling method includes: s210, obtaining the response time of the service request of the client. And S220, comparing the response time with a preset threshold value to obtain a calling result of the service request. And S230, determining whether a target server for providing service needs to be selected for the service request or not based on the calling result.
For example, in some embodiments of the present application, when the client 100 normally requests the server 200, the client 100 may normally talk with the server 200. However, in the daily service process, a sudden increase of sessions is suddenly encountered, and if the sudden increase of sessions is not processed in time, the service capability of the server 200 is abnormal. For example, the seat staff or the client may obviously feel the condition of poor call quality and intermittent sound, and the server 200 cannot sense the condition. Therefore, the server 200 may monitor the response time of the service request of the client 100, compare the response time with a preset threshold, and determine whether the call service quality is abnormal. Whether a target server for providing service is selected for the service request can be determined based on the calling result, and normal processing of the service is further guaranteed.
In some embodiments of the present application, the preset threshold may be set according to actual conditions. For example, the server 200 may select an average response time of the historical service request as a reference value x, and superimpose a constant n on the reference value as a response threshold (as a specific example of a preset threshold) of the current server 200, that is, x + n.
In some embodiments of the present application, S220 may include: and if the response time does not exceed the preset threshold, the calling result is successful. S230 may include: and when the calling result is successful, determining that a target server providing service does not need to be selected for the service request.
For example, in some embodiments of the present application, if the response time does not exceed the response threshold, the service request that characterizes the client 100 is invoked within the response threshold, that is, the service request is successfully invoked to a server that can provide a service for the service request, and then passive selection for the service request is not required.
In some embodiments of the present application, S220 may include: and if the response time exceeds the preset threshold, the calling result is failure. S230 may include: and when the calling result is failure, determining to select a target server for providing service for the service request.
For example, in some embodiments of the present application, if the response time exceeds the response threshold, there is a timeout call for the service request characterizing the client 100, that is, the call fails. In order to prevent the occupation of the calling resource, the service request needs to be quickly removed from the calling memory at this time. In order to ensure the call success rate of the service request, some embodiments of the present application add a retry mechanism to the callback function, that is, select a target server that can provide a service for the service request with a failed call. The addition of the retry mechanism ensures that the service can be tried again after one failure, so that the service requested by the service is not lost.
In some embodiments of the present application, S230 may include: acquiring each service node load of each server in a server cluster; calculating the load rate of each service node of each server based on the load of each service node; and determining the target server according to the load rate of each service node.
For example, in some embodiments of the present application, the concurrent service request of the server 200 rises, and the server 200 needs to detect the service node load. By detecting the service node load rate of each service node, a suitable target server can be selected. For example, the service node load, that is, the number of threads of the current server, can be obtained by the open source algorithm. The service node load may be represented by at least one of service node CPU information, memory information, disk occupation information, network card information, virtual machine state information, and interface processing delay. The service performance of the current server can be reflected through the service node load, and then a target server with relatively proper service performance in the current system can be selected for the service request to provide service for the service request, so that the service corresponding to the service request of the client 100 can be normally processed.
In some embodiments of the present application, S230 may include: acquiring a load threshold value of each service node of each server; and solving the ratio of the load of each service node to the load threshold of each service node to obtain the load rate of each service node.
For example, in some embodiments of the present application, the server 200 may make an estimate of a maximum concurrency threshold (as a specific example of a service node load threshold) for each server. The load rate of each service node of each server can be obtained by the ratio of the number of threads of the current server to the maximum concurrency threshold.
In some embodiments of the present application, S230 may include: and taking the server corresponding to the minimum value in the load rates of the service nodes as the target server.
For example, in some embodiments of the present application, the server 200 includes 5 servers, and the service node load rates of the servers are respectively: 67%, 52%, 30%, 78% and 55%. At this time, the server with the minimum service node load rate of 30% can be used as a target server to provide service for the service request.
In other embodiments of the present application, S230 may include: screening out at least one server which is less than or equal to a preset load threshold value from the load rate of each service node; any one of the at least one server is taken as the target server.
For example, in other embodiments of the present application, a preset load threshold may also be set to select an appropriate target server. For example, the preset load threshold is 60%. And screening out the servers with the service node load rate not exceeding 60%. Taking the above example as an example, the service node load rate occupancy of the servers that do not exceed 60% are 52%, 30%, and 55%, respectively. Any one of the three servers is used as a target server to provide service for the service request.
The following describes a specific process of systematic micro service resource scheduling provided by some embodiments of the present application with reference to fig. 3.
Referring to fig. 3, fig. 3 is a flowchart of a systematic micro service resource scheduling method according to some embodiments of the present application.
The above process is exemplarily set forth below.
S310, response time of the service request of the client is obtained.
For example, as a specific example of the present application, an outbound client (as a specific example of the client 100) normally requests the server 200 to initiate a telephone call to communicate with the client. The line is increased in parallel in the peak time, and at this time, when the outbound client requests the server 200, the call delay can be found to be high, but the server 200 does not sense the call delay, so that the response time of the service request of the outbound client needs to be acquired in real time to ensure that the request can be performed normally.
And S320, judging whether the response time exceeds a preset threshold value, if so, executing S330, and if not, returning to S310.
For example, as a specific example of the present application, the server 200 determines whether the service request is successfully invoked by comparing the response time with a preset threshold. If the call is successful, the process returns to S310 to continue monitoring other response time. If the call fails, S330 is performed.
S330, acquiring the load of each service node and the load threshold of each service node of each server in the server cluster.
For example, as a specific example of the present application, when a concurrent request of the server 200 rises, a program of the server 200 may detect a load of each service node and obtain a load threshold of each service node.
S340, solving the ratio of the load of each service node to the load threshold of each service node to obtain the load rate of each service node.
For example, as a specific example of the present application, the load capacity of each service node is calculated by the following formula: loadCapacity = currentcurrent/MaxConcurrent, where currentcurrent is a service node load and MaxConcurrent is a service node load threshold. For example, the service node load rates of the servers calculated by the above formula are respectively: 67%, 52%, 30%, 78% and 55%.
And S350, determining a target server according to the load rate of each service node.
For example, as a specific example of the present application, a server corresponding to the minimum value of the load rates of the service nodes is taken as a target server, that is, a server with a load rate of 30% of the load rates of the service nodes is taken as a target server to provide a service for the service request, so as to implement a normal call with the client.
Referring to fig. 4, fig. 4 is a block diagram illustrating a systematic micro service resource scheduling apparatus according to some embodiments of the present application. It should be understood that the systematic micro-service resource scheduling apparatus corresponds to the above method embodiments, and can perform the steps related to the above method embodiments, and the specific functions of the systematic micro-service resource scheduling apparatus can be referred to the above description, and the detailed description is appropriately omitted here to avoid repetition.
A systematic micro-service resource scheduling apparatus of fig. 4 includes at least one software function module that can be stored in a memory in the form of software or firmware or solidified in a systematic micro-service resource scheduling apparatus, the systematic micro-service resource scheduling apparatus includes: an obtaining module 410 configured to obtain a response time to a service request of a client; a comparison module 420 configured to compare the response time with a preset threshold to obtain a calling result of the service request; and the selection module 430 is configured to determine whether a target server providing service needs to be selected for the service request based on the calling result.
In some embodiments of the present application, the comparing module 420 is configured to determine that the invoking is successful if the response time does not exceed the preset threshold; and the selecting module 430 is configured to determine that a target server providing service for the service request selection is not needed when the calling result is successful.
In some embodiments of the present application, the comparing module 420 is configured to determine that the invoking is failed if the response time exceeds the preset threshold; and the selecting module 430 is configured to determine that a target server providing a service is selected for the service request when the calling result is failure.
In some embodiments of the present application, the selection module 430 is configured to obtain each service node load of each server in the server cluster; calculating the load rate of each service node of each server based on the load of each service node; and determining the target server according to the load rate of each service node.
In some embodiments of the present application, the selecting module 430 is configured to obtain a load threshold of each service node of each server; and solving the ratio of the load of each service node to the load threshold of each service node to obtain the load rate of each service node.
In some embodiments of the present application, the selecting module 430 is configured to take a server corresponding to a minimum value of the load ratios of the service nodes as the target server.
In some embodiments of the present application, the selecting module 430 is configured to screen out at least one server from the load rates of the service nodes, where the at least one server is less than or equal to a preset load threshold; any one of the at least one server is taken as the target server.
Some embodiments of the present application further provide a computer-readable storage medium, on which a computer program is stored, which when executed by a processor can implement the operations of the method corresponding to any of the above-mentioned methods provided by the above-mentioned embodiments.
Some embodiments of the present application further provide a computer program product, which includes a computer program, wherein the computer program, when executed by a processor, can implement the operations of the method corresponding to any of the above-mentioned methods provided by the above-mentioned embodiments.
As shown in fig. 5, some embodiments of the present application provide an electronic device 500, the electronic device 500 comprising: a memory 510, a processor 520, and a computer program stored on the memory 510 and executable on the processor 520, wherein the method of any of the embodiments described above can be implemented when the processor 520 reads the program from the memory 510 via the bus 530 and executes the program.
The above description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined or explained in subsequent figures.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, 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, an element defined by the phrases "comprising one of 8230; \8230;" 8230; "does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.
Claims (10)
1. A systematic micro-service resource scheduling method is characterized by comprising the following steps:
acquiring response time of a service request of a client;
comparing the response time with a preset threshold value to obtain a calling result of the service request;
and determining whether a target server for providing service needs to be selected for the service request or not based on the calling result.
2. The method of claim 1, wherein comparing the response time with a preset threshold to obtain a calling result of the service request comprises:
if the response time does not exceed the preset threshold, the calling result is successful;
the determining whether a target server providing service needs to be selected for the service request based on the calling result comprises:
and when the calling result is successful, determining that a target server providing service does not need to be selected for the service request.
3. The method according to claim 1 or 2, wherein comparing the response time with a preset threshold to obtain the invoking result of the service request comprises:
if the response time exceeds the preset threshold, the calling result is failure;
the determining whether a target server providing service needs to be selected for the service request based on the calling result includes:
and when the calling result is failure, determining to select a target server for providing service for the service request.
4. The method of claim 3, wherein after the determining selects a target server to service for the service request, the method further comprises:
acquiring each service node load of each server in a server cluster;
calculating the load rate of each service node of each server based on the load of each service node;
and determining the target server according to the load rate of each service node.
5. The method of claim 4, wherein said calculating a respective service node load rate for said respective server based on said respective service node load comprises:
acquiring a load threshold value of each service node of each server;
and solving the ratio of the load of each service node to the load threshold of each service node to obtain the load rate of each service node.
6. The method as claimed in claim 4, wherein said determining said target server by said each service node load rate comprises:
and taking the server corresponding to the minimum value in the load rates of the service nodes as the target server.
7. The method of claim 4, wherein said determining said target server by said service node load rates comprises:
screening out at least one server which is less than or equal to a preset load threshold value from the load rate of each service node;
any one of the at least one server is taken as the target server.
8. A systematic micro-service resource scheduling device, comprising:
the acquisition module is configured to acquire response time of a service request of a client;
the comparison module is configured to compare the response time with a preset threshold value to obtain a calling result of the service request;
and the selection module is configured to determine whether a target server providing service needs to be selected for the service request or not based on the calling result.
9. A computer-readable storage medium, having stored thereon a computer program, wherein the computer program, when executed by a processor, performs the method of any of claims 1-7.
10. An electronic device comprising a memory, a processor, and a computer program stored on the memory and running on the processor, wherein the computer program, when executed by the processor, performs the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211664640.3A CN115964171A (en) | 2022-12-23 | 2022-12-23 | Systematic micro-service resource scheduling method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211664640.3A CN115964171A (en) | 2022-12-23 | 2022-12-23 | Systematic micro-service resource scheduling method and device and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115964171A true CN115964171A (en) | 2023-04-14 |
Family
ID=87357438
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211664640.3A Pending CN115964171A (en) | 2022-12-23 | 2022-12-23 | Systematic micro-service resource scheduling method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115964171A (en) |
-
2022
- 2022-12-23 CN CN202211664640.3A patent/CN115964171A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110138837B (en) | Request processing method and device, computer equipment and storage medium | |
| US11526386B2 (en) | System and method for automatically scaling a cluster based on metrics being monitored | |
| CN107819797B (en) | Access request processing method and device | |
| CN111209110B (en) | Task scheduling management method, system and storage medium for realizing load balancing | |
| CN109960575B (en) | Computing capacity sharing method, system and related equipment | |
| CN108833205B (en) | Information processing method, information processing device, electronic equipment and storage medium | |
| CN112099935B (en) | Task processing method and device | |
| CN112286770A (en) | Alarm notification method, device, computer equipment and storage medium | |
| CN110708196A (en) | Data processing method and device | |
| CN110990245A (en) | Micro-service operation state judgment method and device based on call chain data | |
| EP3399413B1 (en) | Component logical threads quantity adjustment method and device | |
| CN114844809B (en) | Multi-factor arbitration method and device based on network heartbeat and kernel disk heartbeat | |
| CN115544044A (en) | Data consistency keeping method, device, equipment and storage medium | |
| CN109766198B (en) | Stream processing method, device, equipment and computer readable storage medium | |
| EP3672203A1 (en) | Distribution method for distributed data computing, device, server and storage medium | |
| CN112631756A (en) | Distributed regulation and control method and device applied to space flight measurement and control software | |
| CN111181777B (en) | Service degradation method, device, computer equipment and storage medium | |
| CN115964171A (en) | Systematic micro-service resource scheduling method and device and electronic equipment | |
| CN108234658B (en) | Method and device for sensing health condition of server cluster and server | |
| CN116032932A (en) | Cluster management method, system, equipment and medium for edge server | |
| CN115695435A (en) | Method and device for dynamically adjusting node flow, electronic equipment and storage medium | |
| CN115150399A (en) | Load balancing method, load balancing device, processing system and storage medium | |
| CN110944051B (en) | Method and device for realizing load balance, electronic equipment and storage medium | |
| CN111625334A (en) | Service migration method and system | |
| CN110955579A (en) | Ambari-based large data platform monitoring method |
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 |