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

Abstract

The application relates to the technical field of cloud computing, in particular to a cross-region data scheduling method and device, equipment and a storage medium, which are used for solving the problems of low business request processing efficiency and unguaranteed business continuity in the prior art. The method comprises the following steps: obtaining target information of each data center based on a request operation type contained in a business request sent by a client; and determining and sending data plane interface information of a target data center corresponding to the business request to the client based on data description information of to-be-transmitted data contained in the business request and the target information, wherein the target information comprises at least one of metadata information and state information, the metadata information represents stock data description information of each logical disk unit contained in any data center, and the state information represents running state description information of any data center; thus, the business request processing efficiency is improved, and the continuity of the business is guaranteed.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and in particular to a cross-regional data scheduling method, apparatus, device and storage medium. Background Technology

[0002] With the development of cloud computing technology, cloud storage, which is easy to use and access and does not require customers to build data centers, is gaining increasing acceptance. Storage Area Network (SAN) is a network-centric storage architecture that typically includes servers (hosts), storage devices (Logical Disk Units (LUNs) or disk arrays), bridges, and multiplexers. All devices are connected to Fibre Channel switches, making it suitable for services requiring high throughput and low latency.

[0003] Under current technology, cloud storage service providers often build SANs within data centers and implement security and data protection measures for the data center internally. As a result, when the network quality of the data center is poor or the remaining capacity is low, it cannot process client business requests, such as business I / O requests, in a timely manner, resulting in low efficiency in processing business requests and failing to guarantee business continuity. Summary of the Invention

[0004] This application provides a cross-regional data scheduling method, apparatus, device, and storage medium to improve the efficiency of business request processing and ensure business continuity.

[0005] The specific technical solutions provided in this application are as follows:

[0006] In a first aspect, embodiments of this application provide a cross-regional data scheduling method, including:

[0007] Receive a service request sent by the client, wherein the service request includes the request operation type and data description information of the data to be transmitted;

[0008] Based on the requested operation type, target information for each data center is obtained. The storage architecture of each data center is built on a storage area network. The target information includes at least one of metadata information and status information. The metadata information represents the existing 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.

[0009] Based on the data description information and each target information, the target data center corresponding to the service request is determined, wherein the target data center is at least one of the data centers;

[0010] The data plane interface information of the target data center is returned to the client, so that the client can construct the uplink and downlink data transmission channels corresponding to the service request based on the data plane interface information.

[0011] In some possible embodiments, if the request operation type is a read operation, then the target information is the metadata information; if the request operation type is a write operation, then the target information is the status information.

[0012] The step of determining the target data center corresponding to the service request based on the data description information and various target information includes:

[0013] If the request operation type is a read operation, then query the existing data corresponding to the data description information from the various metadata information, and determine the data center corresponding to the data center index information of the queried existing data as the target data center;

[0014] If the requested operation type is a write operation, then based on the data description information and the various status information, a scheduling plan corresponding to the data to be transmitted is determined, and based on the scheduling plan, the target data center is determined, wherein the status information is periodically collected through the status information interface corresponding to any data center.

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

[0016] After the write operation is completed, collect the target metadata information of the target data center;

[0017] Based on the target metadata information, update the existing metadata information in the target information.

[0018] In some possible embodiments, the method includes:

[0019] The target existing data in the first data center is migrated to the second data center, wherein the first data center is any one of the data centers, and the second data center is any one of the data centers other than the first data center.

[0020] 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.

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

[0022] Network operating status description information;

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

[0024] Description of the operating status of auxiliary equipment.

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

[0026] Data center index information;

[0027] The data offset of the stored data in each logical disk unit;

[0028] The length of stored data in each logical disk unit;

[0029] The timestamp of the stored data in each logical disk unit.

[0030] Secondly, embodiments of this application provide a cross-regional data scheduling device, comprising:

[0031] The receiving module is used to receive service requests sent by the client, wherein the service request includes the request operation type and data description information of the data to be transmitted;

[0032] The acquisition module is used to acquire target information of each data center based on the request operation type. The storage architecture of each data center is built on a storage area network. The target information includes at least one of metadata information and status information. The metadata information represents the existing 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.

[0033] The determining module is used 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 data centers;

[0034] The sending module is used to return the data plane interface information of the target data center to the client, so that the client can construct the uplink and downlink data transmission channels corresponding to the service request based on the data plane interface information.

[0035] In some possible embodiments, if the request operation type is a read operation, then the target information is the metadata information; if the request operation type is a write operation, then the target information is the status information.

[0036] The module for determining the target data center corresponding to the service request, based on the data description information and various target information, is used to:

[0037] If the request operation type is a read operation, then query the existing data corresponding to the data description information from the various metadata information, and determine the data center corresponding to the data center index information of the queried existing data as the target data center;

[0038] If the requested operation type is a write operation, then based on the data description information and the various status information, a scheduling plan corresponding to the data to be transmitted is determined, and based on the scheduling plan, the target data center is determined, wherein the status information is periodically collected through the status information interface corresponding to any data center.

[0039] In some possible embodiments, after returning the data plane interface information of the target data center to the client, the sending module is further configured to:

[0040] After the write operation is completed, collect the target metadata information of the target data center;

[0041] Based on the target metadata information, update the existing metadata information in the target information.

[0042] In some possible embodiments, the determining module is used to migrate the target existing data of the first data center to the second data center, wherein the first data center is any one of the various data centers, and the second data center is any one of the various data centers other than the first data center; it is also used to 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 after the data migration is completed.

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

[0044] Network operating status description information;

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

[0046] Description of the operating status of auxiliary equipment.

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

[0048] Data center index information;

[0049] The data offset of the stored data in each logical disk unit;

[0050] The length of stored data in each logical disk unit;

[0051] The timestamp of the stored data in each logical disk unit.

[0052] Thirdly, embodiments of this application provide an electronic device, which includes a processor and a memory.

[0053] The memory is used to store computer programs or instructions;

[0054] The processor is configured to execute computer programs or instructions in memory, such that the method described in any one of the first aspects is performed.

[0055] Fourthly, embodiments of this application provide a computer-readable storage medium having computer program instructions stored thereon, which, when executed by a processor, implement the steps of the method described in any of the first aspects above.

[0056] In this embodiment, based on the request operation type included in the received service request sent by the client, target information of each data center is obtained. Then, based on the data description information of the data to be transmitted included in the service request, the target data center corresponding to the service request is determined, and the data plane interface information of the target data center is returned to the client. This allows the client to construct uplink and downlink data transmission channels corresponding to the service request based on the data plane interface information. Each data center's storage architecture is built on a storage area network. The target information includes at least one of metadata information and status information. The metadata information represents the existing 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. The target data center is at least one of the various data centers. In this way, the client can construct uplink and downlink channels corresponding to the service request with multiple data centers, decoupling the client from the default data center, improving the performance of the storage service of the built storage area network architecture, thereby improving the efficiency of service request processing and maximizing service continuity. Attached Figure Description

[0057] Figure 1 This is a schematic diagram illustrating an application scenario in an embodiment of this application;

[0058] Figure 2 This is a schematic diagram of the architecture of a cross-regional data scheduling system according to an embodiment of this application;

[0059] Figure 3 This is a flowchart illustrating a cross-regional data scheduling method according to an embodiment of this application;

[0060] Figure 4 This is a schematic diagram of the processing logic of the cross-regional data scheduling system in the embodiments of this application;

[0061] Figure 5 This is a flowchart illustrating a method for determining a target data center according to an embodiment of this application;

[0062] Figure 6 This is a flowchart illustrating another method for determining a target data center in an embodiment of this application;

[0063] Figure 7 This is a logical diagram illustrating the cross-regional data scheduling system's data scheduling through a scheduling module in an embodiment of this application.

[0064] Figure 8 This is a flowchart illustrating a method for updating existing metadata information in target information according to an embodiment of this application.

[0065] Figure 9 This is a flowchart illustrating another cross-regional data scheduling method in an embodiment of this application;

[0066] Figure 10 This is a schematic diagram of the logical architecture of a cross-regional data scheduling device in an embodiment of this application;

[0067] Figure 11 This is a schematic diagram of the physical architecture of the electronic device in the embodiments of this application. Detailed Implementation

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

[0069] It should be noted that the terms "first," "second," "third," "fourth," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in sequences other than those illustrated or described herein.

[0070] To address the issues of low efficiency in processing business requests and the inability to guarantee business continuity under existing technologies, this application embodiment obtains target information for each data center based on the request operation type contained in the received business request sent by the client. Then, based on the data description information of the data to be transmitted contained in the business request, the target data center corresponding to the business request is determined, and the data plane interface information of the target data center is returned to the client. This allows the client to construct the uplink and downlink data transmission channels corresponding to the business request based on the data plane interface information. In this embodiment, the storage architecture of each data center is built based on a storage area network. The target information includes at least one of metadata information and status information. The metadata information represents the existing 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. The target data center is at least one of the various data centers.

[0071] In this way, the client can build uplink and downlink channels corresponding to business requests with multiple data centers, decoupling the client from the default data center, improving the performance of the storage service of the established storage area network architecture, thereby improving the efficiency of business request processing and maximizing business continuity.

[0072] Furthermore, the above method enables load balancing scheduling of multiple data centers based on status information, allowing incremental and existing data to be migrated in a schedulable manner, achieving seamless expansion and migration, and enhancing the overall scalability of the storage area.

[0073] The preferred embodiments of this application will be further described in detail below with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are only for illustration and explanation of this application and are not intended to limit this application. Furthermore, the embodiments of this application and the features in the embodiments can be combined with each other without conflict.

[0074] Figure 1 A schematic diagram illustrating an application scenario of an embodiment of this application is shown. (See attached diagram.) Figure 1 As shown in the embodiments of this application, the above application scenario includes a client 1, a cross-regional data scheduling system 2, and a data center 3. The client 1 and the cross-regional data scheduling system 2 communicate via a communication network. Optionally, the communication network can be a wired network or a wireless network. The client 1 and the cross-regional data scheduling system 2 can be directly or indirectly connected via wired or wireless communication methods; this application does not impose any restrictions on this connection.

[0075] Correspondingly, the cross-regional data scheduling system 2 and the data center 3 can also communicate through a communication network, which can be a wired network or a wireless network. The cross-regional data scheduling system 2 and the data center 3 can be directly or indirectly connected through wired or wireless communication, and this application does not impose any restrictions on this.

[0076] In this embodiment, the cross-regional data scheduling system 2 is an electronic device that carries the program of the cross-regional data scheduling method provided in this embodiment. The electronic device may be a smart terminal, computer, tablet computer, laptop computer, e-book reader, or other devices; it may also be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0077] Figure 2 This illustration shows a schematic diagram of the architecture of a cross-regional data scheduling system provided in an embodiment of this application. (See also...) Figure 2 As shown in this embodiment, the cross-regional data scheduling system includes a scheduling module, a data acquisition module, and a metadata server.

[0078] The metadata server is used to record metadata information for each logical disk unit contained in each managed data center, and also to record the corresponding status information of each data center; wherein, the metadata information and / or status information are used by the scheduling module to schedule business requests between the data plane interfaces of different data centers.

[0079] The data acquisition module is used to periodically obtain the status information of different data centers through their respective status information interfaces, and record or update the status information to the metadata server.

[0080] The scheduling module is used to collect metadata information of 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, make decisions based on the metadata information or status information in the metadata server, determine the data plane interface information of the target data center for real-time business requests, and perform migration scheduling of existing data based on the status information of each data center; it is also used to update the metadata information recorded in the metadata server based on the target metadata information of the target data center after the write is completed after a business request (e.g., a write request).

[0081] It should be noted that the cross-regional data scheduling system provided in this application includes an acquisition module, a metadata server, and a scheduling module, which can be deployed simultaneously in one physical device or separately in different physical devices; no specific limitation is made here.

[0082] See Figure 3 As shown in the figure, the cross-regional data scheduling method provided in this application embodiment has the following specific process:

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

[0084] See Figure 4 As shown in this embodiment, before performing step 300, it is necessary to build a status information interface in each data center included in the cross-regional data scheduling system, so as to periodically obtain the status information of each data center through the acquisition module, and record or update the obtained status information to the metadata server.

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

[0086] After the architecture of the cross-regional data scheduling system is built, step 300 is executed to receive service requests sent by the client. The service requests involved in this embodiment include service I / O requests. Therefore, each service request includes a request operation type and data description information of the data to be transmitted, wherein the data description information includes data offset and data length.

[0087] In some embodiments, the data to be transmitted may be data to be read from one or more data centers, data to be written to one or more data centers, or the aforementioned data to be read and data to be written.

[0088] Step 310: Based on the request operation type, obtain the target information of each data center. The storage architecture of each data center is built on a storage area network. The target information includes at least one of metadata information and status information. The metadata information represents the existing 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.

[0089] In this embodiment of the application, when performing step 310, the target information of each data center is obtained based on the request operation type contained in the received business request. That is, if the request operation type is a read operation, the metadata information of each data center is obtained; if the request operation type is a write operation, the status information of each data center is obtained.

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

[0091] 1. Data center index information;

[0092] 2. Data offset of the stored data in each logical disk unit;

[0093] 3. The length of the stored data in each logical disk unit;

[0094] 4. Timestamps of the stored data in each logical disk unit.

[0095] 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 in Table 1:

[0096] Table 1. Overview of Metadata Information for Logical Disk Units

[0097] serial number Data offset Data length Data Center Index Timestamp … 1 0 4K 3 t1 … 2 4K 128K 1 t3 … 3 … … … … … 4 … … … … … … … … … … …

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

[0099] 1. Network operating status description information;

[0100] 2. Description information of the network device operating status of the storage area network;

[0101] 3. Description of the operating status of auxiliary equipment.

[0102] In practical applications, as shown in Table 2, the status information corresponding to each data center can be recorded using Table 2:

[0103] Table 2. Overview of Data Center Status Information

[0104] Data Center Number Message latency / ms Bandwidth utilization Total capacity Capacity utilization temperature … 1 10 80％ 3.6PB 70％ 15℃ … 2 25 50％ 1.5PB 30％ 20℃ … 3 … … … … … … … … … … … … … … … … … … … …

[0105] Step 320: Based on the data description information and each target information, determine the target data center corresponding to the business request, wherein the target data center is at least one of the various data centers.

[0106] In this embodiment of the application, when performing step 320, different data scheduling processes are executed depending on the type of request operation.

[0107] Scenario 1: If the requested operation type is a read operation, see [link / reference]. Figure 5 As shown, the specific process is as follows:

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

[0109] Step 3202: Determine the data center corresponding to the data center index information of the retrieved existing data as the target data center.

[0110] Scenario 2: If the requested operation type is a write operation, see [link / reference]. Figure 6 As shown, the specific process is as follows:

[0111] Step 3201': Based on the data description information and various status information, determine the scheduling plan corresponding to the data to be transmitted. The status information is collected periodically through the status information interface of any data center.

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

[0113] Step 330: Return the data plane interface information of the target data center to the client so that the client can build the uplink and downlink data transmission channels corresponding to the business request based on the data plane interface information.

[0114] In this embodiment of the 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, when executing step 330, the data plane interface information of the target data center is returned to the client. In this way, the client can construct 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 transmission of the data to be transmitted.

[0115] In practical applications, business requests typically include both read and write operations. Therefore, refer to... Figure 7 As shown, Figure 7 This illustration shows a logical diagram of the cross-regional data scheduling system performing data scheduling through a scheduling module in an embodiment of this application.

[0116] During the implementation of this application, see [reference]. Figure 7 As shown, after executing step 300 and before executing step 310, the request operation types contained in the business request need to be classified to distinguish between read operations and write operations. Then, the subsequent data scheduling process is executed in parallel.

[0117] In practice, if the requested operation type is a read operation, the scheduling module retrieves various metadata information from the metadata server and performs a search operation. That is, it queries the existing data corresponding to the data description information from various metadata information and determines the data center corresponding to the data center index information of the queried existing data as the target data center. If the requested operation type is a write operation, the scheduling module retrieves status information from the metadata server and performs a decision operation. That is, based on the data description information and various status information, it determines the scheduling plan corresponding to the data to be transmitted and determines the target data center based on the scheduling plan.

[0118] Then, the data plane interface information of the target data center is returned to the client, so that the client can build the uplink and downlink data transmission channels corresponding to the business request based on the data plane interface information, so as to facilitate the smooth transmission of the data to be transmitted later.

[0119] Accordingly, in this embodiment of the application, after executing step 330, if the request operation type included in the business request is a write operation, then refer to... Figure 8 As shown, further perform the following steps:

[0120] Step 800: After confirming that the write operation is complete, collect the target metadata information of the target data center.

[0121] In this embodiment of the application, when performing step 800, after determining that the write operation has been completed, the target metadata information of the target data center is collected through the scheduling module.

[0122] Step 810: Update the existing metadata information in the target information based on the target metadata information.

[0123] In this embodiment of the application, when performing step 810, the existing metadata information in the target information that has been recorded (i.e., stored) in the metadata server is updated based on the target metadata information. In this way, the metadata information stored in the metadata server can be consistent with the metadata information corresponding to each logical disk unit in each data center, which facilitates the accurate and rapid execution of newly received business requests and thus ensures the continuity of business.

[0124] In some embodiments, since a status information interface is deployed in each managed data center in this application, the cross-regional data scheduling system can migrate existing data in one or more data centers through the scheduling module. For specific implementation details, please refer to [reference needed]. Figure 9 As shown, taking the data migration between the first data center and the second data center as an example, the specific data scheduling process includes:

[0125] Step 900: Migrate the target existing data in the first data center to the second data center. The first data center is any one of the data centers, and the second data center is any one of the data centers other than the first data center.

[0126] Step 910: After the data migration is completed, 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.

[0127] It should be noted that steps 900-910 above are only examples of data migration between the first data center and the second data center. In actual applications, data migration can be performed between the first data center, the second data center, the third data center, or even more data centers. This application does not make any specific limitations.

[0128] For example, some of the target existing data in the first data center can be migrated to the second data center, and the remaining target existing data can be migrated to the third data center, and so on.

[0129] This application embodiment discloses a cross-regional data scheduling method that improves the performance of storage services with an established storage area network architecture through the aforementioned cross-regional data scheduling system. By managing several data centers through the scheduling module, it facilitates the establishment of uplink and downlink data transmission channels for business requests between clients and multiple data centers, thereby achieving load balancing scheduling based on status information. The aforementioned cross-regional data scheduling system also enhances the overall scalability of the storage service, allowing for parallel expansion and contraction by increasing or decreasing the number of managed data centers.

[0130] Furthermore, by scheduling incremental and existing data through the scheduling module, seamless expansion and migration are achieved. At the same time, the internal storage resources of managed data centers are reclaimed based on metadata information, improving the infrastructure utilization of each data center.

[0131] Based on the same inventive concept, see [reference] Figure 10 As shown in the figure, this application provides a cross-regional data scheduling device, including:

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

[0133] The acquisition module 1020 is used to acquire target information of each data center based on the request operation type. The storage architecture of each data center is built on a storage area network. The target information includes at least one of metadata information and status information. The metadata information represents the existing 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.

[0134] The determining module 1030 is used 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 data centers;

[0135] The sending module 1040 is used to return the data plane interface information of the target data center to the client, so that the client can construct the uplink and downlink data transmission channels corresponding to the service request based on the data plane interface information.

[0136] In some possible embodiments, if the request operation type is a read operation, then the target information is the metadata information; if the request operation type is a write operation, then the target information is the status information.

[0137] Based on the data description information and various target information, the target data center corresponding to the service request is determined. The determining module 1030 is used for:

[0138] If the request operation type is a read operation, then query the existing data corresponding to the data description information from the various metadata information, and determine the data center corresponding to the data center index information of the queried existing data as the target data center;

[0139] If the requested operation type is a write operation, then based on the data description information and the various status information, a scheduling plan corresponding to the data to be transmitted is determined, and based on the scheduling plan, the target data center is determined, wherein the status information is periodically collected through the status information interface corresponding to any data center.

[0140] In some possible embodiments, after returning the data plane interface information of the target data center to the client, the sending module 1040 is further configured to:

[0141] After the write operation is completed, collect the target metadata information of the target data center;

[0142] Based on the target metadata information, update the existing metadata information in the target information.

[0143] In some possible embodiments, the determining module 1030 is used to migrate the target existing data of the first data center to the second data center, wherein the first data center is any one of the data centers and the second data center is any one of the data centers other than the first data center; it is also used to 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 after the data migration is completed.

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

[0145] Network operating status description information;

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

[0147] Description of the operating status of auxiliary equipment.

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

[0149] Data center index information;

[0150] The data offset of the stored data in each logical disk unit;

[0151] The length of stored data in each logical disk unit;

[0152] The timestamp of the stored data in each logical disk unit.

[0153] See Figure 11 As shown in the embodiment of this application, an electronic device is provided, including: a processor 1101 and a memory 1102;

[0154] Memory 1102 is used to store computer programs executed by processor 1101. Memory 1102 may be volatile memory, such as random-access memory (RAM); memory 1102 may also be non-volatile memory, such as read-only memory, flash memory, hard disk drive (HDD), or solid-state drive (SSD); or memory 1102 may be any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but is not limited thereto. Memory 1102 may be a segment of the above-described memories.

[0155] The processor 1101 may include one or more central processing units (CPUs), graphics processing units (GPUs), or digital processing units, etc.

[0156] This application embodiment does not limit the specific connection medium between the memory 1102 and the processor 1101. This application embodiment... Figure 11 The memory 1102 and the processor 1101 are connected via a bus 1103, and the bus 1103 is in Figure 11 The bus 1103, represented by thick lines, can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 11 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0157] The memory stores program code, which, when executed by the processor 1101, causes the processor 1101 to perform any of the methods described in the above embodiments.

[0158] Since the electronic device is the same electronic device that executes the method in the embodiments of this application, and the principle of the electronic device in solving the problem is similar to that of the method, the implementation of the electronic device can refer to the implementation of the method, and the repeated parts will not be described again.

[0159] Based on the same inventive concept, embodiments of this application provide a computer-readable storage medium storing computer program instructions thereon, which, when executed by a processor, implement any one of the methods in the above embodiments.

[0160] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can 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.) containing computer-usable program code.

[0161] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0162] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more processes in a flowchart and / or one or more blocks in a block diagram.

[0163] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more blocks in the block diagram.

[0164] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A cross-regional data scheduling method, characterized in that, include: Receive a service request sent by a client, wherein the service request includes a request operation type and data description information of the data to be transmitted; Based on the requested operation type, target information for each data center is obtained. The storage architecture of each data center is built on a Storage Area Network (SAN). The target information includes at least one of metadata information and status information. The metadata information represents the existing 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, the target data center corresponding to the service request is determined, wherein the target data center is at least one of the data centers; The data plane interface information of the target data center is returned to the client, so that the client can construct the uplink and downlink data transmission channels corresponding to the service request based on the data plane interface information. The data description information includes data offset and data length, and the metadata information includes some or all of the following: data center index information; data offset of the existing data in each logical disk unit; data length of the existing data in each logical disk unit; timestamp of the existing data in each logical disk unit; if the request operation type is a read operation, then the target information is the metadata information; determining the target data center corresponding to the service request based on the data description information and each target information includes: Based on the data offset and data length, the existing data corresponding to the data description information is queried from the various metadata information, and the data center corresponding to the data center index information of the queried existing data is determined as the target data center.

2. The method as described in claim 1, characterized in that, If the request operation type is a write operation, then the target information is the status information; determining the target data center corresponding to the business request based on the data description information and each target information includes: Based on the data description information and the various status information, a scheduling plan corresponding to the data to be transmitted is determined, and based on the scheduling plan, the target data center is determined. The status information is periodically collected through the status information interface corresponding to any data center.

3. The method as described in claim 2, characterized in that, After returning the data plane interface information of the target data center to the client, the method further includes: After the write operation is completed, collect the target metadata information of the target data center; Based on the target metadata information, update the existing metadata information in the target information.

4. The method as described in claim 1, characterized in that, The method includes: The target existing data in the first data center is migrated to the second data center, wherein the first data center is any one of the data centers, and the second data center is any one of the data centers other than 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.

5. The method according to any one of claims 1-4, characterized in that, 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; Description of the operating status of auxiliary equipment.

6. A cross-regional data scheduling device, characterized in that, include: The receiving module is used to receive service requests sent by the client, wherein the service request includes the request operation type and data description information of the data to be transmitted; The acquisition module is used to acquire target information of each data center based on the request operation type. The storage architecture of each data center is built on a storage area network (SAN). The target information includes at least one of metadata information and status information. The metadata information represents the existing 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. The determining module is used 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 data centers; The sending module is used to return the data plane interface information of the target data center to the client, so that the client can construct the uplink and downlink data transmission channels corresponding to the service request based on the data plane interface information. The data description information includes data offset and data length, and the metadata information includes some or all of the following: data center index information; data offset of the existing data in each logical disk unit; data length of the existing data in each logical disk unit; timestamp of the existing data in each logical disk unit; if the request operation type is a read operation, then the target information is the metadata information; the determining module is used to: based on the data offset and data length, query the existing data corresponding to the data description information from the various metadata information, and determine the data center corresponding to the data center index information of the queried existing data as the target data center.

7. The apparatus as claimed in claim 6, characterized in that, If the requested operation type is a write operation, then the target information is the status information; the determining module is used to: Based on the data description information and the various status information, a scheduling plan corresponding to the data to be transmitted is determined, and based on the scheduling plan, the target data center is determined. The status information is periodically collected through the status information interface corresponding to any data center.

8. 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 a computer program or instructions in memory, such that the method of any one of claims 1-5 is performed.

9. A computer-readable storage medium having computer program instructions stored thereon, characterized in that, When executed by a processor, the computer program instructions implement the steps of the method described in any one of claims 1-5.

Images