CN111556135A - Request scheduling method, system and device and electronic equipment - Google Patents
Request scheduling method, system and device and electronic equipment Download PDFInfo
- Publication number
- CN111556135A CN111556135A CN202010338088.3A CN202010338088A CN111556135A CN 111556135 A CN111556135 A CN 111556135A CN 202010338088 A CN202010338088 A CN 202010338088A CN 111556135 A CN111556135 A CN 111556135A
- Authority
- CN
- China
- Prior art keywords
- domain name
- scheduling
- equivalent
- group
- 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
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- 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
- H04L67/63—Routing a service request depending on the request content or context
-
- 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
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
-
- 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
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/101—Server selection for load balancing based on network conditions
Abstract
The embodiment of the invention provides a request scheduling method, a system, a device and electronic equipment, wherein the request scheduling method comprises the following steps: receiving an access request of a user for a first domain name; responding to the access request, and determining a target scheduling domain name according to the scheduling weight of each domain name in a first equivalent domain name group, wherein each domain name in the first equivalent domain name group can provide the service provided by the first domain name; and scheduling the access request aiming at the first domain name to a service node corresponding to the target scheduling domain name. The target scheduling node is determined according to the scheduling weight of each domain name in the equivalent domain name group, the service state of the service node corresponding to each domain name is considered, the accuracy of request scheduling is improved, the problem that resource service cannot be accessed due to the failure of a single service node can be avoided, and the disaster tolerance capability of the request scheduling system is improved.
Description
Technical Field
The present invention relates to the field of internet technologies, and in particular, to a request scheduling method, system, device, and electronic device.
Background
In the current client request scheduling, a Content Delivery Network (CDN) can schedule a request of a client to a nearest CDN service node for a user to access according to Network traffic and comprehensive information such as connection of each node, load conditions, a distance to the user, response time, and the like in real time, so that Content transmission is faster and more stable.
However, load balancing and demand scheduling of the CDN network are implemented based on Domain Name resolution (DNS resolution), and service node IP addresses corresponding to some Domain Name resolutions are configured according to demands, and the configuration is sent to a Domain Name Server (DNS Server) of the CDN service provider and then becomes effective. When a certain service node goes down or fails, the CDN service provider needs to be contacted to modify DNS analysis configuration stop loss, and the effective time is long. Before validation, the DNS server will still dispatch the request to the serving node, resulting in a user access failure.
As can be seen, the request scheduling disaster tolerance capability based on DNS resolution is low at present.
Disclosure of Invention
The embodiment of the invention aims to provide a request scheduling method, a request scheduling system, a request scheduling device and electronic equipment, so as to improve the disaster tolerance capability of the request scheduling system. The specific technical scheme is as follows:
in a first aspect of the present invention, there is provided a request scheduling method, including:
receiving an access request of a user for a first domain name;
responding to the access request, and determining a target scheduling domain name according to the scheduling weight of each domain name in a first equivalent domain name group, wherein each domain name in the first equivalent domain name group can provide the service provided by the first domain name;
and scheduling the access request aiming at the first domain name to a service node corresponding to the target scheduling domain name.
In a second aspect of the present invention, there is also provided a request scheduling system, including a configuration management server and a client, where:
the configuration management server is used for establishing a first equivalent domain name group and determining the scheduling weight of each domain name according to the state information of the service node corresponding to each domain name in the first equivalent domain name group; sending the first equivalent domain name group and the scheduling weight of each domain name in the first equivalent domain name group to the client;
the client is used for receiving the first equivalent domain name group sent by the configuration management server and the scheduling weight of each domain name in the first equivalent domain name group; scheduling the access request aiming at the first domain name according to the scheduling weight of each domain name in the first equivalent domain name group;
wherein each domain name in the first equivalent domain name group can provide the service provided by the first domain name.
In a third aspect of the present invention, there is also provided a request scheduling apparatus, including:
the receiving module is used for receiving an access request of a user for a first domain name;
the determining module is used for responding to the access request, and determining a target scheduling domain name according to the scheduling weight of each domain name in a first equivalent domain name group, wherein each domain name in the first equivalent domain name group can provide the service provided by the first domain name;
and the scheduling module is used for scheduling the access request aiming at the first domain name to a service node corresponding to the target scheduling domain name.
In a fourth aspect of the present invention, there is also provided an electronic device, including a processor, a communication interface, a memory and a communication bus, where the processor, the communication interface, and the memory complete communication with each other through the communication bus;
a memory for storing a determining machine program;
the processor is configured to implement the method steps described in the first aspect of the embodiment of the present invention when executing the program stored in the memory.
In yet another aspect of the present invention, there is also provided a determining machine readable storage medium having stored therein instructions which, when run on a determining machine, cause the determining machine to perform any one of the request scheduling methods described above.
In yet another aspect of the present invention, there is also provided a determining machine program product containing instructions which, when run on a determining machine, cause the determining machine to perform any of the request scheduling methods described above.
The embodiment of the invention provides a request scheduling method, a system, a device and electronic equipment, wherein the request scheduling method comprises the following steps: receiving an access request of a user for a first domain name; responding to the access request, and determining a target scheduling domain name according to the scheduling weight of each domain name in a first equivalent domain name group, wherein each domain name in the first equivalent domain name group can provide the service provided by the first domain name; and scheduling the access request aiming at the first domain name to a service node corresponding to the target scheduling domain name. And determining a target scheduling node according to the scheduling weight of each domain name in the first equivalent domain name group, and considering the service state of the service node corresponding to each domain name, thereby not only improving the accuracy of request scheduling, but also avoiding the problem that resource service cannot be accessed due to the fault of a single service node, and improving the disaster tolerance of a request scheduling system.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below.
FIG. 1 is a flowchart of a request scheduling method according to an embodiment of the present invention;
FIG. 2 is a flow chart of another method for request scheduling in accordance with an embodiment of the present invention;
FIG. 3 is a flowchart of a request scheduling method according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a request scheduling system according to an embodiment of the present invention;
FIG. 5 is a block diagram of a request scheduling apparatus according to an embodiment of the present invention;
fig. 6 is a block diagram of an electronic device in an embodiment of the invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention.
Example one
Referring to fig. 1, fig. 1 is a flowchart of a request scheduling method according to an embodiment of the present invention.
As shown in fig. 1, the method comprises the steps of:
and step 103, scheduling the access request aiming at the first domain name to a service node corresponding to the target scheduling domain name.
In the embodiment of the invention, the request scheduling method can be applied to a request scheduling device, the request scheduling device can exist independently of a client, and based on the request scheduling method, the access request of a user is scheduled; the request scheduling method can also be directly applied to the client and can also be applied to the management server. The present invention is not limited to the above embodiments, but may be applied to other embodiments.
The access request of the user may include multiple types of services such as pictures, videos, or Application Programming Interfaces (APIs), and in order to avoid the problem that a service cannot be accessed due to an abnormality of a single domain name, multiple accessible equivalent domain names may be created for the same type of service.
In the embodiment of the present invention, the first domain name corresponds to a first equivalent domain name group, and each domain name in the first equivalent domain name group can provide a service provided by the first domain name. When receiving an access request of a user for a first domain name, responding to the access request, a request scheduling device determines a target scheduling domain name in a first equivalent domain name group corresponding to the first domain name, and schedules the access request for the first domain name to a service node corresponding to the target scheduling domain name.
The service node may be a CDN cache server in a CDN service cluster, or may be a service node in another service cluster, which is not limited herein.
The first equivalent domain name group may be stored in an array form, and may be specifically represented as U ═ a, B, C }, where a, B, and C are equivalent domain names that can provide the same service as that provided by the first domain name, where domain name a corresponds to service node a, domain name B corresponds to service node B, and domain name C corresponds to service node C. It is understood that the first equivalent domain name group can also be stored in other data formats, and the concrete representation thereof is not limited thereto, and is not limited thereto.
Specifically, when receiving an access request of a user for a first domain name, in response to the access request, the request scheduling device may determine a target scheduling domain name in a first equivalent domain name group corresponding to the first domain name according to a scheduling weight of each domain name in the first equivalent domain name group.
Since each domain name in the first equivalent domain name group can provide the service provided by the first domain name, the access request for the first domain name is dispatched to any domain name in the first equivalent domain name group, and the same service can be accessed. However, since the service states of the service nodes corresponding to each domain name may be different, for example, the response speed, throughput, memory performance, or Central Processing Unit (CPU) performance of the physical server corresponding to different service nodes are different, which results in a difference in the load capacity of the physical server corresponding to different service nodes. In order to realize load balancing of the service cluster, when scheduling an access request of a user, service states of different service nodes need to be considered.
Based on this, a scheduling weight can be determined for each domain name to represent the current service state of the domain name, and the domain name with higher scheduling weight has better service state than the domain name with lower scheduling weight, and the probability of being scheduled is higher; if the service node corresponding to a certain domain name has service abnormality, the scheduling weight of the service node is set to be zero, so that the domain name cannot be scheduled, and the condition that the access cannot be caused due to slow response or no response of a system caused by randomly scheduling an access request to the abnormal domain name in the prior art is avoided.
In this embodiment of the present invention, the scheduling weight of each domain name may be represented in a form of U ═ { a: x, b: y, c: z }, where x, y, and z are the scheduling weights of domain name a, domain name b, and domain name c, respectively. In this way, the probability of scheduling an access request to serving node a corresponding to domain name a is x/(x + y + z), the probability of scheduling an access request to serving node B corresponding to domain name B is y/(x + y + z), and the probability of scheduling an access request to serving node C corresponding to domain name C is z/(x + y + z). Here, x + y + z may be 1, 10, or any other value. It is to be understood that the representation of the scheduling weight for each domain name is not limited thereto, and is not limited thereto.
It should be noted that the scheduling weight of each domain name may be preset, for example, preset according to the memory performance of the physical server of the corresponding service node or the performance of a Central Processing Unit (CPU); or may be determined according to the real-time status information of the physical server of the corresponding service node during the operation of the service cluster, which is not limited herein.
The target scheduling domain name is determined in the first equivalent domain name group corresponding to the first domain name according to the scheduling weight of each domain name in the first equivalent domain name group, the target scheduling domain name may be determined in a polling manner based on the scheduling weight of each domain name, or the target scheduling domain name may be hit randomly according to the probability indicated by the scheduling weight, which is not limited herein. Specific implementations are described in detail below for clarity of layout.
The request scheduling method provided by the embodiment of the invention comprises the following steps: receiving an access request of a user for a first domain name; responding to the access request, and determining a target scheduling domain name according to the scheduling weight of each domain name in a first equivalent domain name group, wherein each domain name in the first equivalent domain name group can provide the service provided by the first domain name; and scheduling the access request aiming at the first domain name to a service node corresponding to the target scheduling domain name. And determining a target scheduling node according to the scheduling weight of each domain name in the first equivalent domain name group, and considering the state information of the service node corresponding to each domain name, thereby improving the accuracy of request scheduling. Meanwhile, the problem that the service cannot be accessed due to the failure of a single service node can be avoided, and the disaster tolerance capability of the request scheduling system is improved.
Example two
Referring to fig. 2, fig. 2 is a flowchart of another request scheduling method according to an embodiment of the present invention.
As shown in fig. 2, the method comprises the steps of:
and step 204, scheduling the access request aiming at the first domain name to a service node corresponding to the target scheduling domain name.
In this embodiment, the request scheduling method may be applied to a request scheduling device, which may exist independently from a client and schedules an access request of a user based on the request scheduling method; the request scheduling method can also be directly applied to the client and can also be applied to the management server. The present invention is not limited to the above embodiments, but may be applied to other embodiments.
In this embodiment, since the request scheduling device may establish the equivalent domain name group corresponding to each domain name, when there are N equivalent domain name groups, the first equivalent domain name group corresponding to the first domain name needs to be hit from the N equivalent domain name groups. Specifically, since each domain name in the first equivalent domain name group can provide the service provided by the first domain name, the first domain name is certainly included in the first equivalent domain name group. Based on this, the first equivalent domain name group including the first domain name can be searched in the N equivalent domain name groups. And then determining a target scheduling domain name in the first equivalent domain name group according to the scheduling weight of each domain name in the first equivalent domain name group.
In some embodiments, the determining the target scheduling domain name in the first equivalence domain name group according to the scheduling weight of each domain name in the first equivalence domain name group may be understood as determining the target scheduling domain name by using a random generating function.
Specifically, assuming that the first equivalent domain name group is U ═ { a:1, B:5, C:4}, the probability of scheduling the first domain name to the serving node a corresponding to the domain name a is 0.1, the probability of scheduling to the serving node B corresponding to the domain name B is 0.5, and the probability of scheduling to the serving node C corresponding to the domain name C is 0.4. The request scheduling device can establish a random number generation function for requesting scheduling so as to control the generation of integer random numbers in 1-10, and then the probability of any number in 1-10 appearing is 0.1. Accordingly, random numbers are correspondingly allocated according to the weight of each domain name in U ═ { a:1, b:5, c:4}, for example, the integer random numbers corresponding to the domain names a, b, c are 1, 2-6, 7-10 respectively. When the random number generated by the random number generation function is 6, the random number range of the domain name b is hit. At this time, the domain name B is determined as the target scheduling domain name, and the access request for the first domain name is scheduled to the serving node B corresponding to the domain name B.
It should be noted that, the implementation form of determining the target scheduling domain name in the first equivalent domain name group according to the scheduling weight of each domain name in the first equivalent domain name group is not limited to this. The request scheduling device may also schedule the access request in a polling manner based on the scheduling weight, which may specifically refer to a technical scheme of polling in the prior art and is not described herein again. In addition, the request scheduling device may also directly schedule the access request for the first domain name to the domain name with the largest weight based on the scheduling weight, which is not limited herein.
Optionally, before the receiving the access request of the user for the first domain name, the method further includes:
establishing a first equivalent domain name group, wherein the first equivalent domain name group comprises M domain names, and the M domain names can provide the same service;
acquiring state information of a service node corresponding to each domain name in the M domain names;
determining the scheduling weight of each domain name according to the state information of the service node corresponding to each domain name;
wherein M is an integer greater than or equal to 1.
In this embodiment, the request scheduling device may first establish an equivalent domain name group for different services, and taking the first equivalent domain name group as an example, the first equivalent domain name group may include M domain names, the M domain names may provide the same service, and the M domain names may include the first domain name.
The request scheduling device can determine the scheduling weight of each domain name according to the state information of the service node corresponding to each domain name in the M domain names. Specifically, the request scheduling device may establish connection with all service nodes in the current service network to obtain state information of the service node corresponding to each domain name in the first equivalent domain name group. And respectively determining the scheduling weight of each domain name according to the state information of the service node corresponding to each domain name in the equivalent domain name group.
The state information of the service node may include a connection state of the service node, that is, whether the service node is connected online; the load condition of the service node; the bearable capability of the serving node; the geographic distance between the service node and the client; response time of the serving node, etc. And according to the information, comprehensively evaluating the scheduling weight of each domain name by combining the influence degree of different parameter indexes on the request scheduling to realize load balancing.
After determining the scheduling weight of each domain name in the first equivalent domain name group, the request scheduling apparatus may integrate and store the first equivalent domain name group and the scheduling weight of each domain name in the first equivalent domain name group into weight configuration information. When N equivalent domain name groups are created, a set of weight configuration information can be created for each equivalent domain name group and stored. When an access request for the first domain name is received, the weight configuration information corresponding to the first equivalent domain name group can be directly hit in the stored weight configuration information, and the target scheduling domain name can be determined according to the scheduling weight of each domain name in the first equivalent domain name group.
Further, the determining the scheduling weight of each domain name according to the state information of the service node corresponding to each domain name includes:
determining the scheduling weight of each domain name according to the scheduling parameter of the service node corresponding to each domain name; the scheduling parameter includes at least one of a geographical distance between the service node and the client, and a real-time load status of the service node.
In this embodiment, the request scheduling device may specifically determine the state information of the service node according to at least one scheduling parameter of a geographic distance between the service node corresponding to each domain name and the client and a real-time load state of the service node, so as to determine the scheduling weight of each domain name.
Specifically, the scheduling parameter may include a geographic distance between the service node and the client: if the geographic distance between the service node corresponding to a certain domain name and the client is farther, the scheduling weight of the domain name can be smaller, and if the geographic distance between the service node corresponding to the certain domain name and the client is closer, the scheduling weight of the domain name can be larger.
The scheduling parameters may include a real-time load status of the serving node. The real-time load state of the service node can be specifically determined according to parameters such as the current memory space, throughput and response time of the service node. If the real-time load of a service node corresponding to a certain domain name is larger, the scheduling weight of the domain name can be smaller, and if the real-time load of the service node corresponding to the certain domain name is smaller, the scheduling weight of the domain name can be larger.
The scheduling parameters may also include the geographic distance between the service node and the client, and the real-time load status of the service node. And comprehensively determining the scheduling weight of each domain name according to the influence degree of the two scheduling parameters on the request scheduling.
It should be noted that the scheduling parameter includes, but is not limited to, at least one of a geographical distance between the service node and the client, and a real-time load status of the service node. The scheduling parameters can also comprise the bearing capacity of the service node, and the bearing capacity can be combined with the real-time load condition to comprehensively evaluate the service state of the service node; the scheduling parameter may further include a response time of the service node, and the scheduling weight of a domain name may be larger if the response time of the service node corresponding to the domain name is shorter, and the scheduling weight of the domain name may be smaller if the response time of the service node corresponding to the domain name is longer, which is not limited herein.
In some embodiments, when the request scheduling method is directly applied to the client, in addition to the scheduling parameter, the scheduling weight of each domain name in the first equivalent domain name group may be adjusted according to the application type of the client, the version of the client, the type of the electronic device mounted on the client, the version of the electronic device mounted on the client, and other parameters, so as to adapt to different device requirements, and further improve the accuracy of the client in requesting scheduling.
In this embodiment, the scheduling weight of each domain name can be adjusted according to the state information of each domain name in the first equivalent domain name group, so that the accuracy of request scheduling is further improved, and the disaster tolerance capability of the request scheduling system is further improved.
It should be noted that the technical solutions of the foregoing embodiments are also applicable to the technical solution of the first embodiment, and can achieve the same technical effects, and for avoiding repetition, no further description is provided herein.
Optionally, the method further includes:
under the condition that service nodes corresponding to L domain names in the M domain names cannot provide services, updating the scheduling weights of the L domain names to zero;
updating the scheduling weight of other M-L domain names according to the scheduling parameter of the service node corresponding to each domain name in the other M-L domain names;
wherein L is an integer greater than or equal to 1 and less than or equal to M.
In this embodiment, the request scheduling device may determine the scheduling weight of each domain name according to the status information of the service node corresponding to each domain name in the first equivalent domain name group. When a certain service node is in fault or is down, the request scheduling device can timely acquire the fault and adjust the scheduling weight of each domain name.
Specifically, if there is a service node corresponding to L domain names in the M domain names in the first equivalent domain name group that cannot provide services, an access request for the first domain name cannot be dispatched to the service node corresponding to the L domain names. The request scheduling device may set the scheduling weight of the domain name corresponding to the service node that cannot provide the service to zero, for example, if the service node corresponding to the domain name a cannot provide the service, the scheduling weight of the domain name a in the first equivalent domain name group may be adjusted to 0.
Meanwhile, the request scheduling device can re-determine the scheduling weight of the domain name corresponding to the request scheduling device according to the scheduling parameters of the service node corresponding to other M-L domain names. For a specific implementation form of determining the scheduling weight, reference may be made to the specific description of the foregoing embodiments, and details are not described herein for avoiding repetition. In this way, the weight configuration information of the first equivalent domain name group may be updated from U ═ { a:1, b:5, c:4} to U ═ a:0, b:5, c:5}, and then the access request for the first domain name may not be dispatched to the service node corresponding to the domain name a, so as to ensure that the access request may be normally accessed.
The condition that the service node cannot provide the service may include a fault or a downtime of the service node, or may include a condition that the service node actively drops off and stops working, which is not limited herein.
In this embodiment, the request scheduling device updates the scheduling weight of the offline service node to zero, so that the access request for the first domain name is not scheduled to the service node, but is scheduled to the service nodes corresponding to other equivalent domain names, thereby ensuring that the access request of the user does not cause access failure due to a failure of a single service node, and further improving the disaster tolerance capability of the request scheduling system.
It should be noted that the technical solutions of the foregoing embodiments are also applicable to the technical solution of the first embodiment, and can achieve the same technical effects, and for avoiding repetition, no further description is provided herein.
In some embodiments, the request scheduling device may obtain, at preset time intervals, status information of a service node corresponding to each domain name in the first domain name group based on a connection with each service node in the service cluster, and update the scheduling weight of each domain name according to real-time status information of the service node corresponding to each domain name in the first equivalent domain name group when there is a change in the status information of the service node corresponding to at least one domain name in the first equivalent domain name group. The preset time interval may be 10 seconds, 30 seconds, etc., and is not limited herein.
In some embodiments, a first update threshold may be set. For example, when the sum of the weights of all domain names in the first equivalence domain name group is 10, the first update threshold may be set to 0.5. When the variable quantity of the scheduling weight of at least one domain name in the first equivalent domain name group exceeds 0.5, the scheduling weight is updated so as to reduce unnecessary updating operation and reduce memory consumption.
It should be noted that the technical solutions of the foregoing embodiments are also applicable to the technical solution of the first embodiment, and can achieve the same technical effects, and for avoiding repetition, no further description is provided herein.
The following describes a flow of a request scheduling method according to an embodiment of the present invention, as shown in fig. 3:
the request scheduling device creates N equivalent domain name groups, determines the scheduling weight of each domain name for the N equivalent domain name groups, and shows that: { a:1, b:5, c:4}, { d:0, e:0, f:1}, …, { g:1, h:1, i:1} ], wherein { a:1, b:5, c:4} has access to a first picture resource, { d:0, e:0, f:1} has access to a first video resource, and { g:1, h:1, i:1} has access to a first API resource.
When the request scheduling device receives an access request of a user for a first domain name a, the first domain name a needs to access a first picture resource, and the request scheduling device hits a first equivalent domain name group U containing the first domain name a { a:1, b:5, c:4} based on the first domain name a. The request scheduling device determines a target scheduling domain name through a random number generation function, wherein the random number allocation rule in a first equivalent domain name group U ═ { a:1, b:5, c:4} is as follows: domain name a corresponds to a random number: 1; domain name b corresponds to a random number: 2-6, domain name c corresponds to random number: 7-10.
Then, the request scheduling device randomly generates an integer random number 6 according to the scheduling weight of the domain name a, b, c in the first equivalent domain name group U { a:1, b:5, c:4} and according to a random number generation function, and then hits the random number range of the domain name b. At this time, the domain name B is determined as the target scheduling domain name, and the access request for the first domain name a is scheduled to the serving node B corresponding to the domain name B for access.
When the service node a corresponding to the domain name a in the first equivalent domain name group has a fault and the request scheduling device detects that the connection of the service node a is interrupted, the scheduling weight of the domain name a is updated to be 0, and then the scheduling weights of the domain names B and C are determined according to the state information of the service node B corresponding to the current domain name B and the service node C corresponding to the domain name C, for example, the updated U is { a:0, B:5, C:5 }. At this time, the random number allocation rule in the updated first equivalent domain name group U ═ { a:0, b:5, c:5} is: domain name a corresponds to a random number: none; domain name b corresponds to a random number: 1-5, domain name c corresponds to random number: 6-10.
And then, receiving an access request aiming at the first domain name a, wherein the access request is not dispatched to the service node A corresponding to the domain name a. According to the random number generation function, if the integer random number 6 is randomly generated, the random number range of the domain name c will be hit. At this time, the domain name C is determined as a target scheduling domain name, and an access request for the first domain name a is scheduled to the service node C corresponding to the domain name C for access.
In this embodiment, on the basis of the first embodiment, multiple implementation manners are added, so that the accuracy of request scheduling is further improved, it is further ensured that an access request of a user does not fail to be accessed due to a fault of a single service node, and the disaster tolerance capability of the request scheduling system is further improved.
In summary, the request scheduling method provided in the embodiment of the present invention includes: receiving an access request of a user for a first domain name; responding to the access request, and determining a target scheduling domain name according to the scheduling weight of each domain name in a first equivalent domain name group, wherein each domain name in the first equivalent domain name group can provide the service provided by the first domain name; and scheduling the access request aiming at the first domain name to a service node corresponding to the target scheduling domain name. And determining a target scheduling node according to the scheduling weight of each domain name in the equivalent domain name group, and considering the state information of the service node corresponding to each domain name, thereby improving the accuracy of request scheduling. Meanwhile, the problem that the service cannot be accessed due to the failure of a single service node can be avoided, and the disaster tolerance capability of the request scheduling system is improved.
EXAMPLE III
Referring to fig. 4, fig. 4 is a schematic diagram of a request scheduling system according to an embodiment of the present invention.
As shown in fig. 4, the request scheduling system provided in the embodiment of the present invention includes: configuring a management server and a client, wherein:
the configuration management server is used for establishing a first equivalent domain name group and determining the scheduling weight of each domain name according to the state information of the service node corresponding to each domain name in the first equivalent domain name group; sending the first equivalent domain name group and the scheduling weight of each domain name in the first equivalent domain name group to the client;
the client is used for receiving the first equivalent domain name group sent by the configuration management server and the scheduling weight of each domain name in the first equivalent domain name group; scheduling the access request aiming at the first domain name according to the scheduling weight of each domain name in the first equivalent domain name group;
wherein each domain name in the first equivalent domain name group can provide the service provided by the first domain name.
In the embodiment of the present invention, the configuration management server may be a cloud computer, a server, and other devices or data platforms having a data processing function; the client may be an application providing a service for a user on an electronic Device, such as a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer), a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), or a Wearable Device (Wearable Device), and is not limited herein.
In the embodiment of the invention, the request scheduling system comprises a configuration management server and a client.
The configuration management server can establish a first equivalent domain name group corresponding to the first domain name, and each domain name in the first equivalent domain name group can provide the service provided by the first domain name, so that a plurality of equivalent domain names equivalent to the first domain name can provide the service for the access request of the first domain name, and the problem that the access request of a user cannot respond when a single first domain name cannot provide the service is avoided. Meanwhile, the configuration management server may further establish a connection with a service node corresponding to each domain name in the first equivalent domain name group, and obtain state information of each service node to determine the scheduling weight of each domain name, and for a specific implementation form of determining the scheduling weight, reference may be made to the description of the above embodiment, and details are not repeated here to avoid repetition.
In addition, the configuration management server can also send the created first equivalent domain name and the scheduling weight of each domain name in the first equivalent domain name group to the client. The configuration management server may generate, by using the created first equivalent domain name and the scheduling weight of each domain name in the first equivalent domain name group, weight configuration information of the first equivalent domain name group, where the weight configuration information may be stored in a form of a multidimensional array, for example: u ═ a:1, b:5, c: 4. The configuration management server can directly send the weight configuration information to the client.
The client can receive the first equivalent domain name sent by the configuration management server and the scheduling weight of each domain name in the first equivalent domain name group, and schedules the access request aiming at the first domain name according to the scheduling weight of each domain name in the first equivalent domain name group. For specific implementation of determining the target scheduling domain name, reference may be made to the description of the foregoing embodiment, and details are not described herein in order to avoid repetition.
In some embodiments, the client may establish a request scheduling Module to manage the request scheduling transaction, such as a Traffic Control Module (TC Module). The request scheduling module may be integrated in the mobile client in the form of a Software Development Kit (SDK). The weight configuration information received by the client may be stored in the request scheduling module. Then, the request scheduling module may also schedule the access request for the first domain name according to the scheduling weight of each domain name in the first equivalent domain name group.
In the embodiment of the invention, the configuration management server can communicate with the client through short connection, and the configuration management server can communicate with the client through a User Datagram Protocol (UDP); the communication can also be performed between the configuration management server and the client in a long connection mode, specifically, when the client is cold started each time, a long connection channel can be established between the configuration management server and the client, and the long connection channel can be realized based on a WebSocket Protocol or a private Transmission Control Protocol (TCP); the long connection channel can enable the configuration management platform and the client to communicate at any time, and after each time of transmission of the weight configuration information is completed, the long connection channel cannot be disconnected, and then data can be continuously transmitted by the channel.
Optionally, the configuration management server is further configured to update the scheduling weight of the target domain name according to the state information of the target domain name after the change when the state information of the target domain name in the first equivalent domain name group changes; sending the updated scheduling weight of each domain name in the first equivalent domain name group to the client;
the client is further configured to receive the updated scheduling weight of each domain name in the first equivalent domain name group sent by the configuration management server, and schedule the access request for the first domain name according to the updated scheduling weight of each domain name in the first equivalent domain name group.
In this embodiment, the configuration management server may establish a connection with the service node corresponding to each domain name in the first equivalent domain name group, so as to obtain the state information of each service node. Based on this, the configuration management server may obtain the state information after the change of the domain name when acquiring that the state information of a certain domain name in the first equivalent domain name group changes.
The configuration management server can acquire the state information of the service node corresponding to each domain name in the first domain name group at preset time intervals, and update the scheduling weight of each domain name according to the real-time state information of the service node corresponding to each domain name in the first equivalent domain name group under the condition that the state information of the service node corresponding to at least one domain name in the first equivalent domain name group is changed. The preset time interval may be 10 seconds, 30 seconds, etc., and is not limited herein.
In some embodiments, in a case that a service node corresponding to at least one domain name cannot provide a service in the first equivalent domain name group, the configuration management server may update the scheduling weight of the at least one domain name to zero; meanwhile, the scheduling weights of other domain names are updated according to the scheduling parameters of the service nodes corresponding to the other domain names.
In some embodiments, a first update threshold may be set. For example, when the sum of the weights of all domain names in the first equivalence domain name group is 10, the first update threshold may be set to 0.5. When the variable quantity of the scheduling weight of at least one domain name in the first equivalent domain name group exceeds 0.5, the scheduling weight is updated so as to reduce unnecessary updating operation and reduce memory consumption.
After updating the scheduling weight of each domain name in the first equivalent domain name group, the configuration management server may update the weight configuration information corresponding to the first equivalent domain name group. And, the updated weight configuration information may be sent to the client based on a long connection channel with the client.
In some embodiments, the updated scheduling weight of each domain name in the first equivalent domain name group may be sent to the client only when the amount of change in the scheduling weight of at least one domain name in the first equivalent domain name group reaches the first update threshold, based on the first update threshold, so as to reduce unnecessary data transmission.
Optionally, the configuration management server is specifically configured to determine a scheduling weight of each domain name according to a scheduling parameter of a service node corresponding to each domain name; the scheduling parameter includes at least one of a geographical distance between the service node and the client, and a real-time load status of the service node.
In this embodiment, the configuration management server may specifically determine the scheduling weight of each domain name according to the scheduling parameter of the service node corresponding to each domain name; the scheduling parameter includes at least one of a geographical distance between the service node and the client, and a real-time load status of the service node. For a specific implementation form, reference may be made to the description of the above embodiments, and details are not described herein again to avoid repetition.
The request scheduling system provided by the embodiment of the invention comprises a configuration management server and a client, wherein the configuration management server configures the scheduling weight of each domain name in a first equivalent domain name group, the weight configuration information is sent to the client through communication between the configuration management server and the client, and the client schedules an access request according to the weight configuration information. The scheduling weight of each domain name in the first equivalent domain name group takes the state information of the service node corresponding to each domain name into consideration, and the accuracy of client request scheduling is improved. Meanwhile, the problem that the service cannot be accessed due to the failure of a single service node can be avoided, and the disaster tolerance capability of the request scheduling system is improved.
Example four
Referring to fig. 5, fig. 5 is a structural diagram of a request scheduling apparatus according to an embodiment of the present invention.
As shown in fig. 5, the request scheduling apparatus 500 includes:
a receiving module 501, configured to receive an access request of a user for a first domain name;
a first determining module 502, configured to determine, in response to the access request, a target scheduling domain name according to a scheduling weight of each domain name in a first equivalent domain name group, where each domain name in the first equivalent domain name group may provide a service provided by the first domain name;
a scheduling module 503, configured to schedule the access request for the first domain name to a service node corresponding to the target scheduling domain name.
Optionally, the first determining module 502 includes:
a searching unit, configured to respond to the access request when N equivalent domain name groups exist, and search a first equivalent domain name group including the first domain name from the N equivalent domain name groups;
a first determining unit, configured to determine a target scheduling domain name in the first equivalent domain name group according to a scheduling weight of each domain name in the first equivalent domain name group;
wherein N is an integer greater than or equal to 1.
Optionally, the request scheduling apparatus 500 further includes:
the device comprises an establishing module, a receiving module and a sending module, wherein the establishing module is used for establishing a first equivalent domain name group, the first equivalent domain name group comprises M domain names, and the M domain names can provide the same service;
the acquisition module is used for acquiring the state information of the service node corresponding to each domain name in the M domain names;
a second determining module, configured to determine a scheduling weight of each domain name according to state information of a service node corresponding to the domain name;
wherein M is an integer greater than or equal to 1.
Optionally, the second determining module includes:
a second determining unit, configured to determine a scheduling weight of each domain name according to a scheduling parameter of a service node corresponding to the domain name; the scheduling parameter includes at least one of a geographical distance between the service node and the client, and a real-time load status of the service node.
Optionally, the request scheduling apparatus 500 further includes:
a first updating module, configured to update the scheduling weights of the L domain names to zero when service nodes corresponding to the L domain names in the M domain names cannot provide services;
the second updating module is used for updating the scheduling weight of other M-L domain names according to the scheduling parameter of the service node corresponding to each domain name in the other M-L domain names;
wherein L is an integer greater than or equal to 1 and less than or equal to M.
The request scheduling apparatus 500 can implement the processes implemented in the method embodiments shown in fig. 1 and fig. 2, and is not described here again to avoid repetition.
Referring to fig. 6, fig. 6 is a structural diagram of an electronic device according to an embodiment of the present invention.
As shown in fig. 6, the electronic device 600 includes a processor 601, a communication interface 602, a memory 603 and a communication bus 604, wherein the processor 601, the communication interface 602 and the memory 603 complete communication with each other through the communication bus 604.
The memory 603 is used for storing a determination program.
When the processor 601 is used to execute the program stored in the memory 603, the following steps are implemented:
receiving an access request of a user for a first domain name;
responding to the access request, and determining a target scheduling domain name according to the scheduling weight of each domain name in a first equivalent domain name group, wherein each domain name in the first equivalent domain name group can provide the service provided by the first domain name;
and scheduling the access request aiming at the first domain name to a service node corresponding to the target scheduling domain name.
Optionally, the determining, in response to the access request, a target scheduling domain name according to the scheduling weight of each domain name in the first equivalent domain name group includes:
under the condition that N equivalent domain name groups exist, responding to the access request, and searching a first equivalent domain name group containing the first domain name in the N equivalent domain name groups;
determining a target scheduling domain name in the first equivalent domain name group according to the scheduling weight of each domain name in the first equivalent domain name group;
wherein N is an integer greater than or equal to 1.
Optionally, before the receiving the access request of the user for the first domain name, the method further includes:
establishing a first equivalent domain name group, wherein the first equivalent domain name group comprises M domain names, and the M domain names can provide the same service;
acquiring state information of a service node corresponding to each domain name in the M domain names;
determining the scheduling weight of each domain name according to the state information of the service node corresponding to each domain name;
wherein M is an integer greater than or equal to 1.
Optionally, the determining the scheduling weight of each domain name according to the state information of the service node corresponding to each domain name includes:
determining the scheduling weight of each domain name according to the scheduling parameter of the service node corresponding to each domain name; the scheduling parameter includes at least one of a geographical distance between the service node and the client, and a real-time load status of the service node.
Optionally, the method further includes:
under the condition that service nodes corresponding to L domain names in the M domain names cannot provide services, updating the scheduling weights of the L domain names to zero;
updating the scheduling weight of other M-L domain names according to the scheduling parameter of the service node corresponding to each domain name in the other M-L domain names;
wherein L is an integer greater than or equal to 1 and less than or equal to M.
The communication bus 604 mentioned in the electronic device 600 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus 604 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.
The communication interface 602 is used for communication between the electronic apparatus 600 and other apparatuses.
The Memory 603 may include a Random Access Memory (RAM) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor 601 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the device can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component.
In yet another embodiment of the present invention, there is also provided a determining machine readable storage medium having stored therein instructions, which when run on a determining machine, cause the determining machine to execute the request scheduling method described in any of the above embodiments.
In a further embodiment of the present invention, there is also provided a determining machine program product comprising instructions which, when run on a determining machine, cause the determining machine to perform the request scheduling method of any of the above embodiments.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a deterministic computer program product. The determining machine program product includes one or more determining machine instructions. The procedures or functions according to embodiments of the invention are brought about in whole or in part upon loading and execution of the deterministic machine program instructions on a deterministic machine. The determination machine may be a general purpose determination machine, a dedicated determination machine, a network of determination machines, or other programmable device. The determining machine instructions may be stored in or transmitted from one determining machine readable storage medium to another determining machine readable storage medium, for example, the determining machine instructions may be transmitted from one website site, determining machine, server, or data center to another website site, determining machine, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The determining machine-readable storage medium can be any available medium that the determining machine can access or a data storage device including one or more available media integrated servers, data centers, and the like. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
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 phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (10)
1. A method for request scheduling, the method comprising the steps of:
receiving an access request of a user for a first domain name;
responding to the access request, and determining a target scheduling domain name according to the scheduling weight of each domain name in a first equivalent domain name group, wherein each domain name in the first equivalent domain name group can provide the service provided by the first domain name;
and scheduling the access request aiming at the first domain name to a service node corresponding to the target scheduling domain name.
2. The method of claim 1, wherein determining a target dispatch domain name based on the dispatch weight for each domain name in the first set of equivalent domain names in response to the access request comprises:
under the condition that N equivalent domain name groups exist, responding to the access request, and searching a first equivalent domain name group containing the first domain name in the N equivalent domain name groups;
determining a target scheduling domain name in the first equivalent domain name group according to the scheduling weight of each domain name in the first equivalent domain name group;
wherein N is an integer greater than or equal to 1.
3. The method of claim 1, wherein prior to receiving the user request for access to the first domain name, the method further comprises:
establishing a first equivalent domain name group, wherein the first equivalent domain name group comprises M domain names, and the M domain names can provide the same service;
acquiring state information of a service node corresponding to each domain name in the M domain names;
determining the scheduling weight of each domain name according to the state information of the service node corresponding to each domain name;
wherein M is an integer greater than or equal to 1.
4. The method according to claim 3, wherein the determining the scheduling weight of each domain name according to the state information of the serving node corresponding to each domain name comprises:
determining the scheduling weight of each domain name according to the scheduling parameter of the service node corresponding to each domain name; the scheduling parameter includes at least one of a geographical distance between the service node and the client, and a real-time load status of the service node.
5. The method of claim 4, further comprising:
under the condition that service nodes corresponding to L domain names in the M domain names cannot provide services, updating the scheduling weights of the L domain names to zero;
updating the scheduling weight of other M-L domain names according to the scheduling parameter of the service node corresponding to each domain name in the other M-L domain names;
wherein L is an integer greater than or equal to 1 and less than or equal to M.
6. A request scheduling system comprising a configuration management server and a client, wherein:
the configuration management server is used for establishing a first equivalent domain name group and determining the scheduling weight of each domain name according to the state information of the service node corresponding to each domain name in the first equivalent domain name group; sending the first equivalent domain name group and the scheduling weight of each domain name in the first equivalent domain name group to the client;
the client is used for receiving the first equivalent domain name group sent by the configuration management server and the scheduling weight of each domain name in the first equivalent domain name group; scheduling the access request aiming at the first domain name according to the scheduling weight of each domain name in the first equivalent domain name group;
wherein each domain name in the first equivalent domain name group can provide the service provided by the first domain name.
7. The system according to claim 6, wherein the configuration management server is further configured to, in a case that the status information of the target domain name in the first equivalent domain name group changes, update the scheduling weight of the target domain name according to the changed status information of the target domain name; sending the updated scheduling weight of each domain name in the first equivalent domain name group to the client;
the client is further configured to receive the updated scheduling weight of each domain name in the first equivalent domain name group sent by the configuration management server, and schedule the access request for the first domain name according to the updated scheduling weight of each domain name in the first equivalent domain name group.
8. The system according to claim 6, wherein the configuration management server is specifically configured to determine the scheduling weight of each domain name according to the scheduling parameter of the service node corresponding to each domain name; the scheduling parameter includes at least one of a geographical distance between the service node and the client, and a real-time load status of the service node.
9. A request scheduling apparatus, the apparatus comprising:
the receiving module is used for receiving an access request of a user for a first domain name;
the determining module is used for responding to the access request, and determining a target scheduling domain name according to the scheduling weight of each domain name in a first equivalent domain name group, wherein each domain name in the first equivalent domain name group can provide the service provided by the first domain name;
and the scheduling module is used for scheduling the access request aiming at the first domain name to a service node corresponding to the target scheduling domain name.
10. An electronic device is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing mutual communication by the memory through the communication bus;
a memory for storing a determining machine program;
a processor for implementing the method steps of any one of claims 1 to 5 when executing a program stored in the memory.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010338088.3A CN111556135A (en) | 2020-04-26 | 2020-04-26 | Request scheduling method, system and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010338088.3A CN111556135A (en) | 2020-04-26 | 2020-04-26 | Request scheduling method, system and device and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111556135A true CN111556135A (en) | 2020-08-18 |
Family
ID=72004048
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010338088.3A Pending CN111556135A (en) | 2020-04-26 | 2020-04-26 | Request scheduling method, system and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111556135A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111913732A (en) * | 2020-08-28 | 2020-11-10 | 平安国际智慧城市科技股份有限公司 | Service updating method and device, management server and storage medium |
| CN112422610A (en) * | 2020-09-11 | 2021-02-26 | 深圳市证通电子股份有限公司 | Intelligent gateway method and system based on distributed object storage |
| CN113347020A (en) * | 2021-04-29 | 2021-09-03 | 上海淇玥信息技术有限公司 | Domain name service disaster recovery method, system, device and medium |
| CN114615276A (en) * | 2022-03-11 | 2022-06-10 | 北京字节跳动网络技术有限公司 | Content distribution network domain name scheduling method and device |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104834569A (en) * | 2015-05-11 | 2015-08-12 | 北京京东尚科信息技术有限公司 | Cluster resource scheduling method and cluster resource scheduling system based on application types |
| CN104994156A (en) * | 2015-07-01 | 2015-10-21 | 北京京东尚科信息技术有限公司 | Load balancing method and system for cluster |
| US20150358236A1 (en) * | 2014-06-05 | 2015-12-10 | KEMP Technologies Inc. | Adaptive load balancer and methods for intelligent data traffic steering |
| CN108632397A (en) * | 2017-03-22 | 2018-10-09 | 北京雪球信息科技有限公司 | To the control method and system of network connection |
| CN108737493A (en) * | 2018-04-02 | 2018-11-02 | 北京奇艺世纪科技有限公司 | A kind of address distribution method, device and electronic equipment |
| CN109274707A (en) * | 2017-07-18 | 2019-01-25 | 阿里巴巴集团控股有限公司 | A kind of load dispatching method and device |
| CN109558246A (en) * | 2018-12-04 | 2019-04-02 | 北京字节跳动网络技术有限公司 | A kind of load-balancing method, device, electronic equipment and storage medium |
| CN110535853A (en) * | 2019-08-28 | 2019-12-03 | 北京奇艺世纪科技有限公司 | A kind of video request dispatching method, device, server and storage medium |
-
2020
- 2020-04-26 CN CN202010338088.3A patent/CN111556135A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150358236A1 (en) * | 2014-06-05 | 2015-12-10 | KEMP Technologies Inc. | Adaptive load balancer and methods for intelligent data traffic steering |
| CN104834569A (en) * | 2015-05-11 | 2015-08-12 | 北京京东尚科信息技术有限公司 | Cluster resource scheduling method and cluster resource scheduling system based on application types |
| CN104994156A (en) * | 2015-07-01 | 2015-10-21 | 北京京东尚科信息技术有限公司 | Load balancing method and system for cluster |
| CN108632397A (en) * | 2017-03-22 | 2018-10-09 | 北京雪球信息科技有限公司 | To the control method and system of network connection |
| CN109274707A (en) * | 2017-07-18 | 2019-01-25 | 阿里巴巴集团控股有限公司 | A kind of load dispatching method and device |
| CN108737493A (en) * | 2018-04-02 | 2018-11-02 | 北京奇艺世纪科技有限公司 | A kind of address distribution method, device and electronic equipment |
| CN109558246A (en) * | 2018-12-04 | 2019-04-02 | 北京字节跳动网络技术有限公司 | A kind of load-balancing method, device, electronic equipment and storage medium |
| CN110535853A (en) * | 2019-08-28 | 2019-12-03 | 北京奇艺世纪科技有限公司 | A kind of video request dispatching method, device, server and storage medium |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111913732A (en) * | 2020-08-28 | 2020-11-10 | 平安国际智慧城市科技股份有限公司 | Service updating method and device, management server and storage medium |
| CN112422610A (en) * | 2020-09-11 | 2021-02-26 | 深圳市证通电子股份有限公司 | Intelligent gateway method and system based on distributed object storage |
| CN112422610B (en) * | 2020-09-11 | 2023-06-16 | 深圳市证通电子股份有限公司 | Intelligent gateway method and system based on distributed object storage |
| CN113347020A (en) * | 2021-04-29 | 2021-09-03 | 上海淇玥信息技术有限公司 | Domain name service disaster recovery method, system, device and medium |
| CN113347020B (en) * | 2021-04-29 | 2022-11-15 | 上海淇玥信息技术有限公司 | Domain name service disaster recovery method, system, device and medium |
| CN114615276A (en) * | 2022-03-11 | 2022-06-10 | 北京字节跳动网络技术有限公司 | Content distribution network domain name scheduling method and device |
| CN114615276B (en) * | 2022-03-11 | 2024-01-26 | 抖音视界有限公司 | Domain name scheduling method and device for content distribution network |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111556135A (en) | Request scheduling method, system and device and electronic equipment | |
| US20210337046A1 (en) | Intelligent scheduling method, terminal device, edge node cluster and intelligent scheduling system | |
| US7953887B2 (en) | Asynchronous automated routing of user to optimal host | |
| CN111614748B (en) | Apparatus and method for scalable peer-to-peer matching | |
| CN111327647B (en) | Method and device for providing service to outside by container and electronic equipment | |
| CN110519183B (en) | Node speed limiting method and device, electronic equipment and storage medium | |
| US20130262681A1 (en) | Apparatus and method for providing service availability to a user via selection of data centers for the user | |
| CN107395783B (en) | IP address processing method, system, device and electronic equipment | |
| CN109510878B (en) | Long connection session keeping method and device | |
| CN108427619B (en) | Log management method and device, computing equipment and storage medium | |
| CN108683668A (en) | Resource checksum method, apparatus, storage medium and equipment in content distributing network | |
| CN107172214B (en) | Service node discovery method and device with load balancing function | |
| US9390156B2 (en) | Distributed directory environment using clustered LDAP servers | |
| US20140122723A1 (en) | Dynamic registration of listener resources for cloud services | |
| JP2013157748A (en) | Service bus system, service bus device, and method for assuring connection uniqueness | |
| CN112565406B (en) | Gray release method, gray release system and electronic equipment | |
| CN106888277A (en) | A kind of domain name inquiry method and device | |
| CN114301990A (en) | Node scheduling method, device and storage medium based on content distribution network | |
| CN109873855A (en) | A kind of resource acquiring method and system based on block chain network | |
| CN109413117B (en) | Distributed data calculation method, device, server and computer storage medium | |
| US11297131B2 (en) | Method and apparatus for multi-vendor GTM fabric | |
| CN110113446B (en) | Client addressing method, device and system | |
| US20200267230A1 (en) | Tracking client sessions in publish and subscribe systems using a shared repository | |
| US10812390B2 (en) | Intelligent load shedding of traffic based on current load state of target capacity | |
| CN112035760B (en) | Task allocation method and computer equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200818 |