WO2016173452A1 - 解析任务的处理方法、装置及服务器 - Google Patents

解析任务的处理方法、装置及服务器 Download PDF

Info

Publication number
WO2016173452A1
WO2016173452A1 PCT/CN2016/079867 CN2016079867W WO2016173452A1 WO 2016173452 A1 WO2016173452 A1 WO 2016173452A1 CN 2016079867 W CN2016079867 W CN 2016079867W WO 2016173452 A1 WO2016173452 A1 WO 2016173452A1
Authority
WO
WIPO (PCT)
Prior art keywords
task
parsing
combined
queue
domain name
Prior art date
Application number
PCT/CN2016/079867
Other languages
English (en)
French (fr)
Inventor
刘磊
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2016173452A1 publication Critical patent/WO2016173452A1/zh

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/2866—Architectures; Arrangements

Definitions

  • the present application relates to the field of network communication technologies, and in particular, to a method, an apparatus, and a server for processing a resolution task.
  • Cloud service is an increase, use and delivery mode of Internet-based related services.
  • VM Virtual Machine
  • each VM on the cloud server may correspond to a primary domain name of a website, and each primary domain name may correspond to multiple subdomains.
  • different VMs may send a resolution task of a corresponding website to a server that generates domain name resolution, and the server generates domain name resolutions for different domain names by performing these resolution tasks, so as to point these domain names to the IP of the corresponding website (Internet Protocol, Internet Protocol). The address, so that users can access the website resources corresponding to these primary domain names or subdomains.
  • the server allocates processing resources to these parsing tasks in the order of sending time, which makes it difficult to prioritize some important parsing tasks, thus affecting the progress of domain name parsing. Users cannot prioritize access to website resources.
  • the application provides a method, a device, and a server for processing a resolution task, so as to solve the problem that the server allocates processing resources evenly for the analysis task, thereby affecting the progress of the domain name resolution generation of the website.
  • a method for processing a parsing task comprising:
  • each combined parsing task includes one or more original parsing tasks
  • the parsing resources are allocated to the combined parsing task in descending order of priority.
  • a processing apparatus for a parsing task includes:
  • An obtaining unit configured to obtain an original parsing task of the domain name from a cache queue of each domain name
  • a generating unit configured to generate, according to the original parsing task, a combined parsing task with different priorities for each domain name, where each combined parsing task includes one or more original parsing tasks;
  • an allocating unit configured to allocate an analysis resource to the combined parsing task according to a priority from high to low.
  • a server including:
  • processor a memory for storing the processor executable instructions
  • processor is configured to:
  • each combined parsing task includes one or more original parsing tasks
  • the parsing resources are allocated to the combined parsing task in descending order of priority.
  • the original parsing task of each domain name is cached by the cache queue.
  • the parsing task is processed, the original parsing task of the domain name is obtained from the cache queue of each domain name, and then each domain name is generated with different priorities.
  • the combined parsing tasks are assigned parsing resources for the combined parsing tasks in descending order of priority.
  • the combined parsing task is generated according to the original parsing task of each domain name, the total number of parsing tasks that need to be processed is reduced, and different combined parsing tasks have different priorities, so the parsing resources can be allocated according to the priority.
  • the important parsing tasks can be prioritized to ensure the progress of domain name resolution and ensure that users can preferentially access website resources.
  • FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application
  • FIG. 2 is a flowchart of an embodiment of a processing method of a parsing task of the present application
  • FIG. 3A is a flowchart of another embodiment of a processing method for a parsing task of the present application.
  • FIG. 3B is a schematic diagram of a process of processing a parsing task in FIG. 3A;
  • FIG. 4 is a hardware structural diagram of a server where a processing device of a resolution task of the present application is located;
  • FIG. 5 is a block diagram of an embodiment of a processing device for a parsing task of the present application
  • FIG. 6 is a block diagram of another embodiment of a processing device for a parsing task of the present application.
  • first, second, third, etc. may be used to describe various information in this application, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information without departing from the scope of the present application.
  • second information may also be referred to as the first information.
  • word "if” as used herein may be interpreted as "when” or “when” or “in response to a determination.”
  • FIG. 1 is a schematic diagram of an application scenario of applying the embodiment of the present application:
  • a cloud service system is shown in FIG. 1.
  • the embodiment of the present application may perform a process of parsing a task based on the cloud service system, and further generate a domain name resolution based on the processing result, where the cloud server system includes a cloud server and a resolution task.
  • the server hereinafter referred to as the processing server in the embodiment of the present application
  • the server for generating the domain name resolution hereinafter referred to as the generation server in the embodiment of the present application.
  • n is a natural number greater than 1
  • VMs are set on the cloud server, and each VM can be provided to a website for storing website resources of the website, and each website is identified by the assigned IP address. The user can access the website resources by inputting the domain name registered by the website.
  • the DNS server can convert the domain name into the IP address of the website, thereby completing the access to the website. Therefore, to implement the user to access different website resources through the domain name, the server needs to generate the domain name resolution task in advance, so as to generate domain name resolution for different domain names, so as to follow the generated domain name resolution result from the domain name to the IP address. Conversion.
  • the processing server allocates processing resources on average for the parsing tasks in the order of the sending time, which causes some important parsing tasks to be difficult to be prioritized, thereby affecting the progress of domain name parsing.
  • the processing server may set a processing server in the front end of the generating server, and the processing server first caches the original parsing task sent by the VM corresponding to each domain name through the cache queue, and then uniformly performs the parsing task in the cache queue.
  • processing obtaining the original parsing task of the domain name from the cache queue of each domain name, and then generating a combined parsing task with different priorities for each domain name, and allocating the parsing resources for the combined parsing task according to the order of priority from high to low. Subsequently can be assigned by the build server
  • the parsing resource parses the combined parsing task to generate domain name resolution of different domain names.
  • the processing server shown in FIG. 1 is independent of the generating server setting, and in actual applications, the functions of the processing server and the generating server may also be
  • the embodiment of the present application is not limited to the embodiment of the present application.
  • the embodiment of the present application can be applied to any server that integrates the function of processing a resolution task.
  • FIG. 2 it is a flowchart of an embodiment of a processing method for a parsing task of the present application, which is described from the server side:
  • Step 201 Obtain an original resolution task of the domain name from a cache queue of each domain name.
  • each domain name corresponds to multiple resolution tasks. By performing these resolution tasks, domain name resolution is generated.
  • These parsing tasks may include: parsing tasks of AddZone (configuration domain name domain); configuring parsing tasks of A (Address) records; configuring parsing tasks of CNAME (alias) records; and configuring parsing tasks of MX (Mailbox, mailbox) records;
  • the configuration task of the DelZone deleting the domain name domain), the configuration of the spam filtering, and the configuration of the directory access task, and the configuration of the configuration task are the same as the prior art. .
  • a cache queue may be created for each domain name in advance, and each cache queue is used to cache the domain name resolution task. Therefore, after receiving the domain name resolution task, the chronological order may be received. , the parsing task of the domain name is added to the cache queue of the domain name.
  • the parsing task of each domain name may be extracted from the cache queue, and the parsing task cached in the cache queue may be referred to as a parsing task in the cache queue in the embodiment of the present application. The original parsing task.
  • Step 202 Generate a combined parsing task with different priorities for each domain name according to the original parsing task, where each combined parsing task includes one or more original parsing tasks.
  • the importance of the domain name resolution may be different according to different resolution tasks, and the original analysis task is classified into a preset task type.
  • the task type may include a transaction with a higher degree of importance.
  • Tasks for example, AddZone's parsing task, configuration A record parsing task, configuration CNAME record parsing task, configuration MX record parsing task, etc., as well as regular tasks of less important importance, for example, DelZone parsing tasks, configuration Parsing tasks for spam filtering, parsing tasks for configuring directory access, and so on.
  • each combined parsing task is Contains one or more resolution tasks with the same task type.
  • the parsing task includes a first combined parsing task and a second combined parsing task, wherein the task type of the parsing task included in the first combined parsing task is a transactional task, and the task type of the parsing task included in the second combined parsing task If it is a regular task, it can be known that the priority of the first combined parsing task is higher than the priority of the second combined parsing task.
  • Step 203 Allocate the parsing resource for the combined parsing task according to the order of priority from high to low.
  • a task queue may be set for each priority according to the classification of the task type, or according to the priority of the combined resolution task.
  • the example in the previous step 202 may be the first with higher priority.
  • each combined parsing task can be added to the corresponding task queue, and then the priority of the parsing task in the task queue is in descending order, that is, The priority of the task queues is from high to low, and the resolution resources are allocated for different task queues, that is, the first task queues with higher priority are allocated with the resolution resources.
  • the embodiment generates a combined parsing task according to the original parsing task of each domain name, thereby reducing the total number of parsing tasks that need to be processed, and different combined parsing tasks have different priorities, so Prioritizes the resolution of resources, so that important resolution tasks can be prioritized, ensuring the progress of domain name resolution and ensuring that users can preferentially access website resources.
  • FIG. 3A is a flowchart of another embodiment of a processing method for a parsing task according to the present application.
  • the embodiment describes the processing procedure of the parsing task in detail:
  • Step 301 Create a cache queue for each domain name in advance.
  • the embodiment of the present application can be completed on a processing server, and the processing server communicates with the cloud server to uniformly process the domain name resolution task of the website corresponding to different VMs on the cloud server, where each domain name corresponds to multiple Analytic tasks.
  • These parsing tasks may include: AddZone's parsing task, AddZone is used to indicate the search area for domain name resolution; configuration A records the parsing task, A record is used to specify the IP address corresponding to the domain name; configuration CNAME record parsing task, CNAME record is used for Map multiple domain names to the same IP address; configure the MX record resolution task.
  • the MX record is used to indicate the routing of the mail server corresponding to the domain name. It can also include the DelZone (delete domain name domain) resolution task and configure the spam filtering resolution task.
  • the configuration of the configuration task is the same as that of the prior art, and is not described here.
  • a cache queue may be created for each domain name in advance, and each cache queue is used to cache the resolution task of the corresponding domain name.
  • FIG. 3B a schematic diagram of a process for processing a parsing task in the embodiment of the present application, corresponding to this step, assumes that n (n is a natural number greater than 1) sites need to generate domain name resolution, then for each website The domain name creates a cache queue, which is cache queue 1 to cache queue n.
  • Step 302 After receiving the original parsing task of each domain name, add the received original parsing task to the cache queue corresponding to each domain name.
  • the domain name resolution task can be added to the cache queue of the domain name according to the received chronological order. As shown in FIG. 3B, taking the website 1 as an example, the parsing tasks corresponding to the website 1 are sequentially added to the cache queue 1 according to the chronological order of transmission.
  • Step 303 When starting to process the parsing task, obtain the original parsing task of each domain name from the cache queue of each domain name.
  • the parsing task of each domain name may be extracted from the cache queue.
  • the parsing task cached in the cache queue is referred to as the original. Parsing the task. As shown in FIG. 3B, the original parsing task of the domain names of the website 1 to the website n is respectively obtained from the cache queue 1 to the cache queue n.
  • Step 304 Classify the original parsing task of each domain name obtained according to the preset task type.
  • the importance of the domain name resolution may be different according to different resolution tasks, and the original analysis task is classified into a preset task type.
  • the task type may include a transaction with a higher degree of importance.
  • Tasks for example, AddZone's parsing task, configuration A record parsing task, configuration CNAME record parsing task, configuration MX record parsing task, etc.
  • regular tasks with less important importance for example, DelZone parsing task, configuration The parsing task of spam filtering, configuring the parsing task of directory access, and so on.
  • the original parsing task of each domain name is classified according to the preset task type, as shown in FIG. 3B, and the cache queue 1 is taken as an example to parse the cache queue 1.
  • Tasks are divided into two categories according to the above task types, which are transactional tasks and regular tasks.
  • Step 305 Generate a combined parsing task according to the classification result, where the combined parsing task includes a first combined parsing task and a second combined parsing task, and the first combined parsing task has a higher priority than the second combined parsing task.
  • One or more original parsing tasks are included in the combined parsing task.
  • each combined parsing task includes one or more parsing tasks having the same task type.
  • Hypothetical generation The combined parsing task includes a first combined parsing task and a second combined parsing task, wherein the task type of the parsing task included in the first combined parsing task is a transactional task, and the task of the parsing task included in the second combined parsing task If the types are regular tasks, it can be known that the priority of the first combined parsing task is higher than the priority of the second combined parsing task. Referring to FIG. 3B, by performing this step, a combined resolution task having different priorities can be generated for each of the n domain names of the website 1 to the website n.
  • Step 306 Add each combined parsing task to the task queue corresponding to the priority of each combined parsing task.
  • a task queue may be set for each priority according to the classification of the task type or the priority of the combined resolution task.
  • the first priority is higher.
  • the combination of the high-priority task queues which may be referred to as a first task queue in the present embodiment, and a low-priority task queue for the second combination of the lower-priority resolution tasks, which may also be referred to as The second task queue; for the combined parsing task of each domain name of the generated website 1 to website n, these combined parsing tasks can be added to the task queue of the corresponding priority, that is, the first combination parsing task is added to the high priority The task queue, and the second combined resolution task is added to the low priority task queue.
  • Step 307 Allocate the resolution resource to the task queue according to the priority of the combined resolution tasks in the task queue from high to low.
  • the parsing resources are allocated for different task queues according to the priority of the task queues from high to low. As shown in FIG. 3B, the parsing resources are preferentially allocated to the high priority task queues.
  • the first task quantity of the combined parsing task included in the high-priority task queue can be obtained, and the first parsing production thread that is consistent with the first task quantity is invoked, so that The first parsing production thread performs distributed processing on the combined parsing task in the first task queue, that is, each first parsing production thread is responsible for parsing a combined parsing task, so as to fully ensure that the combined parsing task in the high-priority task queue is obtained.
  • Priority overall processing as shown in FIG.
  • the high priority task queue includes x combined parsing tasks
  • x parsing production threads are called for the high priority task queue
  • the low priority task queues due to the low priority
  • the priority of the task queue is lower, so the number of second parsing production threads called for the low priority task queue can be less than the number of second tasks of the combined parsing task included in the low priority task queue, or in order to satisfy the high
  • the combined resolution task in the priority task queue is distributed and processed.
  • the remaining parsing production thread is called for the combined parsing task in the low-priority task queue, as shown in FIG. 3B, assuming that the low-priority task queue includes m combinations.
  • the processing server can be a low priority task queue Calling the remaining parsing production threads except x parsing production threads, the number of remaining parsing production threads may be greater than m or less than m, correspondingly, as shown in Figure 3B, the low-priority task queue may be from the remaining parsing production threads. Call y to parse the production thread, the number of y does not exceed m.
  • the processing server may further determine whether the access frequency of the current resolution task exceeds a preset upper threshold of the access frequency, and when the upper threshold of the access frequency is exceeded, the current current It is difficult for the parsing resources to process all the combined parsing tasks. In this case, the parsing resources allocated for the high-priority task queues can be maintained, and the parsing resources allocated to the low-priority task queues can be reduced until the access frequency does not exceed the upper threshold of the access frequency.
  • the embodiment of the present application can ensure that the transaction task with higher priority can obtain the resolution resource preferentially, and since the transactional task is the key to generate the domain name resolution, the embodiment of the present application may not be affected.
  • the generation of domain name resolution ensures that users can prioritize access to website resources.
  • the embodiment generates a combined parsing task according to the original parsing task of each domain name, thereby reducing the total number of parsing tasks that need to be processed, and different combined parsing tasks have different priorities, so Priority allocation of the resolution resources, so that important resolution tasks can be prioritized, so as to ensure the progress of domain name resolution, ensuring that users can preferentially access the website resources; and, if the sent resolution task causes the server to reach the access limit, Different from the existing defensive task, the embodiment of the present application can ensure the parsing resource of the high priority task queue, reduce or no longer allocate the parsing resource for the low priority task queue, thereby ensuring that the important parsing task can be preferentially obtained. Processing does not affect the generation of domain name resolution.
  • the present application also provides an embodiment of a processing device and a server for parsing a task.
  • An embodiment of the processing device of the parsing task of the present application can be applied to a server.
  • the device embodiment may be implemented by software, or may be implemented by hardware or a combination of hardware and software.
  • the processor of the device in which it is located reads the corresponding computer program instructions in the non-volatile memory into the memory.
  • FIG. 4 a hardware structure diagram of a server where the processing device of the present invention is located, except for the processor, the memory, the network interface, and the non-volatile memory shown in FIG.
  • the generation server where the device is located in the embodiment may also include other hardware according to the actual function of the device, which is not shown in FIG. 4 .
  • FIG. 5 it is a block diagram of an embodiment of a processing device for a parsing task of the present application:
  • the apparatus includes an acquisition unit 510, a generation unit 520, and an allocation unit 530.
  • the obtaining unit 510 is configured to obtain an original parsing task of the domain name from a cache queue of each domain name.
  • the generating unit 520 is configured to generate, according to the original parsing task, a combined parsing task with different priorities for each domain name, where each combined parsing task includes one or more original parsing tasks;
  • the allocating unit 530 is configured to allocate the parsing resource to the combined parsing task in descending order of priority.
  • FIG. 6 a block diagram of another embodiment of a processing apparatus for a resolution task of the present application is as follows:
  • the apparatus includes a creation unit 610, an addition unit 620, an acquisition unit 630, a generation unit 640, and an allocation unit 650.
  • the creating unit 610 is configured to create a cache queue for each domain name in advance
  • the adding unit 620 is configured to: after receiving the original parsing task of the target domain name, add the received original parsing task to the cache queue of the target domain name;
  • the obtaining unit 630 is configured to obtain an original parsing task of the domain name from a cache queue of each domain name.
  • the generating unit 640 is configured to generate, according to the original parsing task, a combined parsing task with different priorities for each domain name, where each combined parsing task includes one or more original parsing tasks;
  • the allocating unit 650 is configured to allocate the parsing resource to the combined parsing task in descending order of priority.
  • the generating unit 640 can include (not shown in FIG. 6):
  • a task classification sub-unit configured to classify an original parsing task of each domain name obtained according to a preset task type
  • a task generation subunit configured to generate a combined parsing task according to the classification result, where the combined parsing task includes a first combined parsing task and a second combined parsing task, wherein the first combined parsing task has a higher priority than the first
  • the first combination parsing task includes a first original parsing task whose task type is a transactional task, and the second combined parsing task includes a first one other than the first original parsing task. Two original parsing tasks.
  • the first original parsing task may include: configuring a parsing task of the domain name domain AddZone, configuring a parsing task of the A record, and configuring a parsing task of the CNAME record;
  • the second original parsing task may include: deleting the parsing task of the domain name domain DelZone, configuring the parsing task of the spam filtering, and configuring the parsing task of the directory access.
  • the apparatus may also include (not shown in Figure 6):
  • the distribution unit 650 can include (not shown in FIG. 6):
  • a task adding subunit configured to add each combined parsing task to a task queue corresponding to a priority of each of the combined parsing tasks
  • the resource allocation sub-unit is configured to allocate an analysis resource to the task queue according to a priority of the combined resolution tasks in the task queue from high to low.
  • the task queue may include a first task queue and a second task queue, wherein a priority of the combined resolution task in the first task queue is higher than a priority of the combined resolution task in the second task queue;
  • the resource allocation sub-unit may be specifically configured to acquire a first task quantity of the combined parsing task included in the first task queue, and call the first task queue to be consistent with the first task quantity.
  • a first parsing production thread the first parsing production thread is configured to perform distributed processing on the combined parsing task in the first task queue, and invoke a second parsing production thread for the second task queue, The number of second parsing production threads is less than the number of second tasks of the combined parsing tasks included in the second task queue.
  • the apparatus may also include (not shown in Figure 6):
  • a determining unit configured to determine whether the current access frequency exceeds a preset upper threshold of the access frequency
  • an adjusting unit configured to: when the current access frequency exceeds the access frequency upper threshold, maintain the parsing resource allocated for the first task queue, and reduce the parsing resource allocated for the second task queue.
  • the device embodiment since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the objectives of the present application. Those of ordinary skill in the art can understand and implement without any creative effort.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请公开了解析任务的处理方法、装置及服务器，所述方法包括：从每个域名的缓存队列中获取所述域名的原始解析任务；根据所述原始解析任务为每个域名生成具有不同优先级的组合解析任务，每个组合解析任务中包括一个或多个原始解析任务；按照优先级从高到低的顺序为所述组合解析任务分配解析资源。本申请实施例由于根据每个域名的原始解析任务生成组合解析任务，因此减少了需要处理的解析任务的整体数量，且不同的组合解析任务具有不同的优先级，因此可以根据优先级分配解析资源，使重要的解析任务可以得到优先处理，从而确保域名解析的生成进度，保证用户可以优先访问网站资源。

Description

解析任务的处理方法、装置及服务器
本申请要求2015年04月29日递交的申请号为201510214167.2、发明名称为“解析任务的处理方法、装置及服务器”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及网络通信技术领域，尤其涉及解析任务的处理方法、装置及服务器。
背景技术
云服务是基于互联网的相关服务的增加、使用和交付模式，随着虚拟技术的发展，在云服务系统中，可以通过虚拟化技术在一台云服务器的硬件平台上虚拟出若干虚拟化平台，每个虚拟化平台可以对应一台VM(Virtual Machine，虚拟机)。现有技术中，云服务器上的每台VM都可以对应一个网站的主域名，进一步每个主域名下可能对应多个子域名。现有技术中，不同VM可以向生成域名解析的服务器发送对应网站的解析任务，服务器通过执行这些解析任务，为不同域名生成域名解析，以便将这些域名指向对应网站的IP(Internet Protocol，互联网协议)地址，从而使用户可以访问到这些主域名或者子域名对应的网站资源。
但是，当多个VM同时发送解析任务时，服务器为这些解析任务按照发送时间的先后顺序，平均分配处理资源，导致某些重要的解析任务难以得到优先处理，从而影响域名解析的生成进度，导致用户无法优先访问网站资源。
发明内容
本申请提供解析任务的处理方法、装置及服务器，以解决服务器为解析任务平均分配处理资源，从而影响网站的域名解析生成进度的问题。
根据本申请实施例的第一方面，提供一种解析任务的处理方法，所述方法包括：
从每个域名的缓存队列中获取所述域名的原始解析任务；
根据所述原始解析任务为每个域名生成具有不同优先级的组合解析任务，每个组合解析任务中包括一个或多个原始解析任务；
按照优先级从高到低的顺序为所述组合解析任务分配解析资源。
根据本申请实施例的第二方面，提供一种解析任务的处理装置，所述装置包括：
获取单元，用于从每个域名的缓存队列中获取所述域名的原始解析任务；
生成单元，用于根据所述原始解析任务为每个域名生成具有不同优先级的组合解析任务，每个组合解析任务中包括一个或多个原始解析任务；
分配单元，用于按照优先级从高到低的顺序为所述组合解析任务分配解析资源。
根据本申请实施例的第三方面，提供一种服务器，包括：
处理器；用于存储所述处理器可执行指令的存储器；
其中，所述处理器被配置为：
从每个域名的缓存队列中获取所述域名的原始解析任务；
根据所述原始解析任务为每个域名生成具有不同优先级的组合解析任务，每个组合解析任务中包括一个或多个原始解析任务；
按照优先级从高到低的顺序为所述组合解析任务分配解析资源。
本申请实施例中通过缓存队列缓存每个域名的原始解析任务，在对解析任务进行处理时，从每个域名的缓存队列中获取域名的原始解析任务，然后为每个域名生成具有不同优先级的组合解析任务，并按照优先级从高到低的顺序为组合解析任务分配解析资源。本申请实施例由于根据每个域名的原始解析任务生成组合解析任务，因此减少了需要处理的解析任务的整体数量，且不同的组合解析任务具有不同的优先级，因此可以根据优先级分配解析资源，使重要的解析任务可以得到优先处理，从而确保域名解析的生成进度，保证用户可以优先访问网站资源。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本申请。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本申请的实施例，并与说明书一起用于解释本申请的原理。
图1为本申请实施例一种应用场景示意图；
图2为本申请解析任务的处理方法的一个实施例流程图；
图3A为本申请解析任务的处理方法的另一个实施例流程图
图3B为图3A中对解析任务进行处理的过程示意图；
图4为本申请解析任务的处理装置所在服务器的一种硬件结构图；
图5为本申请解析任务的处理装置的一个实施例框图；
图6为本申请解析任务的处理装置的另一个实施例框图。
具体实施方式
在本申请使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本申请。在本申请和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本申请可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本申请范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
参见图1，为应用本申请实施例的一种应用场景示意图：
图1中示出了一种云服务系统，本申请实施例可以基于该云服务系统进行解析任务的处理，进而可以基于处理结果生成域名解析，该云服务器系统中包括云服务器、解析任务的处理服务器(后续本申请实施例中简称为处理服务器)、以及生成域名解析的服务器(后续本申请实施例中简称为生成服务器)。其中，在云服务器上设置了n(n为大于1的自然数)个VM，每个VM可以提供给一个网站，用于存储该网站的网站资源，每个网站通过所分配的IP地址进行标识。用户可以通过输入网站注册的域名对网站资源进行访问，在访问过程中DNS服务器可以将域名转换为网站的IP地址，从而完成对上述网站的访问。由此可知，要实现用户通过域名访问到不同的网站资源，需要生成服务器预先执行不同域名的解析任务，从而为不同域名生成域名解析，以便后续遵循生成的域名解析结果完成从域名到IP地址的转换。
现有技术中，通常由生成服务器为这些解析任务按照发送时间的先后顺序，平均分配处理资源，导致某些重要的解析任务难以得到优先处理，从而影响域名解析的生成进度。如图1中所示，本申请实施例可以在生成服务器前端设置处理服务器，由处理服务器先通过缓存队列缓存每个域名对应的VM发送的原始解析任务，然后对缓存队列中的解析任务统一进行处理，从每个域名的缓存队列中获取域名的原始解析任务，然后为每个域名生成具有不同优先级的组合解析任务，并按照优先级从高到低的顺序为组合解析任务分配解析资源，后续可以由生成服务器按照所分配的 解析资源对组合解析任务进行解析，从而生成不同域名的域名解析；需要说明的是，图1中示出的处理服务器独立于生成服务器设置，在实际应用中，处理服务器和生成服务器的功能也可以集成在一台服务器上，对此本申请实施例不进行限制，本申请实施例可以应用在任意集成了处理解析任务功能的服务器上。
参见图2，为本申请解析任务的处理方法的一个实施例流程图，该实施例从服务器侧进行描述：
步骤201：从每个域名的缓存队列中获取域名的原始解析任务。
在为不同域名生成域名解析的过程中，每个域名都会对应多个解析任务，通过执行这些解析任务，从而生成域名解析。这些解析任务可以包括：AddZone(配置域名域)的解析任务；配置A(Address，地址)记录的解析任务；配置CNAME(别名)记录的解析任务；配置MX(Mailbox，邮箱)记录的解析任务；还可以包括DelZone(删除域名域)的解析任务，配置垃圾邮件过滤的解析任务，配置目录访问的解析任务等；配置上述解析任务的具体内容和配置方式与现有技术一致，在此不再赘述。
本申请实施例中可以预先为每个域名创建一个缓存队列，每个缓存队列用于缓存所对应的域名的解析任务，因此当接收到某个域名的解析任务后，可以按照接收的时间先后顺序，将该域名的解析任务添加到该域名的缓存队列中。当要对解析任务进行处理时，可以从上述缓存队列中提取出每个域名的解析任务，为了区别于后续生成的组合解析任务，本申请实施例中可以将缓存队列中缓存的解析任务称为原始解析任务。
步骤202：根据原始解析任务为每个域名生成具有不同优先级的组合解析任务，每个组合解析任务中包括一个或多个原始解析任务。
本申请实施例可以预先根据不同解析任务对生成域名解析的重要性程度不同，对原始解析任务进行分类得到预设的任务类型，本申请实施例中任务类型可以包括重要性程度较高的事务性任务，例如，AddZone的解析任务、配置A记录的解析任务、配置CNAME记录的解析任务、配置MX记录的解析任务等，以及重要性程度不高的常规性任务，例如，DelZone的解析任务、配置垃圾邮件过滤的解析任务、配置目录访问的解析任务等。
在获取到每个域名的原始解析任务后，按照上述预设的任务类型对每个域名的原始解析任务进行分类，并根据分类结果生成具有不同优先级的组合解析任务，每个组合解析任务中包含具有相同任务类型的一个或多个解析任务。例如，生成的组 合解析任务包括第一组合解析任务和第二组合解析任务，其中，第一组合解析任务中包括的解析任务的任务类型均为事务性任务，第二组合解析任务中包括的解析任务的任务类型均为常规性任务，则可知第一组合解析任务的优先级高于第二组合解析任务的优先级。
步骤203：按照优先级从高到低的顺序为组合解析任务分配解析资源。
本申请实施例可以预先根据任务类型的分类，或者说按照组合解析任务的优先级，为每一种优先级设置一个任务队列，如前步骤202中的示例，可以为优先级较高的第一组合解析任务设置高优先级任务队列，本实施例中也可称为第一任务队列，为优先级相对较低的第二组合解析任务设置低优先级任务队列，本实施例中也可称为第二任务队列。
在为每个域名生成具有不同优先级的组合解析任务后，可以将每个组合解析任务添加到对应的任务队列中，然后按照任务队列中组合解析任务的优先级从高到低的顺序，即任务队列的优先级从高到低的顺序，为不同的任务队列分配解析资源，即优先为优先级较高的第一任务队列分配解析资源。
由上述实施例可见，该实施例由于根据每个域名的原始解析任务生成组合解析任务，因此减少了需要处理的解析任务的整体数量，且不同的组合解析任务具有不同的优先级，因此可以根据优先级分配解析资源，使重要的解析任务可以得到优先处理，从而确保域名解析的生成进度，保证用户可以优先访问网站资源。
参见图3A，为本申请解析任务的处理方法的另一个实施例流程图，该实施例对解析任务的处理过程进行详细描述：
步骤301：预先为每个域名创建缓存队列。
结合图1可知，本申请实施例可以在处理服务器上完成，处理服务器与云服务器进行通信，统一为云服务器上不同VM所对应网站的注册域名的解析任务进行处理，其中每个域名都会对应多个解析任务。这些解析任务可以包括：AddZone的解析任务，AddZone用于指示域名解析的查找区域；配置A记录的解析任务，A记录用于指定域名对应的IP地址；配置CNAME记录的解析任务，CNAME记录用于将多个域名映射到同一IP地址；配置MX记录的解析任务，MX记录用于指示域名对应的邮件服务器的路由；还可以包括DelZone(删除域名域)的解析任务，配置垃圾邮件过滤的解析任务，配置目录访问的解析任务等；配置上述解析任务的具体内容和配置方式与现有技术一致，在此不再赘述。
本申请实施例中可以预先为每个域名创建一个缓存队列，每个缓存队列用于缓存所对应的域名的解析任务。如图3B所示，为本申请实施例中对解析任务进行处理的过程示意图，对应于本步骤，假设有n(n为大于1的自然数)个网站需要生成域名解析，则为每个网站的域名创建一个缓存队列，分别为缓存队列1至缓存队列n。
步骤302：当接收到每个域名的原始解析任务后，将接收到的原始解析任务添加到每个域名对应的缓存队列中。
当接收到某个域名的解析任务后，可以按照接收的时间先后顺序，将该域名的解析任务添加到该域名的缓存队列中。如图3B所示，以网站1为例，对应网站1的解析任务按照发送的时间先后顺序，依次添加到缓存队列1中。
步骤303：当开始处理解析任务时，从每个域名的缓存队列中获取每个域名的原始解析任务。
当要对解析任务进行处理时，可以从上述缓存队列中提取出每个域名的解析任务，为了区别于后续生成的组合解析任务，本申请实施例中将缓存队列中缓存的解析任务称为原始解析任务。如图3B所示，从缓存队列1至缓存队列n中分别获取网站1至网站n的域名的原始解析任务。
步骤304：按照预设的任务类型对获取的每个域名的原始解析任务进行分类。
本申请实施例可以预先根据不同解析任务对生成域名解析的重要性程度不同，对原始解析任务进行分类得到预设的任务类型，本申请实施例中任务类型可以包括重要性程度较高的事务性任务，例如，AddZone的解析任务、配置A记录的解析任务、配置CNAME记录的解析任务，配置MX记录的解析任务等，以及重要性程度不高的常规性任务，例如，DelZone的解析任务，配置垃圾邮件过滤的解析任务，配置目录访问的解析任务等。
在获取到每个域名的原始解析任务后，按照上述预设的任务类型对每个域名的原始解析任务进行分类，如图3B所示，以缓存队列1为例，对缓存队列1中的解析任务按照上述任务类型分为两类，分别为事务性任务和常规性任务。
步骤305：根据分类结果生成组合解析任务，该组合解析任务包括第一组合解析任务和第二组合解析任务，第一组合解析任务的优先级高于所述第二组合解析任务的优先级，每个组合解析任务中包括一个或多个原始解析任务。
本步骤中，根据前述步骤304中的分类结果生成具有不同优先级的组合解析任务，每个组合解析任务中包含具有相同任务类型的一个或多个解析任务。假设生成 的组合解析任务包括第一组合解析任务和第二组合解析任务，其中，第一组合解析任务中包括的解析任务的任务类型均为事务性任务，第二组合解析任务中包括的解析任务的任务类型均为常规性任务，则可知第一组合解析任务的优先级高于第二组合解析任务的优先级。结合图3B，通过执行本步骤，可以为网站1至网站n的n个域名中的每个域名分别生成具有不同优先级的组合解析任务。
步骤306：将每个组合解析任务添加到与每个组合解析任务的优先级对应的任务队列。
本申请实施例可以预先根据任务类型的分类，或者说按照组合解析任务的优先级，为每一种优先级设置一个任务队列，结合前述步骤305和图3B，可以为优先级较高的第一组合解析任务设置高优先级任务队列，本实施例中也可称为第一任务队列，为优先级相对较低的第二组合解析任务设置低优先级任务队列，本实施例中也可称为第二任务队列；对于已生成的网站1至网站n的每个域名的组合解析任务，可以将这些组合解析任务添加到对应优先级的任务队列中，即将第一组合解析任务添加到高优先级任务队列，以及将第二组合解析任务添加到低优先级任务队列。
步骤307：按照任务队列中组合解析任务的优先级从高到低的顺序，为任务队列分配解析资源。
本步骤中按照任务队列的优先级从高到低的顺序，为不同的任务队列分配解析资源，结合图3B可知，优先为高优先级任务队列分配解析资源。
在一个分配解析资源的例子中，对于高优先级任务队列，可以获取高优先级任务队列中包含的组合解析任务的第一任务数量，调用与第一任务数量一致的第一解析生产线程，以便通过第一解析生产线程对第一任务队列中的组合解析任务进行分布式处理，即每个第一解析生产线程负责解析一个组合解析任务，以便充分保证高优先级任务队列中的组合解析任务得到优先全面的处理，如图3B所示，假设高优先级任务队列中包括x个组合解析任务，则为高优先级任务队列调用x个解析生产线程；对于低优先级任务队列，由于低优先级任务队列的优先级较低，因此为低优先级任务队列调用的第二解析生产线程的数量可以小于低优先级任务队列中包含的组合解析任务的第二任务数量，或者说在为了满足对高优先级任务队列中的组合解析任务进行分布式处理，从而优先为高优先级任务队列调用完解析生产线程后，再为低优先级任务队列中的组合解析任务调用剩余的解析生产线程，如图3B所示，假设低优先级任务队列中包括m个组合解析任务，处理服务器可以为低优先级任务队列 调用除x个解析生产线程外的剩余解析生产线程，剩余解析生产线程的数量可能大于m，也可能小于m，相应的，如图3B中，可以从剩余解析生产线程中为低优先级任务队列调用y个解析生产线程，y的数量不超过m。
在另一个可选的例子中，在为不同任务队列分配解析资源之后，处理服务器还可以判断当前解析任务的访问频率是否超过预设的访问频率上限阈值，当超过访问频率上限阈值时，说明当前的解析资源难以满足对所有组合解析任务进行处理，此时可以保持为高优先级任务队列分配的解析资源，同时减少为低优先级任务队列分配的解析资源，直至访问频率不超过访问频率上限阈值；也就是，在任何情况下，采用本申请实施例可以保证优先级较高的事务性任务可以优先获得解析资源，由于事务性任务是生成域名解析的关键，因此采用本申请实施例可以不影响域名解析的生成，保证用户可以优先访问到网站资源。
由上述实施例可见，该实施例由于根据每个域名的原始解析任务生成组合解析任务，因此减少了需要处理的解析任务的整体数量，且不同的组合解析任务具有不同的优先级，因此可以根据优先级分配解析资源，使重要的解析任务可以得到优先处理，从而确保域名解析的生成进度，保证用户可以优先访问网站资源；并且，如果所发送的解析任务导致服务器的访问频率达到访问上限时，与现有屏蔽所有解析任务不同，本申请实施例可以保证高优先级的任务队列的解析资源，减少或者不再为低优先级的任务队列分配解析资源，从而可以确保重要的解析任务可以优先得到处理，不影响域名解析的生成。
与前述提供的解析任务的处理方法的实施例相对应，本申请还提供了解析任务的处理装置及服务器的实施例。
本申请解析任务的处理装置的实施例可以应用在服务器上。装置实施例可以通过软件实现，也可以通过硬件或者软硬件结合的方式实现。以软件实现为例，作为一个逻辑意义上的装置，是通过其所在设备的处理器将非易失性存储器中对应的计算机程序指令读取到内存中运行形成的。从硬件层面而言，如图4所示，为本申请解析任务的处理装置所在服务器的一种硬件结构图，除了图4所示的处理器、内存、网络接口、以及非易失性存储器之外，实施例中装置所在的生成服务器通常根据器实际功能，还可以包括其他硬件，图4中不再一一示出。
参见图5，为本申请解析任务的处理装置的一个实施例框图：
该装置包括：获取单元510、生成单元520和分配单元530。
其中，获取单元510，用于从每个域名的缓存队列中获取所述域名的原始解析任务；
生成单元520，用于根据所述原始解析任务为每个域名生成具有不同优先级的组合解析任务，每个组合解析任务中包括一个或多个原始解析任务；
分配单元530，用于按照优先级从高到低的顺序为所述组合解析任务分配解析资源。
参见图6，为本申请解析任务的处理装置的另一个实施例框图：
该装置包括：创建单元610、添加单元620、获取单元630、生成单元640和分配单元650。
其中，创建单元610，用于预先为每个域名创建缓存队列；
添加单元620，用于当接收到目标域名的原始解析任务后，将接收到的原始解析任务添加到所述目标域名的缓存队列中；
获取单元630，用于从每个域名的缓存队列中获取所述域名的原始解析任务；
生成单元640，用于根据所述原始解析任务为每个域名生成具有不同优先级的组合解析任务，每个组合解析任务中包括一个或多个原始解析任务；
分配单元650，用于按照优先级从高到低的顺序为所述组合解析任务分配解析资源。
在一个可选的实现方式中：
所述生成单元640可以包括(图6中未示出)：
任务分类子单元，用于按照预设的任务类型对获取的每个域名的原始解析任务进行分类；
任务生成子单元，用于根据分类结果生成组合解析任务，所述组合解析任务包括第一组合解析任务和第二组合解析任务，其中，所述第一组合解析任务的优先级高于所述第二组合解析任务的优先级，所述第一组合解析任务中包括任务类型为事务性任务的第一原始解析任务，所述第二组合解析任务中包括除所述第一原始解析任务外的第二原始解析任务。
其中，所述第一原始解析任务可以包括：配置域名域AddZone的解析任务，配置A记录的解析任务，配置CNAME记录的解析任务；
所述第二原始解析任务可以包括：删除域名域DelZone的解析任务，配置垃圾邮件过滤的解析任务，配置目录访问的解析任务。
在另一个可选的实现方式中：
所述装置还可以包括(图6中未示出)：
设置单元，用于分别为每个类型的优先级设置任务队列；
相应的，所述分配单元650可以包括(图6中未示出)：
任务添加子单元，用于将每个组合解析任务添加到与所述每个组合解析任务的优先级对应的任务队列；
资源分配子单元，用于按照所述任务队列中组合解析任务的优先级从高到低的顺序，为所述任务队列分配解析资源。
在另一个可选的实现方式中：
所述任务队列可以包括第一任务队列和第二任务队列，其中，所述第一任务队列中组合解析任务的优先级高于所述第二任务队列中组合解析任务的优先级；
相应的，所述资源分配子单元，可以具体用于获取所述第一任务队列中包含的组合解析任务的第一任务数量，为所述第一任务队列调用与所述第一任务数量一致的第一解析生产线程，所述第一解析生产线程用于对所述第一任务队列中的组合解析任务进行分布式处理，以及，为所述第二任务队列调用第二解析生产线程，所述第二解析生产线程的数量小于所述第二任务队列中包含的组合解析任务的第二任务数量。
在另一个可选的实现方式中：
所述装置还可以包括(图6中未示出)：
判断单元，用于判断当前访问频率是否超过预设的访问频率上限阈值；
调整单元，用于当所述当前访问频率超过所述访问频率上限阈值时，保持为所述第一任务队列分配的解析资源，以及减少为所述第二任务队列分配的解析资源。
上述装置中各个单元的功能和作用的实现过程具体详见上述方法中对应步骤的实现过程，在此不再赘述。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本申请方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
由上述实施例可见，由于根据每个域名的原始解析任务生成组合解析任务，因此减少了需要处理的解析任务的整体数量，且不同的组合解析任务具有不同的优先级，因此可以根据优先级分配解析资源，使重要的解析任务可以得到优先处理，从而确保域名解析的生成进度，保证用户可以优先访问网站资源。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本申请的其它实施方案。本申请旨在涵盖本申请的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本申请的一般性原理并包括本申请未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本申请的真正范围和精神由下面的权利要求指出。
应当理解的是，本申请并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本申请的范围仅由所附的权利要求来限制。

Claims (15)

  1. 一种解析任务的处理方法，其特征在于，所述方法包括：
    从每个域名的缓存队列中获取所述域名的原始解析任务；
    根据所述原始解析任务为每个域名生成具有不同优先级的组合解析任务，每个组合解析任务中包括一个或多个原始解析任务；
    按照优先级从高到低的顺序为所述组合解析任务分配解析资源。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    预先为每个域名创建缓存队列；
    当接收到目标域名的原始解析任务后，将接收到的原始解析任务添加到所述目标域名的缓存队列中。
  3. 根据权利要求1所述的方法，其特征在于，所述根据所述原始解析任务为每个域名生成具有不同优先级的组合解析任务，包括：
    按照预设的任务类型对获取的每个域名的原始解析任务进行分类；
    根据分类结果生成组合解析任务，所述组合解析任务包括第一组合解析任务和第二组合解析任务，其中，所述第一组合解析任务的优先级高于所述第二组合解析任务的优先级，所述第一组合解析任务中包括任务类型为事务性任务的第一原始解析任务，所述第二组合解析任务中包括除所述第一原始解析任务外的第二原始解析任务。
  4. 根据权利要求3所述的方法，其特征在于，
    所述第一原始解析任务包括：配置域名域AddZone的解析任务，配置A记录的解析任务，配置CNAME记录的解析任务；
    所述第二原始解析任务包括：删除域名域DelZone的解析任务，配置垃圾邮件过滤的解析任务，配置目录访问的解析任务。
  5. 根据权利要求1所述的方法，其特征在于，所述按照优先级从高到低的顺序为所述组合解析任务分配解析资源之前，还包括：
    分别为每个类型的优先级设置任务队列；
    所述按照优先级从高到低的顺序为所述组合解析任务分配解析资源，包括：
    将每个组合解析任务添加到与所述每个组合解析任务的优先级对应的任务队列；
    按照所述任务队列中组合解析任务的优先级从高到低的顺序，为所述任务队列 分配解析资源。
  6. 根据权利要求5所述的方法，其特征在于，所述任务队列包括第一任务队列和第二任务队列，其中，所述第一任务队列中组合解析任务的优先级高于所述第二任务队列中组合解析任务的优先级；
    所述按照所述任务队列中组合解析任务的优先级从高到低的顺序，为所述任务队列分配解析资源，包括：
    获取所述第一任务队列中包含的组合解析任务的第一任务数量；
    为所述第一任务队列调用与所述第一任务数量一致的第一解析生产线程，所述第一解析生产线程用于对所述第一任务队列中的组合解析任务进行分布式处理，以及，为所述第二任务队列调用第二解析生产线程，所述第二解析生产线程的数量小于所述第二任务队列中包含的组合解析任务的第二任务数量。
  7. 根据权利要求5或6所述的方法，其特征在于，所述按照所述任务队列中组合解析任务的优先级从高到低的顺序，为所述任务队列分配解析资源之后，还包括：
    判断当前访问频率是否超过预设的访问频率上限阈值；
    当所述当前访问频率超过所述访问频率上限阈值时，保持为所述第一任务队列分配的解析资源，以及减少为所述第二任务队列分配的解析资源。
  8. 一种解析任务的处理装置，其特征在于，所述装置包括：
    获取单元，用于从每个域名的缓存队列中获取所述域名的原始解析任务；
    生成单元，用于根据所述原始解析任务为每个域名生成具有不同优先级的组合解析任务，每个组合解析任务中包括一个或多个原始解析任务；
    分配单元，用于按照优先级从高到低的顺序为所述组合解析任务分配解析资源。
  9. 根据权利要求8所述的装置，其特征在于，所述装置还包括：
    创建单元，用于预先为每个域名创建缓存队列；
    添加单元，用于当接收到目标域名的原始解析任务后，将接收到的原始解析任务添加到所述目标域名的缓存队列中。
  10. 根据权利要求8所述的装置，其特征在于，所述生成单元包括：
    任务分类子单元，用于按照预设的任务类型对获取的每个域名的原始解析任务进行分类；
    任务生成子单元，用于根据分类结果生成组合解析任务，所述组合解析任务包括第一组合解析任务和第二组合解析任务，其中，所述第一组合解析任务的优先级高于所述第二组合解析任务的优先级，所述第一组合解析任务中包括任务类型为事务性任务的第一原始解析任务，所述第二组合解析任务中包括除所述第一原始解析任务外的第二原始解析任务。
  11. 根据权利要求10所述的装置，其特征在于，
    所述第一原始解析任务包括：配置域名域AddZone的解析任务，配置A记录的解析任务，配置CNAME记录的解析任务；
    所述第二原始解析任务包括：删除域名域DelZone的解析任务，配置垃圾邮件过滤的解析任务，配置目录访问的解析任务。
  12. 根据权利要求8所述的装置，其特征在于，所述装置还包括：
    设置单元，用于分别为每个类型的优先级设置任务队列；
    所述分配单元，包括：
    任务添加子单元，用于将每个组合解析任务添加到与所述每个组合解析任务的优先级对应的任务队列；
    资源分配子单元，用于按照所述任务队列中组合解析任务的优先级从高到低的顺序，为所述任务队列分配解析资源。
  13. 根据权利要求12所述的装置，其特征在于，所述任务队列包括第一任务队列和第二任务队列，其中，所述第一任务队列中组合解析任务的优先级高于所述第二任务队列中组合解析任务的优先级；
    所述资源分配子单元，具体用于获取所述第一任务队列中包含的组合解析任务的第一任务数量，为所述第一任务队列调用与所述第一任务数量一致的第一解析生产线程，所述第一解析生产线程用于对所述第一任务队列中的组合解析任务进行分布式处理，以及，为所述第二任务队列调用第二解析生产线程，所述第二解析生产线程的数量小于所述第二任务队列中包含的组合解析任务的第二任务数量。
  14. 根据权利要求12或13所述的装置，其特征在于，所述装置还包括：
    判断单元，用于判断当前访问频率是否超过预设的访问频率上限阈值；
    调整单元，用于当所述当前访问频率超过所述访问频率上限阈值时，保持为所述第一任务队列分配的解析资源，以及减少为所述第二任务队列分配的解析资源。
  15. 一种服务器，其特征在于，包括：
    处理器；用于存储所述处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    从每个域名的缓存队列中获取所述域名的原始解析任务；
    根据所述原始解析任务为每个域名生成具有不同优先级的组合解析任务，每个组合解析任务中包括一个或多个原始解析任务；
    按照优先级从高到低的顺序为所述组合解析任务分配解析资源。
PCT/CN2016/079867 2015-04-29 2016-04-21 解析任务的处理方法、装置及服务器 WO2016173452A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510214167.2A CN106210156B (zh) 2015-04-29 2015-04-29 解析任务的处理方法、装置及服务器
CN201510214167.2 2015-04-29

Publications (1)

Publication Number Publication Date
WO2016173452A1 true WO2016173452A1 (zh) 2016-11-03

Family

ID=57198146

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/079867 WO2016173452A1 (zh) 2015-04-29 2016-04-21 解析任务的处理方法、装置及服务器

Country Status (2)

Country Link
CN (1) CN106210156B (zh)
WO (1) WO2016173452A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111950832A (zh) * 2019-05-17 2020-11-17 拉扎斯网络科技（上海）有限公司 调度方法、装置、服务器、服务器集群和存储介质
CN113904994A (zh) * 2021-09-30 2022-01-07 天翼数字生活科技有限公司 一种家庭网关大数据统一上报平台的方法

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107239342A (zh) * 2017-05-31 2017-10-10 郑州云海信息技术有限公司 一种存储集群任务管理方法及装置
CN110647389B (zh) * 2019-09-16 2023-04-07 北京镁伽机器人科技有限公司 用于自动饮品机的任务处理方法、自动饮品机及存储介质
CN112256418B (zh) * 2020-10-26 2023-10-24 清华大学深圳国际研究生院 一种大数据任务调度方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009111799A2 (en) * 2008-03-07 2009-09-11 3Tera, Inc. Globally distributed utility computing cloud
CN102984275A (zh) * 2012-12-14 2013-03-20 北京奇虎科技有限公司 进行网页下载的方法及浏览器
CN103024044A (zh) * 2012-12-14 2013-04-03 北京奇虎科技有限公司 网页下载方法及装置
CN103701886A (zh) * 2013-12-19 2014-04-02 中国信息安全测评中心 一种云计算环境下的服务及资源分层调度方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070118667A1 (en) * 2005-11-21 2007-05-24 Limelight Networks, Inc. Domain name resolution based dynamic resource assignment
CN101841577B (zh) * 2010-06-07 2015-01-28 中兴通讯股份有限公司 一种实现域名解析代理功能的方法和装置
CN102572014B (zh) * 2012-03-07 2015-12-02 华为终端有限公司 消息处理方法、装置和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009111799A2 (en) * 2008-03-07 2009-09-11 3Tera, Inc. Globally distributed utility computing cloud
CN102984275A (zh) * 2012-12-14 2013-03-20 北京奇虎科技有限公司 进行网页下载的方法及浏览器
CN103024044A (zh) * 2012-12-14 2013-04-03 北京奇虎科技有限公司 网页下载方法及装置
CN103701886A (zh) * 2013-12-19 2014-04-02 中国信息安全测评中心 一种云计算环境下的服务及资源分层调度方法

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111950832A (zh) * 2019-05-17 2020-11-17 拉扎斯网络科技（上海）有限公司 调度方法、装置、服务器、服务器集群和存储介质
CN113904994A (zh) * 2021-09-30 2022-01-07 天翼数字生活科技有限公司 一种家庭网关大数据统一上报平台的方法
CN113904994B (zh) * 2021-09-30 2024-03-19 天翼数字生活科技有限公司 一种家庭网关大数据统一上报平台的方法

Also Published As

Publication number Publication date
CN106210156A (zh) 2016-12-07
CN106210156B (zh) 2019-07-23

Similar Documents

Publication Publication Date Title
US10528390B2 (en) Idempotent task execution in on-demand network code execution systems
WO2016173452A1 (zh) 解析任务的处理方法、装置及服务器
US10084711B2 (en) High-performance quality-of-service packet scheduling for multiple packet processing engines
US10303492B1 (en) Managing custom runtimes in an on-demand code execution system
CN114930295B (zh) 利用预留容量而不抑制缩放的无服务器调用分配方法及系统
US11119813B1 (en) Mapreduce implementation using an on-demand network code execution system
US10360067B1 (en) Dynamic function calls in an on-demand network code execution system
US20190391841A1 (en) Execution of auxiliary functions in an on-demand network code execution system
US9569275B2 (en) Allocation and reservation of virtualization-based resources
US9998531B2 (en) Computer-based, balanced provisioning and optimization of data transfer resources for products and services
KR20210019533A (ko) 온-디맨드 네트워크 코드 실행 시스템에서의 운영 체제 커스터마이제이션
WO2020052605A1 (zh) 一种网络切片的选择方法及装置
WO2018059222A1 (zh) 一种文件切片上传方法、装置及云存储系统
US10397132B2 (en) System and method for granting virtualized network function life cycle management
WO2017157156A1 (zh) 一种用户请求的处理方法和装置
WO2019052225A1 (zh) 开放平台控制方法、系统、计算机设备和存储介质
WO2014194869A1 (zh) 一种请求处理方法、装置及系统
US11768706B2 (en) Method, storage medium storing instructions, and apparatus for implementing hardware resource allocation according to user-requested resource quantity
KR20140098919A (ko) 실시간 가상 데스크탑 서비스를 위한 가상머신 제공 방법 및 서비스 게이트웨이
CN108933829A (zh) 一种负载均衡方法及装置
EP4068725A1 (en) Load balancing method and related device
US11316916B2 (en) Packet processing method, related device, and computer storage medium
US20180167326A1 (en) Method and system for limiting data traffic
US10530887B1 (en) Pre-caching data for use upon execution of program code
CN102868550A (zh) 全网流量调度器及使用该调度器查询域名解析记录的方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16785883

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16785883

Country of ref document: EP

Kind code of ref document: A1