WO2024021470A1 - Procédé et appareil de programmation de données entre des régions, dispositif, et support de stockage - Google Patents

Procédé et appareil de programmation de données entre des régions, dispositif, et support de stockage Download PDF

Info

Publication number
WO2024021470A1
WO2024021470A1 PCT/CN2022/141408 CN2022141408W WO2024021470A1 WO 2024021470 A1 WO2024021470 A1 WO 2024021470A1 CN 2022141408 W CN2022141408 W CN 2022141408W WO 2024021470 A1 WO2024021470 A1 WO 2024021470A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
information
data center
target
metadata
Prior art date
Application number
PCT/CN2022/141408
Other languages
English (en)
Chinese (zh)
Inventor
颜嘉伟
黄润怀
林洁琬
肖露
吴文峰
陈杰
张维杰
Original Assignee
天翼云科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 天翼云科技有限公司 filed Critical 天翼云科技有限公司
Publication of WO2024021470A1 publication Critical patent/WO2024021470A1/fr

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21Design, administration or maintenance of databases
    • G06F16/214Database migration support
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1097Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Definitions

  • 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.
  • SAN Storage Area Network
  • servers hosts
  • storage devices logical disk units (Logical Disk Units, LUNs) or disk arrays
  • bridges and multiplexers are 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.
  • 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.
  • 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.
  • embodiments of the present application provide a cross-region data scheduling method, including:
  • 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;
  • the target 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 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:
  • 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;
  • 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 further includes:
  • the method includes:
  • 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 status information includes some or all of the following information:
  • the network device operating status description information of the storage area network
  • the metadata information includes some or all of the following information:
  • 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.
  • the target information is the metadata information; if the requested operation type is a write operation, the target information is the status information. ;
  • 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;
  • 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 sending module after returning the data plane interface information of the target data center to the client, the sending module is also used to:
  • 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.
  • the status information includes some or all of the following information:
  • the network device operating status description information of the storage area network
  • the metadata information includes some or all of the following information:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Figure 1 shows a schematic diagram of an application scenario according to 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.
  • 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.
  • 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.
  • 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.
  • CDN Content Distribution Network
  • Figure 2 shows a schematic architectural diagram of a cross-region data scheduling system provided 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.
  • 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.
  • 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.
  • 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.
  • step 300 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.
  • 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.
  • 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.
  • 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.
  • step 310 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.
  • Metadata information includes some or all of the following information:
  • status information includes some or all of the following information:
  • 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.
  • step 320 when step 320 is executed, different data scheduling processes are executed based on different request operation types.
  • 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.
  • 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.
  • step 320 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.
  • 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;
  • 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.
  • 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.
  • step 330 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.
  • step 800 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.
  • step 810 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.
  • the cross-regional data scheduling system can use the scheduling module to perform operations on the existing data in one or some data centers.
  • 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.
  • steps 900 to 910 only take data migration between the first data center and the second data center as an example.
  • 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.
  • 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.
  • the data scheduling and data migration of incremental data and stock data through the scheduling module realizes imperceptible expansion and migration.
  • the internal storage resources of the managed data center are recycled based on metadata information, improving The infrastructure utilization of each data center.
  • 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.
  • the target information is the metadata information; if the requested operation type is a write operation, the target information is the status information. ;
  • the determination module 1030 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:
  • 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;
  • 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 sending module 1040 is also used to:
  • 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.
  • the status information includes some or all of the following information:
  • the network device operating status description information of the storage area network
  • the metadata information includes some or all of the following information:
  • an electronic device 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.
  • 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.
  • CPU central processing unit
  • GPU graphics processing unit
  • 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.
  • 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.
  • the program code When executed by the processor 1101, it causes the processor 1101 to perform any of the methods performed in the above embodiments.
  • 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.
  • embodiments of the present application provide a computer-readable storage medium on which computer program instructions are stored.
  • the computer program instructions are executed by a processor, any one of the methods in the above embodiments can be implemented.
  • 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.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente demande, qui relève du domaine technique de l'informatique en nuage, concerne, en particulier, un procédé et un appareil de programmation de données entre des régions, un dispositif et un support de stockage, qui sont utilisés pour résoudre les problèmes dans l'état de la technique selon lesquels l'efficacité de traitement d'une demande de service est faible et la continuité d'un service ne peut pas être garantie. Le procédé comprend : l'acquisition d'informations cibles de centres de données sur la base d'un type d'opération de demande compris dans une demande de service envoyée par un client et, sur la base d'informations de description de données pour des données à transmettre comprises dans la demande de service et des informations cibles, la détermination et l'envoi au client d'informations d'interface de plan de données d'un centre de données cible correspondant à la demande de service, les informations cibles comprenant des informations de métadonnées et/ou des informations d'état, les informations de métadonnées représentant des informations de description de données de base de chaque unité de disque logique comprise dans tout centre de données, et les informations d'état représentant des informations de description d'état d'opération de tout centre de données. De cette manière, l'efficacité de traitement d'une demande de service est améliorée et la continuité d'un service est garantie.
PCT/CN2022/141408 2022-07-28 2022-12-23 Procédé et appareil de programmation de données entre des régions, dispositif, et support de stockage WO2024021470A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210899880.5A CN115292280A (zh) 2022-07-28 2022-07-28 一种跨区域的数据调度方法、装置、设备及存储介质
CN202210899880.5 2022-07-28

Publications (1)

Publication Number Publication Date
WO2024021470A1 true WO2024021470A1 (fr) 2024-02-01

Family

ID=83823298

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/141408 WO2024021470A1 (fr) 2022-07-28 2022-12-23 Procédé et appareil de programmation de données entre des régions, dispositif, et support de stockage

Country Status (2)

Country Link
CN (1) CN115292280A (fr)
WO (1) WO2024021470A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118018549A (zh) * 2024-02-06 2024-05-10 中科云谷科技有限公司 构建跨区域服务系统的方法、处理器、装置及系统

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115292280A (zh) * 2022-07-28 2022-11-04 天翼云科技有限公司 一种跨区域的数据调度方法、装置、设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110233865A (zh) * 2018-03-06 2019-09-13 阿里巴巴集团控股有限公司 跨区域服务调用方法、装置和系统
CN111064802A (zh) * 2019-12-26 2020-04-24 北京奇艺世纪科技有限公司 一种网络请求的处理方法、装置、电子设备及存储介质
JP2021002207A (ja) * 2019-06-21 2021-01-07 Necソリューションイノベータ株式会社 情報運搬装置、バックアップ装置、情報運搬方法、バックアップ方法、プログラム、及び記録媒体
CN113992680A (zh) * 2021-11-10 2022-01-28 中国工商银行股份有限公司 应用于分布式多活系统的调度方法、装置、设备及介质
CN115292280A (zh) * 2022-07-28 2022-11-04 天翼云科技有限公司 一种跨区域的数据调度方法、装置、设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110233865A (zh) * 2018-03-06 2019-09-13 阿里巴巴集团控股有限公司 跨区域服务调用方法、装置和系统
JP2021002207A (ja) * 2019-06-21 2021-01-07 Necソリューションイノベータ株式会社 情報運搬装置、バックアップ装置、情報運搬方法、バックアップ方法、プログラム、及び記録媒体
CN111064802A (zh) * 2019-12-26 2020-04-24 北京奇艺世纪科技有限公司 一种网络请求的处理方法、装置、电子设备及存储介质
CN113992680A (zh) * 2021-11-10 2022-01-28 中国工商银行股份有限公司 应用于分布式多活系统的调度方法、装置、设备及介质
CN115292280A (zh) * 2022-07-28 2022-11-04 天翼云科技有限公司 一种跨区域的数据调度方法、装置、设备及存储介质

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118018549A (zh) * 2024-02-06 2024-05-10 中科云谷科技有限公司 构建跨区域服务系统的方法、处理器、装置及系统

Also Published As

Publication number Publication date
CN115292280A (zh) 2022-11-04

Similar Documents

Publication Publication Date Title
US10412170B2 (en) Retention-based data management in a network-based data store
EP2891051B1 (fr) Accès de niveau bloc à un stockage parallèle
WO2024021470A1 (fr) Procédé et appareil de programmation de données entre des régions, dispositif, et support de stockage
US20130332612A1 (en) Transmission of map/reduce data in a data center
US8135918B1 (en) Data de-duplication for iSCSI
CN107832423B (zh) 一种用于分布式文件系统的文件读写方法
US20150095384A1 (en) File transfer to a distributed file system
US9110820B1 (en) Hybrid data storage system in an HPC exascale environment
US9983823B1 (en) Pre-forking replicas for efficient scaling of a distribued data storage system
CN114201421B (zh) 一种数据流处理方法、存储控制节点及可读存储介质
US20210397373A1 (en) Peer Storage Compute Sharing Using Memory Buffer
US10922272B2 (en) Providing data across multiple clusters in a single namespace
WO2021213281A1 (fr) Procédé et système de lecture de données
CN110119304A (zh) 一种中断处理方法、装置及服务器
CN111159176A (zh) 一种海量流数据的存储和读取的方法和系统
CN113806300B (zh) 数据存储方法、系统、装置、设备及存储介质
CN115129621B (zh) 一种内存管理方法、设备、介质及内存管理模块
US11347413B2 (en) Opportunistic storage service
CN114625762A (zh) 一种元数据获取方法、网络设备及系统
US8386741B2 (en) Method and apparatus for optimizing data allocation
US20240036728A1 (en) Method and apparatus for processing data, reduction server, and mapping server
WO2024001863A1 (fr) Procédé de traitement de données et dispositif associé
US11301306B2 (en) Apparatus, systems, and methods for remote system batch processing
WO2023050856A1 (fr) Procédé de traitement de données et système de stockage
US11093493B1 (en) Dynamically switching between query and scan for optimizing table reads

Legal Events

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

Ref document number: 22952901

Country of ref document: EP

Kind code of ref document: A1