CN115061634A - System service load distribution method, device and medium - Google Patents

Abstract

The application relates to the field of server storage, and discloses a method, a device and a medium for distributing system service load, which comprise the following steps: and judging whether a write operation instruction generated by the server is acquired or not to determine whether a storage service exists currently or not. If the write operation instruction is acquired, determining the logic unit number of the hard disk called by the write operation instruction; dividing the logic unit number into a plurality of fields with the same scale, and determining the field where each logic unit number is located; and writing the write operation data into each target cache node corresponding to each field. Therefore, according to the scheme provided by the application, the LUN is divided into a plurality of fields, the number of the fields corresponding to each cache node is the same, and the cache nodes corresponding to the fields are directly called to complete the system write operation instruction, so that the service load balance of each cache node is ensured.

Description

A system service load distribution method, device and medium

technical field

The present application relates to the field of server storage, and in particular, to a system service load distribution method, device, and medium.

Background technique

In order to ensure the reliability and high performance of storage devices, current storage devices have multiple disk array controllers (ie, cache nodes), wherein the disk array controllers include a CPU, a cache, and a fiber channel. FIG. 1 is a schematic diagram of an existing cache copy distribution and cache flushing path. As shown in FIG. 1 , there are multiple storage blocks in the cache system, and the underlying physical space of each storage block is composed of hard disks. During the working process of the server, multiple storage blocks in the block storage are logically integrated into corresponding Logical Unit Numbers (LUNs). The data in the cache node is flushed to the hard disk.

However, currently, tasks are usually allocated to each cache node according to the LUN granularity. Due to the unbalanced distribution of LUNs in each cache node and the different services on each LUN, the load difference of each cache node will result in the inability to fully utilize the storage performance of the storage device. User experience.

It can be seen that how to provide a method for allocating a service load of a storage device to prevent the service load of each cache node from being unbalanced is an urgent problem to be solved by those skilled in the art.

SUMMARY OF THE INVENTION

The purpose of this application is to provide a system service load distribution method, device, and medium, so that the service load of a storage device is evenly distributed on each cache node, so as to give full play to the storage performance of the storage device, and improve system stability and user experience. .

In order to solve the above problems, the present application provides a system service load distribution method, including:

Determine whether to obtain the write operation instruction generated by the server;

If the write operation instruction is obtained, determine the logical unit number of the hard disk called by the write operation instruction;

The logical unit number is divided into a plurality of fields of the same scale, and each field is evenly distributed to each cache node, and the field where each of the logical unit numbers is located is determined;

Write the write operation data to each target cache node corresponding to each of the fields.

Preferably, after the step of writing the write operation data into each target cache node corresponding to each of the fields, the method further includes:

Get the cache rule file;

The backup node of each cache node is determined according to the cache rule file, and the write operation data corresponding to each cache node is backed up to the backup node.

Preferably, after the step of backing up the write operation data corresponding to each cache node to the backup node, the step further includes:

When there is a faulty cache node, update the cache rule file;

The data in each of the cache nodes is re-backed up according to the updated cache rule file.

Preferably, the determining the backup node of each cache node according to the cache rule file includes:

If the field corresponding to the cache node is the last field of the logical unit number, the backup node is the cache node corresponding to the initial field of the logical unit number;

If the field corresponding to the cache node is not the last field of the logical unit number, the backup node is a node adjacent to the cache node.

Preferably, the re-backing up of the data in each of the cache nodes according to the updated cache rule file includes:

The data in each of the cache nodes is re-backed up by using the reserved computing resources of the controller.

Preferably, before the step of backing up the data in each of the cache nodes according to the updated cache rule file, the method further includes:

Setting different weights for the re-backup request and each service request of the controller;

Correspondingly, performing the backup of the data in each of the cache nodes according to the updated cache rule file includes:

Request messages with higher weights are executed first.

Preferably, the writing of the write operation data to each target cache node corresponding to each of the fields includes:

Sending an IO operation instruction to each of the target cache nodes corresponding to each of the fields, so that each of the target cache nodes executes the command to write the write operation data.

In order to solve the above technical problems, the present application also provides a system service load distribution device, including:

a judgment module for judging whether to obtain the write operation instruction generated by the server;

a first determination module, configured to determine the logical unit number of the hard disk called by the write operation instruction if the write operation instruction is obtained;

a second determining module, configured to divide the logical unit number into a plurality of fields of the same scale and evenly distribute each field to each cache node, and determine the field where each of the logical unit numbers is located;

The writing module is used for writing the write operation data into each target cache node corresponding to each of the fields.

In order to solve the above technical problems, the present application also provides a system service load distribution device, including a memory for storing a computer program;

The processor is configured to implement the steps of the system traffic load distribution method when executing the computer program.

In order to solve the above technical problems, the present application also provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the system service load distribution method is implemented A step of.

The system service load distribution method provided by the present application includes: judging whether a write operation instruction generated by a server is obtained to determine whether a storage service currently exists. If the write operation instruction is obtained, determine the logical unit number of the hard disk called by the write operation instruction; divide the logical unit number into multiple fields of the same scale, and determine the field where each logical unit number is located; write the write operation data into the Each target cache node corresponding to each field. It can be seen that the solution provided by this application divides the LUN into multiple fields, the number of fields corresponding to each cache node is the same, and directly calls the cache node corresponding to the field to complete the system write operation instruction, thereby ensuring that each cache node is business load balancing.

In addition, the present application also provides a system service load distribution device and medium, which correspond to the above method and have the same effects as above.

Description of drawings

In order to describe the embodiments of the present application more clearly, the following will briefly introduce the drawings that are used in the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application, which are not relevant to ordinary skills in the art. As far as personnel are concerned, other drawings can also be obtained from these drawings on the premise of no creative work.

FIG. 1 is a schematic diagram of an existing cache copy distribution and cache flushing path;

FIG. 2 is a flowchart of a system service load distribution method provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of a cache copy distribution and a cache flushing path provided by an embodiment of the present application;

FIG. 4 is a structural diagram of a system service load distribution apparatus provided by an embodiment of the present application;

FIG. 5 is a structural diagram of another system service load distribution apparatus provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative work fall within the protection scope of the present application.

The core of this application is to provide a system service load distribution method, device and medium, so that the service load of a storage device is evenly distributed on each cache node, so as to give full play to the storage performance of the storage device and improve system stability and user experience. .

In the application scenario of a storage device, in order to ensure the reliability and high performance of the storage device, the storage device needs to include multiple cache nodes, and each cache node must ensure load balancing. The traditional cache copy is two copies. When the cache data is distributed on two cache nodes in a multi-controller cache device, if the cache copies are distributed at LUN granularity, the LUN distribution on each controller will be uneven and uneven. The services on each LUN are different, resulting in different loads on each controller, which cannot give full play to the performance of the entire system. In order to solve this problem, this embodiment provides a system service load distribution method, which includes: judging whether a write operation instruction generated by a server is obtained to determine whether a storage service currently exists. If the write operation instruction is obtained, determine the logical unit number of the hard disk called by the write operation instruction; divide the logical unit number into multiple fields of the same scale, and determine the field where each logical unit number is located; write the write operation data into the Each target cache node corresponding to each field. It can be seen that the solution provided by this application divides the LUN into multiple fields, the number of fields corresponding to each cache node is the same, and directly calls the cache node corresponding to the field to complete the system write operation instruction, thereby ensuring that each cache node is business load balancing.

In order to make those skilled in the art better understand the solution of the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

FIG. 2 is a flowchart of a system service load distribution method provided by an embodiment of the present application. As shown in FIG. 2 , the method includes:

S10: Determine whether the write operation instruction generated by the server is obtained.

S11: If the write operation instruction is obtained, determine the logical unit number of the hard disk called by the write operation instruction.

S12: Divide the logical unit number into a plurality of fields of the same scale, and evenly distribute each field to each cache node, and determine the field where each logical unit number is located.

S13: Write the write operation data into each target cache node corresponding to each field.

In a specific implementation, the logical unit number is divided into a plurality of fields with the same scale, and the length of each field can be determined by the system maintenance personnel, for example: 1MB. It should be noted that after the logical unit number is divided into multiple fields, if the remaining logical unit number is less than 1MB, the remaining part is regarded as an independent field. Each field is evenly distributed to different cache nodes, that is, each field has its corresponding cache unit. When the server invokes the entire LUN to execute the write operation instruction, it determines the field where each logical unit number called is located, and writes the write operation data into each target cache node corresponding to each field.

It is understandable that to achieve load balancing, storage alone is not enough, and multi-pathing software on the host side is needed to coordinate the completion. Many operating systems come with multipath software, such as Multipath in Linux and MOIP in windwos. However, these balancing software can only implement basic functions. To achieve more functions, it is necessary to rely on the load balancing software provided by the storage manufacturer. . The role of load balancing software includes deduplication of drive letters and finding optimal paths. The drive letter deduplication refers to removing duplicate drive letters. Taking a dual-controller system as an example, the server host generally uses two host bus adapters (HBAs) to connect to the two controllers respectively, because the data connection formed by the two controllers can find a LUN. , therefore, this LUN will generate two drive letters on the host, but these two drive letters actually point to the same physical hard disk. The load balancing software will use the WWN number to determine whether the two drive letters point to the same hard disk. disk, and if so, remove the duplicate drive letter.

Further, in order to further improve the load balance of each cache node, when the server reads a certain field of the storage volume, it directly sends the IO request sent by the server to the cache node corresponding to the field. Therefore, the server can directly access the cache node without forwarding through other cache nodes, thereby improving work efficiency. Taking the SCSI protocol as an example, for each field, the target port of each cache node is divided into a Target Port Group, the path attributes corresponding to the target ports in the same Target Port Group are the same, and the target ports of different groups correspond to Path attributes report different path optimization strategies through protocols, which can be divided into Active/optimized, Active/non-optimized, Standby, Unavailable, Reserved, Offline, Transitioning betweenstates and other states, and select the corresponding path according to the above states.

FIG. 3 is a schematic diagram of cache copy distribution and cache refresh paths provided by an embodiment of the present application. As shown in FIG. 3 , after the server sends a write operation command, according to the corresponding relationship between each field of the LUN and each cache node, the server reads the The write IO request is sent to the cache node corresponding to each field, so as to ensure the load balance of each cache node and give full play to the performance of the storage device.

The system service load distribution method provided by the present application includes: judging whether a write operation instruction generated by a server is obtained to determine whether a storage service currently exists. If the write operation instruction is obtained, determine the logical unit number of the hard disk called by the write operation instruction; divide the logical unit number into multiple fields of the same scale, and determine the field where each logical unit number is located; write the write operation data into the Each target cache node corresponding to each field. It can be seen that the solution provided by this application divides the LUN into multiple fields, the number of fields corresponding to each cache node is the same, and directly calls the cache node corresponding to the field to complete the system write operation instruction, thereby ensuring that each cache node is business load balancing.

During the operation of the storage device, after the write operation data is written to the cache node, if the cache node fails, the write data will be lost, and eventually the data cannot be flushed from the cache node to the hard disk. In order to solve this problem, a dual-node backup method is currently used, in which two nodes form a backup group and mutually store the mirror files of the other node. However, when a cache node in the backup group fails, the backup cannot be performed normally, which reduces the stability of the system.

In order to solve this problem, on the basis of the above embodiment, after the step of writing the write operation data into each target cache node corresponding to each field, the method further includes:

Get the cache rule file;

Determine the backup node of each cache node according to the cache rule file, and back up the write operation data to the backup node.

In a specific implementation, a plurality of cache nodes are used to mirror each other to implement data backup, and to prevent data loss due to cache node failure. Specifically, the backup node of each cache node is determined according to the cache rule file stored in the system. The cache rule file is a file predetermined by the administrator. This embodiment is described by taking a storage device with four cache nodes as an example. There are 4 mirror pairs in the system, that is, 4 domains, each domain contains 2 nodes, and the data in the domain in each node consists of fields. The data and metadata caches in the system are distributed among 4 mirror pairs, with 2 duplicate mirrors in each mirror pair.

When the node is abnormal, the members of the affected domain are reorganized, triggering the business module to re-mirror the data and metadata caches in the relevant domain, so as to ensure that the domain is still two nodes, and the data and metadata caches in the domain still exist. Mirroring, the business in the domain is still written back. The re-mirror is performed in the background, and IO can be continuously processed during the process, and the business is not affected. After the data and metadata caches in the domain are re-mirrored, each mirror pair is constructed again. After that, if another node fails, domain reorganization and re-mirror of the data and metadata cache in the domain can be performed again. When there is only one node left, there is only one node left in each domain, but the storage device can still provide services. , that is, the business is not affected in the scenario where 4 controllers are broken and 3 controllers are supported, and high availability is achieved.

Specifically, when there are four cache nodes Node0, Node1, Node2, and Node3 in the system, the data in Node0 can be backed up to Node1, the data in Node1 can be backed up to Node2, the data in Node2 can be backed up to Node3, and the data in Node3 can be backed up to Node0 to form a cyclic backup, or use other backup methods, which are not limited here.

It should be noted that the data backed up to the backup node is not all the data of the current cache node, but the data written by the server host to the cache node corresponding to each field according to the LUN field. When it is detected that a faulty cache node exists in the storage device, the cache rule file is updated, and the faulty cache node is deleted; and the data in each cache node is re-backed up according to the updated cache rule file. For example, Node0 saves the cache data of Node0 and the backup data of Node3. When Node0 fails, Node1 performs the tasks of the original Node0, and at the same time backs up the data again, backing up the data in Node1 to Node2, and backing up the data in Node2 to Node3, back up the data in Node3 to Node1.

On the basis of the above embodiment, determining the backup node of each cache node according to the cache rule file includes:

If the field corresponding to the cache node is the last field of the logical unit number, the backup node is the cache node corresponding to the initial field of the logical unit number;

If the field corresponding to the cache node is not the last field of the logical unit number, the backup node is a node adjacent to the cache node.

In this embodiment, the method of cyclic mirroring is used to back up the cache data in each cache node. Compared with other backup rules, this backup rule is more efficient for re-backup when there is a faulty cache node.

It should be noted that in the server working scenario, the business pressure of the storage device is high, and the cache of each cache node is in a state of high business pressure. When a cache node fails, data remapping and server host services may compete for computing resources.

In order to solve this problem, two optimization methods are proposed on the basis of the above embodiments.

(1) Each server reserves a part of the cache for data synchronization in the domain reorganization process

(2) In the process of Domain reorganization, define the priority weighted value of data cross-controller synchronization IO and host business IO to ensure that Domain reorganization and front-end host business IO can be carried out normally according to a certain proportion.

Specifically, for the solution (1), in the daily work of the server, the performance of the server is reduced to achieve the purpose of reserving computing resources. When a cache node failure occurs in the system, the data in each cache node is re-backed up by using the reserved computing resources.

For scheme (2), it is necessary to preset different weights for the re-backup task request and each task request of the server host. Priority is given to re-backing up the data in each cache node.

In the above embodiments, the system service load distribution method is described in detail, and the present application also provides embodiments corresponding to the system service load distribution apparatus. It should be noted that this application describes the embodiments of the device part from two perspectives, one is based on the perspective of functional modules, and the other is based on the perspective of hardware.

FIG. 4 is a structural diagram of a system service load distribution apparatus provided by an embodiment of the application. As shown in FIG. 4 , the system service load distribution apparatus includes:

The judgment module 10 is used for judging whether the write operation instruction generated by the server is obtained.

The first determination module 11 is configured to determine the logical unit number of the hard disk called by the write operation instruction if the write operation instruction is obtained.

The second determination module 12 is used to divide the logical unit number into a plurality of fields of the same scale, and determine the field where each logical unit number is located, and each of the fields is evenly distributed to each cache node.

The writing module 13 is used for writing the write operation data into each target cache node corresponding to each field.

Since the embodiment of the apparatus part corresponds to the embodiment of the method part, for the embodiment of the apparatus part, please refer to the description of the embodiment of the method part, which will not be repeated here.

The system service load distribution method provided by the present application includes: judging whether a write operation instruction generated by a server is obtained to determine whether a storage service currently exists. If the write operation instruction is obtained, determine the logical unit number of the hard disk called by the write operation instruction; divide the logical unit number into multiple fields of the same scale, and determine the field where each logical unit number is located; write the write operation data into the Each target cache node corresponding to each field. It can be seen that the solution provided by this application divides the LUN into multiple fields, the number of fields corresponding to each cache node is the same, and directly calls the cache node corresponding to the field to complete the system write operation instruction, thereby ensuring that each cache node is business load balancing.

FIG. 5 is a structural diagram of a system service load distribution apparatus provided by another embodiment of the present application. As shown in FIG. 5 , the system service load distribution apparatus includes: a memory 20 for storing computer programs;

The processor 21 is configured to implement the steps of the system service load distribution method according to the above embodiment when executing the computer program.

The smart device provided in this embodiment may include, but is not limited to, a smart phone, a tablet computer, a notebook computer, or a desktop computer.

The processor 21 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. The processor 21 may use at least one hardware form of a digital signal processor (Digital Signal Processor, DSP), a Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), and a Programmable Logic Array (Programmable Logic Array, PLA). accomplish. The processor 21 may also include a main processor and a coprocessor. The main processor is a processor used to process data in the wake-up state, also called a central processing unit (CPU); A low-power processor for processing data in a standby state. In some embodiments, the processor 21 may be integrated with a graphics processor (Graphics Processing Unit, GPU), and the GPU is responsible for rendering and drawing the content that needs to be displayed on the display screen. In some embodiments, the processor 21 may further include an artificial intelligence (Artificial Intelligence, AI) processor for processing computing operations related to machine learning.

Memory 20 may include one or more computer-readable storage media, which may be non-transitory. Memory 20 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash storage devices. In this embodiment, the memory 20 is used to store at least the following computer program 201, where, after the computer program is loaded and executed by the processor 21, relevant steps of the system service load distribution method disclosed in any of the foregoing embodiments can be implemented. In addition, the resources stored in the memory 20 may also include an operating system 202, data 203, etc., and the storage mode may be short-term storage or permanent storage. The operating system 202 may include Windows, Unix, Linux, and the like. The data 203 may include, but is not limited to, the correspondence between fields and cache nodes, and the like.

In some embodiments, the system service load distribution apparatus may further include a display screen 22 , an input/output interface 23 , a communication interface 24 , a power supply 25 and a communication bus 26 .

Those skilled in the art can understand that the structure shown in FIG. 5 does not constitute a limitation on the system service load distribution apparatus, and may include more or less components than those shown in the figure.

The system service load distribution device provided by the embodiment of the present application includes a memory and a processor. When the processor executes a program stored in the memory, the processor can implement the following methods:

Determine whether the write operation command generated by the server is obtained.

If the write operation instruction is obtained, the logical unit number of the hard disk called by the write operation instruction is determined.

The logical unit number is divided into a plurality of fields of the same scale, and each field is evenly distributed to each cache node, and the field where each logical unit number is located is determined.

Write the write operation data to each target cache node corresponding to each field.

The system service load distribution method provided by the present application includes: judging whether a write operation instruction generated by a server is obtained to determine whether a storage service currently exists. If the write operation instruction is obtained, determine the logical unit number of the hard disk called by the write operation instruction; divide the logical unit number into multiple fields of the same scale, and determine the field where each logical unit number is located; write the write operation data into the Each target cache node corresponding to each field. It can be seen that the solution provided by this application divides the LUN into multiple fields, the number of fields corresponding to each cache node is the same, and directly calls the cache node corresponding to the field to complete the system write operation instruction, thereby ensuring that each cache node is business load balancing.

Finally, the present application also provides an embodiment corresponding to a computer-readable storage medium. A computer program is stored on the computer-readable storage medium, and when the computer program is executed by the processor, the steps described in the foregoing method embodiments are implemented. The system service load distribution device provided by the present application includes: judging whether a write operation instruction generated by a server is obtained to determine whether a storage service currently exists. If the write operation instruction is obtained, determine the logical unit number of the hard disk called by the write operation instruction; divide the logical unit number into multiple fields of the same scale, and determine the field where each logical unit number is located; write the write operation data into the Each target cache node corresponding to each field. It can be seen that the solution provided by this application divides the LUN into multiple fields, the number of fields corresponding to each cache node is the same, and directly calls the cache node corresponding to the field to complete the system write operation instruction, thereby ensuring that each cache node is business load balancing.

It can be understood that, if the methods in the above embodiments are implemented in the form of software functional units and sold or used as independent products, they may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

The system service load distribution method, device, and medium provided by the present application have been described in detail above. The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same and similar parts between the various embodiments can be referred to each other. As for the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant part can be referred to the description of the method. It should be pointed out that for those of ordinary skill in the art, without departing from the principles of the present application, several improvements and modifications can also be made to the present application, and these improvements and modifications also fall within the protection scope of the claims of the present application.

It should also be noted that, in this specification, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply these entities or operations. There is no such actual relationship or sequence between operations. Moreover, the terms "comprising", "comprising" or any other variation thereof are intended to encompass a non-exclusive inclusion such that a process, method, article or device that includes a list of elements includes not only those elements, but also includes not explicitly listed or other elements inherent to such a process, method, article or apparatus. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in a process, method, article or apparatus that includes the element.

Claims (10)

1. a system service load distribution method, is characterized in that, comprises: Determine whether to obtain the write operation instruction generated by the server; If the write operation instruction is obtained, determine the logical unit number of the hard disk called by the write operation instruction; The logical unit number is divided into a plurality of fields of the same scale, and each field is evenly distributed to each cache node, and the field where each of the logical unit numbers is located is determined; Write the write operation data to each target cache node corresponding to each of the fields. 2. The system service load distribution method according to claim 1, wherein after the step of writing the write operation data into each target cache node corresponding to each of the fields, the method further comprises: Get the cache rule file; The backup node of each cache node is determined according to the cache rule file, and the write operation data corresponding to each cache node is backed up to the backup node. 3. The system service load distribution method according to claim 2, wherein after the step of backing up the write operation data corresponding to each of the cache nodes to the backup node, the method further comprises: When there is a faulty cache node, update the cache rule file; The data in each of the cache nodes is re-backed up according to the updated cache rule file. 4. The system service load distribution method according to claim 2, wherein the determining the backup node of each cache node according to the cache rule file comprises: If the field corresponding to the cache node is the last field of the logical unit number, the backup node is the cache node corresponding to the initial field of the logical unit number; If the field corresponding to the cache node is not the last field of the logical unit number, the backup node is a node adjacent to the cache node. 5. The system service load distribution method according to claim 3, wherein the re-backing up the data in each of the cache nodes according to the updated cache rule file comprises: The data in each of the cache nodes is re-backed up by using the reserved computing resources of the controller. 6. The system service load distribution method according to claim 3, wherein before the step of backing up the data in each of the cache nodes according to the updated cache rule file, the method further comprises: Setting different weights for the re-backup request and each service request of the controller; Correspondingly, performing the backup of the data in each of the cache nodes according to the updated cache rule file includes: Request messages with higher weights are executed first. 7. The system service load distribution method according to claim 1, wherein the writing of the write operation data to each target cache node corresponding to each of the fields comprises: Sending an IO operation instruction to each of the target cache nodes corresponding to each of the fields, so that each of the target cache nodes executes the command to write the write operation data. 8. A system service load distribution device, comprising: a judgment module for judging whether to obtain the write operation instruction generated by the server; a first determination module, configured to determine the logical unit number of the hard disk called by the write operation instruction if the write operation instruction is obtained; a second determining module, configured to divide the logical unit number into a plurality of fields of the same scale and evenly distribute each field to each cache node, and determine the field where each of the logical unit numbers is located; The writing module is used for writing the write operation data into each target cache node corresponding to each of the fields. 9. A system service load distribution device, characterized in that it comprises a memory for storing a computer program; The processor is configured to implement the steps of the system traffic load distribution method according to any one of claims 1 to 7 when executing the computer program. 10. A computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the system according to any one of claims 1 to 7 is implemented The steps of the traffic load distribution method.

Images