CN104239517A - Storage object access method and device for distributed storage system - Google Patents
Storage object access method and device for distributed storage system Download PDFInfo
- Publication number
- CN104239517A CN104239517A CN201410473575.5A CN201410473575A CN104239517A CN 104239517 A CN104239517 A CN 104239517A CN 201410473575 A CN201410473575 A CN 201410473575A CN 104239517 A CN104239517 A CN 104239517A
- Authority
- CN
- China
- Prior art keywords
- obj ect
- ect file
- entity node
- storage entity
- storage
- 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.)
- Granted
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/18—File system types
- G06F16/182—Distributed file systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention discloses a storage object access method and a storage object access device for a distributed storage system. The method comprises the following steps of receiving a data access request comprising a global logical number of an object file; calculating a storage entity node where the object file is located and a local logical number of the object file in the storage entity node based on the global logical number of the object file; calculating a physical block number of the object file based on a starting physical block number of the storage entity node where the object file is located and the local logical number, and accessing the object file according to the physical block number. According to the method and the device, the physical block number of the object file is directly calculated based on the global logical number of the object file, so that a retrieval link of a file system is eliminated, and the data access rate is increased.
Description
Technical field
Embodiment of the present invention belongs to technical field of network storage, particularly a kind of storage object access method of distributed memory system and device.
Background technology
Traditional network store system adopts the storage server concentrated to deposit all data.In this storage mode, storage server becomes system performance bottleneck, is also the focus of reliability and security, therefore can not meet the needs of Mass storage application.
At present, distributed storage technology obtains fast development.In distributed memory system, data scatter is stored on multiple stage autonomous device.Distributed memory system adopts extendible system architecture, utilizes multiple stage storage entity node to share storage load, utilizes location server to locate storage information.Storage entity node provides actual storage ability, and all storage entity nodes are virtualized into unified stores service.This storage mode not only increases the reliability of system, availability and access efficiency, is also easy to expansion.
In the prior art, the data access operation process for storage entity node needs repeatedly access file system usually, causes data access rate slower.Such as, when client expects storage entity node data being write distributed memory system, first need in the global file system of distributed storage, retrieve the target storage entity node that will write, then the local file system of retrieving this target storage entity node, to determine data memory location in a hard disk, writes data finally by this local file system invoking block device drives with access hard disk.
But in this implementation, global file system and local file system need to perform retrieval work respectively, and therefore data access rate is slower.Especially, when reading and writing data request falls into multiple storage entity node or distributed storage has many copies mechanism, the impact of this processing mode repeatedly retrieved on data access rate is larger.
Summary of the invention
Embodiment of the present invention proposes a kind of storage object access method and device of distributed memory system, to improve data access rate.
The technical scheme of embodiment of the present invention is as follows:
The one side of embodiment of the present invention, provides a kind of storage object access method of distributed memory system.
A storage object access method for distributed memory system, the method comprises:
Receiving package is containing the data access request of obj ect file global logic numbering;
Based on storage entity node and the local logical number of this obj ect file in described storage entity node at described obj ect file global logic numbering calculating object file place;
Calculate the physical block number of this obj ect file based on the initial physical block number of the storage entity node at described obj ect file place and described local logical number, and access described obj ect file according to described physical block number.
The another aspect of embodiment of the present invention, provides a kind of storage object access means of distributed memory system.
A storage object access means for distributed memory system, this device comprises:
Receiver module, for the data access request of receiving package containing obj ect file global logic numbering;
Numbering computing module, for based on the storage entity node at described obj ect file global logic numbering calculating object file place and the local logical number of this obj ect file in described storage entity node;
Storage object access modules, calculates the physical block number of this obj ect file, and accesses described obj ect file according to described physical block number for the initial physical block number of the storage entity node based on described obj ect file place and described local logical number.
In the inventive solutions, the data access request that receiving package is numbered containing obj ect file global logic, based on storage entity node and the local logical number of this obj ect file in the storage entity node determined at obj ect file global logic numbering calculating object file place; The physical block number of this obj ect file is calculated based on the initial physical block number of determined storage entity node and local logical number, and according to physical block number access object file.As can be seen here, the present invention can number direct calculating object file physical block number based on obj ect file global logic, eliminates the retrieval link of file system, therefore improves data access rate.
Accompanying drawing explanation
Fig. 1 is the storage object access method process flow diagram of distributed memory system according to an embodiment of the present invention;
Fig. 2 is the distribution schematic diagram of obj ect file in storage entity node according to an embodiment of the present invention;
Fig. 3 is the distribution schematic diagram according to obj ect file in another embodiment storage entity node of the present invention;
Fig. 4 is the structural drawing of the storage object access means of the distributed memory system of an embodiment of the present invention.
Embodiment
For making the object, technical solutions and advantages of the present invention clearly, below in conjunction with accompanying drawing, the present invention is described in further detail.
For the ease of understanding, first simplicity of explanation is carried out to the relational language in distributed storage technology.
Global file system: the file system set up in the block stores service that distributed storage cluster provides.
Storage entity node: the node of store data in distributed memory system.
Obj ect file: certain a part of storage entity representing distributed memory system can be such as Ext4 file.
Metadata node: the attribute data of record distributed memory system, can be an independently physical machine, also can be a program.
Physical block number: the sector number of certain data block of physical storage device.
In embodiments of the present invention, obj ect file has global logic numbering respectively.Storage entity node and the local logical number of this obj ect file in determined storage entity node at obj ect file place can be determined based on obj ect file global logic numbering, and determine the physical block number of obj ect file thus, thus according to the direct access object file of physical block number, and data access rate can be improved.
Fig. 1 is the storage object access method process flow diagram of the distributed memory system of an embodiment of the present invention.
As shown in Figure 1, the method comprises:
Step 101: receiving package is containing the data access request of obj ect file global logic numbering.
Here, client receiving package is containing the data access request of obj ect file global logic numbering.This data access request both can be data write request data being write obj ect file, also can be the data read request reading data from obj ect file.
The global logic numbering of obj ect file is included in data access request.Obj ect file global logic numbering is the unique reference number of obj ect file in distributed memory system, for identification of object file uniquely.
The present invention can in several ways in advance for obj ect file sets up global logic numbering.Such as, obj ect file can be created continuously respectively in each storage entity node, and number for each obj ect file arranges global logic, and record the initial physical block number of each storage entity node, wherein the local logical number in storage entity node can jointly determine the global logic numbering of obj ect file by the numbering of obj ect file place storage entity node and obj ect file.
In one embodiment, in each storage entity node, can create the obj ect file of identical number continuously, the storage space value wherein shared by each obj ect file is identical.
In another embodiment, obj ect file can be created continuously in each storage entity node, and record the initial physical block number of each storage entity node and the obj ect file global logic Serial Number Range of each storage entity node, storage space value wherein shared by each obj ect file is identical, and the obj ect file number of each storage entity node both can be identical, also can be different.
Such as, Fig. 2 is the distribution schematic diagram of obj ect file in storage entity node according to an embodiment of the present invention.
As seen from Figure 2, distributed storage cluster comprises multiple storage entity node, is respectively storage entity node 1, storage entity node 2 ... storage entity node w, wherein w is the numbering of storage entity node.
In storage entity node 1, create the obj ect file having multiple formed objects continuously, the global logic numbering of these obj ect file is 10,11,12,13 respectively, etc.The global logic numbering of these obj ect file includes two-dimensional signal, is numbering (namely 1) and the local logical number of obj ect file in storage entity node 1 (as 0,1,2 etc.) of obj ect file place storage entity node respectively.Particularly, obj ect file 10 shows that this obj ect file is positioned at the 0th local logical number position of storage entity node 1; Obj ect file 11 shows that this obj ect file is positioned at the 1st local logical number position of storage entity node 1; Obj ect file 12 shows that this obj ect file is positioned at the 2nd local logical number position of storage entity node 1; Etc..
Suppose that the initial physical block number of storage entity node 1 is blockbase_1, the physical block number that each obj ect file takies is T.The local logical number of obj ect file 10 is 0, and the physical block number of obj ect file 10 is blockbase_1+0 × T, is blockbase_1; The local logical number of obj ect file 11 is 1, and the physical block number of obj ect file 11 is blockbase_1+1 × T, is blockbase_1+T; The local logical number of obj ect file 12 is 2, and the physical block number of obj ect file 12 is blockbase_1+2 × T, is blockbase_1+2T; The rest may be inferred, and the local logical number of obj ect file 1k is the physical block number of k, obj ect file 1k is blockbase_1+ (k) T, and wherein k is the local logical number of obj ect file in storage entity node 1.
Similarly, create continuously and have multiple obj ect file in storage entity node 2, the global logic numbering of these obj ect file is 20,21,22,23 respectively, etc.Similarly, in storage entity node 2, the global logic numbering of each obj ect file includes two-dimensional signal, numbering (namely 2) and the local logical number of obj ect file in storage entity node 2 (as 0,1,2 etc.) of obj ect file place storage entity node respectively.Particularly, obj ect file 20 shows that this obj ect file is positioned at the 0th local logical number position of storage entity node 2; Obj ect file 21 shows that this obj ect file is positioned at the 1st local logical number position of storage entity node 2; Obj ect file 22 shows that this obj ect file is positioned at the 2nd local logical number position of storage entity node 2; Etc..
Suppose that the initial physical block number of storage entity node 2 is blockbase_2, the physical block number T that each obj ect file takies.The local logical number of obj ect file 20 is 0, then the physical block number of obj ect file 20 is blockbase_2+0 × T, is blockbase_2; The local logical number of obj ect file 21 is 1, and the physical block number of obj ect file 21 is blockbase_2+1 × T, is blockbase_2+T; The local logical number of obj ect file 22 is 2, and the physical block number of obj ect file 22 is blockbase_2+2 × T, is blockbase_2+2T; The rest may be inferred, and the local logical number of obj ect file 2k is the physical block number of k, obj ect file 2k is blockbase_2+ (k) T, and wherein k is the local logical number of obj ect file in storage entity node 2.
The rest may be inferred, and creating continuously in storage entity node w has multiple obj ect file, and the global logic numbering of obj ect file is w0, w1, w2 respectively, w3, etc.In storage entity node w, the global logic numbering of each obj ect file includes two-dimensional signal, be respectively the numbering of obj ect file place storage entity node (namely w) and the local logical number of this obj ect file in storage entity node w (as 0,1,2 etc.).Particularly, obj ect file w0 shows that this obj ect file is positioned at the 0th the local logical number position of storage entity node w; Obj ect file w1 shows that this obj ect file is positioned at the 1st the local logical number position of storage entity node w; Obj ect file w2 shows that this obj ect file is positioned at the 2nd the local logical number position of storage entity node w; Etc..
Suppose that the initial physical block number of storage entity node w is blockbase_w, the physical block number T that each obj ect file takies.The local logical number of obj ect file w0 is 0, then the physical block number of obj ect file w0 is blockbase_w+0 × T, is blockbase_w; The local logical number of obj ect file w1 be 1, obj ect file w1 physical block number be blockbase_w+1 × T, be blockbase_w+T; The local logical number of obj ect file w2 be 2, obj ect file w2 physical block number be blockbase_w+2 × T, be blockbase_w+2T; The rest may be inferred, and the local logical number of obj ect file wk is the physical block number of k, obj ect file wk is blockbase_w+ (k) T, and wherein k is the local logical number of obj ect file in storage entity node w.
In the above-described example, the global logic numbering of obj ect file determined by the numbering of this obj ect file place storage entity node and the local logical number of this obj ect file in storage entity node, and storage space value shared by each obj ect file is identical.
In a kind of embodiment of above-mentioned example, storage entity node 1, storage entity node 2 ... the obj ect file number that storage entity node w is comprised separately is identical, and records storage entity node 1, storage entity node 2 respectively at the metadata node place of distributed memory system further ... the initial physical block number of storage entity node w.
In the another kind of embodiment of above-mentioned example, storage entity node 1, storage entity node 2 ... obj ect file number respective comprised in storage entity node w both can be identical, also can be different.Storage entity node 1, storage entity node 2 is recorded respectively further at the metadata node place of distributed memory system ... the initial physical block number of storage entity node w and storage entity node 1, storage entity node 2 ... the obj ect file global logic Serial Number Range of storage entity node w.
In embodiments of the present invention, can also carry out dividing into groups to realize dynamic capacity-expanding for obj ect file.Such as, when certain storage entity node increase has new hard disk, new dilatation part can be joined existing storage entity node as a new obj ect file group.Now, the local logical number of obj ect file in storage entity node can specifically comprise: the group number of this obj ect file place obj ect file group and this obj ect file local logical number in obj ect file group.That is, can divide into groups for obj ect file in advance, thus the global logic of obj ect file numbering can include three-dimensional information, is respectively: logical number in the numbering of obj ect file place storage entity node, the group number of obj ect file place obj ect file group and the group of obj ect file in obj ect file group.
Fig. 3 is the distribution schematic diagram according to obj ect file in another embodiment storage entity node of the present invention.
As seen from Figure 3, distributed storage cluster comprises multiple storage entity node, is respectively storage entity node 1, storage entity node 2 ... storage entity node w, wherein w is the numbering of storage entity node.
Create continuously in storage entity node 1 and have multiple group of objects, group number is respectively group 0, group 1 ... group A, wherein A is the numbering of group.Create the obj ect file having identical number in each group continuously, and the size of each obj ect file is identical.
The global logic of obj ect file is numbered and determined by the numbering of obj ect file place storage entity node and the local logical number of obj ect file in storage entity node.And the local logical number of obj ect file determined by logical number in the group number of obj ect file place obj ect file group and the group of obj ect file in obj ect file group.Therefore, the global logic numbering of obj ect file determined by logical number in the group in the storage entity node numbering at the obj ect file group place at this obj ect file place, the group number of this obj ect file place obj ect file group and obj ect file group.
Such as, in the group 0 of storage entity node 1, the global logic numbering of each obj ect file created continuously is 100,101,102 respectively, etc.The global logic numbering of these obj ect file includes three-dimensional information, logical number (as 0,1,2 etc.) in the numbering (namely 1) of obj ect file place storage entity node, the group number (namely 0) of obj ect file place obj ect file group and the group of obj ect file in obj ect file group respectively.Such as, obj ect file 100 shows that obj ect file is arranged in the 0th group logical number position of the group 0 of storage entity node 1; Obj ect file 101 shows that obj ect file is arranged in group 0 the 1st the group logical number position of storage entity node 1; Obj ect file 102 shows that obj ect file is arranged in group 0 the 2nd the group logical number position of storage entity node 1; Etc..
Suppose that the initial physical block number of storage entity node 1 is blockbase_1, the physical block number that each obj ect file takies is T, and the physical block number of group is G.The global logic of obj ect file 100 is numbered 100, then the storage entity node numbering at obj ect file 100 place is 1, and the local logical number of obj ect file 100 is 00, namely the group number of obj ect file 100 place obj ect file group is 0, in the group of obj ect file 100 in obj ect file group 0, logical number is 0, so the physical block number of obj ect file 100 is blockbase_1+0 × G+0 × T, is blockbase_1; The global logic of obj ect file 101 is numbered 101, then the storage entity node numbering at obj ect file 101 place is 1, and the local logical number of obj ect file 101 is 01, namely the group number of obj ect file 101 place obj ect file group is 0, in the group of obj ect file 101 in obj ect file group 0, logical number is 1, so the physical block number of obj ect file 101 is blockbase_1+0 × G+1 × T, is blockbase_1+T; The rest may be inferred, the global logic of obj ect file 10k is numbered 10k, then the storage entity node numbering at obj ect file 10k place is 1, and the local logical number of obj ect file 10k is 0k, namely the group number of obj ect file 10k place obj ect file group is 0, in the group of obj ect file 10k in obj ect file group 0, logical number is k, so the physical block number of obj ect file 10k is blockbase_1+0 × G+ (k) T, be blockbase_1+ (k) T, wherein k is logical number in the group of obj ect file in obj ect file group 0.
Similarly, in the group 1 of storage entity node 1, the global logic numbering of each obj ect file created continuously is 110,111,112 respectively, etc.The global logic numbering of these obj ect file includes three-dimensional information, logical number (as 0,1,2 etc.) in the numbering (namely 1) of obj ect file place storage entity node, the group number (namely 1) of this obj ect file place obj ect file group and the group of this obj ect file in obj ect file group respectively.Such as, obj ect file 110 shows that this obj ect file is arranged in the 0th local logical number position of the group 1 of storage entity node 1; Obj ect file 111 shows that this obj ect file is arranged in group 1 the 1st local logical number position of storage entity node 1; Obj ect file 112 shows that this obj ect file is arranged in group 1 the 2nd local logical number position of storage entity node 1; Etc..
Suppose that the initial physical block number of storage entity node 1 is blockbase_1, the physical block number of group is G, and the size of obj ect file is T.The global logic of obj ect file 110 is numbered 110, then the storage entity node numbering at obj ect file 110 place is 1, and the local logical number of obj ect file 110 is 10, namely the group number of obj ect file 110 place obj ect file group is 1, in the group of obj ect file 110 in obj ect file group 1, logical number is 1, so the physical block number of obj ect file 110 is blockbase_1+1 × G+0 × T, is blockbase_1+G; The global logic of obj ect file 111 is numbered 111, then the storage entity node numbering at obj ect file 111 place is 1, and the local logical number of obj ect file 111 is 11, namely the group number of obj ect file 111 place obj ect file group is 1, in the group of obj ect file 111 in obj ect file group 1, logical number is 1, so the physical block number of obj ect file 111 is blockbase_1+1 × G+1 × T, is blockbase_1+G+T; The rest may be inferred, the global logic of obj ect file 11k is numbered 11k, then the storage entity node numbering at obj ect file 11k place is 1, and the local logical number of obj ect file 11k is 1k, namely the group number of obj ect file 11k place obj ect file group is 1, in the group of obj ect file 1k in obj ect file group 1, logical number is k, so the physical block number of obj ect file 11k is blockbase_1+1 × G+ (k) T, be blockbase_1+G+ (k) T, wherein k is logical number in the group of obj ect file in obj ect file group 1.
The rest may be inferred, and in the group A of storage entity node 1, the global logic numbering of each obj ect file created continuously is 1A0,1A1,1A2 respectively, etc.The global logic numbering of these obj ect file includes three-dimensional information, logical number (as 0,1,2 etc.) in the numbering (namely 1) of obj ect file place storage entity node, the group number (i.e. A) of this obj ect file place obj ect file group and the group of this obj ect file in obj ect file group respectively.Such as, obj ect file 1A0 shows that this obj ect file is arranged in the 0th the local logical number position of the group A of storage entity node 1; Obj ect file 1A1 shows that this obj ect file is arranged in group A the 1st local logical number position of storage entity node 1; Obj ect file 1A2 shows that this obj ect file is arranged in group A the 2nd local logical number position of storage entity node 1; Etc..
Suppose that the initial physical block number of storage entity node 1 is blockbase_1, the physical block number of group is G, and the size of obj ect file is T.The global logic of obj ect file 1A0 is numbered 1A0, then the storage entity node numbering at obj ect file 1A0 place is 1, and the local logical number of obj ect file 1A0 is A0, namely the group number of obj ect file 1A0 place obj ect file group is A, in the group of obj ect file 1A0 in obj ect file group A, logical number is 0, so the physical block number of obj ect file 1A0 is blockbase_1+A × G+0 × T, is blockbase_1+AG; The global logic of obj ect file 1A1 is numbered 1A1, then the storage entity node numbering at obj ect file 1A1 place is 1, and the local logical number of obj ect file 1A1 is A1, namely the group number of obj ect file 1A1 place obj ect file group is A, in the group of obj ect file 1A1 in obj ect file group A, logical number is 1, so the physical block number of obj ect file 1A1 is blockbase_1+A × G+1 × T, is blockbase_1+AG+T; The rest may be inferred, the global logic of obj ect file 1Ak is numbered 1Ak, then the storage entity node numbering at obj ect file 1Ak place is 1, and the local logical number of obj ect file 1Ak is Ak, namely the group number of obj ect file 1Ak place obj ect file group is A, in the group of obj ect file 1Ak in obj ect file group A, logical number is k, so the physical block number of obj ect file 1Ak is blockbase_1+A × G+ (k) T, be blockbase_1+AG+ (k) T, wherein k is logical number in the group of obj ect file in obj ect file group A.
More than describe the obj ect file of each group in storage entity node 1 in detail, similarly, storage entity node 2 ... storage entity node w also has similar structure, repeats no more this.
In a kind of embodiment of above-mentioned example, in each storage entity node, create the obj ect file group having identical number.Now, can in the initial physical block number of each storage entity node of metadata node record of distributed memory system and the physical block size often organized.
In a kind of embodiment of above-mentioned example, also can create the obj ect file group of different number in each storage entity node.Now, can at the obj ect file global logic Serial Number Range of the initial physical block number of each storage entity node of metadata node record of distributed memory system, the physical block size often organized and each storage entity node.
In embodiments of the present invention, obj ect file can be created when storage entity node starts.From the local file system of storage entity node, the obj ect file created is a common file, does not destroy the existing file system architecture of storage entity node.Therefore, can so that date restoring when storage entity node failure.
More than describe the physical meaning between obj ect file global logic numbering and actual deposit position in detail.After client obtains obj ect file global logic numbering, corresponding actual deposit position can be determined based on obj ect file global logic numbering.
Step 102: storage entity node and the local logical number of this obj ect file in the storage entity node determined of determining obj ect file place based on obj ect file global logic numbering.
In one embodiment, when the global logic numbering of each obj ect file in storage entity node includes two-dimensional signal (namely comprising numbering and the local logical number of this obj ect file in storage entity node of obj ect file place storage entity node), and when comprising the obj ect file of identical number in each storage entity node:
Assuming that the obj ect file number created in each storage entity node is n, obj ect file global logic is numbered m.So, determine that the storage entity node at obj ect file place and the local logical number of this obj ect file in the storage entity node determined specifically comprise based on obj ect file global logic numbering:
The lower round numbers of (m/n) is defined as the numbering of the storage entity node at obj ect file place, wherein/be division arithmetic symbol;
The value of (m%n) is defined as the local logical number of this obj ect file in storage entity node, wherein % is complementation operational symbol.
Such as, assuming that the obj ect file total number of distributed memory system is 10000, the obj ect file number of each storage entity node is 1000; The obj ect file global logic comprised in data access request is numbered 2100;
First calculate the numbering of storage entity node, namely calculate the lower round numbers of (2100/1000), result is 2, namely storage entity node be numbered 2.
Then, the value of (2100%1000) is defined as the local logical number in storage entity node 2, result of calculation is 100, and namely local logical number is 100.
In one embodiment, when the global logic numbering of each obj ect file in storage entity node includes two-dimensional signal (namely comprising numbering and the local logical number of this obj ect file in storage entity node of obj ect file place storage entity node), and obj ect file number in each storage entity node may be identical, also may not identical time:
First, obj ect file global logic Serial Number Range is comprised the storage entity node of m, be defined as the storage entity node at obj ect file place; Then, the origin object file global logic number value of this storage entity node is determined based on the obj ect file global logic Serial Number Range of the storage entity node at obj ect file place; Again by the value of (m-p), be defined as the local logical number of this obj ect file in storage entity node.
Such as, assuming that distributed memory system has 3 storage entity nodes, storage entity node 1, storage entity node 2 and storage entity node 3 is respectively.Wherein: the obj ect file global logic Serial Number Range of storage entity node 1 is (1 ~ 1000); The obj ect file global logic Serial Number Range of storage entity node 2 is (1001 ~ 3000); The obj ect file global logic Serial Number Range of storage entity node 3 is (3001 ~ 4300); The obj ect file global logic comprised in data access request is numbered 2100:
First, because 2100 are positioned within the interval of scope (1001 ~ 3000), therefore the storage entity node at obj ect file place is storage entity node 2.Then, from scope (1001 ~ 3000), the origin object file global logic number value of storage entity node is 1001.Then, calculate (2100-1001), obtain value 1099, be the local logical number of obj ect file in storage entity node 2.
Similarly, in another embodiment, when the global logic numbering of each obj ect file in storage entity node includes three-dimensional information (namely comprising logical number in the numbering of obj ect file place storage entity node, the group number of this obj ect file place obj ect file group and the group of obj ect file in storage entity node), and when in storage entity node, the number of obj ect file group is equal:
Assuming that the obj ect file number created in each storage entity node is n1, the obj ect file number in each obj ect file group is n2, and obj ect file global logic is numbered m.So, determine that the storage entity node at obj ect file place and the local logical number of this obj ect file in the storage entity node determined comprise based on obj ect file global logic numbering:
The lower round numbers of (m/n1) is defined as the numbering of the storage entity node at obj ect file place, wherein/be division arithmetic symbol;
The value of (m%n1) is defined as the local logical number of this obj ect file in storage entity node, wherein % is complementation operational symbol.Further, again the lower round numbers of ((m%n1)/n2) is defined as the group number of the storage entity group at obj ect file place, the value of ((m%n1) %n2) is defined as logical number in the group of this obj ect file in storage entity group.
Such as, assuming that the obj ect file total number of distributed memory system is 10000, the obj ect file number of each storage entity node is 1000, includes 10 obj ect file groups in each storage entity node, and the obj ect file number in so each obj ect file group is 100; The obj ect file global logic comprised in data access request is numbered 3020;
First calculate the numbering of storage entity node, namely calculate the lower round numbers of (3120/1000), result is 3, namely storage entity node be numbered 3.
Then, by (3020%1000)/100) lower round numbers be defined as the group number of storage entity group, result of calculation is 0, and namely group number is 0.Calculate (3020%1000) %100 again), result is 20, is logical number in the group of obj ect file in storage entity group.
In another embodiment, when the global logic numbering of each obj ect file in storage entity node includes three-dimensional information (namely comprising logical number in the numbering of obj ect file place storage entity node, the group number of this obj ect file place obj ect file group and the group of obj ect file in obj ect file group), and the number of obj ect file group may be identical in storage entity node, also may not identical time:
Assuming that obj ect file global logic is numbered m, first obj ect file global logic Serial Number Range is comprised the storage entity node of m, be defined as the storage entity node at obj ect file place; Then group logical number scope is comprised the group of m, be defined as the group at obj ect file place; Determine the origin object file global logic number value of the group at obj ect file place; Again by the value of (m-p), be defined as the local logical number of this obj ect file in group.
Such as, assuming that distributed memory system has 3 storage entity nodes, storage entity node 1, storage entity node 2 and storage entity node 3 is respectively.Wherein: the obj ect file global logic Serial Number Range of storage entity node 1 is (1 ~ 300), includes 3 groups; The obj ect file global logic Serial Number Range of storage entity node 2 is (301 ~ 400), includes 2 groups; The obj ect file global logic Serial Number Range of storage entity node 3 is (401 ~ 800), includes 4 groups; The obj ect file global logic comprised in data access request is numbered 555.
First, because 555 are positioned within the interval of (401 ~ 800), therefore the storage entity node at obj ect file place is storage entity node 3.And because 555 are positioned within the class range of second sub-range (501 ~ 600) of (401 ~ 800), therefore group number is 1 (group number counts from 0).
Then, from class range (501 ~ 600), the origin object file global logic number value of origin object place group is 501.Then, calculate (555-501), obtain value 54, be logical number in the group of obj ect file in the group 1 of storage entity node 2.
In addition, when creating obj ect file, can divide in group further, such as, can multiple groups etc. be comprised in a group, but the method obtaining storage entity node numbering and local logical number is similar, repeats no more.
More than describe in detail and determine the storage entity node at obj ect file place and the representative instance of the local logical number of this obj ect file in the storage entity node determined based on obj ect file global logic numbering; those skilled in the art can recognize; this description is only exemplary, and is not used in the protection domain formation restriction to embodiment of the present invention.
Step 103: the physical block number determining this obj ect file based on the initial physical block number of determined storage entity node and local logical number, and according to physical block number access object file.
Here, the initial physical block number of determined storage entity node can be inquired about from metadata node.After the initial physical block number obtaining determined storage entity node, can the physical block number of calculating object file in several ways.
In one embodiment, when the global logic numbering of each obj ect file in storage entity node includes two-dimensional signal (namely comprising numbering and the local logical number of this obj ect file in storage entity node of obj ect file place storage entity node), and when comprising the obj ect file of identical number in each storage entity node: assuming that the physical block number of obj ect file is realblock; Obj ect file global logic is numbered m; The obj ect file number created in each storage entity node is n; The initial physical block number of determined storage entity node is blockbase_i, and wherein i is the numbering of the storage entity node at obj ect file place; K is the storage space value of each obj ect file; T is the storage space value of single physical block;
realblock＝blockbase_i+(m％n)*(K/T)。
Such as, example in undertaking: assuming that the obj ect file total number of distributed memory system is 10000, the obj ect file number of each storage entity node is 1000; The obj ect file global logic comprised in data access request is numbered 2100; What calculate storage entity node according to step 102 is numbered 2; Local logical number is 100.Now, the physical block number realblock of this obj ect file is determined based on the initial physical block number of storage entity node 2.Assuming that the initial physical block number of storage entity node 2 is 5244, the storage space value of each obj ect file is 64M, and the storage space value of physical block is 512K, then:
realblock＝5244+(2100％1000)*(64M)/512K＝18044。
Therefore, can determine that the obj ect file physical block number of data access request is 18044, now directly invoking block device drives can access this physical block number.
In one embodiment, when the global logic numbering of each obj ect file in storage entity node includes two-dimensional signal (namely comprising numbering and the local logical number of this obj ect file in storage entity node of obj ect file place storage entity node), and obj ect file in each storage entity node may be identical, also may not identical time:
Assuming that the physical block number of obj ect file is realblock; The initial physical block number of determined storage entity node is blockbase_i, and wherein i is the numbering of the storage entity node at obj ect file place; K is the storage space value of each obj ect file; T is the storage space value of single physical block; Obj ect file global logic is numbered m; The origin object file global logic of storage entity node is numbered p;
Realblock, wherein realblock=blockbase_i+ (m-p) * (K/T).
Such as, in undertaking, example, assuming that distributed memory system has 3 storage entity nodes, is respectively storage entity node 1, storage entity node 2 and storage entity node 3.Wherein: the obj ect file global logic Serial Number Range of storage entity node 1 is (1 ~ 1000); The obj ect file global logic Serial Number Range of storage entity node 2 is (1001 ~ 3000); The obj ect file global logic Serial Number Range of storage entity node 3 is (3001 ~ 4300); The obj ect file global logic comprised in data access request is numbered 2100;
What calculate storage entity node according to step 102 is numbered 2; Obj ect file global logic numbering m is 2100, and origin object file global logic numbering p is 1001; Local logical number is (2100-1001)=1099; Assuming that the initial physical block number of storage entity node 2 is 5244, the storage space value of each obj ect file is 64M, and the storage space value of physical block is 512K, then
realblock＝5244+(1099)*(64M)/512K＝145916。
For another example, in another embodiment, when the global logic numbering of each obj ect file in storage entity node includes three-dimensional information (namely comprising logical number in the numbering of obj ect file place storage entity node, the group number of this obj ect file place obj ect file group and the group of obj ect file in obj ect file group), and when in storage entity node, the number of obj ect file group is equal:
Assuming that the physical block number of obj ect file is realblock; The initial physical block number of determined storage entity node is blockbase_i, and wherein i is the numbering of the storage entity node at obj ect file place; K is the storage space value of each obj ect file; T is the storage space value of single physical block; Obj ect file global logic is numbered m; The origin object file global logic of storage entity node is numbered p; Group number is G; The physical block size often organized is T; Q is logical number in the group of obj ect file in group;
Realblock, wherein realblock=blockbase_i+G*T+Q* (K/T);
Example in undertaking: assuming that the obj ect file total number of distributed memory system is 10000, the obj ect file number of each storage entity node is 1000, include 10 obj ect file groups in each storage entity node, the obj ect file number in so each obj ect file group is 100; The obj ect file global logic comprised in data access request is numbered 3020;
What calculate storage entity node according to step 102 is numbered 3; Group number is 0; In the group of obj ect file in group 0, logical number is 20.Now, the physical block number realblock of this obj ect file is determined based on the initial physical block number of storage entity node 3.
Assuming that the initial physical block number of storage entity node 3 is 8244, the storage space value of each obj ect file is 64M, and the storage space value of physical block is 512K, then:
realblock＝8244+(20)*(64M)/512K＝10804。
For another example, in another embodiment, when the global logic numbering of each obj ect file in storage entity node includes three-dimensional information (namely comprising logical number in the numbering of obj ect file place storage entity node, the group number of this obj ect file place obj ect file group and the group of obj ect file in obj ect file group), and the number of obj ect file group can be equal in storage entity node, also can unequal time:
Assuming that the physical block number of obj ect file is realblock; The initial physical block number of determined storage entity node is blockbase_i, and wherein i is the numbering of the storage entity node at obj ect file place; K is the storage space value of each obj ect file; T is the storage space value of single physical block; Obj ect file global logic is numbered m; The origin object file global logic of storage entity node is numbered p; Group number is G; The physical block size often organized is T; Q is logical number in the group of obj ect file in group;
Realblock, wherein realblock=blockbase_i+G*T+Q* (K/T);
Example in undertaking: assuming that distributed memory system has 3 storage entity nodes, be respectively storage entity node 1, storage entity node 2 and storage entity node 3.Wherein: the obj ect file global logic Serial Number Range of storage entity node 1 is (1 ~ 300), includes 3 groups; The obj ect file global logic Serial Number Range of storage entity node 2 is (301 ~ 400), includes 2 groups; The obj ect file global logic Serial Number Range of storage entity node 3 is (401 ~ 800), includes 4 groups; The obj ect file global logic comprised in data access request is numbered 555;
What calculate storage entity node according to step 102 is numbered 3; Group number is 2; In the group of obj ect file in group 2, logical number is 54.Now, the physical block number realblock of this obj ect file is determined based on the initial physical block number of storage entity node 3; Assuming that the initial physical block number of storage entity node 3 is 8244, the storage space value of each obj ect file is 64M, and the storage space value of physical block is 512K; The physical block size often organized is 1000;
realblock＝8244+1000*1+(54)*(64M)/512K＝16156。
In one embodiment, can also in the metadata node record storage entity node of distributed memory system the initial physical block number of each group.When determining local logical number in storage entity node of the numbering of obj ect file place storage entity node, the group number of obj ect file place obj ect file group and obj ect file based on global logic numbering, can according to the physical block number of the direct calculating object file of initial physical block number of group.
Such as, assuming that the global logic of obj ect file is numbered 303, be positioned at the 0th group of storage entity node 1, and the local logical number in the 0th group is 4; The initial physical block number that query metadata node gets the group number 0 of storage entity node 1 is 510; The storage space value of each obj ect file is 64M, and the storage space value of physical block is 512K; Now
realblock＝510+3*(64M)/512K＝1790。
When determining the physical block number of obj ect file, according to the direct access object file of physical block number, and without the need to calling local file system, therefore data access rate can be significantly improved.
More than describe the instantiation of calculating object file physical block number in detail, it will be appreciated by those of skill in the art that this example is only for purposes of illustration, and be not used in the restriction of scope formation.
Based on above-mentioned labor, the invention allows for a kind of storage object access means of distributed memory system.
Fig. 4 is the storage object access means structural drawing according to distributed memory system of the present invention.As shown in Figure 4, this device 400 comprises:
Receiver module 401, for the data access request of receiving package containing obj ect file global logic numbering;
Numbering computing module 402, for based on the storage entity node at obj ect file global logic numbering calculating object file place and the local logical number of this obj ect file in storage entity node;
Storage object access modules 403, calculates the physical block number of this obj ect file for the initial physical block number of the storage entity node based on obj ect file place and local logical number, and according to physical block number access object file.
In one embodiment:
Data access request is data write request; Storage object access modules 403, for being positioned at by data write in the obj ect file of the storage space of physical block number; Or
Data access request is data read request; Storage object access modules 403, for reading data from the obj ect file of the storage space being arranged in physical block number.
In one embodiment, distributed memory system comprises at least two storage entity nodes, and this device comprises further:
Obj ect file creation module 404, for creating obj ect file continuously respectively in each storage entity node;
Global logic numbering arranges module 405, for arranging obj ect file global logic numbering for each obj ect file, wherein obj ect file global logic is numbered and determined by the numbering of this obj ect file place storage entity node and the local logical number of this obj ect file in storage entity node;
Physical block number logging modle 406, for recording the initial physical block number of each storage entity node.
In one embodiment:
Obj ect file creation module 404, for creating the obj ect file of identical number respectively in each storage entity node continuously, the storage space value wherein shared by each obj ect file is identical.
In one embodiment:
The obj ect file number created in each storage entity node is n, and obj ect file global logic is numbered m; Numbering computing module 402, for the lower round numbers of (m/n) being defined as the numbering of the storage entity node at obj ect file place, wherein/be division arithmetic symbol; The value of (m%n) is defined as the local logical number of this obj ect file in storage entity node, wherein % is complementation operational symbol;
Storage object access modules 403, for determining realblock, wherein realblock=blockbase_i+ (m%n) * (K/T);
The wherein obj ect file number of n for creating in each storage entity node; M is obj ect file global logic numbering; Realblock is the physical block number of obj ect file; Blockbase_i is the initial physical block number of determined storage entity node; I is the numbering of the storage entity node at obj ect file place; K is the storage space value of each obj ect file; T is the storage space value of single physical block.
In one embodiment:
Obj ect file creation module 404, for creating the identical obj ect file of storage space value continuously respectively in each storage entity node; Logging modle 406, is further used for the obj ect file global logic Serial Number Range recording each storage entity node.
In one embodiment:
Numbering computing module 402, for obj ect file global logic Serial Number Range being comprised the storage entity node of m, is defined as the storage entity node at obj ect file place; Based on the origin object file global logic numbering p of the obj ect file global logic Serial Number Range determination storage entity node of the storage entity node at obj ect file place; By the value of (m-p), be defined as the local logical number of this obj ect file in storage entity node; Storage object access modules 403, for determining realblock, wherein realblock=blockbase_i+ (m-p) * (K/T); Wherein m is obj ect file global logic numbering; Realblock is the physical block number of obj ect file; Blockbase_i is the initial physical block number of determined storage entity node; I is the numbering of the storage entity node at obj ect file place; K is the storage space value of each obj ect file; T is the storage space value of single physical block.
In one embodiment, this device 400 comprises further: obj ect file creation module 404, also for creating obj ect file group continuously respectively in each storage entity node, and creates obj ect file continuously in each obj ect file group; And local logical number in storage entity node determined by logical number in the group number of this obj ect file place obj ect file group and the group of this obj ect file in obj ect file group.
In sum, the present invention includes: the data access request that receiving package is numbered containing obj ect file global logic, based on storage entity node and the local logical number of this obj ect file in the storage entity node determined at obj ect file global logic numbering calculating object file place; The physical block number of this obj ect file is calculated based on the initial physical block number of determined storage entity node and local logical number, and according to physical block number access object file.As can be seen here, the present invention can number direct calculating object file physical block number based on obj ect file global logic, eliminates the retrieval link of file system, therefore improves data access rate.
And the present invention according to calculating physical block number direct invoking block device drives access object file, can be conducive to the raising of data access performance further.
The above, be only preferred embodiment of the present invention, be not intended to limit protection scope of the present invention.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (16)
1. a storage object access method for distributed memory system, it is characterized in that, the method comprises:
Receiving package is containing the data access request of obj ect file global logic numbering;
Based on storage entity node and the local logical number of this obj ect file in described storage entity node at described obj ect file global logic numbering calculating object file place;
Calculate the physical block number of this obj ect file based on the initial physical block number of the storage entity node at described obj ect file place and described local logical number, and access described obj ect file according to described physical block number.
2. the storage object access method of distributed memory system according to claim 1, is characterized in that, described distributed memory system comprises at least two storage entity nodes, and the method comprises in advance:
Obj ect file is created continuously respectively in each storage entity node;
For each obj ect file arranges obj ect file global logic numbering, wherein said obj ect file global logic is numbered and determined by the numbering of this obj ect file place storage entity node and the local logical number of this obj ect file in described storage entity node;
Record the initial physical block number of each storage entity node.
3. the storage object access method of distributed memory system according to claim 2, it is characterized in that, the described obj ect file that creates continuously in each storage entity node respectively comprises: the obj ect file creating identical number respectively in each storage entity node continuously, the storage space value wherein shared by each obj ect file is identical.
4. the storage object access method of distributed memory system according to claim 3, is characterized in that;
The described storage entity node based on the described obj ect file place of obj ect file global logic numbering calculating and the local logical number of this obj ect file in the described storage entity node determined comprise:
The lower round numbers of (m/n) is defined as the numbering of the storage entity node at described obj ect file place, wherein/be division arithmetic symbol;
The value of (m%n) is defined as the local logical number of described obj ect file in described storage entity node, wherein % is complementation operational symbol;
The physical block number that the initial physical block number of the described storage entity node based on obj ect file place and described local logical number calculate this obj ect file comprises:
Determine realblock, wherein realblock=blockbase_i+ (m%n) * (K/T);
The wherein obj ect file number of n for creating in each storage entity node; M is described obj ect file global logic numbering; Realblock is the physical block number of described obj ect file; Blockbase_i is the initial physical block number of determined storage entity node; I is the numbering of the storage entity node at described obj ect file place; K is the storage space value of each obj ect file; T is the storage space value of single physical block.
5. the storage object access method of distributed memory system according to claim 2, it is characterized in that, the described obj ect file that creates continuously in each storage entity node respectively comprises: in each storage entity node, create the identical obj ect file of storage space value continuously respectively;
The method also comprises: the obj ect file global logic Serial Number Range recording each storage entity node.
6. the storage object access method of distributed memory system according to claim 5, is characterized in that;
The described storage entity node based on the described obj ect file place of described obj ect file global logic numbering calculating and the local logical number of this obj ect file in the described storage entity node determined comprise:
Obj ect file global logic Serial Number Range is comprised the storage entity node of m, be defined as the storage entity node at described obj ect file place;
Obj ect file global logic Serial Number Range based on the storage entity node at described obj ect file place determines the origin object file global logic numbering p of this storage entity node;
By the value of (m-p), be defined as the local logical number of this obj ect file in described storage entity node;
The physical block number that the initial physical block number of the described storage entity node based on obj ect file place and described local logical number calculate this obj ect file comprises:
Determine realblock, wherein realblock=blockbase_i+ (m-p) * (K/T);
Wherein m is described obj ect file global logic numbering; Realblock is the physical block number of described obj ect file; Blockbase_i is the initial physical block number of determined storage entity node; I is the numbering of the storage entity node at described obj ect file place; K is the storage space value of each obj ect file; T is the storage space value of single physical block.
7. the storage object access method of distributed memory system according to claim 2, is characterized in that,
Describedly in each storage entity node, create obj ect file continuously respectively, comprising:
In each storage entity node, create obj ect file group continuously respectively, in each obj ect file group, create obj ect file continuously;
Local logical number in described storage entity node determined by logical number in the group number of this obj ect file place obj ect file group and the group of this obj ect file in described obj ect file group.
8. the storage object access method of the distributed memory system according to any one of claim 1-7, is characterized in that,
Described data access request is data write request; Describedly access described obj ect file according to physical block number and comprise: obj ect file data write being positioned at the storage space of described physical block number; Or
Described data access request is data read request; Describedly access described obj ect file according to physical block number and comprise: read data from the obj ect file of the storage space being arranged in described physical block number.
9. a storage object access means for distributed memory system, is characterized in that, this device comprises:
Receiver module, for the data access request of receiving package containing obj ect file global logic numbering;
Numbering computing module, for based on the storage entity node at described obj ect file global logic numbering calculating object file place and the local logical number of this obj ect file in described storage entity node;
Storage object access modules, calculates the physical block number of this obj ect file, and accesses described obj ect file according to described physical block number for the initial physical block number of the storage entity node based on described obj ect file place and described local logical number.
10. the storage object access means of distributed memory system according to claim 9, is characterized in that, described distributed memory system comprises at least two storage entity nodes, comprises further:
Obj ect file creation module, for creating obj ect file continuously respectively in each storage entity node;
Global logic numbering arranges module, for arranging described obj ect file global logic numbering for each obj ect file, wherein said obj ect file global logic is numbered and determined by the numbering of this obj ect file place storage entity node and the local logical number of this obj ect file in described storage entity node;
Physical block number logging modle, for recording the initial physical block number of each storage entity node.
The storage object access means of 11. distributed memory systems according to claim 10, it is characterized in that, described obj ect file creation module, for creating the obj ect file of identical number respectively in each storage entity node continuously, the storage space value wherein shared by each obj ect file is identical.
The storage object access means of 12. distributed memory systems according to claim 11, is characterized in that,
Described numbering computing module, for the lower round numbers of (m/n) being defined as the numbering of the storage entity node at described obj ect file place, wherein/be division arithmetic symbol; The value of (m%n) is defined as the local logical number of this obj ect file in described storage entity node, wherein % is complementation operational symbol;
Described storage object access modules, for determining realblock, wherein realblock=blockbase_i+ (m%n) * (K/T);
The wherein obj ect file number of n for creating in each storage entity node; M is described obj ect file global logic numbering; Realblock is the physical block number of described obj ect file; Blockbase_i is the initial physical block number of determined storage entity node; I is the numbering of the storage entity node at described obj ect file place; K is the storage space value of each obj ect file; T is the storage space value of single physical block.
The storage object access means of 13. distributed memory systems according to claim 10, is characterized in that,
Described obj ect file creation module, for creating the identical obj ect file of storage space value continuously respectively in each storage entity node; Described logging modle, is further used for the obj ect file global logic Serial Number Range recording each storage entity node.
The storage object access means of 14. distributed memory systems according to claim 13, is characterized in that;
Described numbering computing module, for obj ect file global logic Serial Number Range being comprised the storage entity node of m, is defined as the storage entity node at described obj ect file place; Based on the origin object file global logic numbering p of the obj ect file global logic Serial Number Range determination storage entity node of the storage entity node at described obj ect file place; By the value of (m-p), be defined as the local logical number of this obj ect file in described storage entity node;
Described storage object access modules, for determining realblock, wherein realblock=blockbase_i+ (m-p) * (K/T);
Wherein m is described obj ect file global logic numbering; Realblock is the physical block number of described obj ect file; Blockbase_i is the initial physical block number of determined storage entity node; I is the numbering of the storage entity node at described obj ect file place; K is the storage space value of each obj ect file; T is the storage space value of single physical block.
The storage object access means of 15. distributed memory systems according to claim 10, is characterized in that,
Described obj ect file creation module, also for creating obj ect file group continuously respectively in each storage entity node, creates obj ect file continuously in each obj ect file group;
Local logical number in described storage entity node determined by logical number in the group number of this obj ect file place obj ect file group and the group of this obj ect file in described obj ect file group.
The storage object access means of 16. distributed memory systems according to any one of claim 9-15, is characterized in that,
Described data access request is data write request; Storage object access modules, for being positioned at by data write in the obj ect file of the storage space of described physical block number; Or
Described data access request is data read request; Storage object access modules, for reading data from the obj ect file of the storage space being arranged in described physical block number.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410473575.5A CN104239517B (en) | 2014-09-17 | 2014-09-17 | The storage object access method and device of a kind of distributed memory system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410473575.5A CN104239517B (en) | 2014-09-17 | 2014-09-17 | The storage object access method and device of a kind of distributed memory system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104239517A true CN104239517A (en) | 2014-12-24 |
| CN104239517B CN104239517B (en) | 2018-05-15 |
Family
ID=52227576
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410473575.5A Active CN104239517B (en) | 2014-09-17 | 2014-09-17 | The storage object access method and device of a kind of distributed memory system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104239517B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101751233A (en) * | 2009-12-31 | 2010-06-23 | 成都索贝数码科技股份有限公司 | Method and system for expanding capacity of memory device |
| CN102043795A (en) * | 2009-10-13 | 2011-05-04 | 上海新华控制技术(集团)有限公司 | Establishing method for process control historical data file structure and data read-write method |
| CN102594852A (en) * | 2011-01-04 | 2012-07-18 | 中国移动通信集团公司 | Data access method, node and system |
| CN103984607A (en) * | 2013-02-08 | 2014-08-13 | 华为技术有限公司 | Distributed storage method, device and system |
-
2014
- 2014-09-17 CN CN201410473575.5A patent/CN104239517B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102043795A (en) * | 2009-10-13 | 2011-05-04 | 上海新华控制技术(集团)有限公司 | Establishing method for process control historical data file structure and data read-write method |
| CN101751233A (en) * | 2009-12-31 | 2010-06-23 | 成都索贝数码科技股份有限公司 | Method and system for expanding capacity of memory device |
| CN102594852A (en) * | 2011-01-04 | 2012-07-18 | 中国移动通信集团公司 | Data access method, node and system |
| CN103984607A (en) * | 2013-02-08 | 2014-08-13 | 华为技术有限公司 | Distributed storage method, device and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104239517B (en) | 2018-05-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108389118B (en) | Asset management system, method and device and electronic equipment | |
| US9916176B2 (en) | Method and apparatus of accessing data of virtual machine | |
| CN104685498B (en) | The hardware implementation mode of polymerization/division operation：Hash table method | |
| CN107423422B (en) | Spatial data distributed storage and search method and system based on grid | |
| CN109086388B (en) | Block chain data storage method, device, equipment and medium | |
| CN104156380A (en) | Distributed memory Hash indexing method and system | |
| CN106649828B (en) | Data query method and system | |
| CN103324533A (en) | distributed data processing method, device and system | |
| CN109074309A (en) | Data access between calculate node | |
| CN104346458A (en) | Data storage method and device | |
| CN104881466A (en) | Method and device for processing data fragments and deleting garbage files | |
| CN111459948B (en) | Transaction integrity verification method based on centralized block chain type account book | |
| CN114817341B (en) | Method and device for accessing database | |
| CN111309245B (en) | Hierarchical storage writing method and device, reading method and device and system | |
| CN104484131A (en) | Device and corresponding method for processing data of multi-disk servers | |
| WO2021174763A1 (en) | Database management method and apparatus based on lookup table | |
| CN103942301A (en) | Distributed file system oriented to access and application of multiple data types | |
| CN107205024A (en) | Data duplicate removal method and system in a kind of cloud storage system | |
| CN103279489A (en) | Method and device for storing metadata | |
| CN104158863A (en) | Cloud storage mechanism based on transaction-level whole-course high-speed buffer | |
| CN105468644A (en) | Method and device for performing query in database | |
| CN109460406A (en) | A kind of data processing method and device | |
| CN106570029B (en) | Data processing method and system for distributed relational database | |
| CN106302667A (en) | Code management system and method | |
| CN107590077A (en) | A kind of Spark load memory access behavior method for tracing and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant after: Xinhua three Technology Co., Ltd. Address before: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant before: Huasan Communication Technology Co., Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |