CN110336848B - Scheduling method, scheduling system and scheduling equipment for access request - Google Patents
Scheduling method, scheduling system and scheduling equipment for access request Download PDFInfo
- Publication number
- CN110336848B CN110336848B CN201910327867.0A CN201910327867A CN110336848B CN 110336848 B CN110336848 B CN 110336848B CN 201910327867 A CN201910327867 A CN 201910327867A CN 110336848 B CN110336848 B CN 110336848B
- Authority
- CN
- China
- Prior art keywords
- scheduling
- access request
- cache server
- server
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a scheduling method, a scheduling system and scheduling equipment of an access request, wherein the method comprises the following steps: receiving an access request sent by a client, and scheduling the access request to a first cache server; receiving and analyzing response information fed back by the first cache server aiming at the access request, and generating a redirection link pointing to a second cache server if the response information indicates that the first cache server cannot provide the resource pointed by the access request; and sending the redirection link to the client, so that the client reinitiates an access request to the second cache server according to the redirection link. According to the technical scheme, the probability of responding to the access request can be improved, and therefore the use experience of a user is improved.
Description
Technical Field
The present invention relates to the field of internet technologies, and in particular, to a scheduling method, a scheduling system, and a scheduling device for an access request.
Background
In a current CDN (Content Delivery Network), after receiving an access request sent by a client, a scheduling system may calculate a hash value through a hash algorithm according to information such as a request IP address, a URL (Uniform Resource Locator), and a domain name carried in the access request, and schedule the access request to a cache server corresponding to the calculated hash value, so as to provide a Resource to which the access request points to the client through the cache server.
In practical applications, there may be a series of scenarios, so that the cache server calculated by the hash algorithm cannot normally provide the cache resource to the client. For example, when the customer service platform migrates, the scheduling system may not update the node information in time, which results in whether the node information is calculated by the hash algorithm or an old cache server, and thus the old cache server cannot respond to the access request of the client. For another example, when the DNS cache in the client is not cleared, the scheduling system may schedule the access request sent by the client to a non-existing cache server or a cache server that cannot provide resources, and thus the access request may also be unable to be responded.
In the prior art, when an access request of a client cannot be responded, a scheduling system feeds back prompt information of request failure to the client, which undoubtedly affects the use experience of a user.
Disclosure of Invention
The application aims to provide a scheduling method, a scheduling system and scheduling equipment of an access request, which can improve the probability of the access request being responded, thereby improving the use experience of a user.
In order to achieve the above object, an aspect of the present application provides a method for scheduling an access request, where the method is applied in a scheduling system, and the method includes: receiving an access request sent by a client, and scheduling the access request to a first cache server; receiving and analyzing response information fed back by the first cache server aiming at the access request, and if the response information indicates that the first cache server cannot provide the resource pointed by the access request, generating a redirection link pointed to a second cache server; and sending the redirection link to the client, so that the client reinitiates an access request to the second cache server according to the redirection link.
In order to achieve the above object, another aspect of the present application further provides a scheduling system, including: the first scheduling unit is used for receiving an access request sent by a client and scheduling the access request to a first cache server; a redirection link generation unit, configured to receive and analyze response information fed back by the first cache server for the access request, and generate a redirection link pointing to a second cache server if the response information indicates that the first cache server cannot provide a resource to which the access request points; and the second scheduling unit is used for sending the redirection link to the client so that the client reinitiates an access request to the second cache server according to the redirection link.
In order to achieve the above object, another aspect of the present application further provides a scheduling apparatus, which includes a processor and a memory, where the memory is used to store a computer program, and the computer program, when executed by the processor, implements the above scheduling method for access requests.
Therefore, according to the technical scheme provided by the application, after the access request sent by the client is received, the access request can be dispatched to the first cache server. The first cache server may then feed back response information to the scheduling system for the access request. The scheduling system may parse the response information, and if the response information indicates that the first cache server cannot provide the resource to which the access request is directed, the scheduling system may trigger secondary scheduling to schedule the access request to another cache server. Specifically, the scheduling system may generate a redirection link to the second cache server and send the redirection link to the client. In this way, after receiving the redirection link, the client may initiate an access request to the second cache server, so that the corresponding cache resource may be obtained from the second cache server. According to the technical scheme, when the current cache server cannot normally provide cache resources, the secondary scheduling process can be triggered, so that the access request of the client can be processed by other cache servers, the probability of response of the access request is improved, and the use experience of a user can be improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a schematic diagram of a CDN system architecture according to an embodiment of the present invention;
FIG. 2 is a schematic diagram illustrating a method for scheduling access requests according to an embodiment of the present invention;
FIG. 3 is a first schematic diagram of forwarding an access request in an embodiment of the invention;
FIG. 4 is a second diagram illustrating forwarding of an access request in an embodiment of the invention;
fig. 5 is a functional block diagram of a scheduling system according to an embodiment of the present invention.
Detailed Description
To make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
The application provides a scheduling method of access requests, which can be applied to a scheduling system. Referring to fig. 1, the CDN in which the scheduling system is located may include a plurality of scheduling systems, and each scheduling system may correspond to one server cluster. One or more cache servers may be included in the server cluster, and each network resource may be stored in the cache server. Generally, each cache server in the same server cluster may have the same resource pool, that is, each cache server in the same server cluster may store the same network resource. As shown in fig. 1, the CDN may further include a central server, and the central server may be connected to each scheduling system. In the central server, system information of the respective scheduling systems may be stored. The system information may include, for example, a communication address of the scheduling system, a resource pool to which the scheduling system belongs, the number of cache servers included in a server cluster corresponding to the scheduling system, and a current operating state of the scheduling system.
Referring to fig. 2, the scheduling method for an access request in the scheduling system provided by the present application may include the following steps.
S1: and receiving an access request sent by a client, and scheduling the access request to a first cache server.
In this embodiment, when a client needs to access a certain network resource, an access request may be initiated for the network resource, where the access request may carry information such as an IP address (or a domain name) where a server (or a server cluster) storing the network resource is located, and a resource identifier of the network resource. The access request may be received by a scheduling system in the CDN. Subsequently, the scheduling system may schedule the access request to a cache server in its own server cluster. Specifically, the scheduling system may calculate a hash value through a hash algorithm according to the access request, and schedule the access request to the first cache server corresponding to the hash value.
S3: and receiving and analyzing response information fed back by the first cache server aiming at the access request, and generating a redirection link pointing to a second cache server if the response information indicates that the first cache server cannot provide the resource pointed by the access request.
In this embodiment, after receiving the access request sent by the scheduling system, the first cache server may locally query whether a resource to which the access request points exists. If the resource exists, the corresponding resource can be provided for the client, and normal response information is fed back to the scheduling system. If the resource is not available, the first cache server cannot provide the required resource to the client, and at this time, the first cache server may feed back response information representing that the resource to which the access request is directed cannot be provided to the scheduling system.
In this embodiment, after receiving the response information fed back by the first cache server, the scheduling system may analyze the response information, so as to determine whether the response information indicates that the first cache server cannot provide the corresponding resource. If the response information indicates that the first cache server cannot provide the corresponding resource, the scheduling system may trigger a secondary scheduling process to schedule the access request to another cache server in the server cluster, so as to provide the corresponding resource to the client through the another cache server.
In a specific application scenario, in response information fed back by the first cache server, whether a resource corresponding to the access request can be provided may be indicated by a carried status code or by a specified field in header information. In this way, the scheduling system may identify a specified field in the header information of the response information, or identify a status code carried in the response information, and if the assignment of the specified field is an assignment indicating that the cache resource cannot be acquired, or the status code is a status code indicating that the cache resource cannot be acquired, the scheduling system may determine that the response information indicates that the first cache server cannot provide the resource to which the access request points. For example, the status code indicating that the cache resource cannot be acquired may be, for example, a-1 status code, a 502 status code, or a 503 status code. The specified field in the header information may be, for example, an Not _ CF field. If the assignment of the Not _ CF field is Yes, this indicates that the first cache server cannot provide the resource to which the access request is directed.
In an embodiment, after triggering the secondary scheduling process, the scheduling system may determine a cache server currently in an available state in the server cluster where the first cache server is located. Wherein, for the cache server which is fed back and is characterized by being incapable of providing the resource, the scheduling system can mark the working state of the cache server as unavailable. For example, if the first cache server cannot provide the resource corresponding to the access request, the scheduling system may mark the operating state of the first cache server as unavailable after parsing the response information fed back by the first cache server. Then, after triggering the secondary scheduling, the scheduling system may remove the cache server marked as unavailable from the selectable range, and the remaining other cache servers in the server cluster may be used as the cache servers currently in an available state. For the cache servers which are currently in the available state, the scheduling system can arbitrarily select one cache server from the cache servers as the second cache server. Of course, the scheduling system may also select a relatively idle cache server from the currently available cache servers as the second cache server according to the existing load balancing policy. Subsequently, the dispatch system may use the communication address of the second cache server as the generated redirection link. Wherein the redirection link may be implemented by 302 redirection. Because the second cache server and the first cache server are in the same server cluster, the first cache server and the second cache server have the same cache resources. This ensures that the redirected second cache server can normally provide the client with the required resources.
It should be noted that the first cache server and the second cache server may originally be in the same server cluster, and therefore may have the same cache resource. Subsequently, for the reason that the DNS record of the client is not cleared, or the first cache server is off-shelf, or the first cache server is removed from the original server cluster, and the like, after the access request initiated by the client is scheduled to the first cache server, the first cache server cannot provide the corresponding cache resource. At this time, the scheduling system may select, according to the response information fed back by the first cache server, another cache server originally located in the same server cluster as the first cache server, and provide the corresponding cache resource to the client through the selected another cache server.
S5: and sending the redirection link to the client so that the client reinitiates an access request to the second cache server according to the redirection link.
In this embodiment, after the scheduling system generates the redirection link, the scheduling system may feed back the redirection link to the client. Subsequently, the client may reinitiate the access request according to the redirection link. The reinitiated access request can be scheduled to the second cache server by the scheduling system, so that the corresponding resource is fed back to the client through the second cache server. If the second cache server still cannot provide the corresponding resource, the scheduling system may trigger the secondary scheduling process again, generate a redirection link pointing to the third cache server, and feed back the redirection link pointing to the third cache server to the client. Certainly, in practical applications, in order to avoid that the waiting time of the client is long due to excessive generation of the redirection link, after the redirection link is generated for a fixed number of times, if the corresponding resource still cannot be provided, the scheduling system may feed back a prompt message indicating that an access error occurs to the client, and stop triggering the secondary scheduling.
In an embodiment, after receiving an access request sent by a client, a scheduling system may further determine whether an available cache server exists in its own server cluster. If there are cache servers available, the access request may be scheduled to the first cache server therein as described in step S1. In some application scenarios, a collective failure may occur in a server cluster corresponding to a scheduling system, or the scheduling system and the corresponding server cluster cannot normally communicate, and at this time, the scheduling system cannot detect that an available cache server exists in the server cluster. At this time, the scheduling system cannot process the access request through its own server cluster. In this case, the dispatching system may also trigger secondary dispatching and forward the access request to another dispatching system to process the access request through a server cluster under the other dispatching system.
Referring to fig. 3, if there is no available cache server under the current scheduling system, a scheduling request may be sent to the central server, where the scheduling request may carry a system identifier of the current scheduling system itself. In this way, since the central server stores the system information of each scheduling system, and the system information may represent which scheduling systems are currently in an available state and which scheduling systems are in the same resource pool, the central server may identify the resource pool corresponding to the scheduling system that sent the scheduling request, and select another scheduling system that is currently in an available state from among the scheduling systems corresponding to the resource pool. For example, the plurality of scheduling systems connected to the central server may be divided according to resource pools. Multiple scheduling systems corresponding to the same resource pool may be divided into the same scheduling system group. In this way, after the central server identifies the resource pool corresponding to the scheduling system that sent the scheduling request, in order to ensure that the reselected scheduling system can normally process the access request of the client, it may select one scheduling system in an available state from the scheduling systems corresponding to the identified resource pool. Specifically, for the scheduling system sending the scheduling request, the corresponding server cluster is currently in an unavailable state, so the central server may mark the scheduling system as unavailable as well. In selecting a dispatch system, the central server may eliminate the dispatch systems marked as unavailable from the selectable range and select one of the dispatch systems from the remaining dispatch systems as the other dispatch system in the available state as described above. Subsequently, the central server may feed back the communication address of the other scheduling system to the scheduling system that sent the scheduling request. In this way, the dispatching system sending the dispatching request may receive the communication address of the other dispatching system fed back by the central server, and forward the access request to the other dispatching system according to the communication address, so as to process the access request through the cache server under the other dispatching system.
In one embodiment, the scheduling system may include only the first cache server, and no other cache servers are available in addition to the first cache server. Referring to fig. 4, when the scheduling system analyzes the response information fed back by the first cache server and learns that the first cache server cannot provide corresponding resources, it is found that there is no cache server currently in an available state in the server cluster where the first cache server is located. In this case, the dispatch system may forward the access request to another dispatch system for processing by a cluster of servers under the other dispatch system. Specifically, in the manner described above, the scheduling system may send a scheduling request to the central server, so that the central server selects another scheduling system to process the access request of the client according to the resource pool corresponding to the scheduling system.
In one embodiment, the central server may periodically update the system information for each scheduling system. Specifically, each scheduling system may feed back its own system information to the central server according to a specified period agreed with the central server. The system information may include information such as the number of cache servers currently in a shared state in a server cluster corresponding to the scheduling system, a communication address where the scheduling system is currently located, and a resource pool corresponding to the scheduling system. Therefore, after the central server receives the system information reported by each scheduling system, the central server can mark the working state of each scheduling system and divide the scheduling systems according to the resource pools according to the latest resource pool information.
The present application further provides a scheduling system, please refer to fig. 5, the scheduling system includes:
the first scheduling unit is used for receiving an access request sent by a client and scheduling the access request to a first cache server;
a redirection link generating unit, configured to receive and analyze response information fed back by the first cache server for the access request, and generate a redirection link pointing to a second cache server if the response information indicates that the first cache server cannot provide a resource pointed to by the access request;
and the second scheduling unit is used for sending the redirection link to the client so that the client reinitiates an access request to the second cache server according to the redirection link.
In one embodiment, the redirection link generation unit includes:
the identification module is used for identifying a specified field in the header information of the response information or identifying a state code carried in the response information;
and the judging module is used for judging that the response information represents that the first cache server cannot provide the resource pointed by the access request if the assignment of the specified field is the assignment representing that the cache resource cannot be obtained or the status code represents the status code representing that the cache resource cannot be obtained.
In one embodiment, the redirection link generation unit includes:
an available cache server determining module, configured to determine, in a server cluster where the first cache server is located, a cache server currently in an available state;
the server selection module is used for selecting a second cache server from the cache servers in the available state at present and taking the communication address of the second cache server as the generated redirection link; each cache server in the server cluster where the first cache server is located has the same cache resource.
In an embodiment, the first scheduling unit is further configured to, if there is no cache server currently in an available state in the server cluster where the first cache server is located, forward the access request to another scheduling system, so as to process the access request through the server cluster under the another scheduling system.
In one embodiment, the first scheduling unit further comprises:
the server judging module is used for judging whether an available cache server exists under the scheduling system;
correspondingly, the first scheduling unit is configured to schedule the access request to a first cache server if an available cache server exists in the scheduling system; and if no available cache server exists under the dispatching system, forwarding the access request to another dispatching system so as to process the access request through a server cluster under the other dispatching system.
In one embodiment, the first scheduling unit includes:
a scheduling request sending module, configured to send a scheduling request to a central server, so that the central server identifies a resource pool corresponding to a scheduling system that sends the scheduling request, and selects, from among scheduling systems corresponding to the resource pool, another scheduling system that is currently in an available state;
and the access request forwarding module is used for receiving the communication address of the other dispatching system fed back by the central server and forwarding the access request to the other dispatching system according to the communication address.
The present application further provides a scheduling apparatus, which may include a processor and a memory, where the memory is used to store a computer program, and when the computer program is executed by the processor, the scheduling apparatus may implement the foregoing scheduling method for access requests.
The memory may be used to store software programs and modules of application software, and the processor may execute various functional applications and data processing by operating the software programs and modules stored in the memory. The memory may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory may further include memory remotely located from the processor, which may be connected to the computer terminal over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
Therefore, according to the technical scheme provided by the application, after the access request sent by the client is received, the access request can be dispatched to the first cache server. The first cache server may then feed back response information to the scheduling system for the access request. The scheduling system may parse the response information, and if the response information indicates that the first cache server cannot provide the resource to which the access request is directed, the scheduling system may trigger secondary scheduling to schedule the access request to another cache server. Specifically, the scheduling system may generate a redirection link to the second cache server and send the redirection link to the client. In this way, after receiving the redirection link, the client may initiate an access request to the second cache server, so that the corresponding cache resource may be obtained from the second cache server. According to the technical scheme, when the current cache server cannot normally provide cache resources, the secondary scheduling process can be triggered, so that the access request of the client can be processed by other cache servers, the probability of response of the access request is improved, and the use experience of a user can be improved.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and should not be taken as limiting the scope of the present invention, which is intended to cover any modifications, equivalents, improvements, etc. within the spirit and scope of the present invention.
Claims (14)
1. A scheduling method of an access request is applied to a scheduling system, a CDN in which the scheduling system is located includes a plurality of scheduling systems, each scheduling system corresponds to a server cluster, the server cluster includes at least one cache server, and the method includes:
receiving an access request sent by a client, and scheduling the access request to a first cache server;
receiving and analyzing response information fed back by the first cache server aiming at the access request, and if the response information indicates that the first cache server cannot provide the resource pointed by the access request, judging whether an available cache server exists in the scheduling system;
if the first cache server exists, selecting a cache server which is originally in the same server cluster as the first cache server and is currently in an available state as a second cache server, and generating a redirection link pointing to the second cache server; each cache server in the server cluster where the first cache server is located has the same cache resource;
sending the redirection link to the client, so that the client reinitiates an access request to the second cache server according to the redirection link;
if not, the access request is forwarded to another dispatching system so as to process the access request through a server cluster under the other dispatching system.
2. The method of claim 1, wherein parsing the response information fed back by the first cache server for the access request comprises:
identifying a specified field in header information of the response information, or identifying a state code carried in the response information;
correspondingly, if the assignment of the specified field is an assignment representing that the cache resource cannot be obtained, or the status code is a status code representing that the cache resource cannot be obtained, it is determined that the response information represents that the first cache server cannot provide the resource to which the access request points.
3. The method of claim 1, wherein generating the redirect link to the second cache server comprises:
and taking the communication address of the second cache server as the generated redirection link.
4. The method of claim 1, further comprising:
and if no cache server currently in an available state exists in the server cluster where the first cache server is located, forwarding the access request to another scheduling system so as to process the access request through the server cluster under the another scheduling system.
5. The method of claim 1, wherein prior to scheduling the access request to the first cache server, the method further comprises:
judging whether an available cache server exists under the scheduling system;
correspondingly, if an available cache server exists in the scheduling system, the access request is scheduled to a first cache server;
and if no available cache server exists under the dispatching system, forwarding the access request to another dispatching system so as to process the access request through a server cluster under the other dispatching system.
6. The method of claim 4 or 5, wherein forwarding the access request to another scheduling system comprises:
sending a scheduling request to a central server, so that the central server identifies a resource pool corresponding to a scheduling system sending the scheduling request, and the central server selects another scheduling system which is currently in an available state from various scheduling systems corresponding to the resource pool;
and receiving the communication address of the other dispatching system fed back by the central server, and forwarding the access request to the other dispatching system according to the communication address.
7. The method of claim 1, further comprising:
reporting own system information to a central server according to a specified period, so that the central server marks the working state of each scheduling system according to the received system information of each scheduling system, and dividing each scheduling system according to a resource pool.
8. The utility model provides a scheduling system, characterized in that, the CDN that scheduling system is located includes a plurality of scheduling systems, and each scheduling system corresponds a server cluster, the server cluster includes at least one cache server, scheduling system includes: the system comprises a first scheduling unit, a redirection link generating unit and a second scheduling unit;
the first scheduling unit is used for receiving an access request sent by a client and scheduling the access request to a first cache server;
the redirection link generation unit is configured to receive and analyze response information fed back by the first cache server for the access request, and if the response information indicates that the first cache server cannot provide a resource pointed by the access request, determine whether an available cache server exists in the scheduling system;
if an available cache server exists in the scheduling system, selecting a cache server which is originally in the same server cluster as the first cache server and is currently in an available state as a second cache server, and generating a redirection link pointing to the second cache server; the second scheduling unit sends the redirection link to the client, so that the client reinitiates an access request to the second cache server according to the redirection link; each cache server in the server cluster where the first cache server is located has the same cache resource;
if no available cache server exists under the dispatching system, the first dispatching unit forwards the access request to another dispatching system so as to process the access request through a server cluster under the other dispatching system.
9. The system according to claim 8, wherein the redirection link generation unit comprises:
the identification module is used for identifying a specified field in the header information of the response information or identifying a state code carried in the response information;
and the judging module is used for judging that the response information represents that the first cache server cannot provide the resource pointed by the access request if the assignment of the specified field represents that the cache resource cannot be obtained, or the status code represents that the cache resource cannot be obtained.
10. The system according to claim 8, wherein the redirection link generation unit comprises:
and the server selection module is used for taking the communication address of the second cache server as the generated redirection link.
11. The system according to claim 8, wherein the first scheduling unit is further configured to, if there is no cache server currently in an available state in the server cluster where the first cache server is located, forward the access request to another scheduling system, so as to process the access request through the server cluster under the another scheduling system.
12. The system of claim 8, wherein the first scheduling unit further comprises:
the server judgment module is used for judging whether an available cache server exists under the scheduling system;
correspondingly, the first scheduling unit is configured to schedule the access request to a first cache server if an available cache server exists in the scheduling system; and if no available cache server exists under the dispatching system, forwarding the access request to another dispatching system so as to process the access request through a server cluster under the other dispatching system.
13. The system according to claim 11 or 12, wherein the first scheduling unit comprises:
a scheduling request sending module, configured to send a scheduling request to a central server, so that the central server identifies a resource pool corresponding to a scheduling system that sends the scheduling request, and selects, from among scheduling systems corresponding to the resource pool, another scheduling system that is currently in an available state;
and the access request forwarding module is used for receiving the communication address of the other dispatching system fed back by the central server and forwarding the access request to the other dispatching system according to the communication address.
14. A scheduling apparatus comprising a processor and a memory for storing a computer program which, when executed by the processor, implements the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910327867.0A CN110336848B (en) | 2019-04-23 | 2019-04-23 | Scheduling method, scheduling system and scheduling equipment for access request |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910327867.0A CN110336848B (en) | 2019-04-23 | 2019-04-23 | Scheduling method, scheduling system and scheduling equipment for access request |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110336848A CN110336848A (en) | 2019-10-15 |
| CN110336848B true CN110336848B (en) | 2022-12-20 |
Family
ID=68140129
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910327867.0A Active CN110336848B (en) | 2019-04-23 | 2019-04-23 | Scheduling method, scheduling system and scheduling equipment for access request |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110336848B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111371866B (en) * | 2020-02-26 | 2023-03-21 | 厦门网宿有限公司 | Method and device for processing service request |
| CN111641732B (en) * | 2020-06-01 | 2023-01-24 | 湖南快乐阳光互动娱乐传媒有限公司 | Intelligent scheduling method and device |
| CN114615333A (en) * | 2020-11-25 | 2022-06-10 | 贵州白山云科技股份有限公司 | Resource access request processing method, device, equipment and medium |
| CN113238836A (en) * | 2021-04-15 | 2021-08-10 | 网宿科技股份有限公司 | Distributed content scheduling method, scheduling system and central server |
| CN114598701B (en) * | 2022-02-16 | 2023-08-22 | 阿里巴巴（中国）有限公司 | CDN scheduling method, CDN scheduling system, computing device and storage medium |
| CN116366657B (en) * | 2023-05-31 | 2023-08-04 | 天翼云科技有限公司 | Data request scheduling method and system of cache server |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101764824A (en) * | 2010-01-28 | 2010-06-30 | 深圳市同洲电子股份有限公司 | Distributed cache control method, device and system |
| CN102047244A (en) * | 2008-04-04 | 2011-05-04 | 第三雷沃通讯有限责任公司 | Handling long-tail content in a content delivery network (CDN) |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9450804B2 (en) * | 2009-09-03 | 2016-09-20 | At&T Intellectual Property I, L.P. | Anycast aware transport for content distribution networks |
| US8856281B2 (en) * | 2010-03-22 | 2014-10-07 | At&T Intellectual Property I, L.P. | Internet protocol version 6 content routing |
| US10104141B2 (en) * | 2012-12-31 | 2018-10-16 | DISH Technologies L.L.C. | Methods and apparatus for proactive multi-path routing |
| CN104519088A (en) * | 2013-09-27 | 2015-04-15 | 方正宽带网络服务股份有限公司 | Buffer memory system realization method and buffer memory system |
| CN104202362B (en) * | 2014-08-14 | 2017-11-03 | 上海帝联信息科技股份有限公司 | SiteServer LBS and its content distribution method and device, load equalizer |
| CN106101231B (en) * | 2014-12-22 | 2020-02-21 | 北京奇虎科技有限公司 | Method and device for realizing resource downloading through CDN (content delivery network), server and client |
| CN106487607A (en) * | 2015-08-28 | 2017-03-08 | 中国电信股份有限公司 | A kind of reorientation method based on cache server status and Redirectional system |
| CN109246199A (en) * | 2018-08-16 | 2019-01-18 | 咪咕视讯科技有限公司 | A kind of node scheduling method, system and storage medium |
-
2019
- 2019-04-23 CN CN201910327867.0A patent/CN110336848B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102047244A (en) * | 2008-04-04 | 2011-05-04 | 第三雷沃通讯有限责任公司 | Handling long-tail content in a content delivery network (CDN) |
| CN101764824A (en) * | 2010-01-28 | 2010-06-30 | 深圳市同洲电子股份有限公司 | Distributed cache control method, device and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110336848A (en) | 2019-10-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110336848B (en) | Scheduling method, scheduling system and scheduling equipment for access request | |
| CN107332876B (en) | Method and device for synchronizing block chain state | |
| EP3547649B1 (en) | Method and system for sending request for acquiring data resource | |
| CN109246229B (en) | Method and device for distributing resource acquisition request | |
| CN103051740B (en) | Domain name analytic method, dns server and domain name analysis system | |
| CN106790340B (en) | Link scheduling method and device | |
| CN110995513B (en) | Data sending and receiving method in Internet of things system, internet of things equipment and platform | |
| US11991779B2 (en) | Subscription message processing method and apparatus, and computer device and storage medium | |
| CN110888735A (en) | Distributed message distribution method and device based on consistent hash and scheduling node | |
| CN110677475A (en) | Micro-service processing method, device, equipment and storage medium | |
| US20220166842A1 (en) | Data distribution method and electronic device | |
| EP4033719A1 (en) | System for providing exact communication delay protection of request response for distributed service | |
| CN113014672B (en) | Message pushing method and device, electronic equipment and storage medium | |
| US11606415B2 (en) | Method, apparatus and system for processing an access request in a content delivery system | |
| CN106790354B (en) | Communication method and device for preventing data congestion | |
| CN117354312A (en) | Access request processing method, device, system, computer equipment and storage medium | |
| CN117032987A (en) | Distributed task scheduling method, system, equipment and computer readable medium | |
| CN101695049A (en) | Method and device for processing businesses in monitoring system | |
| CN113596105B (en) | Content acquisition method, edge node and computer readable storage medium | |
| CN108781215B (en) | Network service implementation method, service controller and communication system | |
| US20160261476A1 (en) | Message system for avoiding processing-performance decline | |
| CN110635927B (en) | Node switching method, network node and network system | |
| CN113032188A (en) | Method, device, server and storage medium for determining main server | |
| US10405180B2 (en) | Stub network establishing method, device and system, and storage medium | |
| WO2022205830A1 (en) | Message processing method, message processing apparatus, distribution control apparatus, and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |