CN111090629B - Data file storage method, device, equipment and storage medium - Google Patents

Data file storage method, device, equipment and storage medium Download PDF

Info

Publication number
CN111090629B
CN111090629B CN201911349603.1A CN201911349603A CN111090629B CN 111090629 B CN111090629 B CN 111090629B CN 201911349603 A CN201911349603 A CN 201911349603A CN 111090629 B CN111090629 B CN 111090629B
Authority
CN
China
Prior art keywords
disaster recovery
copy
recovery domain
domain
file
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201911349603.1A
Other languages
Chinese (zh)
Other versions
CN111090629A (en
Inventor
郭琰
周智伟
韩朱忠
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Dameng Database Co Ltd
Original Assignee
Shanghai Dameng Database Co Ltd
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 Shanghai Dameng Database Co Ltd filed Critical Shanghai Dameng Database Co Ltd
Priority to CN201911349603.1A priority Critical patent/CN111090629B/en
Publication of CN111090629A publication Critical patent/CN111090629A/en
Application granted granted Critical
Publication of CN111090629B publication Critical patent/CN111090629B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/172—Caching, prefetching or hoarding of files
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The embodiment of the invention discloses a data file storage method, a device, equipment and a storage medium. The method comprises the following steps: dividing a data file to obtain a data file block, wherein the data file comprises file copies, determining the target copy space number matched with the file copy number in each disaster recovery domain according to the file copy number, the current idle copy space number of each disaster recovery domain and the available copy space number of each disaster recovery domain, and respectively storing the file copies in the data file block into disaster recovery domains corresponding to the target copy space numbers. Compared with the prior art, the embodiment of the invention realizes that the file copies in the data file block are respectively stored in the disaster recovery domains corresponding to the space numbers of the target copies, and solves the problem that the data file cannot be continuously stored in the disaster recovery domains subsequently due to uneven distribution of the file copies in the data file in the prior art.

Description

Data file storage method, device, equipment and storage medium
Technical Field
The embodiment of the invention relates to the technical field of data processing, in particular to a data file storage method, a device, equipment and a storage medium.
Background
A distributed file system refers to a system where the physical storage resources managed by the file system are not necessarily directly connected to a local node, but are connected to the node through a computer network, where the node can be simply understood as a computer. The distributed file system can extend a certain file system fixed at a certain place to any multiple places/multiple file systems, and a plurality of nodes form a file system network. Each node can be distributed in different places, and communication and data transmission among the nodes are carried out through a network, so that the difficult problems of data storage and management are effectively solved.
The storage node is used for providing data storage service and storing data files. A disaster recovery domain is a logical combination of a set of storage nodes. In a distributed file system, the reliability of data is generally improved by adopting a multi-copy mode, namely, a data file is divided into a plurality of blocks according to a fixed block size, and each block is stored in a different disaster recovery domain in a multi-copy mode. For the same block, the data in each copy corresponding to the block is the same.
The data file storage method commonly used at present mainly comprises a statistics-based and monitoring method, a consistency-based hash method, a pseudo-random method and the like. All the storage methods may cause that the copy of a disaster recovery domain is used more, so that no idle copy of the disaster recovery domain is available, and further, the multi-copy block cannot be stored continuously.
Disclosure of Invention
The embodiment of the invention provides a data file storage method, a device, equipment and a storage medium, which are used for solving the problem that the follow-up data file cannot be stored continuously due to uneven distribution of file copies in a data file in a disaster recovery domain in the prior art.
In a first aspect, an embodiment of the present invention provides a data file storage method, including:
dividing a data file to obtain a data file block, wherein the data file comprises a file copy;
if the sum of the available copy space numbers of each disaster recovery domain is greater than or equal to the file copy number, determining a target copy space number matched with the file copy number in each disaster recovery domain according to the file copy number, the current idle copy space number of each disaster recovery domain and the available copy space number of each disaster recovery domain;
and storing the file copies in the data file blocks into disaster recovery domains corresponding to the space numbers of the target copies respectively.
In a second aspect, an embodiment of the present invention further provides a data file storage device, including:
the dividing module is used for dividing the data file to obtain a data file block, wherein the data file comprises a file copy;
the copy space number determining module is used for determining the target copy space number matched with the file copy number in each disaster recovery domain according to the file copy number, the current idle copy space number of each disaster recovery domain and the available copy space number of each disaster recovery domain if the sum of the available copy space numbers of each disaster recovery domain is larger than or equal to the file copy number;
And the storage module is used for respectively storing the file copies in the data file blocks into disaster recovery domains corresponding to the space numbers of the target copies.
In a third aspect, an embodiment of the present invention further provides an apparatus, including:
one or more processors;
a memory for storing one or more programs;
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the data file storage method as described in the first aspect.
In a fourth aspect, an embodiment of the present invention further provides a storage medium having stored thereon a computer program which, when executed by a processor, implements the data file storage method according to the first aspect.
The embodiment of the invention provides a data file storage method, a device, equipment and a storage medium, wherein a data file block is obtained by dividing a data file, the data file comprises file copies, if the sum of the available copy space numbers of all disaster tolerant domains is greater than or equal to the file copy number, the current idle copy space number of each disaster tolerant domain and the available copy space number of each disaster tolerant domain are used for determining the target copy space number matched with the file copy number in each disaster tolerant domain, and the file copies in the data file block are respectively stored in disaster tolerant domains corresponding to the target copy space numbers. Compared with the prior art, the embodiment of the invention realizes that the file copies in the data file block are respectively stored in the disaster recovery domains corresponding to the space numbers of the target copies, and solves the problem that the data file cannot be continuously stored in the disaster recovery domains subsequently due to uneven distribution of the file copies in the data file in the prior art.
Drawings
FIG. 1 is a flowchart of a method for storing data files according to a first embodiment of the present invention;
FIG. 2 is a flowchart of a data file storing method according to a second embodiment of the present invention;
FIG. 3 is a flowchart illustrating a method for storing a data file according to a second embodiment of the present invention;
FIG. 4 is a block diagram of a data file storage device according to a third embodiment of the present invention;
fig. 5 is a block diagram of an apparatus according to a fourth embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings. Furthermore, embodiments of the invention and features of the embodiments may be combined with each other without conflict.
Example 1
Fig. 1 is a flowchart of a data file storage method according to a first embodiment of the present invention, where the method may be applicable to a case of storing data files in different disaster domains, and the method may be performed by a data file storage device, where the device may be implemented in a software and/or hardware manner and may be configured in a notebook computer, a palm computer, or other devices, and referring to fig. 1, the method may include the following steps:
S110, dividing the data file to obtain a data file block.
Wherein the data file includes a copy of the file. Optionally, the data file may be obtained according to a file storage request sent by the user, where the file storage request includes address information of the data file, and the data file to be stored may be obtained according to the address information. In order to facilitate storage and management of data files, the embodiment stores the data files in a distributed file system, namely, stores the data files in copy spaces of different disaster recovery domains, wherein the copy spaces are located on storage nodes of the disaster recovery domains, namely, are equivalent to storing the data files on the storage nodes of the corresponding disaster recovery domains. When certain data of the data file needs to be accessed, the copy space corresponding to the data can be directly accessed. The size of the data file is exemplified as 8M, the data file may be divided according to a fixed size, for example, the data file is divided into four parts, and the size of each part is 2M, or may be unequal, and the division manner of the data file is not limited in the embodiment.
It will be appreciated that the replica space in which data is stored is typically inaccessible due to machine failure or network problems, thereby rendering the data in the replica space inaccessible. In order to solve the problem, the embodiment stores in a multi-copy mode when storing the data file block, and when one copy cannot be accessed, the other copies can be accessed, so that the data access requirement is met. Wherein, the data in each copy corresponding to the same data file block is the same. The number of copies corresponding to each data file block may be the same or different, and in the embodiment, the data file is equally divided into a data file blocks, each data file block corresponds to b copies, and the number of file copies corresponding to the data file is a×b. In this embodiment, the file copy of the data file is a copy of each data file block.
S120, if the sum of the available copy space numbers of the disaster recovery domains is greater than or equal to the file copy number, determining the target copy space number matched with the file copy number in each disaster recovery domain according to the file copy number, the current idle copy space number of each disaster recovery domain and the available copy space number of each disaster recovery domain.
The disaster recovery domains are areas where storage nodes are located, and each disaster recovery domain may include a plurality of storage nodes, that is, a plurality of copy spaces. The available copy space is a storage space capable of storing file copies, and the number of available copy spaces contained in each disaster recovery domain can be the same or different. When a certain file copy cannot be accessed, in order not to affect access of the data file in the whole distributed file system, the embodiment stores the file copies in the data file block into different disaster recovery domains, for example, the data file block a has three file copies, and the three file copies need to be respectively stored into the three disaster recovery domains.
Alternatively, the number of available copy spaces in the disaster recovery domain may be determined according to the number of free copy spaces and the number of data file blocks in the disaster recovery domain. For example, when the number of free copy spaces of the disaster recovery domain is 5 and the number of blocks of the data file is 12, it may be determined that the number of available copy spaces of the disaster recovery domain is 5. For another example, when the number of free copy spaces in the disaster recovery domain is 15 and the number of blocks of the data file is 12, it may be determined that the number of available copy spaces in the disaster recovery domain is 12. When the sum of the available copy space numbers of each disaster recovery domain is greater than or equal to the file copy number, the data file can be stored, otherwise, information of failure in storage is returned to the user to inform the user that the data file cannot be stored in the distributed file system.
The target copy space number is matched with the file copy number, namely the sum of the target copy space numbers of each disaster recovery domain is equal to the file copy number. It can be understood that when the sum of the available copy space numbers of each disaster recovery domain is greater than the file copy number, part of the available copy space is unused, so that in order to ensure that the remaining available copy space numbers of each disaster recovery domain are the same as possible after storage is finished, the utilization rate of the available copy space numbers of each disaster recovery domain is improved, the number of file copies in each disaster recovery domain needs to be reasonably distributed, and in the embodiment, the available copy space numbers used for storing the file copies in each disaster recovery domain are called as target copy space, so that the remaining available copy space numbers of each disaster recovery domain can still store the data file blocks of multiple copies when storage is finished.
For example, there are four disaster recovery domains, FD1, FD2, FD3 and FD4, the current free copy space number of each disaster recovery domain is 10, 4 and 3, the number of data file blocks is 4, the number of file copies contained in each data file block is 3, the number of file copies 4*3 =12, and the available copy space number of each disaster recovery domain is 4, 4 and 3. In order to ensure that the number of the remaining available copy spaces of each disaster recovery domain is the same as much as possible when the storage is finished, it can be determined that the number of the target copy spaces corresponding to the four disaster recovery domains is 4, 3 and 2 respectively, and the number of the remaining available copy spaces of each disaster recovery domain is 0, 1 and 1 respectively. The embodiment does not limit the determining process of the target copy space number, so long as the residual available copy space number of each disaster recovery domain is ensured to be the same as possible.
S130, storing the file copies in the data file blocks into disaster recovery domains corresponding to the space numbers of the target copies respectively.
For example, the number of data file blocks corresponding to the data file is 4, each data file block is stored in a manner of 3 file copies, and the number of file copies is 4*3 =12. Assume that four disaster recovery domains exist, namely FD1, FD2, FD3 and FD4, and the sum of the target copy space numbers of the disaster recovery domains is equal to 12, and is 4, 3 and 2 respectively. For ease of description, the embodiment numbers 4 data file blocks, numbered 1, 2, 3, and 4, respectively, with the file copies in each data file block numbered 1, 2, and 3, respectively.
During storage, the 1 st file copy in the four data file blocks can be respectively stored in four available copy spaces in the disaster recovery domain FD1, namely, the 1 st file copy in the disaster recovery domain FD1 is respectively 1-1, 2-1, 3-1 and 4-1, the 2 nd file copies in the 1 st data file block, 2 nd data file block and 3 rd data file block are respectively stored in three available copy spaces in the disaster recovery domain FD2, namely, the 3 rd available copy spaces in the disaster recovery domain FD2 are respectively 1-2, 2-2 and 3-2, the 2 nd file copy in the 4 nd data file block, the 3 rd file copy in the 1 st data file block and the 3 rd file copy in the 2 nd data file block are respectively stored in three available copy spaces in the disaster recovery domain FD3, namely, the 3 nd file copies in the disaster recovery domain FD3 are respectively 4-2, 1-3 and 2-3, the 3 rd file copies in the 3 nd data file block and the 4 th file copy in the two available copy spaces in the two and 4 nd data file copy space in the 4 nd 2 are respectively stored in the two available copy spaces in the 4 nd domain FD 3. Wherein 1-1 represents the copy of the number 1 file in the number 1 data file block, 1-2 represents the copy of the number 2 file in the number 1 data file block, and the others are similar, thereby ensuring that multiple copies of the same data file block are stored in different disaster recovery domains respectively, and when one copy of the files cannot be accessed, the copy of the file in other disaster recovery domains can be accessed.
The first embodiment of the invention provides a data file storage method, which is characterized in that a data file block is obtained by dividing a data file, the data file comprises file copies, if the sum of the available copy space numbers of all disaster tolerant domains is greater than or equal to the file copy number, the current idle copy space numbers of all disaster tolerant domains and the available copy space numbers of all disaster tolerant domains are determined according to the file copy number, the current idle copy space numbers of all disaster tolerant domains and the available copy space numbers of all disaster tolerant domains, the target copy space numbers matched with the file copy numbers in all disaster tolerant domains are determined, and file copies in the data file block are respectively stored in disaster tolerant domains corresponding to the target copy space numbers. Compared with the prior art, the embodiment of the invention realizes that the file copies in the data file block are respectively stored in the disaster recovery domains corresponding to the space numbers of the target copies, and solves the problem that the data file cannot be continuously stored in the disaster recovery domains subsequently due to uneven distribution of the file copies in the data file in the prior art.
Example two
Fig. 2 is a flowchart of a data file storage method according to a second embodiment of the present invention, where the data file storage method is optimized based on the foregoing embodiment, and referring to fig. 2, the method includes the following steps:
S210, dividing the data file to obtain a data file block.
S220, arranging the disaster tolerant domains in a descending order according to the current free copy space number of the disaster tolerant domains.
The free copy space is a copy space of a file copy not stored currently in the disaster recovery domain, and in order to determine the target copy space number of each disaster recovery domain, the embodiment firstly arranges each disaster recovery domain in descending order according to the current copy space number of each disaster recovery domain. For example, the current number of free copy spaces of disaster recovery domain FD1, disaster recovery domain FD2, disaster recovery domain FD3, and disaster recovery domain FD4 is 10, 4, and 3, respectively, and the order of each disaster recovery domain after descending is disaster recovery domain FD1, disaster recovery domain FD2, disaster recovery domain FD3, and disaster recovery domain FD4.
S230, determining the available copy space number of each disaster recovery domain according to the current idle copy space number and the data file block number of each disaster recovery domain after sequencing.
The traditional storage mode takes the number of idle copy spaces as the number of available copy spaces, which results in excessive use of copy spaces in some disaster recovery domains, so that the disaster recovery domains have no idle copy spaces available, and further, the subsequent failure to allocate multi-copy data file blocks is caused. For example, four disaster recovery domains, namely FD1, FD2, FD3 and FD4, exist, and the number of idle copy spaces corresponding to each disaster recovery domain is 10, 4 and 3. Suppose that four data file blocks are to be stored at this time, each corresponding to three copies of the file. According to the traditional storage mode, the number of the remaining free copy spaces of each disaster recovery domain after the storage is finished may be 6, 0 and 3, at this time, although nine free copy spaces are remained, in order to ensure that multiple file copies of the same data file block are stored in different disaster recovery domains, the remaining nine free copy spaces only can store data file blocks containing two file copies, cannot store data file blocks containing three file copies, so that the space utilization is reduced, and the reliability of the data file blocks containing two file copies is lower than that of the data file blocks containing three file copies. In order to avoid such a situation, the present embodiment determines the available copy space number of each disaster recovery domain according to the current idle copy space number and the data file block number of each disaster recovery domain, and makes the remaining idle copy space number of each disaster recovery domain as close as possible when the storage is finished.
Alternatively, the number of available copy spaces for each disaster recovery domain may be determined as follows:
for each disaster recovery domain after sequencing, if the current idle copy space number of the disaster recovery domain is smaller than the data file block number, determining the current idle copy space number of the disaster recovery domain as the available copy space number of the disaster recovery domain;
otherwise, determining the number of the data file blocks as the number of available copy spaces of the disaster recovery domain.
Assuming that the disaster recovery domains after sequencing are respectively a disaster recovery domain FD1, a disaster recovery domain FD2, a disaster recovery domain FD3 and a disaster recovery domain FD4, t (i) is defined as the current free copy space number of the disaster recovery domain FDi, for example, t (1) =5, the current free copy space number of the disaster recovery domain FD1 is denoted as 5, and the number of the data file blocks is a. Specifically, if t (i) < a, the current available copy space number of the disaster recovery domain FDi is t (i), and if t (i) > =a, the current available copy space number of the disaster recovery domain FDi is a. For example, the number of data file blocks is 4, t (1) =10 >4, t (2) =4=4, t (3) =4=4, t (4) =3 <4, and then the number of available copy spaces of disaster-tolerant domain FD1, disaster-tolerant domain FD2, disaster-tolerant domain FD3, and disaster-tolerant domain FD4 is 4, and 3, respectively.
S240, whether the sum of the available copy space numbers of each disaster recovery domain is larger than or equal to the file copy number, if yes, executing S250, otherwise, executing S270.
S250, determining the target copy space number matched with the file copy number in each disaster recovery domain after sequencing according to the file copy number, the current idle copy space number of each disaster recovery domain after sequencing and the available copy space number of each disaster recovery domain after sequencing.
When the sum of the available copy space numbers of each disaster recovery domain is greater than or equal to the file copy number, the file copy contained in each data file block can be stored. Alternatively, the target copy space number of each disaster recovery domain may be determined as follows:
the first disaster recovery domain after sequencing is recorded as the current disaster recovery domain;
the available copy space number of the current disaster recovery domain is recorded as the initial target copy space number of the current disaster recovery domain;
recording the difference value between the idle copy space number and the initial target copy space number of the current disaster recovery domain as the residual copy space number of the current disaster recovery domain;
if the number of idle copy spaces of the subsequent disaster recovery domain is larger than the number of residual copy spaces, recording the difference value between the number of idle copy spaces of the subsequent disaster recovery domain and the number of residual copy spaces as the initial target copy space number of the subsequent disaster recovery domain; otherwise, the initial target copy space number of the subsequent disaster recovery domain is recorded as 0;
If the sum of the initial target copy space numbers of the disaster recovery domains is smaller than the file copy number, determining the available copy space number of the current disaster recovery domain as the target copy space number of the current disaster recovery domain, taking the next disaster recovery domain as the current disaster recovery domain, and repeating the process; otherwise, reducing the number of the initial target copy spaces in the current disaster recovery domain and the subsequent disaster recovery domain according to the rollback rule.
For example, the disaster recovery domains after sequencing are disaster recovery domain FD1, disaster recovery domain FD2, disaster recovery domain FD3 and disaster recovery domain FD4, the disaster recovery domain FD1 is taken as the current disaster recovery domain, the initial target copy space number of the disaster recovery domain FD1 is 4 assuming that the available copy space number of the disaster recovery domain FD1 is 4 and the current free copy space number is 6, the remaining copy space number of the disaster recovery domain FD1 is 2, and if the free copy space numbers of the disaster recovery domain FD2, the disaster recovery domain FD3 and the disaster recovery domain FD4 are 4, 4 and 3 respectively and are greater than the remaining copy space number 2 of the disaster recovery domain FD1, the initial target copy space numbers of the disaster recovery domain FD2, the disaster recovery domain FD3 and the disaster recovery domain FD4 are 2, 2 and 1 respectively, the accumulated sum of the initial target copy numbers of the four disaster recovery domains is 9 and the target copy space number of the disaster recovery domain FD1 is determined to be 4 if the number of the file copy is less than 12.
Taking disaster recovery domain FD2 as a current disaster recovery domain, wherein the available copy space numbers of disaster recovery domain FD2, disaster recovery domain FD3 and disaster recovery domain FD4 are 4, 4 and 3 respectively, the current idle copy space numbers are 4, 4 and 3 respectively, the initial target copy space number of disaster recovery domain FD2 is 4, the residual copy space number of disaster recovery domain FD2 is 4-4=0, the idle copy space numbers smaller than those of disaster recovery domain FD3 and disaster recovery domain FD4 are 4, the difference between the idle copy space numbers of disaster recovery domain FD3 and disaster recovery domain FD4 and the residual copy space numbers of disaster recovery domain FD2 is 4 and 3 respectively, and the initial target copy space numbers of disaster recovery domain FD3 and disaster recovery domain FD4 are 4 and 3 respectively. The sum of the target copy space number of disaster recovery domain FD1 and the initial target copy space numbers of disaster recovery domain FD2, disaster recovery domain FD3 and disaster recovery domain FD4 is 15, which is greater than the file copy number 12, so that the initial target copy space numbers of disaster recovery domain FD2, disaster recovery domain FD3 and FD4 in the latest loop iteration need to be reduced. It should be noted that, the initial target copy space number is the number of each disaster recovery domain in the latest loop iterative computation process.
Optionally, the number of initial target copy spaces in the current disaster recovery domain and the subsequent disaster recovery domain may be reduced as follows:
determining the total number of the initial target copy spaces to be reduced in the current disaster recovery domain and the subsequent disaster recovery domain according to the target copy space number, the initial target copy space number and the file copy number;
And determining the number of the initial target copy spaces in the current disaster recovery domain and the subsequent disaster recovery domain respectively according to the total number to be reduced of the initial target copy spaces in the current disaster recovery domain and the subsequent disaster recovery domain and the number of the current disaster recovery domain and the subsequent disaster recovery domain, so as to obtain the target copy space numbers of the current disaster recovery domain and the subsequent disaster recovery domain.
Assuming that the number of disaster recovery domains is n, the disaster recovery domain of the last stored file copy is FDn, and the current disaster recovery domain in the latest one-time loop iteration is FDi, the number of disaster recovery domains needing to reduce the number of initial target copy spaces is n-i+1, and the total number of initial target copy spaces needing to be reduced is R * R, wherein R is * For the sum of the target copy space number of the disaster-tolerant domain before the disaster-tolerant domain FDi and the initial target copy space number of the disaster-tolerant domain FDi and the disaster-tolerant domain after the disaster-tolerant domain FDi, R is the file copy number, and the number of the initial target copy spaces required to be reduced from the disaster-tolerant domain FDi is [ (R-R)/(n-i+1)]Wherein [ the]Representing rounding. Illustratively, n=4, i=2, r * When r=15, r=12, the number of initial target copy spaces reduced by disaster recovery domain FD2, disaster recovery domain FD3, and disaster recovery domain FD4 is 1, respectively, so that the number of target copy spaces of disaster recovery domain FD2, disaster recovery domain FD3, and disaster recovery domain FD4 can be determined to be 3, and 2, respectively. At this time, the number of remaining spatial copies of each disaster recovery domain is 6, 1 and 1, and compared with the prior art, the embodiment can still store a data file block containing three file copies after the storage is finished.
If (R) * The remainder m=0 of-R)/(n-i+1) represents the same number of available copy spaces reduced by each disaster recovery domain, if m-! =0, meaning that there are more disaster recovery domains to continue to reduce the number of available copy spaces, then selecting the last m disaster recovery domains, and reducing the number of disaster recovery domains from FD (n-m+1) to FDn by one more initial target copy space.
S260, storing the file copies in the data file blocks into disaster recovery domains corresponding to the space numbers of the target copies respectively.
Optionally, according to the number of target copy spaces of each disaster recovery domain after sorting, storing the file copies in the data file block into the disaster recovery domain corresponding to the number of target copy spaces.
For example, the target copy space numbers of disaster recovery domain FD1, disaster recovery domain FD2, disaster recovery domain FD3 and disaster recovery domain FD4 are 4, 3 and 2, the file copy number is 12, the data file block number is 4, and the data file block numbers are 1 data file block, 2 data file block, 3 data file block and 4 data file block, respectively, each data file block contains 3 file copies, and is 1 file copy, 2 file copy and 3 file copy, respectively, and then the file copies can be stored according to the storage manner described in the above embodiments, and referring to table 1, table 1 is the storage result of the file copies.
Table 1 stored results for file copies
Copy number 1 file Copy number 2 file Copy number 3 file
Number 1 data file block FD1 FD2 FD3
Number 2 data file block FD1 FD2 FD3
Data file block No. 3 FD1 FD2 FD4
Data file block No. 4 FD1 FD3 FD4
It can be seen from table 1 that three file copies of the same data file block are respectively stored in different disaster recovery domains, and when a certain file copy cannot be accessed, the data corresponding to the file copy can be accessed by accessing other disaster recovery domains because the file copies of the same data file block are the same.
S270, returning prompt information of the data file storage failure to the user.
When the sum of the available copy space numbers of each disaster recovery domain is smaller than the file copy number, the data file cannot be stored, and prompt information of failure in storing the data file can be returned to the user.
The second embodiment of the present invention provides a data file storage method, on the basis of the foregoing embodiment, the available copy space number of each disaster recovery domain is first determined, then, according to the file copy number, the current free copy space number of each disaster recovery domain, and the available copy space number of each disaster recovery domain, the target copy space number matched with the file copy number in each disaster recovery domain is determined, according to the sorted target copy space number of each disaster recovery domain, the file copies in the data file block are stored in the disaster recovery domain corresponding to each target copy space number, thereby not only ensuring that the file copies of the same data file block are stored in different disaster recovery domains, preventing the situation that the whole data file access is affected due to the fact that a certain file copy cannot be accessed, but also fully utilizing the storage space of each disaster recovery domain, so that the remaining copy space numbers of each disaster recovery domain are as close as possible, and improving the utilization rate of the storage space.
Referring to fig. 3, fig. 3 is a flowchart illustrating a data file storage method according to a second embodiment of the present invention. Specifically, dividing a data file to obtain a data file blocks, wherein each data file block comprises b file copies, the total number of the file copies, r=a×b, is arranged in descending order for each disaster-tolerant domain according to the current free copy space number of each disaster-tolerant domain, the available copy space number of each disaster-tolerant domain is determined, if the sum of the available copy space numbers of each disaster-tolerant domain is greater than or equal to the file copy number R, the first disaster-tolerant domain after sorting is recorded as the current disaster-tolerant domain, the available copy space number of the current disaster-tolerant domain is recorded as the initial target copy space number of the current disaster-tolerant domain, the difference value between the free copy space number of the current disaster-tolerant domain and the target copy space number is recorded as the residual copy space number of the current disaster-tolerant domain, and for the subsequent disaster-tolerant domain, if the free copy space number of the subsequent disaster-tolerant domain is greater than the residual copy space number of the current disaster-tolerant domain, the difference value between the free copy space number of the subsequent disaster-tolerant domain and the residual copy space number of the current disaster-tolerant domain is recorded as the initial target copy space number of the subsequent disaster-tolerant domain, and otherwise the initial copy number of the subsequent disaster-tolerant domain is recorded as the initial target copy number of the current disaster-tolerant domain. After the iteration is finished, if the sum R of the initial target copy space numbers of each disaster recovery domain * The available copy space number of the current disaster recovery domain is determined as the target copy space number of the current disaster recovery domain when the available copy space number is smaller than the file copy number R, then the next disaster recovery domain is taken as the current disaster recovery domain, the process is repeated, and if the sum R of the initial target copy space numbers of the disaster recovery domains is equal to the sum R of the initial target copy space numbers of the disaster recovery domains * And if the number of the target copy spaces is larger than the number R of the file copies, reducing the number of the initial target copy spaces in the current disaster recovery domain and the subsequent disaster recovery domain in the latest loop iteration to obtain the number of the final target copy spaces in the current disaster recovery domain and the subsequent disaster recovery domain.
After the number of target copy spaces is determined, file copies are sequentially stored in the corresponding target copy spaces from the first disaster recovery domain. When R is * When the number is R, the initial target copy space in the current disaster recovery domain and the subsequent disaster recovery domain in the latest loop iteration does not need to be reducedThe initial target copy space number of the current disaster recovery domain and the subsequent disaster recovery domain is the target copy space number of the current disaster recovery domain and the subsequent disaster recovery domain, and the file copy is directly stored in the disaster recovery domain corresponding to each target copy space number. In fig. 3, i=1 indicates the first disaster recovery domain. Fig. 3 shows only part of the process by way of example.
For example, the current number of free copy spaces of each disaster recovery domain is t (1) =10, t (2) =4, t (3) =4 and t (4) =3, the number of available copy spaces corresponding to each disaster recovery domain is 4, 4 and 3, the number of remaining space copies of disaster recovery domain FD1 is 6, and when disaster recovery domain FD1 is taken as the current disaster recovery domain, the initial target copy space number of disaster recovery domain FD1 is recorded as 4, and since the number of remaining copy spaces of disaster recovery domain FD1 is 6, the number of free copy spaces of disaster recovery domain FD2, disaster recovery domain FD3 and disaster recovery domain FD4 is larger than the number of initial target copy spaces of disaster recovery domain FD2, disaster recovery domain FD3 and disaster recovery domain FD4, respectively recorded as 0, 0 and 0, the sum of the initial target copy space numbers of all disaster recovery domains is 4, and the number of copies of file is smaller than 12, the target copy number of disaster recovery domain FD1 is determined as 4. Taking disaster recovery domain FD2 as a current disaster recovery domain, wherein the available copy space number of disaster recovery domain FD2 is 4, the initial target copy space number of disaster recovery domain FD2 is 4, the residual space copy number of disaster recovery domain FD2 is 0 and is smaller than the idle copy space numbers of disaster recovery domain FD3 and disaster recovery domain FD4, the initial target copy space numbers of disaster recovery domain FD3 and disaster recovery domain FD4 are respectively recorded as 4 and 3, and the sum of the target copy space number of disaster recovery domain FD1 and the initial target copy space numbers of disaster recovery domain FD2, disaster recovery domain FD3 and disaster recovery domain FD4 is R * =15, greater than 12, from disaster recovery domain FD2, disaster recovery domain FD3, and disaster recovery domain FD4 each reduce one free copy space to make R * And (R), finally determining that the target copy space numbers of disaster recovery domain FD1, disaster recovery domain FD2, disaster recovery domain FD3 and disaster recovery domain FD4 are 4, 3 and 2 respectively, and storing each file copy in different disaster recovery domains from disaster recovery domain FD 1.
Example III
Fig. 4 is a block diagram of a data file storage device according to a third embodiment of the present invention, where the device may execute the data file storage method according to the foregoing embodiment, and referring to fig. 4, the device includes:
the dividing module 310 is configured to divide a data file to obtain a data file block, where the data file includes a file copy;
a copy space number determining module 320, configured to determine, if the sum of the available copy space numbers of each disaster recovery domain is greater than or equal to the file copy number, a target copy space number in each disaster recovery domain that matches the file copy number according to the file copy number, the current free copy space number of each disaster recovery domain, and the available copy space number of each disaster recovery domain;
and the storage module 330 is configured to store the file copies in the data file block into disaster recovery domains corresponding to the target copy space numbers respectively.
The third embodiment of the present invention provides a data file storage device, where a data file is divided to obtain a data file block, where the data file includes file copies, and a target copy space number in each disaster recovery domain, which is matched with the file copy number, is determined according to the file copy number, the current free copy space number in each disaster recovery domain, and the available copy space number in each disaster recovery domain, and file copies in the data file block are respectively stored in disaster recovery domains corresponding to the target copy space numbers. Compared with the prior art, the embodiment of the invention realizes that the file copies in the data file block are respectively stored in the disaster recovery domains corresponding to the space numbers of the target copies, and solves the problem that the data file cannot be continuously stored in the disaster recovery domains subsequently due to uneven distribution of the file copies in the data file in the prior art.
Based on the above embodiment, the copy space number determining module 320 includes:
the arrangement unit is used for arranging the disaster tolerant domains in a descending order according to the current idle copy space number of the disaster tolerant domains;
the available copy space number determining unit is used for determining the available copy space number of each disaster recovery domain according to the current idle copy space number and the data file block number of each disaster recovery domain after sequencing;
And the target copy space number determining unit is used for determining the target copy space number matched with the file copy number in each disaster recovery domain after sequencing according to the file copy number, the current idle copy space number of each disaster recovery domain after sequencing and the available copy space number of each disaster recovery domain after sequencing if the sum of the available copy space numbers of each disaster recovery domain is greater than or equal to the file copy number.
On the basis of the above embodiment, the available copy space number determining unit is specifically configured to:
for each disaster recovery domain after sequencing, if the current idle copy space number of the disaster recovery domain is smaller than the data file block number, determining the current idle copy space number of the disaster recovery domain as the available copy space number of the disaster recovery domain;
otherwise, determining the number of the data file blocks as the number of available copy spaces of the disaster recovery domain.
On the basis of the above embodiment, the target copy space number determination unit includes:
the first marking unit is used for marking the first disaster recovery domain after sequencing as the current disaster recovery domain;
the second marking unit is used for marking the available copy space number of the current disaster recovery domain as the initial target copy space number of the current disaster recovery domain;
A third marking unit, configured to record, as a remaining number of copy spaces of the current disaster recovery domain, a difference between the number of free copy spaces of the current disaster recovery domain and the number of initial target copy spaces;
a fourth marking unit, configured to, if the number of free copy spaces in the subsequent disaster recovery domain is greater than the number of remaining copy spaces, mark a difference between the number of free copy spaces in the subsequent disaster recovery domain and the number of remaining copy spaces as an initial target number of copy spaces in the subsequent disaster recovery domain; otherwise, the initial target copy space number of the subsequent disaster recovery domain is recorded as 0;
the target copy space number determining unit is used for determining the available copy space number of the current disaster recovery domain as the target copy space number of the current disaster recovery domain if the sum of the initial target copy space numbers of the disaster recovery domains is smaller than the file copy number, taking the next disaster recovery domain as the current disaster recovery domain, and repeating the process; otherwise, reducing the number of the initial target copy spaces in the current disaster recovery domain and the subsequent disaster recovery domain according to the rollback rule.
On the basis of the above embodiment, the target copy space number determining unit is specifically configured to:
determining the total number of the initial target copy spaces to be reduced in the current disaster recovery domain and the subsequent disaster recovery domain according to the target copy space number, the initial target copy space number and the file copy number;
And determining the number of the initial target copy spaces in the current disaster recovery domain and the subsequent disaster recovery domain respectively according to the total number to be reduced of the initial target copy spaces in the current disaster recovery domain and the subsequent disaster recovery domain and the number of the current disaster recovery domain and the subsequent disaster recovery domain, so as to obtain the target copy space numbers of the current disaster recovery domain and the subsequent disaster recovery domain.
Based on the above embodiment, the storage module 330 is specifically configured to:
and storing the file copies in the data file block into the disaster recovery domains corresponding to the target copy space numbers according to the target copy space numbers of the disaster recovery domains after the sequencing.
On the basis of the above embodiment, the device further includes:
and the prompt module is used for returning prompt information of failure in storing the data file to the user if the available copy space number of each disaster recovery domain is smaller than the file copy number.
The data file storage device provided by the third embodiment of the invention can execute the data file storage method provided by the above embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
Example IV
Fig. 5 is a structural diagram of an apparatus according to a fourth embodiment of the present invention, and referring to fig. 5, the apparatus includes: the apparatus includes: the number of processors 410 in the apparatus may be one or more, in fig. 5, one processor 410 is an example, and the processors 410, the memory 420, the input device 430, and the output device 440 in the apparatus may be connected by a bus or other means, in fig. 5, by a bus connection is an example.
The memory 420 is a computer readable storage medium, and may be used to store a software program, a computer executable program, and modules, such as program instructions/modules corresponding to the data file storage method in the embodiments of the present application. The processor 410 executes various functional applications of the device and data processing, i.e., implements the data file storage method of the above-described embodiments, by running software programs, instructions, and modules stored in the memory 420.
The memory 420 mainly includes a memory program area and a memory data area, wherein the memory program area can store an operating system, at least one application program required for functions; the storage data area may store data created according to the use of the terminal, etc. In addition, memory 420 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some examples, memory 420 may further include memory located remotely from processor 410, which may be connected to the device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input means 430 may be used to receive entered numeric or character information and to generate key signal inputs related to user settings and function control of the device. The output device 440 may include a display device such as a display screen, a speaker, and an audio device such as a buzzer.
The apparatus provided by the embodiment of the present invention belongs to the same concept as the data file storage method provided by the above embodiment, and technical details which are not described in detail in the present embodiment can be seen in the above embodiment, and the present embodiment has the same advantages as those of executing the data file storage method.
Example five
The embodiment of the present invention also provides a storage medium having stored thereon a computer program which, when executed by a processor, implements the data file storage method according to the above-described embodiment of the present invention.
Of course, the storage medium containing the computer executable instructions provided in the embodiments of the present application is not limited to the operations in the data file storage method described above, but may also perform the related operations in the data file storage method provided in any embodiment of the present application, and has corresponding functions and beneficial effects.
From the above description of embodiments, it will be clear to a person skilled in the art that the present application may be implemented by means of software and necessary general purpose hardware, but of course also by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, etc., and include several instructions for causing a computer device (which may be a robot, a personal computer, a server, or a network device, etc.) to execute the data file storing method according to the above embodiment of the present invention.
Note that the above is only a preferred embodiment of the present invention and the technical principle applied. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.

Claims (9)

1. A method of storing a data file, comprising:
dividing a data file to obtain a data file block, wherein the data file comprises a file copy;
if the sum of the available copy space numbers of each disaster recovery domain is greater than or equal to the file copy number, determining a target copy space number matched with the file copy number in each disaster recovery domain according to the file copy number, the current idle copy space number of each disaster recovery domain and the available copy space number of each disaster recovery domain; the available copy space number is determined according to the idle copy space number and the data file block number;
Storing the file copies in the data file blocks into disaster recovery domains corresponding to the space numbers of the target copies respectively;
wherein if the sum of the available copy space numbers of each disaster recovery domain is greater than or equal to the file copy number, determining a target copy space number matched with the file copy number in each disaster recovery domain according to the file copy number, the current free copy space number of each disaster recovery domain and the available copy space number of each disaster recovery domain, including:
according to the current free copy space number of each disaster tolerant domain, the disaster tolerant domains are arranged in a descending order;
determining the available copy space number of each disaster recovery domain according to the current idle copy space number and the data file block number of each disaster recovery domain after sequencing;
and if the sum of the available copy space numbers of the disaster recovery domains is greater than or equal to the file copy number, determining the target copy space number matched with the file copy number in each disaster recovery domain after sequencing according to the file copy number, the current idle copy space number of each disaster recovery domain after sequencing and the available copy space number of each disaster recovery domain after sequencing.
2. The method of claim 1, wherein determining the available copy space number for each disaster recovery domain based on the current free copy space number and the data file block number for each disaster recovery domain after sorting comprises:
For each disaster recovery domain after sequencing, if the current idle copy space number of the disaster recovery domain is smaller than the data file block number, determining the current idle copy space number of the disaster recovery domain as the available copy space number of the disaster recovery domain;
otherwise, determining the number of the data file blocks as the number of available copy spaces of the disaster recovery domain.
3. The method of claim 1, wherein determining the target copy space number in each disaster recovery domain after sorting that matches the file copy number based on the file copy number, the current free copy space number in each disaster recovery domain after sorting, and the available copy space number in each disaster recovery domain after sorting, comprises:
the first disaster recovery domain after sequencing is recorded as the current disaster recovery domain;
the available copy space number of the current disaster recovery domain is recorded as the initial target copy space number of the current disaster recovery domain;
recording the difference value between the idle copy space number and the initial target copy space number of the current disaster recovery domain as the residual copy space number of the current disaster recovery domain;
if the number of idle copy spaces of the subsequent disaster recovery domain is larger than the number of residual copy spaces, recording the difference value between the number of idle copy spaces of the subsequent disaster recovery domain and the number of residual copy spaces as the initial target copy space number of the subsequent disaster recovery domain; otherwise, the initial target copy space number of the subsequent disaster recovery domain is recorded as 0;
If the sum of the initial target copy space numbers of the disaster recovery domains is smaller than the file copy number, determining the available copy space number of the current disaster recovery domain as the target copy space number of the current disaster recovery domain, taking the next disaster recovery domain as the current disaster recovery domain, and repeating the process; otherwise, reducing the number of the initial target copy spaces in the current disaster recovery domain and the subsequent disaster recovery domain according to the rollback rule.
4. The method of claim 3, wherein reducing the number of initial target replica spaces in the current disaster recovery domain and in the subsequent disaster recovery domain according to the rollback rules comprises:
determining the total number of the initial target copy spaces to be reduced in the current disaster recovery domain and the subsequent disaster recovery domain according to the target copy space number, the initial target copy space number and the file copy number;
and determining the number of the initial target copy spaces in the current disaster recovery domain and the subsequent disaster recovery domain respectively according to the total number to be reduced of the initial target copy spaces in the current disaster recovery domain and the subsequent disaster recovery domain and the number of the current disaster recovery domain and the subsequent disaster recovery domain, so as to obtain the target copy space numbers of the current disaster recovery domain and the subsequent disaster recovery domain.
5. The method of claim 1, wherein storing the file copies in the data file block in disaster recovery domains corresponding to the target copy space numbers, respectively, comprises:
and storing the file copies in the data file block into the disaster recovery domains corresponding to the target copy space numbers according to the target copy space numbers of the disaster recovery domains after the sequencing.
6. The method of any one of claims 1-5, further comprising:
and if the sum of the available copy space numbers of the disaster recovery domains is smaller than the file copy number, returning prompt information of failure in storing the data file to the user.
7. A data file storage device, comprising:
the dividing module is used for dividing the data file to obtain a data file block, wherein the data file comprises a file copy;
the copy space number determining module is used for determining the target copy space number matched with the file copy number in each disaster recovery domain according to the file copy number, the current idle copy space number of each disaster recovery domain and the available copy space number of each disaster recovery domain if the sum of the available copy space numbers of each disaster recovery domain is larger than or equal to the file copy number; the available copy space number is determined according to the idle copy space number and the data file block number;
The storage module is used for respectively storing the file copies in the data file block into disaster recovery domains corresponding to the space numbers of the target copies;
wherein, duplicate space number determination module includes:
the arrangement unit is used for arranging the disaster tolerant domains in a descending order according to the current idle copy space number of the disaster tolerant domains;
the available copy space number determining unit is used for determining the available copy space number of each disaster recovery domain according to the current idle copy space number and the data file block number of each disaster recovery domain after sequencing;
and the target copy space number determining unit is used for determining the target copy space number matched with the file copy number in each disaster recovery domain after sequencing according to the file copy number, the current idle copy space number of each disaster recovery domain after sequencing and the available copy space number of each disaster recovery domain after sequencing if the sum of the available copy space numbers of each disaster recovery domain is greater than or equal to the file copy number.
8. An apparatus, comprising:
one or more processors;
a memory for storing one or more programs;
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the data file storage method of any of claims 1-6.
9. A storage medium having stored thereon a computer program, which when executed by a processor implements a data file storage method according to any of claims 1-6.
CN201911349603.1A 2019-12-24 2019-12-24 Data file storage method, device, equipment and storage medium Active CN111090629B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911349603.1A CN111090629B (en) 2019-12-24 2019-12-24 Data file storage method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911349603.1A CN111090629B (en) 2019-12-24 2019-12-24 Data file storage method, device, equipment and storage medium

Publications (2)

Publication Number Publication Date
CN111090629A CN111090629A (en) 2020-05-01
CN111090629B true CN111090629B (en) 2024-02-06

Family

ID=70398087

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911349603.1A Active CN111090629B (en) 2019-12-24 2019-12-24 Data file storage method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN111090629B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103793425A (en) * 2012-10-31 2014-05-14 国际商业机器公司 Data processing method and data processing device for distributed system
CN104461768A (en) * 2013-09-22 2015-03-25 华为技术有限公司 Copy storing device and copy storing method
US9483367B1 (en) * 2014-06-27 2016-11-01 Veritas Technologies Llc Data recovery in distributed storage environments
CN109582509A (en) * 2017-09-29 2019-04-05 中兴通讯股份有限公司 Distributed file system disaster tolerance configuration method, device and readable storage medium storing program for executing

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103793425A (en) * 2012-10-31 2014-05-14 国际商业机器公司 Data processing method and data processing device for distributed system
CN104461768A (en) * 2013-09-22 2015-03-25 华为技术有限公司 Copy storing device and copy storing method
US9483367B1 (en) * 2014-06-27 2016-11-01 Veritas Technologies Llc Data recovery in distributed storage environments
CN109582509A (en) * 2017-09-29 2019-04-05 中兴通讯股份有限公司 Distributed file system disaster tolerance configuration method, device and readable storage medium storing program for executing

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
何骞 ; .一种容灾系统存储空间分配方法.通讯世界.2016,(18),全文. *

Also Published As

Publication number Publication date
CN111090629A (en) 2020-05-01

Similar Documents

Publication Publication Date Title
EP3333718B1 (en) Task allocation method and task allocation apparatus for distributed data calculation
EP4053711A1 (en) Consensus method for blockchain, and consensus node, electronic device and storage medium
CN108897628A (en) A kind of implementation method of distributed lock, device and electronic equipment
CN104809129A (en) Method, device and system for storing distributed data
CN112738172B (en) Block chain node management method and device, computer equipment and storage medium
CN112269661B (en) Partition migration method and device based on Kafka cluster
CN107920101B (en) File access method, device and system and electronic equipment
CN111897493B (en) Storage space management method and device, electronic equipment and storage medium
CN111046004B (en) Data file storage method, device, equipment and storage medium
CN112835885B (en) Processing method, device and system for distributed form storage
CN110336813B (en) Access control method, device, equipment and storage medium
CN112000285A (en) Strong consistent storage system, strong consistent data storage method, server and medium
CN108897858B (en) Distributed cluster index fragmentation evaluation method and device and electronic equipment
CN109408711B (en) Data filtering method and device, electronic equipment and storage medium
CN111125240B (en) Distributed transaction realization method and device, electronic equipment and storage medium
CN111090629B (en) Data file storage method, device, equipment and storage medium
CN110764705B (en) Data reading and writing method, device, equipment and storage medium
CN107463638A (en) File sharing method and equipment between offline virtual machine
CN115934354A (en) Online storage method and device
CN115756955A (en) Data backup and data recovery method and device and computer equipment
CN115391341A (en) Distributed graph data processing system, method, device, equipment and storage medium
CN112181829B (en) User distribution method, device, terminal and medium for AB experiment
CN114493598A (en) Computing resource management method, device, computer equipment and storage medium
CN114513469A (en) Traffic shaping method and device for distributed system and storage medium
CN110046040B (en) Distributed task processing method and system and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant