CN109005071B - Decision deployment method and scheduling equipment - Google Patents
Decision deployment method and scheduling equipment Download PDFInfo
- Publication number
- CN109005071B CN109005071B CN201811033629.0A CN201811033629A CN109005071B CN 109005071 B CN109005071 B CN 109005071B CN 201811033629 A CN201811033629 A CN 201811033629A CN 109005071 B CN109005071 B CN 109005071B
- Authority
- CN
- China
- Prior art keywords
- target
- unit
- deployment
- scheduling
- decision
- 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
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- 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]
Abstract
The invention discloses a decision deployment method and scheduling equipment, and belongs to the technical field of load balancing. The method comprises the following steps: a target decision unit of target scheduling equipment acquires a target scheduling number corresponding to a target domain name system; the target decision unit generates a target deployment task for updating target configuration information corresponding to the target domain name system based on the target scheduling data, and sends the target deployment task to a target deployment unit of the target scheduling device; and the target deployment unit executes the target deployment task and updates the target configuration information. By adopting the invention, the decision deployment efficiency can be improved.
Description
Technical Field
The present invention relates to the field of load balancing technologies, and in particular, to a decision deployment method and a scheduling device.
Background
The CDN (Content Delivery Network) system may include a scheduling device and a large number of CDN servers for processing a CDN service request, where the scheduling device performs scheduling management on the CDN servers according to configuration information, and an IP address set of the CDN server corresponding to each domain name system in different partition levels may be recorded in the configuration information.
As time goes on, some CDN servers may have scenes that do not meet the requirement of the bearer service, such as insufficient bandwidth, performance degradation, or even failure, and at this time, the configuration information needs to be updated, and the CDN servers that do not meet the scheduling requirement are replaced or deleted. The scheduling device may obtain scheduling data of each CDN server in the CDN system, such as a domain name system to which a certain CDN server belongs, disaster tolerance information, and scheduling data of the CDN server, such as a redundant bandwidth and a health value, and update the configuration information based on the scheduling data. When the configuration information is updated, the decision unit in the scheduling device generates a deployment task for updating the configuration information based on the scheduling data, and then the decision unit sends the deployment task to the deployment unit in the scheduling device. After receiving the deployment task, the deployment unit may execute the deployment task and update the configuration information.
In the process of implementing the invention, the inventor finds that the prior art has at least the following problems:
with the continuous expansion of the number of CDN servers, a large amount of scheduling data is generated, and the existing scheduling device is generally a single decision unit and single deployment unit architecture, so that a single decision unit and a single deployment unit both face higher loads and can complete update processing of configuration information in a longer time, and thus the efficiency of the decision deployment processing is low.
Disclosure of Invention
In order to solve the problems in the prior art, embodiments of the present invention provide a decision deployment method and a scheduling device. The technical scheme is as follows:
in a first aspect, a decision deployment method is provided, where the decision deployment method is applied to a scheduling device, the scheduling device includes a plurality of decision units and a plurality of deployment units, and the scheduling device allocates a domain name system to each decision unit and each deployment unit in advance, where the method includes:
a target decision unit of target scheduling equipment acquires target scheduling data corresponding to a target domain name system;
the target decision unit generates a target deployment task for updating target configuration information corresponding to the target domain name system based on the target scheduling data, and sends the target deployment task to a target deployment unit of the target scheduling device;
and the target deployment unit executes the target deployment task and updates the target configuration information.
Further, the allocating, by the target scheduling device, a domain name system to each decision unit and each deployment unit in advance includes:
the target scheduling device configures unit identifiers for the decision units and the deployment units, establishes mapping relationships between the domain name systems and the unit identifiers, and allocates the domain name systems to the decision units and the deployment units based on the mapping relationships.
Further, the obtaining, by the target decision unit of the target scheduling device, target scheduling data corresponding to the target domain name system includes:
and the target decision unit sends a scheduling data acquisition request to the target scheduling equipment based on the mapping relation between the target domain name system and the unit identifier of the target decision unit, so that the target scheduling equipment returns the pre-acquired target scheduling data corresponding to the target domain name system to the target decision unit.
Further, the sending the target deployment task to the target deployment unit of the target scheduling device includes:
the target decision unit determines the unit identifier of the target deployment unit corresponding to the target domain name system based on the mapping relation between the unit identifiers of the target domain name system and the target deployment unit;
and the target decision unit sends the target deployment task to the target deployment unit based on the unit identification of the target deployment unit.
Further, the method further comprises:
the target scheduling equipment periodically detects the working states of each decision unit and each deployment unit;
if the target decision unit is detected to be in a fault state, determining a disaster tolerance decision unit of the target decision unit in the target scheduling device or other scheduling devices except the target scheduling device based on a preset disaster tolerance standard;
or, if it is detected that the target deployment unit is in a fault state, determining a disaster recovery deployment unit of the target deployment unit in the target scheduling device or in other scheduling devices except the target scheduling device based on a preset disaster recovery standard.
Further, the determining, in the target scheduling device or in another scheduling device other than the target scheduling device based on a preset disaster tolerance standard, a disaster tolerance decision unit of the target decision unit includes:
when at least one decision unit meeting a preset disaster tolerance standard exists in the target scheduling equipment, determining a disaster tolerance decision unit of the target decision unit in the at least one decision unit;
or, when the other decision units of the target scheduling device do not meet a preset disaster tolerance standard and at least one decision unit meeting the preset disaster tolerance standard exists in other scheduling devices of a cluster where the target scheduling device is located, determining a disaster tolerance decision unit of the target decision unit in the at least one decision unit;
or, when the remaining decision units of the target scheduling device and the decision units in other scheduling devices of the cluster where the target scheduling device is located do not meet a preset disaster tolerance standard, and at least one decision unit meeting the preset disaster tolerance standard exists in other scheduling devices outside the cluster where the target scheduling device is located, determining a disaster tolerance decision unit of the target decision unit in the at least one decision unit.
Further, the determining a disaster recovery deployment unit of the target deployment unit in the target scheduling device or in other scheduling devices except the target scheduling device based on a preset disaster recovery standard includes:
when at least one deployment unit meeting a preset disaster tolerance standard exists in the target scheduling device, determining a disaster tolerance deployment unit of the target deployment unit in the at least one deployment unit;
or when the other deployment units of the target scheduling device do not meet a preset disaster tolerance standard and at least one deployment unit meeting the preset disaster tolerance standard exists in other scheduling devices of a cluster where the target scheduling device is located, determining a disaster tolerance deployment unit of the target deployment unit in the at least one deployment unit;
or when the other deployment units of the target scheduling device and the deployment units in the other scheduling devices of the cluster where the target scheduling device is located do not meet a preset disaster tolerance standard, and at least one deployment unit meeting the preset disaster tolerance standard exists in the other scheduling devices outside the cluster where the target scheduling device is located, determining a disaster tolerance deployment unit of the target deployment unit in the at least one deployment unit.
In a second aspect, a scheduling apparatus is provided, where the scheduling apparatus includes a plurality of decision units and a plurality of deployment units, and the scheduling apparatus allocates a domain name system to each decision unit and each deployment unit in advance, where:
the target decision unit is used for acquiring target scheduling data corresponding to a target domain name system;
the target decision unit is further configured to generate a target deployment task for updating target configuration information corresponding to the target domain name system based on the target scheduling data, and send the target deployment task to the target deployment unit;
the target deployment unit is used for executing the target deployment task and updating the target configuration information.
Further, the scheduling apparatus further includes an allocating unit, configured to:
configuring unit identifiers for the decision units and the deployment units, establishing mapping relations between the domain name systems and the unit identifiers, and distributing the domain name systems for the decision units and the deployment units based on the mapping relations.
Further, the scheduling device further includes a disaster recovery unit configured to:
periodically detecting the working states of each decision unit and each deployment unit;
if the target decision unit is detected to be in a fault state, determining a disaster tolerance decision unit of the target decision unit in the target scheduling device or other scheduling devices except the target scheduling device based on a preset disaster tolerance standard;
or, if it is detected that the target deployment unit is in a fault state, determining a disaster recovery deployment unit of the target deployment unit in the target scheduling device or in other scheduling devices except the target scheduling device based on a preset disaster recovery standard.
The technical scheme provided by the embodiment of the invention has the following beneficial effects:
in this embodiment, a target decision unit of a target scheduling device obtains target scheduling data corresponding to a target domain name system; the target decision unit generates a target deployment task for updating target configuration information corresponding to the target domain name system based on the target scheduling data, and sends the target deployment task to a target deployment unit of the target scheduling device; and the target deployment unit executes the target deployment task and updates the target configuration information. In this way, a scheduling device architecture of multiple decision units and multiple deployment units is built by splitting a single decision unit in one scheduling device into multiple decision units and splitting a single deployment unit into multiple deployment units, and all domain name systems can be allocated to each decision unit and deployment unit by taking the unit as a unit, so that each decision unit is only responsible for generating a deployment task for updating configuration information corresponding to the allocated domain name system, and each deployment unit is only responsible for executing the deployment task corresponding to the allocated domain name system, thereby fully utilizing system resources of the scheduling device, improving the processing efficiency of each unit, shortening the time for updating the configuration information corresponding to each domain name system, and improving the processing efficiency of decision deployment. In addition, the scheduling device may perform scheduling management on the CDN server based on the latest updated configuration information as much as possible, so that the scheduling quality may 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 flowchart of a decision deployment method according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a scheduling apparatus according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a scheduling apparatus according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a scheduling apparatus according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a scheduling apparatus according to an embodiment of the present invention.
Detailed Description
In order 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 embodiment of the invention provides a decision deployment method, wherein an execution main body of the method can be scheduling equipment, and the scheduling equipment can be a scheduling server of a CDN system and can be deployed in a machine room of a CDN service provider. The scheduling device may maintain configuration information, where the configuration information may record a set of IP addresses of CDN servers corresponding to each domain name system, and information of a main domain name, a secondary domain name, a region, and the like in the domain name system. When a user accesses a domain name with any terminal (e.g., a smart phone, a tablet computer, etc.), if the domain name is provided with acceleration service by the domain name system, the scheduling device may determine, based on the configuration information, one or more appropriate CDN servers to provide acceleration service for the domain name, that is, an IP address of the CDN server is returned to the terminal by resolution, and then the user may request corresponding network resources through the IP address. The CDN server may be an arbitrary server or a CDN service cluster composed of multiple servers, where the CDN server may be configured to cache a network resource, and if the network resource already exists in the CDN server, the CDN server may directly return the network resource to the terminal, otherwise, the CDN server may pull the network resource from the source station and then return the network resource to the terminal.
It should be noted that, the scheduling device may split the single decision unit into multiple decision units, and split the single deployment unit into multiple deployment units, where each decision unit may be any decision process or decision thread running in the target scheduling device, and each deployment unit may be any deployment process or deployment thread running in the target scheduling device. The decision unit may generate a deployment task for updating configuration information corresponding to a domain name system, and the deployment unit may receive the deployment task generated by the decision unit, and then may execute the deployment task, and update an IP (Internet Protocol ) address of a CDN server to be scheduled, which is recorded in the configuration information and corresponds to the domain name system. The scheduling device may assign a domain name system to each decision unit and each deployment unit in advance.
The scheduling device may include a processor, a memory, and a transceiver, where the processor may be configured to perform the scheduling process in the following process, the memory may be configured to store data required and generated in the following process, and the transceiver may be configured to receive and transmit related data in the following process.
The following will describe in detail a processing flow of the decision deployment method shown in fig. 1 with reference to specific embodiments, and the content may be as follows:
step 101: and a target decision unit of the target scheduling equipment acquires target scheduling data corresponding to the target domain name system.
In implementation, a certain scheduling device (may be referred to as a target scheduling device) of the CDN system may configure an access domain name system in the CDN system in advance for each website domain name system based on the CNAME technology, for convenience of description, only web acceleration is taken as an example for the following description, the target domain name system of the acceleration service platform of the CDN system may be www.abc.com, and when a user accesses www.baidu.com, the user domain name www.baidu.com may be accessed to the domain name system www.abc.com of the acceleration service platform for acceleration service. Specifically, a CNAME record may be added to the domain name in the domain name resolution configuration, so that the domain name www.baidu.com may point to www.abc.com (generally, CNAME is also supported to a secondary domain name inside the platform, for example, www.abc.com may be CNAME to www.xyx.abc.com, and this process is not described in this embodiment with emphasis). When the user accesses domain name www.baidu.com, the user may enter the user domain name in a browser program run by the terminal and click an access button to access the website. In this way, the terminal initiates a domain name resolution request for the domain name www.baidu.com to the acceleration service platform. Then, the target scheduling device may return an IP address of a CDN server to the terminal based on the configuration information corresponding to the target domain name system www.abc.com based on the domain name resolution request. And the terminal can obtain corresponding network resources through the CDN server corresponding to the IP address.
In this way, the target scheduling device may obtain scheduling data (which may be referred to as target scheduling data) of each CDN server to be scheduled corresponding to the target domain name system based on the target domain name system, where the target scheduling data may include dynamic data and static data, and the dynamic data may include data such as a real-time bandwidth, a peak bandwidth, and a health value of each CDN server; the static data may include modeling data of all CDN servers in the CDN system, such as data of a main domain name, a secondary domain name, a region, a cluster, an IP, and the like, and data in which disaster recovery decision units corresponding to the decision units or disaster recovery information of disaster recovery deployment units corresponding to the deployment units are recorded, and the static data may be stored in a database, where the database may be deployed in a target scheduling device, or may be deployed in other scheduling devices in a distributed manner, and is not limited here. Then, a decision unit (which may be referred to as a target decision unit) in the target scheduling device corresponding to the target domain name system may obtain the target scheduling data.
Optionally, the target scheduling device may allocate a domain name system to each decision unit in advance, and accordingly, the specific processing may be as follows: the target scheduling equipment configures unit identifications for each decision unit and allocates a domain name system for each decision unit based on the unit identifications.
In implementation, the target scheduling device may configure a unit identifier for each decision unit in advance based on its own device identifier and the process sequence number of each decision process. Specifically, the target scheduling device may identify each decision unit by using a dispatch IP + server id, where the dispatch IP may be a device identifier of the target scheduling device, for example, an IP address of the target scheduling device, the server id may be a unit serial number pre-allocated to the target scheduling device, and may be a string of characters, such as 001, 002, and the like, and if the target scheduling device is the dispatch IP and the server id is the IP address 210.61.180.132, for example, if the target scheduling device is a target scheduling deviceIf the device operates with four decision units, 210.61.180.132: 001. 210.61.180.132: 002. 210.61.180.132: 003. 210.61.180.132: 004 to identify the four decision units, respectively. The target scheduling device may then assign a domain name system to each decision unit based on the respective unit identifier of each decision unit. Taking M domain name systems and N decision units as examples (M is more than or equal to N), the M domain name systems can be marked as A1、A2、A3……AMN decision units can be labeled B1、B2、B3……BNThe target scheduling device may randomly allocate the M domain name systems to the N decision units, or may allocate the M domain name systems according to a preset rule, where if the M domain name systems are allocated according to a mode that the sequence number is equal to or differs by N, the allocation result may be as follows:
B1：A1、AN+1、A2N+1……；
B2：A2、AN+2、A2N+2……；
B3：A3、AN+3、A2N+3……；
BN：AN、A2N、A3N……。
optionally, the processing that the target decision unit of the target scheduling device obtains the target scheduling data corresponding to the target domain name system may be as follows: and the target decision unit sends a scheduling data acquisition request to the target scheduling equipment based on the target domain name system and the unit identifier of the target decision unit so that the target scheduling equipment returns the pre-acquired target scheduling data corresponding to the target domain name system to the target decision unit.
In implementation, the target scheduling device may obtain the scheduling data corresponding to each domain name system in advance, or may obtain the scheduling data corresponding to a domain name system in real time after receiving a scheduling data obtaining request for the domain name system. In this way, the target decision unit may send a scheduling data acquisition request to the target scheduling device based on the target domain name system and the unit identifier of the target decision unit. After receiving the scheduling data acquisition request, the target scheduling device may return the target scheduling data corresponding to the target domain name system, which is acquired in advance or acquired in real time, to the target decision unit based on the unit identifier of the target decision unit. In this way, the target decision unit may receive target scheduling data corresponding to the target domain name system from the target scheduling device.
Step 102: and the target decision unit generates a target deployment task for updating target configuration information corresponding to the target domain name system based on the target scheduling data, and sends the target deployment task to the target deployment unit of the target scheduling device.
In implementation, after obtaining target scheduling data corresponding to a target domain name system, a target decision unit may perform decision processing based on the target scheduling data, and determine whether each CDN server to be scheduled in current configuration information corresponding to the target domain name system meets a scheduling requirement, and when there is a CDN server that does not meet the scheduling requirement, the target decision unit may perform processing such as deletion or replacement on the CDN server that does not meet the scheduling requirement in a manner of sending a deployment task to a target deployment unit of the target scheduling device.
Optionally, the target scheduling device may allocate a domain name system to each deployment unit in advance, and accordingly, the specific processing may be as follows: the target scheduling device configures unit identifiers for the deployment units, and allocates a domain name system to the deployment units based on the unit identifiers.
In implementation, the target scheduling device may configure a unit identifier for each deployment unit in advance based on its own device identifier and the process sequence number of each deployment process. Specifically, the target scheduling device may also identify each deployment unit according to the above-mentioned manner of dispatch ip + server id. Then, the target scheduling device may assign a domain name system to each deployment unit based on the unit identifier of each deployment unit. Taking M domain name systems and N deployment units as examples (M is more than or equal to N), the M domain name systems can be marked as A1、A2、A3……AMN deployment units may be labeled C1、C2、C3……CNThe target scheduling device may randomly allocate the M domain name systems to the N deployment units, or may allocate the M domain name systems according to a preset rule, where if the M domain name systems are allocated according to a mode that a sequence number is equal to or differs by N, an allocation result may be as follows:
C1：A1、AN+1、A2N+1……；
C2：A2、AN+2、A2N+2……；
C3：A3、AN+3、A2N+3……；
CN：AN、A2N、A3N……。
optionally, the processing that the target decision unit sends the target deployment task to the target deployment unit may specifically be as follows: the target decision unit determines the unit identifier of a target deployment unit corresponding to the target domain name system based on the target domain name system; and the target decision unit sends the target deployment task to the target deployment unit based on the unit identifier of the target deployment unit.
In implementation, after the target decision unit generates the target deployment task for updating the target configuration information corresponding to the target domain name system, the unit identifier of the target deployment unit corresponding to the target domain name system may be determined based on the target domain name system. The target decision unit may then send the target deployment task to the target deployment unit based on the unit identification of the target deployment unit.
Step 103: and the target deployment unit executes the target deployment task and updates the target configuration information.
In implementation, after receiving the target deployment task, the target deployment unit may execute the target deployment task and update the target configuration information corresponding to the target domain name system. Specifically, the target deployment unit may obtain change information of current configuration information corresponding to the target domain name system based on task details of the target deployment task, for example, an IP address of a CDN server to be deleted or an IP address of a newly added CDN server in each region of the target domain name system, and then the target deployment unit may update the target configuration information based on the change information.
Optionally, a corresponding disaster recovery unit may be configured for each decision unit and each deployment unit, and accordingly, the specific processing may be as follows: the target scheduling equipment periodically detects the working states of each decision unit and each deployment unit; if the target decision unit is detected to be in a fault state, determining the disaster tolerance decision unit of the target decision unit in the target scheduling device or other scheduling devices except the target scheduling device based on a preset disaster tolerance standard; or, if the target deployment unit is detected to be in a fault state, determining the disaster recovery deployment unit of the target deployment unit in the target scheduling device or in other scheduling devices except the target scheduling device based on a preset disaster recovery standard.
In implementation, the CDN system may deploy multiple scheduling devices in different computer rooms, and a decision unit in each scheduling device that meets a preset disaster tolerance criterion may serve as a disaster tolerance decision unit of another decision unit, where the preset disaster tolerance criterion may include that an average processing time (x) is less than a preset processing time (x '), a queue space usage rate (y) is less than a preset threshold (y'), and other disaster tolerance criteria.
For example, the disaster recovery function f (x, y) can be expressed simply by a two-dimensional index, 0: disaster recovery, 1: in the normal state, the operation of the device,
further, the target scheduling device may periodically detect the working states of each decision unit and each deployment unit. Specifically, the scheduling device may periodically collect health data of each decision unit, for example, information such as average processing time, heartbeat packets, queue capacity, IO read-write, CPU utilization rate, and the like, and for example, the scheduling device may collect the health data of each decision unit after each round of decision is completed. In this way, the scheduling device may determine whether each decision unit or each deployment unit fails based on the health data.
Thus, when the target decision unit is detected to be in a fault state, the target scheduling device may determine the disaster tolerance decision unit of the target decision unit in the target scheduling device or in other scheduling devices except the target scheduling device based on the preset disaster tolerance standard; when it is detected that the target deployment unit is in a fault state, the target scheduling device may determine, based on a preset disaster tolerance standard, the disaster tolerance deployment unit of the target deployment unit in the target scheduling device or in another scheduling device other than the target scheduling device.
Optionally, the processing of the disaster tolerance decision unit of the target decision unit may specifically be as follows: when at least one decision unit meeting a preset disaster tolerance standard exists in the target scheduling equipment, determining a disaster tolerance decision unit of the target decision unit in the at least one decision unit; or when the other decision units of the target scheduling device do not accord with the preset disaster tolerance standard and at least one decision unit which accords with the preset disaster tolerance standard exists in other scheduling devices of the cluster where the target scheduling device is located, determining the disaster tolerance decision unit of the target decision unit in the at least one decision unit; or, when the other decision units of the target scheduling device and the decision units in the other scheduling devices of the cluster where the target scheduling device is located do not meet the preset disaster tolerance standard, and at least one decision unit meeting the preset disaster tolerance standard exists in the other scheduling devices outside the cluster where the target scheduling device is located, determining the disaster tolerance decision unit of the target decision unit in the at least one decision unit.
In implementation, when a failure of the target decision unit is detected, the target scheduling device may determine the disaster tolerance decision unit of the target decision unit based on the disaster tolerance rule of the nearby disaster tolerance. For example, when at least one decision unit meeting a preset disaster tolerance standard exists in the target scheduling device, the target scheduling device may select one decision unit from the decision units meeting the preset disaster tolerance standard in the target scheduling device as the disaster tolerance decision unit of the target decision unit; when the other decision units of the target scheduling device do not accord with the preset disaster tolerance standard, but at least one decision unit which accords with the preset disaster tolerance standard exists in other scheduling devices of the cluster where the target scheduling device is located, the target scheduling device can select one decision unit from the decision units which accord with the preset disaster tolerance standard in the other scheduling devices of the cluster where the target scheduling device is located as a disaster tolerance decision unit of the target decision unit; when the other decision units of the target scheduling device and the decision units in the other scheduling devices of the cluster where the target scheduling device is located do not meet the preset disaster tolerance standard, but at least one decision unit meeting the preset disaster tolerance standard exists in the other scheduling devices outside the cluster where the target scheduling device is located, the target scheduling device may select one decision unit from the decision units meeting the preset disaster tolerance standard in the other scheduling devices outside the cluster where the target scheduling device is located, as the disaster tolerance decision unit of the target decision unit.
Optionally, the processing for determining the disaster recovery deployment unit of the target deployment unit may specifically be as follows: when at least one deployment unit meeting a preset disaster tolerance standard exists in the target scheduling equipment, determining a disaster tolerance deployment unit of the target deployment unit in the at least one deployment unit; or when the other deployment units of the target scheduling device do not accord with the preset disaster tolerance standard and at least one deployment unit which accords with the preset disaster tolerance standard exists in other scheduling devices of the cluster where the target scheduling device is located, determining the disaster tolerance deployment unit of the target deployment unit in the at least one deployment unit; or when the other deployment units of the target scheduling device and the deployment units in the other scheduling devices of the cluster where the target scheduling device is located do not meet the preset disaster tolerance standard, and at least one deployment unit meeting the preset disaster tolerance standard exists in the other scheduling devices outside the cluster where the target scheduling device is located, determining the disaster tolerance deployment unit of the target deployment unit in the at least one deployment unit.
In implementation, when a failure of the target deployment unit is detected, the target scheduling device may determine the disaster recovery deployment unit of the target deployment unit based on the disaster recovery rule of the nearby disaster recovery. For example, when the target scheduling device has at least one deployment unit meeting the preset disaster tolerance standard, the target scheduling device may select one deployment unit from the deployment units meeting the preset disaster tolerance standard in the target scheduling device as the disaster tolerance deployment unit of the target deployment unit; when the other deployment units of the target scheduling device do not meet the preset disaster tolerance standard, but at least one deployment unit meeting the preset disaster tolerance standard exists in other scheduling devices of the cluster where the target scheduling device is located, the target scheduling device can select one deployment unit from the deployment units meeting the preset disaster tolerance standard in the other scheduling devices of the cluster where the target scheduling device is located as a disaster tolerance deployment unit of the target deployment unit; when the other deployment units of the target scheduling device and the deployment units in the other scheduling devices of the cluster where the target scheduling device is located do not meet the preset disaster tolerance standard, but at least one deployment unit meeting the preset disaster tolerance standard exists in the other scheduling devices outside the cluster where the target scheduling device is located, the target scheduling device may select one deployment unit from the deployment units meeting the preset disaster tolerance standard of the other scheduling devices outside the cluster where the target scheduling device is located, as the disaster tolerance deployment unit of the target deployment unit.
In this embodiment, a target decision unit of a target scheduling device obtains target scheduling data corresponding to a target domain name system; the target decision unit generates a target deployment task for updating target configuration information corresponding to the target domain name system based on the target scheduling data, and sends the target deployment task to a target deployment unit of the target scheduling device; and the target deployment unit executes the target deployment task and updates the target configuration information. In this way, a scheduling device architecture of multiple decision units and multiple deployment units is built by splitting a single decision unit in one scheduling device into multiple decision units and splitting a single deployment unit into multiple deployment units, and all domain name systems can be allocated to each decision unit and deployment unit by taking the unit as a unit, so that each decision unit is only responsible for generating a deployment task for updating configuration information corresponding to the allocated domain name system, and each deployment unit is only responsible for executing the deployment task corresponding to the allocated domain name system, thereby fully utilizing system resources of the scheduling device, improving the processing efficiency of each unit, shortening the time for updating the configuration information corresponding to each domain name system, and improving the processing efficiency of decision deployment. In addition, the scheduling device may perform scheduling management on the CDN server based on the latest updated configuration information as much as possible, so that the scheduling quality may be improved.
Based on the same technical concept, an embodiment of the present invention further provides a scheduling apparatus, as shown in fig. 2, where the scheduling apparatus includes a plurality of decision units and a plurality of deployment units, and the scheduling apparatus allocates a domain name system to each decision unit and each deployment unit in advance, where:
the target decision unit 201 is configured to obtain target scheduling data corresponding to a target domain name system;
the target decision unit 201 is further configured to generate a target deployment task for updating target configuration information corresponding to the target domain name system based on the target scheduling data, and send the target deployment task to the target deployment unit 202;
the target deployment unit 202 is configured to execute the target deployment task and update the target configuration information.
As shown in fig. 3, optionally, the scheduling apparatus further includes an allocating unit 203, configured to:
configuring unit identifiers for the decision units and the deployment units, establishing mapping relations between the domain name systems and the unit identifiers, and distributing the domain name systems for the decision units and the deployment units based on the mapping relations.
Optionally, the goal decision unit 201 is further configured to:
based on the target domain name system and the unit identifier of the target decision unit 201, sending a scheduling data acquisition request to the target scheduling device, so that the target scheduling device returns the pre-acquired target scheduling data corresponding to the target domain name system to the target decision unit 201.
Optionally, the goal decision unit 201 is further configured to:
determining a unit identifier of a target deployment unit 202 corresponding to the target domain name system based on the target domain name system;
based on the unit identity of the target deployment unit 202, the target deployment task is sent to the target deployment unit 202.
As shown in fig. 4, optionally, the scheduling device further includes a disaster recovery unit 204, configured to:
periodically detecting the working states of each decision unit and each deployment unit;
if the target decision unit 201 is detected to be in a fault state, determining a disaster tolerance decision unit of the target decision unit 201 in the target scheduling device or in other scheduling devices except the target scheduling device based on a preset disaster tolerance standard;
or, if it is detected that the target deployment unit 202 is in a failure state, determining a disaster recovery deployment unit of the target deployment unit 202 in the target scheduling device or in other scheduling devices except the target scheduling device based on a preset disaster recovery standard.
Optionally, the disaster recovery unit 204 is further configured to:
when at least one decision unit meeting a preset disaster tolerance standard exists in the target scheduling device, determining a disaster tolerance decision unit of the target decision unit 201 in the at least one decision unit;
or, when the remaining decision units of the target scheduling device do not meet a preset disaster tolerance standard, and at least one decision unit meeting the preset disaster tolerance standard exists in other scheduling devices of the cluster where the target scheduling device is located, determining a disaster tolerance decision unit of the target decision unit 201 in the at least one decision unit;
or, when the remaining decision units of the target scheduling device and the decision units in other scheduling devices of the cluster where the target scheduling device is located do not meet the preset disaster tolerance standard, and at least one decision unit meeting the preset disaster tolerance standard exists in other scheduling devices outside the cluster where the target scheduling device is located, determining the disaster tolerance decision unit of the target decision unit 201 in the at least one decision unit.
Optionally, the disaster recovery unit 204 is further configured to:
when at least one deployment unit meeting a preset disaster tolerance standard exists in the target scheduling device, determining a disaster tolerance deployment unit of the target deployment unit 202 in the at least one deployment unit;
or, when the remaining deployment units of the target scheduling device do not meet a preset disaster tolerance standard, and at least one deployment unit meeting the preset disaster tolerance standard exists in other scheduling devices of a cluster where the target scheduling device is located, determining a disaster tolerance deployment unit of the target deployment unit 202 in the at least one deployment unit;
or, when none of the other deployment units of the target scheduling device and the deployment units in the other scheduling devices of the cluster where the target scheduling device is located meet a preset disaster tolerance standard, and at least one deployment unit meeting the preset disaster tolerance standard exists in the other scheduling devices outside the cluster where the target scheduling device is located, determining a disaster tolerance deployment unit of the target deployment unit 202 in the at least one deployment unit.
It should be noted that: in the scheduling apparatus provided in the foregoing embodiment, only the division of the functional modules is illustrated in the foregoing, and in practical applications, the function allocation may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the scheduling device and the decision deployment method provided by the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments in detail and are not described herein again.
Fig. 5 is a schematic structural diagram of a scheduling apparatus according to an embodiment of the present invention. The scheduling apparatus 500 may vary widely due to configuration or performance differences and may include one or more central processors 522 (e.g., one or more processors) and memory 532, one or more storage media 530 (e.g., one or more mass storage devices) storing applications 542 or data 544. Memory 532 and storage media 530 may be, among other things, transient storage or persistent storage. The program stored on the storage medium 530 may include one or more modules (not shown), each of which may include a sequence of instructions operating on a scheduling device. Still further, the central processor 522 may be configured to communicate with the storage medium 530 to execute a series of instruction operations in the storage medium 530 on the scheduling device 500.
The scheduler 500 may also include one or more power supplies 526, one or more wired or wireless network interfaces 550, one or more input-output interfaces 558, and/or one or more operating systems 531 such as Windows Server (TM), Mac OS XTM, Unix (TM), Linux (TM), FreeBSD (TM), etc.
The scheduling apparatus 500 may include a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by one or more processors, the one or more programs including instructions for performing the scheduling described above.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (10)
1. A decision deployment method is applied to scheduling equipment, the scheduling equipment comprises a plurality of decision units and a plurality of deployment units, and the scheduling equipment allocates a domain name system for each decision unit and each deployment unit in advance, wherein the method comprises the following steps:
a target decision unit of target scheduling equipment acquires target scheduling data corresponding to a target domain name system;
the target decision unit generates a target deployment task for updating target configuration information corresponding to the target domain name system based on the target scheduling data, and sends the target deployment task to a target deployment unit of the target scheduling device;
and the target deployment unit executes the target deployment task and updates the target configuration information.
2. The method according to claim 1, wherein the target scheduling device assigns a domain name system to each of the decision units and each of the deployment units in advance, and the method comprises:
the target scheduling device configures unit identifiers for the decision units and the deployment units, and allocates domain name systems to the decision units and the deployment units based on the unit identifiers.
3. The method according to claim 2, wherein the obtaining, by the target decision unit of the target scheduling device, target scheduling data corresponding to a target domain name system includes:
and the target decision unit sends a scheduling data acquisition request to the target scheduling equipment based on the target domain name system and the unit identifier of the target decision unit, so that the target scheduling equipment returns the pre-acquired target scheduling data corresponding to the target domain name system to the target decision unit.
4. The method of claim 2, wherein sending the target deployment task to the target deployment unit of the target scheduling device comprises:
the target decision unit determines a unit identifier of a target deployment unit corresponding to the target domain name system based on the target domain name system;
and the target decision unit sends the target deployment task to the target deployment unit based on the unit identification of the target deployment unit.
5. The method of claim 1, further comprising:
the target scheduling equipment periodically detects the working states of each decision unit and each deployment unit;
if the target decision unit is detected to be in a fault state, determining a disaster tolerance decision unit of the target decision unit in the target scheduling device or other scheduling devices except the target scheduling device based on a preset disaster tolerance standard;
or, if it is detected that the target deployment unit is in a fault state, determining a disaster recovery deployment unit of the target deployment unit in the target scheduling device or in other scheduling devices except the target scheduling device based on a preset disaster recovery standard.
6. The method according to claim 5, wherein the determining a disaster recovery decision unit of the target decision unit in the target scheduling device or in another scheduling device other than the target scheduling device based on a preset disaster recovery criterion includes:
when at least one decision unit meeting a preset disaster tolerance standard exists in the target scheduling equipment, determining a disaster tolerance decision unit of the target decision unit in the at least one decision unit;
or, when the other decision units of the target scheduling device do not meet a preset disaster tolerance standard and at least one decision unit meeting the preset disaster tolerance standard exists in other scheduling devices of a cluster where the target scheduling device is located, determining a disaster tolerance decision unit of the target decision unit in the at least one decision unit;
or, when the remaining decision units of the target scheduling device and the decision units in other scheduling devices of the cluster where the target scheduling device is located do not meet a preset disaster tolerance standard, and at least one decision unit meeting the preset disaster tolerance standard exists in other scheduling devices outside the cluster where the target scheduling device is located, determining a disaster tolerance decision unit of the target decision unit in the at least one decision unit.
7. The method according to claim 5, wherein the determining a disaster recovery deployment unit of the target deployment unit in the target scheduling device or in another scheduling device other than the target scheduling device based on a preset disaster recovery criterion includes:
when at least one deployment unit meeting a preset disaster tolerance standard exists in the target scheduling device, determining a disaster tolerance deployment unit of the target deployment unit in the at least one deployment unit;
or when the other deployment units of the target scheduling device do not meet a preset disaster tolerance standard and at least one deployment unit meeting the preset disaster tolerance standard exists in other scheduling devices of a cluster where the target scheduling device is located, determining a disaster tolerance deployment unit of the target deployment unit in the at least one deployment unit;
or when the other deployment units of the target scheduling device and the deployment units in the other scheduling devices of the cluster where the target scheduling device is located do not meet a preset disaster tolerance standard, and at least one deployment unit meeting the preset disaster tolerance standard exists in the other scheduling devices outside the cluster where the target scheduling device is located, determining a disaster tolerance deployment unit of the target deployment unit in the at least one deployment unit.
8. A scheduling apparatus, characterized in that the scheduling apparatus includes a plurality of decision units and a plurality of deployment units, and the scheduling apparatus allocates a domain name system to each decision unit and each deployment unit in advance, wherein:
the target decision unit of the target scheduling device is used for acquiring target scheduling data corresponding to a target domain name system;
the target decision unit is further configured to generate a target deployment task for updating target configuration information corresponding to the target domain name system based on the target scheduling data, and send the target deployment task to the target deployment unit;
the target deployment unit is used for executing the target deployment task and updating the target configuration information.
9. The scheduling apparatus of claim 8, wherein the scheduling apparatus further comprises an allocating unit configured to:
and configuring unit identifications for each decision unit and each deployment unit, and distributing a domain name system for each decision unit and each deployment unit based on the unit identifications.
10. The scheduling device of claim 8, wherein the scheduling device further comprises a disaster recovery unit configured to:
periodically detecting the working states of each decision unit and each deployment unit;
if the target decision unit is detected to be in a fault state, determining a disaster tolerance decision unit of the target decision unit in the target scheduling device or other scheduling devices except the target scheduling device based on a preset disaster tolerance standard;
or, if it is detected that the target deployment unit is in a fault state, determining a disaster recovery deployment unit of the target deployment unit in the target scheduling device or in other scheduling devices except the target scheduling device based on a preset disaster recovery standard.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811033629.0A CN109005071B (en) | 2018-09-05 | 2018-09-05 | Decision deployment method and scheduling equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811033629.0A CN109005071B (en) | 2018-09-05 | 2018-09-05 | Decision deployment method and scheduling equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109005071A CN109005071A (en) | 2018-12-14 |
| CN109005071B true CN109005071B (en) | 2021-05-25 |
Family
ID=64590369
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811033629.0A Active CN109005071B (en) | 2018-09-05 | 2018-09-05 | Decision deployment method and scheduling equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109005071B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109379244B (en) * | 2018-12-28 | 2022-06-21 | 北京云中融信网络科技有限公司 | Network acceleration communication method and device and electronic equipment |
| CN109889569B (en) * | 2019-01-03 | 2022-04-22 | 网宿科技股份有限公司 | CDN service scheduling method and system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104252381A (en) * | 2013-06-30 | 2014-12-31 | 北京百度网讯科技有限公司 | Method and equipment for scheduling ETL (Extraction-Transform-Loading) task |
| WO2016064589A1 (en) * | 2014-10-24 | 2016-04-28 | Asurion, Llc | Centralized control and management systems for digital devices |
| CN106982236A (en) * | 2016-01-18 | 2017-07-25 | 阿里巴巴集团控股有限公司 | A kind of information processing method, device and system |
-
2018
- 2018-09-05 CN CN201811033629.0A patent/CN109005071B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104252381A (en) * | 2013-06-30 | 2014-12-31 | 北京百度网讯科技有限公司 | Method and equipment for scheduling ETL (Extraction-Transform-Loading) task |
| WO2016064589A1 (en) * | 2014-10-24 | 2016-04-28 | Asurion, Llc | Centralized control and management systems for digital devices |
| CN106982236A (en) * | 2016-01-18 | 2017-07-25 | 阿里巴巴集团控股有限公司 | A kind of information processing method, device and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109005071A (en) | 2018-12-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10635664B2 (en) | Map-reduce job virtualization | |
| US11586673B2 (en) | Data writing and reading method and apparatus, and cloud storage system | |
| US20180365074A1 (en) | Thread pool management | |
| US8032780B2 (en) | Virtualization based high availability cluster system and method for managing failure in virtualization based high availability cluster system | |
| CN108924268B (en) | Container cloud service system and pod creation method and device | |
| US8185905B2 (en) | Resource allocation in computing systems according to permissible flexibilities in the recommended resource requirements | |
| US20130185404A1 (en) | Efficient port management for a distributed network address translation | |
| US20100138540A1 (en) | Method of managing organization of a computer system, computer system, and program for managing organization | |
| CN109451088A (en) | A kind of data access method and device | |
| CN114070822B (en) | Kubernetes Overlay IP address management method | |
| CN111092921B (en) | Data acquisition method, device and storage medium | |
| CN113965560A (en) | Data transmission method, proxy server, storage medium, and electronic device | |
| US10761869B2 (en) | Cloud platform construction method and cloud platform storing image files in storage backend cluster according to image file type | |
| US20220318071A1 (en) | Load balancing method and related device | |
| CN111666131A (en) | Load balancing distribution method and device, computer equipment and storage medium | |
| CN109005071B (en) | Decision deployment method and scheduling equipment | |
| CN115086330A (en) | Cross-cluster load balancing system | |
| CN113382077A (en) | Micro-service scheduling method and device, computer equipment and storage medium | |
| CN110798507B (en) | Method and system for DHCP address allocation memory | |
| US8972604B1 (en) | Network address retention and assignment | |
| CN111294220B (en) | Nginx-based network isolation configuration method and device | |
| CN108228272B (en) | WEB container generation processing method, equipment and server | |
| CN112799849B (en) | Data processing method, device, equipment and storage medium | |
| CN111274022A (en) | Server resource allocation method and system | |
| CN111404980B (en) | Data storage method and object storage system |
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 |