WO2024021470A1

WO2024021470A1 - Cross-region data scheduling method and apparatus, device, and storage medium

Info

Publication number: WO2024021470A1
Application number: PCT/CN2022/141408
Authority: WO
Inventors: 颜嘉伟; 黄润怀; 林洁琬; 肖露; 吴文峰; 陈杰; 张维杰
Original assignee: 天翼云科技有限公司
Priority date: 2022-07-28
Filing date: 2022-12-23
Publication date: 2024-02-01
Also published as: CN115292280A

Abstract

The present application relates to the technical field of cloud computing, and in particular, to a cross-region data scheduling method and apparatus, a device, and a storage medium, which are used for solving the problems in the prior art that the service request processing efficiency is low and the service continuity cannot be ensured. The method comprises: acquiring target information of data centers on the basis of a request operation type comprised in a service request sent by a client, and on the basis of data description information of data to be transmitted comprised in the service request and the target information, determining and sending data plane interface information of a target data center corresponding to the service request to the client, wherein the target information comprises at least one of metadata information and state information, the metadata information represents base data description information of each logical disk unit comprised in any data center, and the state information represents operation state description information of any data center. In this way, the service request processing efficiency is improved, and the service continuity is ensured.

Description

A cross-regional data scheduling method, device, equipment and storage medium

Technical field

The present application relates to the field of cloud computing technology, and in particular to a cross-regional data scheduling method, device, equipment and storage medium.

Background technique

With the development of cloud computing technology, cloud storage that is easy to use and access and does not require customers to build a data center is increasingly recognized by everyone. Storage Area Network (SAN) is a network-centric storage structure that usually includes servers (hosts), storage devices (logical disk units (Logical Disk Units, LUNs) or disk arrays), and bridges and multiplexers. Road multiplexer, in which all devices are connected to Fiber Channel switches, is suitable for services requiring high throughput and low latency.

technical problem

Under the existing technology, cloud storage service providers often build SANs inside data centers and implement security protection and data protection for the data centers internally. In this way, when the network quality of the data center is poor or the remaining capacity is small, The client's business requests, such as business I/O requests, cannot be processed in a timely manner, resulting in low efficiency in business request processing and the inability to ensure business continuity.

Technical solutions

Embodiments of the present application provide a cross-regional data scheduling method, device, equipment and storage medium to improve service request processing efficiency and ensure business continuity.

The specific technical solutions provided by the embodiments of this application are as follows:

In the first aspect, embodiments of the present application provide a cross-region data scheduling method, including:

Receive a service request sent by the client, where the service request includes the requested operation type and data description information of the data to be transmitted;

Based on the request operation type, the target information of each data center is obtained, where the storage architecture of each data center is built based on the storage area network, and the target information includes at least one of metadata information and status information, so The metadata information represents the inventory data description information of each logical disk unit contained in any data center, and the status information represents the operating status description information of any data center;

Based on the data description information and each target information, determine the target data center corresponding to the service request, wherein the target data center is at least one of the various data centers;

The data plane interface information of the target data center is returned to the client, so that the client constructs an uplink and downlink data transmission channel corresponding to the service request based on the data plane interface information.

In some possible embodiments, if the requested operation type is a read operation, the target information is the metadata information; if the requested operation type is a write operation, the target information is the status information. ;

Determining the target data center corresponding to the service request based on the data description information and each target information includes:

If the requested operation type is a read operation, query the inventory data corresponding to the data description information from each metadata information, and determine the data center corresponding to the data center index information of the queried inventory data. For the target data center;

If the requested operation type is a write operation, determine the scheduling plan corresponding to the data to be transmitted based on the data description information and the respective status information, and determine the target data center based on the scheduling plan, where , the status information is collected regularly through the status information interface corresponding to any data center.

In some possible embodiments, after returning the data plane interface information of the target data center to the client, the method further includes:

After determining that the write operation is completed, collect target metadata information of the target data center;

Based on the target metadata information, existing metadata information in the target information is updated.

In some possible embodiments, the method includes:

Migrate the target inventory data of the first data center to a second data center, where the first data center is any one of the data centers, and the second data center is one of the data centers, Any data center except the first data center;

After the data migration is completed, the existing metadata information is updated based on the first metadata information of the first data center and the second metadata information of the second data center.

In some possible embodiments, the status information includes some or all of the following information:

Network operating status description information;

The network device operating status description information of the storage area network;

Auxiliary equipment operating status description information.

In some possible embodiments, the metadata information includes some or all of the following information:

Data center index information;

Data offset of the inventory data of each logical disk unit;

The data length of the inventory data of each logical disk unit;

The timestamp of the inventory data for each logical disk unit.

In the second aspect, embodiments of the present application provide a cross-region data scheduling device, including:

A receiving module, configured to receive a service request sent by the client, where the service request includes the requested operation type and data description information of the data to be transmitted;

The acquisition module is used to obtain the target information of each data center based on the request operation type. The storage architecture of each data center is built based on the storage area network. The target information includes metadata information and status information. At least one, the metadata information represents the inventory data description information of each logical disk unit included in any data center, and the status information represents the operating status description information of any data center;

Determining module, configured to determine the target data center corresponding to the service request based on the data description information and each target information, wherein the target data center is at least one of the various data centers;

A sending module, configured to return the data plane interface information of the target data center to the client, so that the client can construct an uplink and downlink data transmission channel corresponding to the service request based on the data plane interface information.

Determine the target data center corresponding to the service request based on the data description information and each target information, and the determination module is used to:

In some possible embodiments, after returning the data plane interface information of the target data center to the client, the sending module is also used to:

In some possible embodiments, the determining module is used to migrate the target inventory data of the first data center to a second data center, where the first data center is any one of the respective data centers, The second data center is any one of the data centers except the first data center; it is also used to, after completing the data migration, based on the first metadata of the first data center information, and the second metadata information of the second data center updates the existing metadata information.

Network operating status description information;

Auxiliary equipment operating status description information.

Data center index information;

Data offset of the inventory data of each logical disk unit;

The data length of the inventory data of each logical disk unit;

The timestamp of the inventory data for each logical disk unit.

In a third aspect, embodiments of the present application provide an electronic device, which includes a processor and a memory,

The memory is used to store computer programs or instructions;

The processor is configured to execute computer programs or instructions in the memory, so that the method described in any one of the above first aspects is executed.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium on which computer program instructions are stored. When the computer program instructions are executed by a processor, the steps of any one of the methods described in the first aspect are implemented.

In the embodiment of this application, based on the request operation type contained in the received business request sent by the client, the target information of each data center is obtained, and then, based on the data description information of the data to be transmitted contained in the business request, the corresponding data center of the business request is determined. The target data center, and returns the data plane interface information of the target data center to the client, so that the client can build uplink and downlink data transmission channels corresponding to the business request based on the data plane interface information. The storage architecture of each data center is based on The storage area network is built, and the target information includes at least one of metadata information and status information. The metadata information represents the inventory data description information of each logical disk unit contained in any data center, and the status information represents the storage data description information of any data center. Running status description information, the target data center is at least one of each data center; in this way, the client can build upstream and downstream channels corresponding to business requests with multiple data centers, unbinding the client from the default data center, and improving It improves the performance of storage services of the established storage area network architecture, thereby improving the efficiency of business request processing and ensuring business continuity to the greatest extent.

Description of drawings

Figure 1 is a schematic diagram of an application scenario in an embodiment of the present application;

Figure 2 is a schematic architectural diagram of a cross-region data scheduling system in an embodiment of the present application;

Figure 3 is a schematic flowchart of a cross-region data scheduling method in an embodiment of the present application;

Figure 4 is a schematic diagram of the processing logic of the cross-region data scheduling system in the embodiment of the present application;

Figure 5 is a schematic flowchart of a method for determining a target data center in an embodiment of the present application;

Figure 6 is a schematic flowchart of another method for determining a target data center in an embodiment of the present application;

Figure 7 is a logical schematic diagram of the cross-region data scheduling system performing data scheduling through the scheduling module in the embodiment of the present application;

Figure 8 is a schematic flowchart of a method for updating existing metadata information in target information in an embodiment of the present application;

Figure 9 is a schematic flowchart of another cross-region data scheduling method in an embodiment of the present application;

Figure 10 is a schematic diagram of the logical architecture of a cross-region data scheduling device in an embodiment of the present application;

Figure 11 is a schematic diagram of the physical architecture of an electronic device in an embodiment of the present application.

Embodiments of the invention

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this application.

It should be noted that the terms "first", "second", "third", "fourth", etc. in the description and claims of this application and the above-mentioned drawings are used to distinguish similar objects and do not necessarily Used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments of the present application described herein are capable of being practiced in sequences other than those illustrated or described herein.

In order to solve the problem of low service request processing efficiency and inability to ensure service continuity under the existing technology, in the embodiment of this application, the target information of each data center is obtained based on the request operation type contained in the received service request sent by the client. , and then, based on the data description information of the data to be transmitted contained in the business request, determine the target data center corresponding to the business request, and return the data plane interface information of the target data center to the client, so that the client can build a data center based on the data plane interface information. Uplink and downlink data transmission channels corresponding to business requests. The storage architecture of each data center is based on the storage area network. The target information includes at least one of metadata information and status information. The metadata information represents any data center. It contains the inventory data description information of each logical disk unit, and the status information represents the operating status description information of any data center. The target data center is at least one of each data center.

In this way, the client can build uplink and downlink channels corresponding to business requests with multiple data centers, unbinding the client from the default data center, improving the performance of storage services that have built a storage area network architecture, thereby improving business Request processing efficiency ensures business continuity to the greatest extent.

Furthermore, the above method realizes load balancing scheduling for multiple data centers based on status information, making incremental data and existing data schedulable for migration, realizing imperceptible expansion and migration, and also enhancing the overall availability of the storage area. Expandability.

The preferred embodiments of the present application will be described in further detail below in conjunction with the accompanying drawings. It should be understood that the preferred embodiments described here are only used to illustrate and explain the present application and are not used to limit the present application. In the absence of conflict, The embodiments of the present application and the features in the embodiments can be combined with each other.

Figure 1 shows a schematic diagram of an application scenario according to the embodiment of the present application. Referring to Figure 1 , in the embodiment of the present application, the above application scenario includes a client 1, a cross-region data scheduling system 2 and a data center 3, where the client 1 and the cross-region data scheduling system 2 are connected through a communication network. communication. Alternatively, the communication network may be a wired network or a wireless network. The client 1 and the cross-region data scheduling system 2 can be connected directly or indirectly through wired or wireless communication methods, which is not limited in this application.

Correspondingly, the cross-regional data scheduling system 2 and the data center 3 can also communicate through a communication network, and the communication network can also be a wired network or a wireless network. The cross-regional data scheduling system 2 and the data center 3 can be connected directly or indirectly through wired or wireless communication methods, and this application is not limited here.

In the embodiment of the present application, the cross-region data scheduling system 2 is an electronic device equipped with the program of the cross-regional data scheduling method provided by the embodiment of the present application. The electronic device may be a smart terminal, a computer, a tablet, a notebook, or an e-book. Readers and other devices; it can also be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or it can provide cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, Cloud communications, middleware services, domain name services, security services, content distribution network (Content Delivery Network (CDN), as well as cloud servers for basic cloud computing services such as big data and artificial intelligence platforms.

Figure 2 shows a schematic architectural diagram of a cross-region data scheduling system provided in this embodiment of the present application. Referring to Figure 2, in this embodiment of the present application, the cross-region data scheduling system includes a scheduling module, a collection module and a metadata server, where,

The metadata server is used to record the metadata information of each logical disk unit contained in each managed data center, and is also used to record the corresponding status information of each data center; among which, the metadata information and/or status information is used to The scheduling module performs data scheduling on business requests between data plane interfaces in different data centers.

The collection module is used to regularly obtain the status information of different data centers through the respective status information interfaces of each data center, and record or update the status information to the metadata server.

The scheduling module is used to collect the metadata information of the existing data in each data center and record it in the metadata server; it is also used to record the data plane interface information of each managed data center. According to each element in the metadata server Data information or each status information is used to make decisions, determine the data plane interface information of the target data center for real-time business requests, and migrate and schedule the existing data based on the status information of each data center; it is also used for business requests (such as writing After the incoming request) is completed, the metadata information recorded in the metadata server is updated based on the written target metadata information of the target data center.

It should be noted that the collection module, metadata server and scheduling module included in the cross-region data scheduling system provided by this application can be deployed in one physical device at the same time, or can be deployed in different physical devices respectively, which will not be discussed here. Specific limitations.

Referring to Figure 3, an embodiment of the present application provides a cross-region data scheduling method. The specific process is as follows:

Step 300: Receive a service request sent by the client, where the service request includes the requested operation type and data description information of the data to be transmitted.

Referring to Figure 4, in the embodiment of the present application, before executing step 300, it is necessary to construct respective status information interfaces in each data center included in the cross-regional data scheduling system, which is used to regularly obtain the status of each data center through the collection module. information, and record or update the obtained status information to the metadata server.

Then, the cross-regional data scheduling system collects the data plane interface information of each data center through the scheduling module (the data plane interface is an existing interface, this application can directly collect the data plane interface information for use), and based on each data plane interface Information, collect metadata information of the existing data in each data center, and record the collected metadata information into the metadata server, thereby obtaining the initial metadata information of each data center.

After the architecture of the cross-region data scheduling system is completed, step 300 is executed to receive the service request sent by the client. The service requests involved in the embodiments of this application include service I/O requests. Therefore, each service request includes the requested operation type and data description information of the data to be transmitted, where the data description information includes data offset and data length.

In some embodiments, the data to be transmitted may be data to be read from one or some data centers, data to be written to one or some data centers, or the above-mentioned data. Data to be read and data to be written.

Step 310: Based on the requested operation type, obtain the target information of each data center. The storage architecture of each data center is built based on the storage area network. The target information includes at least one of metadata information and status information. Metadata The information represents the inventory data description information of each logical disk unit contained in any data center, and the status information represents the operating status description information of any data center.

In the embodiment of this application, when step 310 is executed, the target information of each data center is obtained based on the request operation type included in the received business request. That is, if the request operation type is a read operation, the metadata of each data center is obtained. Information, if the requested operation type is a write operation, obtain the status information of each data center.

In the embodiment of this application, metadata information includes some or all of the following information:

1. Data center index information;

2. Data offset of the existing data of each logical disk unit;

3. The data length of the existing data of each logical disk unit;

4. The timestamp of the existing data of each logical disk unit.

In practical applications, as shown in Table 1, the metadata information corresponding to each logical disk unit contained in each data center can be recorded through Table 1:

Table 1 List of metadata information of logical disk units

In the embodiment of this application, status information includes some or all of the following information:

1. Network operating status description information;

2. Description information of the operating status of the network equipment of the storage area network;

3. Description information of the operating status of auxiliary equipment.

In practical applications, refer to Table 2. The status information corresponding to each data center can be recorded through Table 2:

Table 2 List of status information of data center

Step 320: Determine the target data center corresponding to the service request based on the data description information and each target information, where the target data center is at least one of each data center.

In the embodiment of the present application, when step 320 is executed, different data scheduling processes are executed based on different request operation types.

Case 1: If the requested operation type is a read operation, see Figure 5. The specific process is as follows:

Step 3201: Query the existing data corresponding to the data description information from each metadata information.

Step 3202: Determine the data center corresponding to the queried data center index information of the existing data as the target data center.

Case 2: If the requested operation type is a write operation, see Figure 6. The specific process is as follows:

Step 3201': Determine the scheduling plan corresponding to the data to be transmitted based on the data description information and each status information. The status information is regularly collected through the status information interface corresponding to any data center.

Step 3202': Based on the scheduling plan, determine the target data center.

Step 330: Return the data plane interface information of the target data center to the client, so that the client can construct an uplink and downlink data transmission channel corresponding to the service request based on the data plane interface information.

In the embodiment of this application, after executing step 320 and determining the target data center corresponding to the service request, since the cross-regional data scheduling system has collected the data plane interface information of each data center through the scheduling module, then when executing step 330, Return the data plane interface information of the target data center to the client. In this way, the client can build uplink and downlink data transmission channels with the target data center based on the data plane interface information returned by the cross-regional data scheduling system, thereby realizing the data to be transmitted. data transmission.

In practical applications, usually service requests include both read operations and write operations. Then, refer to Figure 7, which shows a logical schematic diagram of the cross-region data scheduling system in the embodiment of the present application performing data scheduling through the scheduling module.

In the implementation of this application, as shown in Figure 7, after executing step 300 and before executing step 310, the request operation types contained in the business request need to be classified to distinguish read operations and write operations, and then execute subsequent data in parallel. Scheduling process.

In the specific implementation, if the requested operation type is a read operation, each metadata information is obtained from the metadata server through the scheduling module, and a search operation is performed, that is, the existing data corresponding to the data description information is queried from each metadata information, and The data center corresponding to the data center index information of the queried stock data is determined as the target data center; if the requested operation type is a write operation, the status information is obtained from the metadata server through the scheduling module and the decision-making operation is performed, that is Based on the data description information and each status information, the scheduling plan corresponding to the data to be transmitted is determined; and based on the scheduling plan, the target data center is determined.

Then, the data plane interface information of the target data center is returned to the client, so that the client can construct an uplink and downlink data transmission channel corresponding to the service request based on the data plane interface information, so as to facilitate subsequent smooth transmission of the data to be transmitted.

Accordingly, in this embodiment of the present application, after step 330 is executed, if the request operation type included in the service request is a write operation, refer to Figure 8 to further perform the following steps:

Step 800: After determining that the write operation is completed, collect target metadata information of the target data center.

In the embodiment of the present application, when step 800 is executed, after it is determined that the write operation is completed, the target metadata information of the target data center is collected through the scheduling module.

Step 810: Based on the target metadata information, update the existing metadata information in the target information.

In the embodiment of the present application, when step 810 is executed, based on the target metadata information, the existing metadata information in the target information that has been recorded (that is, stored) in the metadata server is updated. In this way, it can be ensured that the The stored metadata information is consistent with the metadata information corresponding to each logical disk unit in each data center, which facilitates the subsequent accurate and rapid execution of newly received business requests, thereby ensuring business continuity.

In some embodiments, since in this application, a status information interface is deployed in each managed data center, in this way, the cross-regional data scheduling system can use the scheduling module to perform operations on the existing data in one or some data centers. In the specific implementation of data migration, refer to Figure 9, taking data migration between the first data center and the second data center as an example. The specific data scheduling process includes:

Step 900: Migrate the target stock data of the first data center to the second data center, where the first data center is any one of the data centers, and the second data center is any one of the data centers, except the first data center. any data center outside.

Step 910: After completing the data migration, update the existing metadata information based on the first metadata information of the first data center and the second metadata information of the second data center.

It should be noted that the above steps 900 to 910 only take data migration between the first data center and the second data center as an example. In actual applications, the data migration may be performed between the first data center, the second data center, and the third data center. Data migration between centers or even between more data centers is not specifically limited in this application.

For example, part of the target inventory data in the first data center is migrated to the second data center, the remaining target inventory data is migrated to the third data center, and so on.

The cross-region data scheduling method adopted in the embodiment of this application improves the performance of storage services of the established storage area network architecture through the above-mentioned cross-region data scheduling system; several data centers are managed through the scheduling module to facilitate customers It builds uplink and downlink data transmission channels for business requests with multiple data centers, thereby realizing load balancing scheduling based on status information; the above cross-regional data scheduling system also enhances the overall scalability of storage services, and can increase or decrease storage capacity by increasing or decreasing capacity. The number of managed data centers enables parallel expansion and contraction.

Furthermore, the data scheduling and data migration of incremental data and stock data through the scheduling module realizes imperceptible expansion and migration. At the same time, the internal storage resources of the managed data center are recycled based on metadata information, improving The infrastructure utilization of each data center.

Based on the same inventive concept, as shown in Figure 10, an embodiment of the present application provides a cross-region data scheduling device, including:

The receiving module 1010 is used to receive a service request sent by the client, where the service request includes the requested operation type and data description information of the data to be transmitted;

The acquisition module 1020 is used to obtain the target information of each data center based on the requested operation type. The storage architecture of each data center is built based on the storage area network. The target information includes metadata information and status information. At least one of, the metadata information represents the inventory data description information of each logical disk unit included in any data center, and the status information represents the operating status description information of any data center;

Determining module 1030, configured to determine the target data center corresponding to the service request based on the data description information and each target information, wherein the target data center is at least one of the various data centers;

The sending module 1040 is configured to return the data plane interface information of the target data center to the client, so that the client can construct an uplink and downlink data transmission channel corresponding to the service request based on the data plane interface information.

Determining the target data center corresponding to the service request based on the data description information and each target information, the determination module 1030 is used to:

In some possible embodiments, after returning the data plane interface information of the target data center to the client, the sending module 1040 is also used to:

In some possible embodiments, the determining module 1030 is used to migrate the target inventory data of the first data center to a second data center, where the first data center is any one of the respective data centers. , the second data center is any one of the data centers except the first data center; it is also used to, after the data migration is completed, the first element based on the first data center The data information, and the second metadata information of the second data center, update the existing metadata information.

Network operating status description information;

Auxiliary equipment operating status description information.

Data center index information;

Data offset of the inventory data of each logical disk unit;

The data length of the inventory data of each logical disk unit;

The timestamp of the inventory data for each logical disk unit.

Referring to Figure 11, an electronic device is provided in an embodiment of the present application, including: a processor 1101 and a memory 1102;

Memory 1102 is used to store computer programs executed by the processor 1101. The memory 1102 may be a volatile memory (volatile memory), such as a random-access memory (RAM); the memory 1102 may also be a non-volatile memory (non-volatile memory). memory), such as read-only memory, flash memory, hard disk drive (HDD) or solid-state drive (SSD), or the memory 1102 is capable of carrying or storing instructions or data. Without limitation, any other medium that may be in the form of the desired program code and capable of being accessed by a computer. The memory 1102 may be a combination of the above-described memories.

Processor 1101 may include one or more central processing units (central processing units). processing unit (CPU), graphics processing unit (GPU) or digital processing unit, etc.

The specific connection medium between the above-mentioned memory 1102 and the processor 1101 is not limited in the embodiment of the present application. In the embodiment of the present application, the memory 1102 and the processor 1101 are connected through a bus 1103 in Figure 11. The bus 1103 is represented by a thick line in Figure 11. The bus 1103 can be divided into an address bus, a data bus, a control bus, etc. For ease of presentation, only one thick line is used in Figure 11, but it does not mean that there is only one bus or one type of bus.

The memory stores program code. When the program code is executed by the processor 1101, it causes the processor 1101 to perform any of the methods performed in the above embodiments.

Since the electronic device is an electronic device that performs the method in the embodiment of the present application, and the principle of solving the problem of the electronic device is similar to that of the method, the implementation of the electronic device can be referred to the implementation of the method, and repeated details will not be repeated.

Based on the same inventive concept, embodiments of the present application provide a computer-readable storage medium on which computer program instructions are stored. When the computer program instructions are executed by a processor, any one of the methods in the above embodiments can be implemented.

Those skilled in the art will understand that embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the present application. It will be understood that each process and/or block in the flowchart illustrations and/or block diagrams, and combinations of processes and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing device produce a use Means for implementing the functions specified in one process or processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions The device implements the functions specified in the process or processes in the flowchart and/or the block or blocks in the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device. Instructions provide steps for implementing the functions specified in a process or processes in a flowchart diagram and/or in a block or blocks in a block diagram.

Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. In this way, if these modifications and variations of the present application fall within the scope of the claims of the present application and equivalent technologies, the present application is also intended to include these modifications and variations.

Claims

A cross-region data scheduling method is characterized by including:

Receive a service request sent by the client, where the service request includes the requested operation type and data description information of the data to be transmitted;

Based on the request operation type, the target information of each data center is obtained, where the storage architecture of each data center is built based on the storage area network, and the target information includes at least one of metadata information and status information, so The metadata information represents the inventory data description information of each logical disk unit contained in any data center, and the status information represents the operating status description information of any data center;

Based on the data description information and each target information, determine the target data center corresponding to the service request, wherein the target data center is at least one of the various data centers;

The data plane interface information of the target data center is returned to the client, so that the client constructs an uplink and downlink data transmission channel corresponding to the service request based on the data plane interface information.
The method of claim 1, wherein if the requested operation type is a read operation, the target information is the metadata information; if the requested operation type is a write operation, the target information is the status information;

Determining the target data center corresponding to the service request based on the data description information and each target information includes:

If the requested operation type is a read operation, query the inventory data corresponding to the data description information from each metadata information, and determine the data center corresponding to the data center index information of the queried inventory data. For the target data center;

If the requested operation type is a write operation, determine the scheduling plan corresponding to the data to be transmitted based on the data description information and the respective status information, and determine the target data center based on the scheduling plan, where , the status information is collected regularly through the status information interface corresponding to any data center.
The method of claim 2, wherein after returning the data plane interface information of the target data center to the client, it further includes:

After determining that the write operation is completed, collect target metadata information of the target data center;

Based on the target metadata information, existing metadata information in the target information is updated.
The method of claim 1, wherein the method includes:

Migrate the target inventory data of the first data center to a second data center, where the first data center is any one of the data centers, and the second data center is one of the data centers, Any data center except the first data center;

After the data migration is completed, the existing metadata information is updated based on the first metadata information of the first data center and the second metadata information of the second data center.
The method according to any one of claims 1 to 4, characterized in that the status information includes part or all of the following information:

Network operating status description information;

The network device operating status description information of the storage area network;

Auxiliary equipment operating status description information.
The method according to any one of claims 1 to 4, characterized in that the metadata information includes part or all of the following information:

Data center index information;

Data offset of the inventory data of each logical disk unit;

The data length of the inventory data of each logical disk unit;

The timestamp of the inventory data for each logical disk unit.
A cross-regional data scheduling device, characterized by including:

A receiving module, configured to receive a service request sent by the client, where the service request includes the requested operation type and data description information of the data to be transmitted;

The acquisition module is used to obtain the target information of each data center based on the request operation type. The storage architecture of each data center is built based on the storage area network. The target information includes metadata information and status information. At least one, the metadata information represents the inventory data description information of each logical disk unit included in any data center, and the status information represents the operating status description information of any data center;

Determining module, configured to determine the target data center corresponding to the service request based on the data description information and each target information, wherein the target data center is at least one of the various data centers;

A sending module, configured to return the data plane interface information of the target data center to the client, so that the client can construct an uplink and downlink data transmission channel corresponding to the service request based on the data plane interface information.
The device of claim 7, wherein if the requested operation type is a read operation, the target information is the metadata information; if the requested operation type is a write operation, the target information is the status information;

Determine the target data center corresponding to the service request based on the data description information and each target information, and the determination module is used to:

If the requested operation type is a read operation, query the inventory data corresponding to the data description information from each metadata information, and determine the data center corresponding to the data center index information of the queried inventory data. For the target data center;

If the requested operation type is a write operation, determine the scheduling plan corresponding to the data to be transmitted based on the data description information and the respective status information, and determine the target data center based on the scheduling plan, where , the status information is collected regularly through the status information interface corresponding to any data center.
An electronic device, characterized in that the electronic device includes a processor and a memory,

The memory is used to store computer programs or instructions;

The processor is configured to execute computer programs or instructions in the memory, so that the method described in any one of claims 1-6 is executed.
A computer-readable storage medium with computer program instructions stored thereon, characterized in that when the computer program instructions are executed by a processor, the steps of the method described in any one of claims 1-6 are implemented.