Optimization method and system for 302 scheduling server, equipment and storage medium
By deploying agent processes on edge servers, monitoring device status in real time and updating scheduling weights, the problem of untimely scheduling weight configuration in the prior art is solved, and rapid response to emergencies and efficient utilization of device resources are achieved.
Patent Information
- Application Number
- CN202311140257.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-09-05
- Publication Date
- 2024-12-13
AI Technical Summary
In the prior art, the 302 scheduling server is not timely configured to deal with emergency situations in a timely manner, resulting in problems such as edge equipment bandwidth reaching the upper limit, service quality decline, equipment abnormality, etc. It requires professional operation and maintenance intervention and has a long response time.
Deploy the agent process on the edge server, monitor the operating status of the device in real time, report information such as maximum bandwidth, current bandwidth, download speed, etc. to the data management center, and convert the data management center into readable cache service data, and send it periodically to 302 scheduling. Server, dynamically updates scheduling weights, and uses asynchronous processes and message queues to achieve real-time scheduling weight adjustment.
Real-time configuration of scheduling weights can be realized, and can respond to emergencies in a timely manner, reduce labor costs, maximize equipment utilization, and improve service response speed.
Smart Images
Figure CN119135521A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of computer technology and relates to an optimization method and system, device, and storage medium for a 302 scheduling server. Background Art
[0002] CDN302 scheduling uses HTTP302 features to redirect Internet users' requests to the nearest and fastest edge nodes based on the user's geographic location to provide services. It also has functions such as anti-attack, load balancing, and hotspot dispersion. Conventional configuration of CDN302 scheduling often requires experienced operation and maintenance. Based on basic information such as edge device service bandwidth capacity and device load capacity, the configurable scheduling weight of a device is calculated. Then, through the configuration platform, a specific 302 scheduling configuration is generated and sent to the scheduling device.
[0003] However, the actual capabilities of edge devices in existing technologies are often very different from the pre-approved service capabilities. In addition, the CDN business traffic model is complex and the differences are large, which increases this difference. When encountering problems such as a certain edge device reaching the maximum bandwidth warning, download speed degradation, or even abnormal service of the edge device, such as: the edge node bandwidth reaches the upper limit, the service quality decreases, and the service software / device is abnormally interrupted, the device scheduling bandwidth can only be modified again through the configuration platform, or even the edge device can be temporarily increased or disabled for emergency processing. From the discovery of the problem to the temporary emergency processing of the problem, the only way to intervene and schedule is to rely on operation and maintenance monitoring means, with a long time interval and untimely response. Summary of the invention
[0004] In order to provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. The summary is not an extensive review, nor is it intended to identify key / critical components or delineate the scope of protection of these embodiments, but rather serves as a prelude to the detailed description that follows.
[0005] In order to solve the problems existing in the related art, the embodiments of the present disclosure disclose an optimization method and system, device, and storage medium for a 302 scheduling server, which are used to solve the problem that the 302 scheduling server in the prior art fails to configure scheduling weights in a timely manner and cannot respond to emergencies.
[0006] In some embodiments, an optimization method for a 302 scheduling server is provided, which is applied to an optimization system for the 302 scheduling server, the system comprising: a scheduling control platform, a data management center, an edge server and the 302 scheduling server, the method comprising:
[0007] Obtain the initial scheduling weight configured by the operation and maintenance personnel, and send the initial scheduling weight configured to the scheduling server 302 for configuration;
[0008] Deploy the agent process on the edge node of the edge server to collect the first cache service data;
[0009] The agent process sends the first cache service data to the data management center;
[0010] The data management center formats the first cache service data to generate converted second cache service data; the second cache service data is readable data of the 302 scheduling server;
[0011] The data management center periodically sends the second cache service data to the scheduling server 302;
[0012] 302 The scheduling server updates the scheduling weight.
[0013] Preferably, before the scheduling server updates the scheduling weight 302, the method further includes:
[0014] The data management center identifies service status information according to the second cache service data; the service status information includes running or stopped running;
[0015] The service status information is sent to the 302 dispatch server in real time.
[0016] Preferably, the data management center periodically sends the second cache service data to the scheduling server 302 through an API timing method.
[0017] Preferably, the data management center sends the service status information to the 302 scheduling server in real time via an MQ message queue.
[0018] Preferably, the first cache service data and the second cache service data include device download speed, current bandwidth, and maximum bandwidth information.
[0019] Preferably, the 302 scheduling server transmits the second cache service data to the 302 scheduling server synchronously through an asynchronous process.
[0020] Preferably, the scheduling server updates the scheduling weight 302 by comparing the obtained current cycle request QPS with the previous cycle request QPS to make adjustments, so as to adjust the edge server's request to be as close as possible to the maximum loadable request.
[0021] Preferably, the growth ratio of the QPS requested in the previous cycle compared with the QPS requested in the current cycle is controlled.
[0022] In some embodiments, an optimization system for a 302 dispatch server is disclosed, including a dispatch control platform, a data management center, an edge server, and a 302 dispatch server;
[0023] The scheduling control platform is used to obtain the configuration scheduling weight of the operation and maintenance personnel and send it to the 302 scheduling server;
[0024] The data management center includes a database module and a message queue MQ module.
[0025] In some embodiments, a device is disclosed, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the optimization method for 302 scheduling a server as described above is performed.
[0026] In some embodiments, a computer-readable storage medium is disclosed, on which a computer program is stored, and the program is executed by a processor as described above for the optimization method for 302 scheduling a server.
[0027] The optimization method, system, device, and storage medium for the 302 scheduling server provided in the embodiments of the present disclosure can achieve the following technical effects:
[0028] The disclosed embodiment uses an agent process implanted in the edge server to monitor the device operation status in real time and report the first cache service data, including the maximum bandwidth, current bandwidth, download speed and other information, to the data management center. The data management center converts it into the second cache service data that can be read by the 302 scheduling server. The 302 scheduling server can dynamically obtain the cache service data and then update the scheduling weight. Therefore, the disclosed embodiment can configure the scheduling weight in real time and can cope with various emergencies. Compared with the prior art, it has the following advantages:
[0029] 1. No need for professional operation and maintenance personnel to calculate the configurable dispatching weight of the device, saving manpower costs;
[0030] 2. More reasonable configuration to maximize the use of equipment;
[0031] 3. If any abnormal situation occurs during the service process, it can be dealt with effectively and promptly.
[0032] The above general description and the following description are exemplary and explanatory only and are not intended to limit the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] One or more embodiments are exemplarily described by corresponding drawings, which do not limit the embodiments. Elements with the same reference numerals in the drawings are shown as similar elements, and the drawings do not constitute a scale limitation, and wherein:
[0034] Figure 1 is a schematic diagram of an optimization system for a 302 scheduling server provided by an embodiment of the present disclosure;
[0035] Figure 2 is a flow chart of an optimization method for 302 scheduling server provided by an embodiment of the present disclosure;
[0036] Figure 3 It is a schematic diagram of an optimization device for a 302 scheduling server provided in an embodiment of the present disclosure. DETAILED DESCRIPTION
[0037] In order to be able to understand the features and technical contents of the embodiments of the present disclosure in more detail, the implementation of the embodiments of the present disclosure is described in detail below in conjunction with the accompanying drawings. The attached drawings are for reference only and are not used to limit the embodiments of the present disclosure. In the following technical description, for the convenience of explanation, a full understanding of the disclosed embodiments is provided through multiple details. However, one or more embodiments can still be implemented without these details. In other cases, to simplify the drawings, well-known structures and systems can be simplified for display.
[0038] The following description and accompanying drawings fully illustrate specific embodiments of the present invention so that those skilled in the art can practice them. Other embodiments may include structural, logical, electrical, process and other changes. The examples represent possible changes only. Unless explicitly required, separate components and functions are optional, and the order of operations may vary. The parts and features of some embodiments may be included in or replace the parts and features of other embodiments. The scope of the embodiments of the present invention includes the entire scope of the claims, and all available equivalents of the claims. In this article, each embodiment may be represented individually or generally by the term "invention", which is only for convenience, and if more than one invention is disclosed in fact, it is not intended to automatically limit the scope of the application to any single invention or inventive concept. In this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, without requiring or implying any actual relationship or order between these entities or operations. Moreover, the terms "comprises", "includes" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method or device. In the absence of further restrictions, the elements defined by the sentence "including a..." do not exclude the presence of other identical elements in the process, method or device including the elements. The various embodiments herein are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same and similar parts between the various embodiments can be referred to each other. For the methods, products, etc. disclosed in the embodiments, since they correspond to the method part disclosed in the embodiments, the description is relatively simple, and the relevant parts can be referred to the method part description.
[0039] In the existing technology, the actual capabilities of edge devices are often very different from the pre-approved service capabilities. In addition, the CDN business traffic model is complex and the differences are large, which increases this difference. When encountering problems such as a certain edge device reaching the maximum bandwidth warning, download speed degradation, or even abnormal service of the edge device, such as: the edge node bandwidth reaches the upper limit, the service quality decreases, and the service software / device is abnormally interrupted, the device scheduling bandwidth can only be modified again through the configuration platform, or even temporarily increase or disable the edge device for emergency treatment. From the discovery of the problem through monitoring to the temporary emergency treatment of the problem, it can only rely on operation and maintenance monitoring means to intervene in the scheduling, and the time interval is long and the response is not timely.
[0040] In order to solve the problems existing in the related art, the embodiment of the present disclosure discloses an optimization method and system, device, and storage medium for the scheduling server 302. In this way, the scheduling weight can be configured in real time to cope with various emergencies.
[0041] Combination Figure 1 As shown, the embodiment of the present disclosure provides a schematic diagram of an optimization system for a 302 scheduling server. The optimization system for the 302 scheduling server includes a scheduling control platform, a data management center, an edge server and a 302 scheduling server; the scheduling control platform is used to obtain the configuration scheduling weight of the operation and maintenance personnel and send it to the 302 scheduling server; the data management center includes a database module and a message queue MQ module.
[0042] Combination Figure 2 As shown, the embodiment of the present disclosure provides an optimization method for 302 scheduling server, including:
[0043] S210, obtaining the initial scheduling weight configured by the operation and maintenance personnel, and sending the initial scheduling weight configured to the scheduling server 302 for configuration.
[0044] S220, deploying an agent process on an edge node of an edge server to collect first cache service data;
[0045] S230: The agent process sends the first cache service data to the data management center.
[0046] S240, the data management center formats the first cache service data to generate converted second cache service data; the second cache service data is readable data of the 302 scheduling server.
[0047] S250, the data management center periodically sends the second cache service data to the scheduling server 302;
[0048] S260, 302 The scheduling server updates the scheduling weight.
[0049] It should be understood that the first cache service data and the second cache service data include device download speed, current bandwidth, and maximum bandwidth information. By using the implanted edge server program agent, the server operation status is monitored in real time, and the maximum bandwidth, current bandwidth, download speed and other information are reported to the data management center. The data management center converts the acquired first cache service data into the second cache service data that can be read by the 302 scheduling server. The 302 scheduling server periodically obtains the information status of all edge servers provided through the interface, that is, the first cache service data. Based on the maximum bandwidth, combined with multiple dimensions such as load capacity and download speed, the available bandwidth is dynamically calculated, and then the weight value is calculated.
[0050] In an optimized embodiment, before the scheduling server updates the scheduling weight 302, the following steps are also included:
[0051] The data management center identifies the service status information according to the second cache service data; the service status information includes running or stopped running; and sends the service status information to the scheduling server 302 in real time.
[0052] The data management center periodically sends the second cache service data to the scheduling server 302 through an API timing method. The data management center sends the service status information to the scheduling server 302 in real time through an MQ message queue method.
[0053] It should be understood that there are two ways to send cache service data to the 302 scheduling server. One is to send the second cache service data through the API timing method for conventionally calculating the weight value. It should be noted that the above-mentioned timing cycle time is not specifically limited in this application and can be determined according to actual conditions. It is sent in real time through the MQ message queue method, which is used to detect emergency situations. The corresponding edge server can be obtained in the first time when it stops running, so that the 302 scheduling server can quickly change the scheduling weight.
[0054] Further, the 302 scheduling server transmits the second cache service data to the 302 scheduling server synchronously through an asynchronous process.
[0055] In an optimized embodiment, the scheduling server 302 updates the scheduling weight by comparing the obtained current cycle request QPS with the previous cycle request QPS, and makes adjustments to adjust the edge server's request to be as close to the maximum loadable request as possible, and controls the growth ratio of the previous cycle request QPS to the current cycle request QPS.
[0056] It should be understood that QPS is a measure of the amount of traffic processed by an edge server within a specified time. The disclosed embodiment regulates the edge server to use the preset maximum loadable request as much as possible. For example, the preset maximum loadable request is 80% of the edge server's limit QPS. Then, the edge server is used to reach 80% of the limit QPS as much as possible.
[0057] A specific example is that the maximum bandwidth load ratio of the edge server is configured to 80%, that is, the actual running volume of each server is controlled at 80% of the maximum bandwidth. The bandwidth load ratio of each network card of the multi-network card server is configured to 80%, that is, a single server has multiple network cards, and the traffic of each network card is controlled at 80% of the maximum bandwidth. The Qps increase control strength is configured to 1.2. It can be understood that the Qps of the next second cannot exceed 1.2 times of the previous second, and the control traffic increases unnecessarily.
[0058] The data information results of the single network card server are shown in Table 1.
[0059] Table 1
[0060]
[0061] As shown in the above data, the interface obtains the information of the three servers as shown in the table above. Since cache2 is down, it means that the edge server has stopped running, so cache2 is no longer scheduled. Cache1 and cache3 are scheduled according to the ratio of 96:80, that is, 6:5 weight, based on cur_qps, that is, the QPS of the previous cycle request. Calculate the max_qps that the two servers can carry. max_qps is the maximum loadable request.
[0062] cache1: max_qps / qps = available bandwidth / current bandwidth, i.e. max_qps = 600*96 / 80 = 720;
[0063] cache3: max_qps / qps = carryable bandwidth / current bandwidth, that is, max_qps = 500*80 / 60 = 666.
[0064] When it is lower than max_qps, it is scheduled normally according to the 6:5 weight. When the statistical qps reaches max_qps, it means that the preset load limit of the edge server has been reached, and the requests are dispatched to the adjacent servers. When the statistical qps exceeds cur_qps*1.2, it means that the request growth is too fast, and the excess requests are dispatched to the adjacent servers. The adjacent servers cannot bear the load, and they are further dispatched to the parent server.
[0065] Data information of multi-NIC servers, such as PCDN servers. PCDN servers are different from the above situation and have multiple NIC IP services. Therefore, each NIC has its own independent loadable bandwidth information and current bandwidth information. The scheduling ratio is calculated according to "loadable / available bandwidth", and max_qps is calculated in the same way to control the traffic scheduling speed.
[0066] Combination Figure 3 As shown, the embodiment of the present disclosure provides a device for optimizing the scheduling server 302, including a processor and a memory. Optionally, the device may also include a communication interface and a bus. The processor, the communication interface, and the memory may communicate with each other through the bus. The communication interface may be used for information transmission. The processor may call the logic instructions in the memory to execute the optimization method for the scheduling server 302 of the above embodiment.
[0067] The embodiment of the present disclosure provides a storage medium storing computer executable instructions, wherein the computer executable instructions are configured to execute the above-mentioned optimization method for 302 scheduling server.
[0068] The above-mentioned storage medium may be a transient computer-readable storage medium or a non-transient computer-readable storage medium. Non-transient storage media include: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes, and may also be a transient storage medium.
[0069] The disclosed embodiment discloses an optimization method and system, device, and storage medium for a 302 scheduling server. The system includes: a scheduling control platform, a data management center, an edge server, and a 302 scheduling server. The method includes: obtaining the initial scheduling weight configured by the operation and maintenance personnel, and sending the initial scheduling weight configured to the 302 scheduling server for configuration; deploying the agent process at the edge node of the edge server to collect the first cache service data; the agent process sends the first cache service data to the data management center; the data management center formats the first cache service data to generate the converted second cache service data, and the data management center periodically sends the second cache service data to the 302 scheduling server; and updating the scheduling weight. Therefore, the disclosed embodiment configures the scheduling weight by periodically acquiring the edge server data, and can intervene in the scheduling in response to an emergency, and the response is faster.
[0070] The above description and the accompanying drawings fully illustrate the embodiments of the present disclosure so that those skilled in the art can practice them. Other embodiments may include structural, logical, electrical, process and other changes. The embodiments represent only possible changes. Unless explicitly required, separate components and functions are optional, and the order of operation may vary. The parts and features of some embodiments may be included in or replace the parts and features of other embodiments. Moreover, the words used in this application are only used to describe the embodiments and are not used to limit the claims. As used in the description of the embodiments and the claims, unless the context clearly indicates, the singular forms of "a", "an" and "the" are intended to include plural forms as well. Similarly, the term "and / or" as used in this application refers to any and all possible combinations of listings containing one or more associated ones. In addition, when used in the present application, the term "comprise" and its variants "comprises" and / or comprising refer to the presence of stated features, wholes, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or groups thereof. In the absence of further restrictions, the elements defined by the sentence "comprising a ..." do not exclude the presence of other identical elements in the process, method or device comprising the elements. In this article, each embodiment may focus on the differences from other embodiments, and the same and similar parts between the various embodiments may refer to each other. For the methods, products, etc. disclosed in the embodiments, if they correspond to the method part disclosed in the embodiments, then the relevant parts can refer to the description of the method part.
[0071] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software may depend on the specific application and design constraints of the technical solution. The technicians may use different methods for each specific application to implement the described functions, but such implementations should not be considered to exceed the scope of the embodiments of the present disclosure. The technicians may clearly understand that, for the convenience and simplicity of description, the specific working processes of the systems, systems and units described above may refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here.
[0072] The flowchart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to the embodiment of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of the code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. In some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which can depend on the functions involved. In the description corresponding to the flowchart and the block diagram in the accompanying drawings, the operations or steps corresponding to different boxes can also occur in a different order from the order disclosed in the description, and sometimes there is no specific order between different operations or steps. For example, two consecutive operations or steps can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which can depend on the functions involved. Each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented by a dedicated hardware-based system that performs the specified functions or actions, or may be implemented by a combination of dedicated hardware and computer instructions.
Claims
1. An optimization method for a 302 scheduling server, characterized in that: The optimization system applied to the 302 dispatch server includes: a dispatch control platform, a data management center, an edge server and the 302 dispatch server, and the method includes: Obtain the initial scheduling weight configured by the operation and maintenance personnel, and send the initial scheduling weight configured to the scheduling server 302 for configuration; Deploy the agent process on the edge node of the edge server to collect the first cache service data; The agent process sends the first cache service data to the data management center; The data management center formats the first cache service data to generate converted second cache service data; the second cache service data is readable data of the 302 scheduling server; The data management center periodically sends the second cache service data to the scheduling server 302; 302 The scheduling server updates the scheduling weight.
2. The method according to claim 1, characterized in that: 302 The scheduling server updates the scheduling weight, which also includes: The data management center identifies service status information according to the second cache service data; the service status information includes running or stopped running; The service status information is sent to the 302 dispatch server in real time.
3. The method according to claim 2, characterized in that The data management center periodically sends the second cache service data to the scheduling server 302 through an API timing method.
4. The method according to claim 2, characterized in that: The data management center sends service status information to the 302 scheduling server in real time through the MQ message queue.
5. The method according to claim 1, characterized in that: 302 The scheduling server updates the scheduling weight by comparing the obtained current cycle request QPS with the previous cycle request QPS to make adjustments and regulate the edge server's request to be as close as possible to the maximum loadable request.
6. The method according to claim 5, characterized in that Controls the growth ratio of the previous cycle's request QPS compared to the current cycle's request QPS.
7. The method according to claim 1, characterized in that The 302 scheduling server transmits the second cache service data to the 302 scheduling server synchronously through an asynchronous process.
8. An optimization system for a 302 dispatch server, characterized in that: Including dispatch control platform, data management center, edge server and 302 dispatch server; The scheduling control platform is used to obtain the configuration scheduling weight of the operation and maintenance personnel and send it to the 302 scheduling server; The data management center includes a database module and a message queue MQ module.
9. A device, characterized in that: The method comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the method according to any one of claims 1 to 7 is implemented.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.