WO2013189063A1

WO2013189063A1 - Key-value database data merging method and device

Info

Publication number: WO2013189063A1
Application number: PCT/CN2012/077314
Authority: WO
Inventors: 周帅锋; 智伟; 赵智峰
Original assignee: 华为技术有限公司
Priority date: 2012-06-21
Filing date: 2012-06-21
Publication date: 2013-12-27
Also published as: CN103649948A

Abstract

The present invention provides a key-value database data merging method and device, to control a data merging task, so as to prevent a heavier burden on the system incurred by concurrence of a large number of data merging tasks. The method comprises: obtaining a load level of a current system and an urgency level of a to-be-merged task; according to the load level of the current system and the urgency level of the to-be-merged task, matching a task-merging execution policy to determine whether the to-be-merged task is permitted to be executed; if it is determined that the to-be-merged task is permitted to be executed, sending the to-be-merged task to a task-merging execution module to execute task merging. The method provided by the present invention can control the data merging task according to the occupation of the system resources, so as to make the data merging task be automatically delayed when the load of the system is high, thereby reducing the impact of execution of task merging on service accessing, and reducing the burden on the system.

Description

Data merging method and device for key value database

The present invention relates to the field of data processing, and in particular, to a data merging method and apparatus for a key value database. Background technique

The Key-Value database is a database management system based on key-value data storage. Key-value data storage technology stores data in a key-value pair data model that provides persistence mechanisms and data synchronization. In some key-value databases, data is stored sequentially in terms of keys (Key) and written to disk in chasing mode. For example, BigTable and HBase are the modes. In this mode, files written to the file system are not modified once they are written. Thus, data written at different times will form multiple storage files in the file system. In order to facilitate access, maintain orderly data and timely clean up expired data, and improve the speed of data access, the key-value database will start the merge operation and merge multiple files after the storage file reaches a certain size or for a period of time. At the same time, some data cleaning work is done.

In some large-capacity distributed key-value databases, sub-tables are the basic unit for performing data merge tasks, and sub-tables are usually managed by multiple sub-table servers. For ease of management, the data table is divided into a number of sub-tables according to the scope of the key. Each sub-table stores and manages all data whose key values fall within its range.

The data merging method in a key value database provided by the prior art is: using a sub-table as a basic unit of scheduling execution, and when the number of files in the sub-table reaches or exceeds a predefined upper limit, the merging task is triggered, and the sub-task is triggered. The table is placed in the data merge execution queue, from which the data merge thread obtains the child table, and the merge is performed, as shown in FIG.

Since a series of processes for performing data merge tasks usually consume a large amount of system resources, the unrestricted execution of all the merge tasks obviously increases the system burden and affects the performance of the data access service. Summary of the invention

Embodiments of the present invention provide a data merging method and apparatus for a key value database, and control the data merging task to avoid a large amount of data merging tasks while burdening the system.

An embodiment of the present invention provides a data merging method for a key value database, where the method includes: acquiring The load level of the current system and the urgency level of the task to be merged;

According to the current system load level and the urgency level of the task to be merged, the higher the load level of the current system is, the higher the urgency level is allowed to perform the task to be merged, when the current system load level is saturated. , does not allow any tasks to be merged;

If it is determined that the task to be merged is allowed to be executed, the task to be merged is sent to the merge task execution module to perform task merge.

An embodiment of the present invention provides a data merging device for a key value database, where the device includes: an acquiring module, configured to acquire a load level of a current system and an urgency level of a task to be merged;

a determining module, configured to merge the task execution policy according to the load level of the current system and the urgency of the task to be merged, etc., the higher the load level of the current system, the higher the urgency level is allowed to perform the task to be merged, in the current system When the load level is saturated, the task to be merged is not allowed to be executed; and the processing module is configured to send the to-be-consolidated task to the merge task execution module to perform task combination if the determining module determines to perform the to-be-combined task.

According to the embodiment of the present invention, the merging is allowed according to the load level of the current system and the urgency level of the task to be merged according to the load level of the current system and the merging task execution strategy, that is, the urgency is allowed according to the system resource load level. High task to be merged. Therefore, the method provided by the embodiment of the present invention can control the data merging task according to the system resource occupation, so that the data merging task is automatically delayed when the system load is high, thereby reducing the impact of the execution task merging on the access service and reducing the system burden.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the prior art or the embodiments will be briefly described below. Obviously, the drawings in the following description are only the present invention. For some embodiments, other drawings may be obtained as those of ordinary skill in the art without any inventive labor.

1 is a schematic diagram of a data merging method in a key value database provided by the prior art;

2 is a schematic flowchart of a data merging method of a key value database according to an embodiment of the present invention; 3 is a schematic structural diagram of a data merging device of a key value database according to an embodiment of the present invention; FIG. 4 is a schematic structural diagram of a data merging device of a key value database according to another embodiment of the present invention; FIG. 6 is a schematic structural diagram of a data merging device of a key value database according to another embodiment of the present invention; FIG. 6b is a data merging device for a key value database according to another embodiment of the present invention; FIG. 7 is a schematic structural diagram of a data merging device of a key value database according to another embodiment of the present invention; FIG. 7b is a schematic structural diagram of a data merging device of a key value database according to another embodiment of the present invention; FIG. 7 is a schematic structural diagram of a data merging device of a key value database according to another embodiment of the present invention; FIG. 8 is a structural diagram of a data merging device according to another embodiment of the present invention; A schematic diagram of a data merging device of a database; FIG. 8b is a key value provided by another embodiment of the present invention; FIG. 8 is a schematic structural diagram of a data merging device of a key value database according to another embodiment of the present invention; FIG. 8 is a schematic structural diagram of a data merging device of a key value database according to another embodiment of the present invention; FIG. 9 is a schematic structural diagram of a data merging device of a key value database according to another embodiment of the present invention; FIG. 9b is a schematic structural diagram of a data merging device of a key value database according to another embodiment of the present invention; FIG. 9 is a schematic structural diagram of a data merging device of a key value database according to another embodiment of the present invention; FIG. 10 is a schematic diagram of a data merging database provided by another embodiment of the present invention; Schematic diagram of the data merging device;

FIG. 10b is a schematic structural diagram of a data merging device of a key value database according to another embodiment of the present invention; FIG.

FIG. 10c is a schematic structural diagram of a data merging device of a key value database according to another embodiment of the present invention; FIG.

Figure 10d is a schematic diagram showing the structure of a data merging device of a key value database according to another embodiment of the present invention.

detailed description

Embodiments of the present invention provide a data merging method and apparatus for a key value database to schedule a data merging task according to system resource occupancy. The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without departing from the inventive scope are the scope of the present invention.

Referring to FIG. 2, it is a flowchart of a data merging method of a key value database according to an embodiment of the present invention. The executor may be a sub-table server in a key value database, and mainly includes step S201, step S202, and step S203:

S201. Obtain a load level of the current system and an urgency level of the task to be merged.

Whether the merge task of the key value database is related to the load of the current system, for example, when the system is busy and/or the system load is relatively high, the unconstrained execution of the key database database merge task will increase the system burden and affect the data access service. Performance. In addition to this, whether or not the merge task of the key-value database is executed is also related to the urgency of the task to be merged. Therefore, in the embodiment of the present invention, the load level of the current system and the urgency level of the task to be merged may be first acquired, where the load level of the current system includes but is not limited to low load, medium load, high load, and saturation. The urgency levels of the tasks to be combined include, but are not limited to, non-emergency, normal, and emergency.

As an embodiment of acquiring the load level of the current system, the usage of the resources of the current system may be weighted and summed according to the weight, and the load of the current system is given a corresponding level according to the value obtained by the weighted summation. In the embodiment of the present invention, a central processing unit (CPU), a memory, a network, and a disk belong to the resources included in the current system, and after obtaining the usage of the resources, the weights of the resources may be weighted. And, the weighted sum is equivalent to the score of the current system load. For example, if the current system's load score is represented by L, then: where ^ and ^ respectively represent the CPU score weight, the memory score weight, and the network score weight. And disk scoring weights, and u _cpu u _m t ^ and respectively indicate CPU usage, memory usage, network usage, and disk usage. If the load of the system can be divided into low load, medium load, high load and saturation according to the level from low to high, the current system load can be assigned to the corresponding level according to the system load score L from low to high. , for example, if the load on the system When the score L is 100, the load of the system can be scored in the range of 0 ~ 25, 25 - 50, 50 ~ 75 and 75 ~ 100, and the current system load level is sequentially assigned to the low load, medium load, High load and saturation.

As an embodiment of obtaining the urgency level of the task to be merged, the factors affecting the urgency of the task to be merged may be linearly weighted and summed according to the weight, and the value to be merged according to the value obtained by the linear weighted summation The urgency of the task corresponds to the level. In the embodiment of the present invention, factors affecting the urgency of the task to be merged include, but are not limited to, the file size in the sub-table, the number of files in the sub-table, and the overdue time of the oldest data in the sub-table. Since there are quantitative differences in different influencing factors, the urgency score of the tasks to be combined can be calculated by linear weighted summation. In this way, for each factor affecting the urgency of the task to be combined, the percentage is calculated based on the maximum value of each factor and weighted and summed, as shown below, if the urgency score of the task to be combined is used

ScoreiX^X^...^,)^^, Bay ¹ J:

Score{X _l , X ₂ ,...,X _k ) = _j w _k {X _k I MAX _Xk )^lQQ% where (2) where ^ represents the first factor affecting the urgency of the task to be merged, ^ Indicates the weight of the first factor affecting the urgency of the task to be merged, and MX indicates the maximum value that the first factor affecting the urgency of the task to be merged can reach or set. If the urgency level of the task to be merged can be divided into non-emergency, normal and emergency, etc., it can be scored according to the urgency of the task to be merged ^^(^,...,^) The urgency of the task to be merged is assigned to the corresponding level in turn, for example, if the urgency score of the task to be combined is ΟΓ, Χ, ..., ^) is 100, the urgency degree of the task to be combined can be scored. ₁ 3⁄4^( ₁ , ₂ ,..., ^) In the interval of 0 ~ 30, 30 ~ 60 and 60 ~ 100, the urgency level of the task to be merged is sequentially assigned to non-emergency, normal and emergency.

According to formula (2), the urgency of the combined task is scored, considering the general state of each factor in the common scenario. However, in some scenarios, the scores of other factors affecting the urgency of the task to be merged may still be If the factors affecting the urgency of the task to be merged are close to or reach the maximum value, the overall impact of the urgency of the execution combination of the tasks to be merged begins to increase non-linearly. Due to the urgency of the formula (2) to treat the combined task Is a linear weighted summation. When the factor affecting the urgency of the task to be merged is close to or reaches the maximum value, if the urgency of the combined task is still scored according to formula (2), the scored result cannot be faithfully reflected. The urgency of the merger to be merged is obviously unreasonable.

The embodiment of the invention provides a scoring method for a single item affecting the extreme value amplification weighted summation, so as to achieve a non-linear enlargement of the urgency degree of the combined task when the urgency affecting the task to be combined individually reaches or approaches the maximum value. That is, if the influence value of one of the factors affecting the urgency of the task to be merged has reached or is close to the maximum value of the factor, the factors affecting the urgency of the task to be merged are weighted according to the weight. The nonlinear weighted summation assigns a corresponding level to the urgency of the task to be merged according to the value obtained by the nonlinear weighted summation. Specifically, the nonlinear weighted summation of each factor affecting the urgency of the task to be merged according to the weight includes: enlarging the weight of the factor affecting the urgency of the task to be merged to a new weight for the urgency of the combined task, a factor that affects the urgency of the task to be merged, a nonlinear weighted summation according to the new weight, and a value pair obtained by the nonlinear weighted summation The urgency level of the task to be merged is the urgency score of the task to be merged ^/^:^,:^,...,:^;! Expressed as:

Score{X _l , X ₂ ,...,X _k ) = _j f{A _k )w _k {X _k l ΜΑΧ _Χι ) * 100% where (3) where ^ denotes the first emergency affecting the task to be merged The degree factor, ^ represents the weight of the first factor affecting the urgency of the task to be merged, MX represents the first task to be merged, and the weight amplification function, which can be expressed as:

f(A _k )=MAX _Xt /(MAX _Xt -X _k +AX _k ) Equation (4) In the above expression, MAX _Xt represents the maximum value of the influence factor of the first urgency affecting the task to be combined, ΔΧ _λ is a minimum value of the first factor affecting the urgency of the task to be merged, and is used to adjust equation (4) such that the denominator of equation (4) is not zero.

It should be noted that the load level of the current system obtained by the above-mentioned score calculated according to the formula (1), and the urgency level of the task to be combined obtained by the score calculated according to the formula (2) or the formula (3) are only For example, it is not limited to the formula (1), (2) or (3) above. Style.

S202, according to the load level of the current system and the urgency level of the task to be merged, the matching is performed in the embodiment of the present invention, and the combined task execution strategy is pre-defined according to the load level of the system and the urgency level of the task to be merged. The principle of determining a set of tasks for performing task consolidation includes: The higher the load level of the current system, the higher the urgency level is allowed to perform the task to be merged, that is, the task to be merged is allowed to be higher. The merge operation is performed. When the load level of the current system is saturated, no tasks to be merged are allowed to be executed, that is, the merge of any tasks to be merged is not allowed. The execution strategy of the merged task can also be interpreted as: When the urgency level of the task to be merged is determined, the higher the load level of the current system, the lower the possibility that the task to be merged is allowed to perform the merge, and vice versa, the current system The lower the load level, the higher the probability that the task to be merged is allowed to perform the merge; or the higher the urgency level of the task to be merged when the load level of the current system is determined (ie, the degree to which the task to be merged needs to perform the merge) The more urgent, the higher the probability that the task to be merged is allowed to perform the merge, and the lower the level of urgency of the task to be merged (that is, the more relaxed the degree of the merge to be merged), the task to be merged is not allowed. The higher the probability of performing a merge; when the load level of the current system is the lowest, for example, when the load level of the current system is low load, the merged task of any urgency level can be merged; when the load level of the current system is the highest For example, when the load level of the current system is saturated, no permission is allowed. The urgency level of the tasks to be merged is merged; when the urgency level of the task to be merged is the highest, for example, when the urgency level of the task to be merged is urgent, unless the load level of the current system is the highest, for example, the load of the current system The level is saturated, otherwise, the merging is allowed for the task to be merged with the urgency level being urgent.

As mentioned earlier, the current system's load levels include, but are not limited to, low load, medium load, high load, and saturation, and the urgency levels of the tasks to be combined include, but are not limited to, non-emergency, normal, and emergency. For example, the merge task execution policy provided by the embodiment of the present invention may be as shown in Table 1 below:

Table 1

In the above Table 1, the "load level" is the cartridge of the "current system load level" in the foregoing embodiment, including "low load", "medium load", "high load" and "saturated", "urgency level". " is the nickname of the urgency level of the task to be merged in the foregoing embodiment, including "non-emergency", "normal", and "emergency". The item at the intersection of "load level" and "urgency level" indicates whether to perform the combination of the tasks to be merged. For example, when the "load level" is "low load" and the "urgency level" is "non-emergency", Perform a merge of the tasks to be merged. The general principle of the combined task execution strategy reflected in Table 1 above is that for a task to be merged with a urgency level of non-emergency, when the load level of the system is above the medium load or the medium load, the merged service is not allowed to be merged. , the task to be merged is returned to the queue and waits; for the task to be merged with the urgency level is normal, when the load level of the system is high load or high load, the merged service is not allowed to be merged, but The to-be-consolidated task returns to the queue to wait; for the to-be-consolidated task whose urgency level is urgent, as long as the load level of the system is not saturated, that is, when the current system load level is low load, medium load or high load, the to-be-committed is allowed. Business execution merges. And according to the load level of the current system and the urgency level of the task to be merged, matching the merge task execution policy to determine whether to allow the task to be merged includes: if the urgency level matching the task to be merged is urgent, When the load level of the current system is low load, medium load or high load, it is determined that the task to be merged is allowed to be executed, that is, it is determined that the merge is allowed to be performed on the task to be merged; if the task is to be merged to the task to be merged If the level of the current system is non-emergency, when the load level of the current system is above the medium load or the medium load, it is determined that the task to be merged is not allowed to be executed, that is, it is determined that the merged task is not allowed to be merged; The urgency level assigned to the task to be merged is normal. When the load level of the current system is high load or high load, it is determined that the task to be merged is not allowed to be executed, that is, the waiting for the waiting is not allowed. The merge task performs the merge.

For the merge task execution policy of the example in Table 1, if the load level of the current system acquired in step S201 is "low load", the merge task execution policy of the example of Table 1 is matched, regardless of the urgency of the task to be merged acquired in step S201. Whether the level is "non-emergency", "normal" or "emergency", it is determined that the combination of the tasks to be merged can be performed; if the load level of the current system acquired in step S201 is "medium load", it matches the example of Table 1. The merging task execution policy, when the urgency level of the task to be merged obtained in step S201 is "normal" or "emergency", it is also determined that the merging of the tasks to be merged can be performed; if the load level of the current system acquired in step S201 is "High load", then matching to the merge task execution policy of the example in Table 1, only when the urgency level of the task to be merged acquired in step S201 is "emergency", it is determined that the merge of the task to be merged can be performed; When the load level of the current system acquired by S201 is "saturated", it matches the merge task execution of the example in Table 1. It should be noted that, regardless of whether the urgency level of the task to be merged obtained in step S201 is "non-emergency", "normal" or "emergency", it is determined that the merging of the tasks to be merged cannot be performed; if the load level of the current system acquired in step S201 The "high load" is matched to the merge task execution policy of the example in Table 1. When the urgency level of the task to be merged acquired in step S201 is "non-emergency" or "normal", it is also determined that the to-be-committed may not be executed. If the load level of the current system acquired in step S201 is "medium load", the matching task execution policy of the example in Table 1 is matched, and when the urgency level of the task to be merged acquired in step S201 is "non-emergency" It is also determined that the merging of the tasks to be merged cannot be performed.

S203. If it is determined that the to-be-committed task is allowed to be executed, send the to-be-consolidated task to the merged task execution module to perform task consolidation.

In the embodiment of the present invention, the merge task execution module is a functional unit that performs task merge, and one or more such functional units may exist in the child table server. When the merged task execution module is idle, the task can be performed, and the task is actively requested from the scheduler, or the active report is idle, and the scheduler is assigned to the task. Therefore, according to step S201 and step S202, if it is determined that the task to be merged can be executed, that is, it is determined that the merge can be performed on the task to be merged, The merged task is sent to the merge task execution module, and the merge task execution module performs task merge. If it is determined that the to-be-combined task cannot be executed, that is, it is determined that the merged task cannot be merged, the to-be-combined task is returned to the waiting queue, and waits for an appropriate timing to be taken out from the waiting queue to perform task combining.

In the embodiment of the present invention, it is possible that the sub-table server is not suitable for performing task consolidation for a relatively long period of time, for example, if the load of the current system is in a long period of time. Will be at the level of "saturation", then according to the combined task execution strategy as exemplified in Table 1, no matter whether the urgency level of the task to be merged is "non-emergency", "normal" or "emergency", the to-be-committed can not be executed. The merging of tasks. If, during the period of the above example, the tasks in the waiting queue cannot be performed according to the merge task execution policy before the queue is fetched frequently from the waiting queue, it is obviously a waste of resources.

Therefore, in order to prevent the sub-table server from performing the task merging for a relatively long period of time, the task to be merged is still frequently taken out from the waiting queue to perform the task merging. In the embodiment of the present invention, in step S201 and step S202 After the merge task execution policy according to the example in Table 1 cannot perform the task merge and returns to the waiting queue in the waiting queue, the task to be merged may be frozen, so that the task to be merged is within the set freeze time. It is in a state in which the waiting queue cannot be taken out. The size of the freeze time setting may be set by the user according to the load level of the current system and/or the expected duration of the urgency level of the task to be merged, which is not particularly limited in the present invention.

In the embodiment of the present invention, after the task to be merged is frozen, a timer may be started to time the set freeze time so that after the set freeze time is over, In step S201 and step S202, the merge task execution policy according to the table 1 cannot perform the task merge and the task to be merged in the wait queue is changed to the state in which the wait queue can be taken out, thereby reevaluating whether the merge task can perform the merge.

Since the freeze time is set based on the length of the expected duration of the current system's load level, it is also impossible to exclude that the freeze time setting exceeds the expected duration of the current system load level. For example, if the load level of the current system or/and the urgency level of the task to be merged changes, thereby performing the merge task execution strategy as exemplified in Table 1, the previous example according to Table 1 And the task execution strategy can not perform the merged to-be-merge task, and the merge can be re-executed. At this time, if the mechanical merge is waited for the set freeze time to end, the task merge is performed, which is also a waste of resources for the system.

Therefore, in the embodiment of the present invention, a change occurs in the load level of the current system, that is, if the load level of the current system is decreased from "saturated" to "high load", "medium load" or "low load", Then, in step S201 and step S202, the merge task execution policy according to the table 1 may not perform task merge, and the task to be merged in the wait queue is changed to a state in which the wait queue can be taken out; or, if the load of the current system is If the level is lowered from "high load" to "medium load" or "low load", the merge task execution strategy according to Table 1 in step S201 and step S202 can not perform task merge and return to the task to be merged in the wait queue. Change to a state in which the waiting queue can be taken out; or, if the load level of the current system is decreased from "medium load" to "low load", the merge task execution strategy according to Table 1 in steps S201 and S202 can be executed. The task to be merged and the task to be merged in the waiting queue cannot be changed to the state in which the waiting queue can be taken out.

In another embodiment of the present invention, the change of the urgency level of the task to be merged, that is, if the merged task execution policy according to the table 1 in step S201 and step S202 cannot perform the task merging and returns to the waiting queue If the urgency level of the merging task is raised from "non-emergency" to "normal" or "emergency", the task to be merged is changed to a state in which the waiting queue can be taken out; or, if in step S201 and step S202, according to Table 1 The example merge task execution policy cannot perform task merge and the urgency level of the task to be merged in the wait queue is raised from "normal" to "emergency", and the task to be merged is changed to a state in which the wait queue can be taken out.

As another embodiment of the present invention for ending the freeze time in advance, when all the tasks to be merged in the waiting queue are frozen and the merge task execution module is in an idle state, if the merge task execution strategy according to Table 1 is performed in steps S201 and S202 If the urgency level of the task to be merged in the waiting queue cannot be performed and the urgency level of the task to be merged is higher than that of the other tasks to be merged, the merged task execution policy according to the example in Table 1 in step S201 and step S202 cannot be executed. The tasks to be merged and returned to the waiting queue are changed to a state in which the waiting queue can be taken out.

According to the data merging method of the key value database provided by the embodiment of the present invention, whether the merging of the task to be merged is based on the load level of the current system and the urgency level of the task to be merged, Match the merge task execution strategy to determine. Therefore, the method provided by the embodiment of the present invention can be based on the prior art without considering the load or the state of the system (for example, the system is relatively busy and/or the system load is relatively high) and the merge of the tasks to be merged is still performed without limitation. The system resource occupation situation is used to schedule the data merge task, so that the data merge task is automatically delayed when the system load is high, and is automatically executed when the system is under low load, thereby reducing the impact of the execution task merge on the access service, and allowing the task to be merged. The merger is performed automatically and in a timely manner at the right time.

Referring to FIG. 3, it is a structural diagram of a data merging device of a key value database according to an embodiment of the present invention. For the convenience of description, only parts related to the embodiment of the present invention are shown. The data combining apparatus of the key value database illustrated in Fig. 3 includes an obtaining module 301, a determining module 302, and a processing module 303, wherein:

The obtaining module 301 is configured to acquire a load level of the current system and an urgency level of the task to be merged.

Whether the merge task of the key value database is related to the load of the current system, for example, when the system is busy and/or the system load is relatively high, the unrestricted execution of the key database merge task will increase the system burden and affect the data access service. Performance. In addition to this, whether or not the merge task of the key-value database is executed is also related to the urgency of the task to be merged. Therefore, in this embodiment, the level of the current system and the level of urgency of the task to be merged may be first acquired by the level obtaining module 301, where the load level of the current system includes but is not limited to low load, medium load, high load, and There are several types of saturation, such as non-emergency, normal and emergency.

The determining module 302 is configured to use, according to the load level of the current system and the emergency process of the task to be merged, in the embodiment, the combined task execution policy is pre-defined according to the load level of the system and the urgency level of the task to be merged. The principle of determining whether to perform task consolidation includes the following examples: the higher the load level of the current system, the higher the urgency task to be merged, that is, the higher the urgency level is to be performed. Merging, when the current system's load level is saturated, it is not allowed to perform any tasks to be merged, that is, it is not allowed to perform the merge of any tasks to be merged. In the embodiment of the present invention, the execution policy of the merged task may also be interpreted as: when the urgency level of the task to be merged is determined, the higher the load level of the current system, the task to be merged is allowed to execute. The lower the probability of the sum, the lower the load level of the current system, the higher the probability that the task to be merged is allowed to perform the merge; or the urgency level of the task to be merged when the load level of the current system is determined The higher the degree (ie, the more urgent the task to be merged needs to perform the merge), the higher the probability that the task to be merged is allowed to perform the merge, and vice versa, the lower the level of urgency of the task to be merged (ie, the task to be merged needs to perform the merge) The more relaxed the degree, the higher the probability that the task to be merged is not allowed to perform the merge; when the load level of the current system is the lowest, for example, when the load level of the current system is low load, the urgency level can be merged. Task execution merge; When the current system's load level is the highest, for example, when the current system's load level is saturated, it is not allowed to perform merging for any urgency level to be merged task; when the urgency level of the task to be merged is the highest, for example , the urgency level of the task to be merged is urgent, unless the current system The load level is the highest, for example, the load level of the current system is saturated, otherwise, the merge is allowed to be performed on the task to be merged whose emergency level is urgent.

As mentioned earlier, the current system's load levels include, but are not limited to, low load, medium load, high load, and saturation, and the urgency levels of the tasks to be combined include, but are not limited to, non-emergency, normal, and emergency. For example, the merge task execution policy provided in this embodiment may be as shown in Table 1 above.

The processing module 303 is configured to: if the determining module 302 determines to perform the to-be-committed task, send the to-be-combined task to the merged task execution module to perform task combining.

In this embodiment, the merge task execution module is a functional unit that performs task merge, and one or more such functional units may exist in the child table server. When the merged task execution module is idle, the task can be performed, and the task is actively requested from the scheduler, or the active report is idle, and the scheduler is assigned to the task. Therefore, once the determining module 302 determines that the to-be-combined task can be performed, that is, it is determined that the merge can be performed on the to-be-combined task, the processing module 303 sends the to-be-combined task to the merged task execution module, which is executed by the merged task execution module. Task consolidation. If the determining module 302 determines that the to-be-combined task cannot be performed, that is, it is determined that the merged task cannot be merged, the processing module 303 may further return the to-be-combined task to the waiting queue, wait for a suitable timing, and wait for another time. Take out the queue to perform task consolidation.

It should be noted that, in the implementation manner of the data merging device of the above key value database, the division of each functional module is only an example, and the actual application may be configured according to requirements, for example, corresponding hardware requirements. Or the convenience of the implementation of the software, and the above-mentioned function allocation is completed by different functional modules, that is, the internal structure of the data combining device of the key value database is divided into different functional modules to complete all or part of the functions described above. Moreover, in practical applications, the corresponding functional modules in this embodiment may be implemented by corresponding hardware, or may be executed by corresponding hardware. For example, the foregoing level obtaining module may have the foregoing acquisition current The hardware of the load level of the system and the urgency level of the task to be merged, such as a level acquirer, may also be a general processor or other hardware device capable of executing a corresponding computer program to perform the aforementioned functions; An emergency program, such as a determiner, that performs the foregoing load level according to the current system and a task to be merged, such as a determiner, may also be a general processor or other hardware device capable of executing a corresponding computer program to perform the aforementioned functions (each provided in this specification) The above described principles can be applied to the embodiments).

The acquisition module 301 of the example of FIG. 3 may include a first acquisition unit 401, such as the data integration device of the key value database provided by another embodiment of the present invention as shown in FIG. The first obtaining unit 401 is configured to perform a weighted summation of the usage of the resources included in the current system according to the weight, and assign a corresponding level to the load of the current system according to the value obtained by the weighted summation, where the system is Resource usage includes any combination of CPU usage, memory usage, network usage, and disk usage, including current load, medium load, high load, and saturation.

In the data merging device of the key value database illustrated in FIG. 4, a central processing unit (CPU), a memory, a network, a disk, and the like all belong to resources included in the current system. The first obtaining unit 401 may perform weighted summation according to the weight of each resource after acquiring the usage of the resources, and the weighted summation value is equivalent to scoring the current system load, for example, if the current system load score When L is used, the expression of L is as shown in the above formula (1). If the load of the system can be divided into low load, medium load, high load and saturation according to the level from low to high, the first obtaining unit 401 can load the current system according to the load score L of the system from low to high. The corresponding level is assigned in turn. For example, if the load score of the system is 100, the first acquisition unit is when the load score of the system is in the range of 0 to 25, 25 to 50, 50 to 75, and 75 to 100. 401 correspondingly sequentially assigns the load level of the current system to low load, medium load, high load, and saturation. It should be noted that, in the data merging device of the key value database illustrated in FIG. 4, the acquiring module 301 may further include other functional modules or units for acquiring the urgency level of the task to be merged, and the obtaining manner thereof is in the drawing. 4 The device of the example is not limited.

The level obtaining module 301 of the example of FIG. 3 may also include a second obtaining unit 501, such as the data combining device of the key value database provided by another embodiment of the present invention as shown in FIG. The second obtaining unit 501 is configured to linearly weight the factors affecting the urgency of the task to be merged according to the weight, and assign a corresponding level to the urgency of the task to be merged according to the value obtained by the linear weighted summation. The factors affecting the urgency of the task to be merged include any combination of the file size in the sub-table, the number of files in the sub-table, and the expiration time of the oldest data in the sub-table, where the task to be merged Urgency levels include general, urgent, and mandatory.

In the data merging device of the key value database illustrated in FIG. 5, factors affecting the urgency of the task to be merged include, but are not limited to, the file size in the sub-table, the number of files in the sub-table, and the overdue time of the oldest data in the sub-table. and many more. Since there are quantitative differences in different influencing factors, the second obtaining unit 501 can calculate the urgency score of the task to be merged by means of linear weighted summation. In this way, for each factor affecting the urgency of the task to be combined, the percentage is calculated according to the maximum value of each factor and weighted and summed. If the urgency score Srar of the task to be combined is expressed by the above formula (2) The urgency level of the task to be merged may be divided into normal, urgent, and mandatory, and the second obtaining unit 501 may score according to the urgency of the task to be merged.

, from low to high, assign the urgency of the task to be merged to the corresponding level, for example, if the urgency score of the task to be merged

A perfect score of 100, the urgency of the task to be combined is scored. ( ₁ , ₂ , ..., ^) In the interval of 0 to 30, 30 to 60, and 60 to 100, the second obtaining unit 501 sequentially assigns the urgency level of the task to be combined to ordinary, urgent, and necessary .

It should be noted that, in the data merging device of the key value database illustrated in FIG. 5, the obtaining module 301 may further include other functional modules or units for acquiring the load level of the current system, and the obtaining manner thereof is illustrated in FIG. 5. The device is not limited.

According to formula (2), the urgency of the combined task is scored, considering the general state of each factor in the common scenario, however, in some scenarios, despite other emergency affecting the task to be merged The score of the degree factor may still be relatively low, but when the factor affecting the urgency of the task to be merged is close to or reaches the maximum value, the overall impact of the urgency of the execution combination of the task to be merged begins to be nonlinear. The ground is enlarged. Since the urgency of the merging task is evaluated by the formula (2), the linear weighted summation is used. When the factor affecting the urgency of the task to be merged has approached or reached the maximum value, the second obtaining unit 501 still follows the formula (2). The urgency of the combined task is scored, and the scored result cannot accurately reflect the urgency of the task to be merged, which is obviously unreasonable. It is necessary to non-linearly amplify the urgency of the task to be combined when the urgency of the individual task to be merged reaches or approaches the maximum value, that is, if the factors affecting the urgency of the task to be combined currently The acquisition module 301 exemplified in FIG. 3 may also include a third acquisition unit 601, as shown in FIG. 6a, which is a key value database provided by another embodiment of the present invention. Data merge device.

a third obtaining unit 601, configured to perform non-linear weighted summation of each factor affecting the urgency of the task to be merged according to a weight, and assign a urgency to the task to be merged according to the value obtained by the weighted summation The level of the urgency affecting the task to be merged includes any combination of the file size in the child table, the number of files in the child table, and the time of the oldest data in the child table, the task to be merged Urgency levels include non-emergency, general and emergency.

It should be noted that, in the data merging device of the key value database illustrated in FIG. 6a, the obtaining module 301 may further include other functional modules or units for acquiring the load level of the current system, and the obtaining manner thereof is illustrated in FIG. 6a. The device is not limited.

The third obtaining unit 601 illustrated in Fig. 6a may further include an amplifying unit 6011 and a summing unit

6012, as shown in FIG. 6b, a data merging device for a key value database according to another embodiment of the present invention, wherein:

The amplifying unit 6011 is configured to expand the weight of the factor affecting the urgency of the task to be merged to the weight amplifying function.

a summation unit 6012, configured to weight the factors affecting the urgency of the task to be merged according to the new weight according to the new weight as a factor affecting the urgency of the task to be merged, according to the new weight a value corresponding to the urgency of the task to be merged, that is, a summation unit 6012 assigns a urgency to the task to be merged according to formula (3) The level of responsibility, including general, urgent, and must, and so on.

The determining module 302 illustrated in FIG. 4 to FIG. 6b may include a first determining unit 701, a second determining unit 702, and a third determining unit 703, as shown in FIG. 7a to FIG. 7d, which are provided by another embodiment of the present invention. A data merging device for a key value database, where:

The first determining unit 701 is configured to: if the urgency level of the task to be merged is urgent, when the load level of the current system is low load, medium load, or high load, determine to allow execution of the to-be-committed The merging of tasks.

That is, if the urgency level of the to-be-combined task is "emergency", the acquisition module 301 matches the merge task execution policy of the example in Table 1. The load level of the current system acquired by the acquisition module 301 is "low load". The first determining unit 701 determines that the task to be merged is allowed to be executed, that is, determines that the merging is allowed to be performed on the task to be merged, or the load level of the current system acquired by the obtaining module 301 is “medium load”, and the first determining unit 701 determines The task to be merged is allowed to be executed, that is, it is determined that the merging is allowed to be performed on the to-be-combined task, or the load level of the current system acquired by the obtaining module 301 is “high load”, and the first determining unit 701 determines that the to-be-committed is allowed to be executed. The task, ie determining to allow the merging of the tasks to be merged.

The second determining unit 702 is configured to: if the urgency level of the task to be merged is non-emergency, when the load level of the current system is greater than the medium load or the medium load, determine that the to-be-committed is not allowed to be performed. The task, that is, determines that the merging of the tasks to be merged is not allowed.

That is, if the urgency level of the to-be-combined task is "non-emergency", the acquisition module 301 matches the merge task execution policy of the example in Table 1. The load level of the current system acquired by the acquisition module 301 is "medium load". The second determining unit 702 determines that the to-be-combined task is not allowed to be executed, that is, it is determined that the merging is not allowed to be performed on the to-be-joined task, or the load level of the current system acquired by the obtaining module 301 is “high load”, and the second determination is performed. The unit 702 determines that the task to be merged is not allowed to be executed, that is, it is determined that the merge is not allowed to be performed on the task to be merged, or the load level of the current system acquired by the obtaining module 301 is "saturated", and the second determining unit 702 determines that the task is not allowed. The tasks to be merged are executed, that is, it is determined that the merge is not allowed to be performed on the tasks to be merged.

The third determining unit 703 is configured to: if the urgency level of the task to be merged is normal, when the load level of the current system is higher than a high load or a high load, determine that the performing is not allowed To be merged.

That is, if the urgency level of the task to be merged acquired by the obtaining module 301 is "normal", the merge task execution policy of the example of Table 1 is matched, and the load level of the current system acquired by the obtaining module 301 is " When the high load is "saturated" or "saturated", the third determining unit 703 determines that the to-be-combined task is not allowed to be executed, that is, it is determined that the merging of the to-be-combined task is not allowed.

The data merging apparatus of the key value database illustrated in Figures 4 through 6b may include a task freeze module 801, such as the data merging apparatus of the key value database provided by another embodiment of the present invention, as shown in Figures 8a to 8d. The task freeze module 801 is configured to freeze the to-be-consolidated task, so that the to-be-combined task is in a state in which the waiting queue cannot be taken out within a set freeze time.

At the level of the current system load, it is possible that the sub-table server should not perform task consolidation for a relatively long period of time, for example, if the current system load is in a long period of time

For the "saturated" level, according to the combined task execution strategy exemplified in Table 1, whether the urgency level of the task to be merged is "normal", "emergency" or "must", the merge of the tasks to be merged cannot be performed. . If, during the period of the above example, it is still frequently taken out of the waiting queue before the task is merged, the task cannot be performed and the task in the waiting queue is returned, which is obviously a waste of resources. Therefore, in order to avoid that the sub-table server is not suitable for performing task merging for a relatively long period of time and still frequently removes the task to be merged from the waiting queue to perform task merging, the data of the key value database exemplified in FIGS. 8a to 8d. In the merging device, after the merge task execution policy according to the example in Table 1 fails to perform task merging and returns to the waiting queue in the waiting queue to return to the waiting queue, the task freezing module 801 may freeze the to-be-consolidated task to make the waiting The merge task is in a state in which the wait queue cannot be fetched within the set freeze time. The size of the freeze time setting may be set by the user according to the load level of the current system and/or the expected duration of the urgency level of the task to be merged, which is not specifically limited by the present invention.

The data merging device of the key value database illustrated in Figures 8a to 8d may include a first defrosting module 901, such as the data merging device of the key value database provided by another embodiment of the present invention as shown in Figures 9a to 9d. The first defrosting module 901 is configured to start a timer to time the set freezing time, so that after the set freezing time ends, the to-be-combined task is changed to a state in which the waiting queue can be taken out. . Since the freeze time is set based on the length of the expected duration of the current system's load level, it is also impossible to exclude that the freeze time setting exceeds the expected duration of the current system load level. For example, if the load level of the current system or/and the urgency level of the task to be merged changes, so as according to the merge task execution policy exemplified in Table 1, the merged task execution policy according to the previous example according to Table 1 cannot be performed. The merge task can re-execute the merge. At this point, if the job merge is performed mechanically waiting for the set freeze time to end, it is also a waste of resources for the system. Therefore, the data merging device of the key value database illustrated in FIGS. 8a to 8d may also include a second defrosting module 1001, a third defrosting module 1002, or a fourth defrosting module 1003, as shown in FIG. 10a to FIG. 10d. A data merging device for a key value database provided by another embodiment, wherein:

The second defrosting module 1001 is configured to: if the load level of the current system decreases from saturation to high load, medium load or low load, from high load to medium load or low load, or from medium load to low load, The task to be merged is changed to a state in which the waiting queue can be taken out.

The third defrosting module 1002 is configured to change the to-be-combined task to be able to take out the waiting queue if the urgency level of the task to be merged rises from non-emergency to normal or urgent, or from ordinary to urgent. status.

The fourth defrosting module 1003 is configured to: when all the tasks to be merged are frozen in the waiting queue and the merging task execution module is in an idle state, if the urgency level of the task to be merged is higher than the urgency level of other tasks to be merged And changing the to-be-combined task to a state in which the waiting queue can be taken out.

It should be noted that the information interaction, the execution process, and the like between the modules/units of the foregoing device are the same as the embodiment of the method of the present invention. Reference is made to the description in the method embodiment of the present invention, and details are not described herein again.

One of ordinary skill in the art will appreciate that all or a portion of the various methods of the above-described embodiments can be performed by a program to instruct the associated hardware, such as one or more or all of the following various methods:

Obtain the current system's load level and the urgency level of the task to be merged;

According to the load level of the current system and the urgency level of the task to be merged, matching and merging The higher the load level of the current system, the higher the urgency level is allowed to perform the tasks to be merged. When the load level of the current system is saturated, no tasks to be merged are allowed.

If it is determined that the to-be-combined task is executed, the to-be-combined task is sent to the merged task execution module to perform a merge task.

A person skilled in the art may understand that all or part of the various steps of the foregoing embodiments may be completed by a program instructing related hardware. The program may be stored in a computer readable storage medium, and the storage medium may include: Read Only Memory (ROM), Random Access Memory (RAM), disk or optical disk.

The foregoing detailed description of the data merging method and apparatus for the key value database provided by the embodiment of the present invention is only for helping to understand the method of the present invention and its core idea; meanwhile, for those skilled in the art, according to the present invention The scope of the present invention is not limited by the scope of the present invention.

Claims

Rights request

1. A data merging method for a key-value database, characterized in that the method includes: obtaining the load level of the current system and the urgency level of the tasks to be merged;

According to the load level of the current system and the urgency level of the tasks to be merged, the matching merging option is that the higher the load level of the current system, the higher the urgency level of the tasks to be merged is allowed to be executed, when the load level of the current system is saturated. , no tasks to be merged are allowed to be executed;

2. The method of claim 1, wherein obtaining the load level of the current system includes:

The resource usage of the current system is weighted and summed according to the weight, and the load of the current system is assigned a corresponding level according to the value obtained by the weighted sum. The resource usage of the system includes the usage of CPU, Any combination of memory usage, network usage and disk usage, the load level of the current system includes low load, medium load, high load and saturation in order from low to high.

3. The method of claim 1, wherein obtaining the urgency level of tasks to be merged includes:

The factors that affect the urgency of the tasks to be merged are linearly weighted and summed according to the weights, and the urgency of the tasks to be merged is assigned a corresponding level according to the value obtained by the linear weighted sum. The factors of the urgency of the tasks to be merged include any combination of the file size in the sub-table, the number of files in the sub-table and the expiration time of the oldest data in the sub-table. The urgency level of the tasks to be merged includes non-urgent, ordinary and urgent.

4. The method according to claim 1, characterized in that, if the influence value of factor ¾ among the factors that currently affect the urgency of the task to be merged has reached or is close to the maximum value of the factor ¾, then the The urgency levels of tasks to be merged include:

The factors that affect the urgency of the tasks to be merged are subjected to a nonlinear weighted sum according to the weights, and the urgency of the tasks to be merged is assigned a corresponding value based on the value obtained by the nonlinear weighted sum. The factors that affect the urgency of the tasks to be merged include any combination of the file size in the sub-table, the number of files in the sub-table and the expiration time of the oldest data in the sub-table, the tasks to be merged are Urgency levels include non-urgent, normal and urgent.

5. The method of claim 4, wherein the nonlinear weighted summation of factors that affect the urgency of the tasks to be merged according to weights includes:

Amplify the weight ^ of the factors that affect the urgency of the tasks to be merged to , where ^ is the weight amplification function;

Using the new weights as factors that affect the urgency of the tasks to be merged, perform a nonlinear weighted sum of the factors that affect the urgency of the tasks to be merged according to the new weights, and based on the nonlinear weighting The value obtained by the summation assigns a corresponding level to the urgency of the tasks to be merged, and the urgency levels of the tasks to be merged include non-urgent, normal and urgent.

6. The method according to any one of claims 2 to 5, characterized in that, according to the load level of the current system and the urgency level of the tasks to be merged, the merged task execution policy is matched to determine whether to allow execution of the tasks to be merged. Tasks to be merged include:

If the matching urgency level of the task to be merged is urgent, and when the load level of the current system is low load, medium load or high load, it is determined that the task to be merged is allowed to be executed;

If the urgency level of the task to be merged is matched to non-emergency, and the load level of the current system is medium load or above, it is determined that the task to be merged is not allowed to be executed;

If the matching urgency level of the task to be merged is normal and the load level of the current system is high load or above, it is determined that the task to be merged is not allowed to be executed.

7. The method according to any one of claims 2 to 5, wherein returning the tasks to be merged to the waiting queue further includes:

The tasks to be merged are frozen so that the tasks to be merged are in a state where they cannot be taken out of the waiting queue within the set freezing time.

8. The method of claim 7, wherein the freezing of the tasks to be merged further includes:

A timer is started to count the set freezing time, so that after the set freezing time ends, the tasks to be merged are changed to a state in which the waiting queue can be taken out.

9. The method of claim 7, wherein the freezing of the tasks to be merged further includes:

If the load level of the current system drops from saturation to high load, medium load or low load, from high load to medium load or low load, or from medium load to low load, then the tasks to be merged are changed to Be able to retrieve the status of the waiting queue; or

If the urgency level of the tasks to be merged is raised from non-urgent to normal or urgent, or from normal to urgent, then the tasks to be merged are changed to a state where the waiting queue can be taken out; or

When all tasks to be merged in the waiting queue are frozen and the merge task execution module is in an idle state, if the urgency level of the task to be merged is higher than the urgency level of other tasks to be merged, the task to be merged will be Change to a state where the waiting queue can be removed.

10. A data merging device for a key-value database, characterized in that the device includes: an acquisition module, used to acquire the load level of the current system and the urgency level of the tasks to be merged; a determination module, used to obtain the load level of the current system and the urgency level of the tasks to be merged; a determination module, used to determine according to the current The load level of the system and the urgency of the tasks to be merged are determined by the merge task execution policy. The higher the load level of the current system, the higher the urgency level of the tasks to be merged is allowed to be executed. When the load level of the current system is saturated, execution is not allowed. Any task to be merged; a processing module, configured to send the task to be merged to the merge task execution module to perform task merge if the determination module determines to execute the task to be merged.

11. The device according to claim 10, wherein the acquisition module includes: a first acquisition unit, configured to perform a weighted sum of the current system resource usage according to weights, and obtain the result according to the weighted sum. The value of assigns a corresponding level to the load of the current system. The resource usage of the system includes any combination of CPU usage, memory usage, network usage and disk usage. The load level of the current system The order from low to high includes low load, medium load, high load and saturation.

12. The device according to claim 10, wherein the acquisition module includes: a second acquisition unit, configured to linearly weight and sum the factors that affect the urgency of the tasks to be merged according to the weights. The value obtained by the linear weighted summation has an impact on the emergency process of the tasks to be merged. The degree is assigned a corresponding level, and the factors that affect the urgency of the task to be merged include any combination of the file size in the sub-table, the number of files in the sub-table, and the expiration time of the oldest data in the sub-table. The urgency levels of merged tasks include normal, urgent and necessary.

13. The device according to claim 10, wherein if the influence value of factor ¾ among the factors that currently affect the urgency of the task to be merged has reached or is close to the maximum value of the factor ¾, then the The above acquisition modules include:

The third acquisition unit is configured to perform a nonlinear weighted sum of the factors that affect the urgency of the tasks to be merged according to weights, and assign a corresponding value to the urgency of the tasks to be merged based on the value obtained by the weighted sum. Level, the factors that affect the urgency of the tasks to be merged include any combination of the file size in the sub-table, the number of files in the sub-table and the expiration time of the oldest data in the sub-table, the urgency of the tasks to be merged Levels include non-urgent, normal and urgent.

14. The device according to claim 13, wherein the third acquisition unit includes: an amplification unit, configured to amplify the weights of factors affecting the urgency of the tasks to be merged to f {A _k ) w _k , said is the weight amplification function;

The summation unit is configured to use the new weights as the factors that affect the urgency of the tasks to be merged, and perform a nonlinear weighted sum of the factors that affect the urgency of the tasks to be merged according to the new weights, The urgency of the tasks to be merged is assigned a corresponding level according to the value obtained by the nonlinear weighted sum. The urgency levels of the tasks to be merged include ordinary, urgent and necessary.

15. The device according to any one of claims 11 to 14, characterized in that the determining module includes:

A first determination unit configured to determine whether the task to be merged is allowed to be executed if the emergency level of the task to be merged is urgent and the load level of the current system is low load, medium load or high load. ;

The second determination unit is configured to determine that if the emergency level of the task to be merged is non-urgent and the load level of the current system is medium load or above, it is determined that the task to be merged is not allowed to be executed. ;

The third determination unit is configured to determine that if the emergency level of the tasks to be merged is normal and the load level of the current system is high load or above, it is determined that the execution of the tasks to be merged is not allowed. Merge of merge tasks.

16. The device according to any one of claims 11 to 14, characterized in that the device further includes:

A task freezing module is used to freeze the tasks to be merged, so that the tasks to be merged are in a state where they cannot be taken out of the waiting queue within the set freezing time.

17. The device according to claim 16, wherein the device further includes: a first thawing module, configured to start a timer to time the set freezing time, so that the set freezing time is After the freezing time is over, the tasks to be merged are changed to a state where they can be taken out of the waiting queue.

18. The device according to claim 16, wherein the device further includes a second thawing module, a third thawing module or a fourth thawing module;

The second unfreezing module is used if the load level of the current system drops from saturation to high load, medium load or low load, from high load to medium load or low load, or from medium load to low load, Then change the task to be merged to a state where the waiting queue can be taken out;

The third unfreezing module is used to change the task to be merged to be able to take out the waiting queue if the urgency level of the task to be merged is raised from non-urgent to normal or urgent, or from normal to urgent. status;

The fourth unfreezing module is used to, when all tasks to be merged in the waiting queue are frozen and the merge task execution module is in an idle state, if the urgency level of the task to be merged is higher than the urgency level of other tasks to be merged If it is high, the task to be merged will be changed to a state where the waiting queue can be taken out.