CN112241243B - Method for realizing active object storage system - Google Patents
Method for realizing active object storage system Download PDFInfo
- Publication number
- CN112241243B CN112241243B CN202011115392.8A CN202011115392A CN112241243B CN 112241243 B CN112241243 B CN 112241243B CN 202011115392 A CN202011115392 A CN 202011115392A CN 112241243 B CN112241243 B CN 112241243B
- Authority
- CN
- China
- Prior art keywords
- user
- osd
- method object
- policy
- active
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 228
- 238000012545 processing Methods 0.000 claims description 44
- 238000004891 communication Methods 0.000 claims description 12
- 238000012217 deletion Methods 0.000 claims description 6
- 230000037430 deletion Effects 0.000 claims description 6
- 230000008569 process Effects 0.000 claims description 5
- 230000001960 triggered effect Effects 0.000 claims description 3
- 238000005516 engineering process Methods 0.000 claims 1
- 230000006870 function Effects 0.000 abstract description 5
- 238000007781 pre-processing Methods 0.000 abstract description 3
- 238000013524 data verification Methods 0.000 abstract description 2
- 238000003745 diagnosis Methods 0.000 abstract description 2
- 238000001914 filtration Methods 0.000 abstract description 2
- 238000011084 recovery Methods 0.000 abstract description 2
- 238000012216 screening Methods 0.000 abstract description 2
- 238000007726 management method Methods 0.000 description 9
- 230000003993 interaction Effects 0.000 description 4
- 238000004364 calculation method Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides an implementation method of an active object storage system, and relates to the technical field of cloud computing. The invention provides an intelligent active object storage system, which can flexibly realize data preprocessing, such as filtering and screening, data verification and various custom functions, in the nodes of the object storage system by adding interfaces supporting active storage, modifying each layer of modules of the traditional object storage system and adding the active storage modules, and endow the nodes with certain autonomy, such as active fault diagnosis, data recovery and the like, so as to improve the performance of the storage system.
Description
Technical Field
The invention relates to the technical field of network storage, in particular to a method for realizing an active object storage system.
Background
Conventional object storage systems do not support active storage functions.
Disclosure of Invention
The invention aims to provide an implementation method of an active object storage system.
The invention adopts the following technical scheme that the invention provides a realization method of an active object storage system, which is designed to comprise a client and an active storage node OSD, wherein the client is used for providing files, blocks and object interfaces for users, and also comprises an active object service and a communication service module; the OSD is positioned on the file, the block and the object interface, the OSD comprises an active storage module, an active object management module, a file interface VFS and a communication service module, the objects are stored in a local file system of the OSD through the file interface VFS at the bottom layer of the OSD, and each object in the active object storage system is finally mapped into one file of the local file system according to the ID;
the active storage module is positioned between an active object management module of the OSD and a file interface VFS at the bottom layer, and comprises a method object processing module and a strategy object processing module; the active object service and communication service module of the client comprises a package for actively storing related commands; the OSD communication service module is used for analyzing the command transmitted by the client, and if the command is irrelevant to the active storage, the command is processed according to the processing mode of the traditional object storage system; if the method is related to the active storage, the method object processing module and the strategy object processing module are transmitted to perform the active storage processing;
the method object processing module adopts a method object to realize active storage processing, the method object is a main implementation means of active storage, after the method object is introduced, a user can download required operation into the OSD, and the OSD is used as the method object for storage and management; the method object is divided into a user method object and a system method object, wherein the user method object is a method object for operating the user object, the system method object is a method object for realizing an OSD autonomous management function according to a strategy object, and the two triggering execution methods are different; when the method object is triggered to be executed, the OSD reads the content operation of the method object through the file interface VFS autonomously.
Preferably, the method object processing module completes the registration and deletion of the method object according to the user method object related request, and associates and de-associates the corresponding user object; when a user sends a read command with an active storage mark to a system, the method object processing module can automatically read the content of the associated method object according to a given user object, schedule the user object as the input of the method object for execution, and return the executed result to the user; when a user sends a write command with an active storage mark to the system, the method object processing module can automatically read the content of the associated method object according to the given user object, input stream is used as the input of the method object for scheduling execution, and the executed result is stored in the corresponding user object.
Preferably, when the data is divided into a plurality of user objects and stored on different OSDs, the storage positions are considered when the method objects are realized, and the operation results are synchronized;
for the user method object, uploading the user method object to the OSD of each user object associated with the user method object, for the system method object, uploading the user method object to the OSD of each strategy object associated with the system method object, and all the method objects and the strategy objects are not segmented any more;
the uploading process is as follows: if the user method object is required to be uploaded, the user method object is firstly uploaded to an OSD at random, the information is stored in an external metadata server, when a client sends an associated command related to the user method object, the metadata server is searched, the OSD where the user method object and the corresponding user object are located is found, the method object is saved and copied to the OSD where all the user objects associated with the method object are located, and the associated information is written in the information attribute pages of the method object and the user object. It should be noted that if a user object is deleted or migrated, then the user method object associated therewith also needs to do the same;
if the system method object is needed to be uploaded, the system method object is uploaded to an OSD at random, the information is stored in a metadata server, when a client sends an associated command related to the system method object, the metadata server is searched, the OSD where the system method object and the corresponding strategy object are located is found, the system method object is transferred and copied to the OSD where the strategy object related to the system method object is located, the associated information is written in information attribute pages of the system method object and the OSD, and if the strategy object is deleted and migrated, the system method object related to the strategy object needs to do the same work.
Preferably, the method object is stored as multiple copies on different devices, when data is distributed on multiple OSDs, a user sequentially sends out read-write requests for using the method object to different OSDs according to (offset, len) of the user when requesting the data, reads corresponding user objects according to (offset, len) of the corresponding objects obtained by the user on each OSD, and returns a final result, so that the data are sequentially integrated at the client according to the read sequence.
Preferably, the OSD monitors the system condition according to the condition of the policy object, the policy object is also associated with a system method object, when each condition of the policy object returns a true value, the policy object triggers the corresponding system method object to execute automatically, and the policy object is a precondition for executing automatically.
Preferably, when the policy object processing module interacts with the file interface VFS, the policy object processing module completes registration and deletion of the policy object according to the policy request, and associates and de-associates the corresponding method object; after the strategy object is associated with the method object, a kernel thread is operated to read the system information in the root information attribute page and compare with the conditions, and once the conditions are met, the method object associated with the strategy object is called to be executed, and the realization of the strategy object is the basis of the automatic execution of the system method object.
Preferably, when a user needs to use a policy object to implement automatic execution of a system method object, the following procedure is executed:
(1) Submitting a system method object to be executed to a system;
(2) Registering AND writing POLICY objects to the system using osd_create_and_write_policy commands;
(3) Using an OSD_ASSOCIATE_POLICY command, associating the strategy object with a system method object to be executed;
(4) After the user finishes the steps, the policy object processing module automatically reads information in the root object attribute page, monitors the running condition of the system, reads the attribute of the policy object attribute page to obtain a system method object ID (identity) associated with the attribute, and when the running condition of the system returns true conditions in the policy object, invokes the system method object to execute;
(5) When the user no longer needs to use the POLICY object, the osd_unassociate_policy command is used to disassociate the POLICY object from the system METHOD object, and the osd_remove_method command is used to delete the POLICY object.
The invention also provides an active object storage system designed by the method.
The invention also provides an application of the active object storage system in the technical field of network storage.
The beneficial effects of the invention include: the invention provides an intelligent active object storage system, which can flexibly realize data preprocessing, such as filtering and screening, data verification and various custom functions, in the nodes of the object storage system by adding interfaces supporting active storage, modifying each layer of modules of the traditional object storage system and adding the active storage modules, and endow the nodes with certain autonomy, such as active fault diagnosis, data recovery and the like, so as to improve the performance of the storage system.
Drawings
FIG. 1 is a block diagram of an active object storage system in accordance with the present invention;
FIG. 2 is a flow chart of interaction between a method object processing module and a system according to the present invention;
FIG. 3 is a flow chart of a process for storing method objects according to the present invention;
fig. 4 is a flowchart illustrating interaction between the policy object handling module and the file interface VFS according to the present invention.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.
The invention designs an active object storage system added with an active storage module, as shown in figure 1, which comprises a Client (Client) and an active storage node (OSD), wherein the Client is used for providing files, blocks and object interfaces for users, and also comprises an active object service and a communication service module; the OSD is positioned on the file, the block and the object interface, the OSD comprises an active storage module, an active object management module, a file interface VFS and a communication service module, the objects are stored in a local file system of the OSD through the file interface VFS at the bottom layer of the OSD, and each object in the active object storage system is finally mapped into one file of the local file system according to the ID;
the active storage module is positioned between an active object management module of the OSD and a file interface VFS at the bottom layer, and comprises a method object processing module and a strategy object processing module; the active object service and communication service module of the client comprises a package for actively storing related commands; the OSD communication service module is used for analyzing the command transmitted by the client, and if the command is irrelevant to the active storage, the command is processed according to the processing mode of the traditional object storage system; if the method is related to the active storage, the method object processing module and the strategy object processing module are transmitted to perform the active storage processing.
The method object processing module adopts a method object to realize active storage processing, the method object is a main implementation means of active storage, after the method object is introduced, a user can conveniently download required operation into the OSD, and the OSD is used as the method object to store and manage. The method object is divided into a user method object and a system method object, wherein the user method object is a method object for operating the user object, the system method object is a method object for realizing an OSD autonomous management function according to a strategy object, and the main difference between the user method object and the system method object is that the triggering execution methods are different; when the method object is triggered and executed, the OSD reads the content operation of the method object through the file interface VFS autonomously; the method object is put forward so that the operation which can be put down on the storage equipment can be a calculation task or a management task, and the calculation task and the management task can be unified.
The interaction flow of the method object processing module and other modules of the whole system is shown in figure 1. The method object processing module completes the registration and deletion of the method object according to the user method object related request, and associates and de-associates the corresponding user object; when a user sends a read command with an active storage mark to a system, the method object processing module can automatically read the content of the associated method object according to a given user object, schedule the user object as the input of the method object for execution, and return the executed result to the user; when a user sends a write command with an active storage mark to the system, the method object processing module can automatically read the content of the associated method object according to the given user object, input stream is used as the input of the method object for scheduling execution, and the executed result is stored in the corresponding user object.
When data is divided into a plurality of user objects and stored on different OSDs, more factors, such as storage locations, synchronization of operation results, etc., need to be considered when implementing method objects.
For a user method object, it needs to be uploaded to the OSD where each user object associated with it is located, for a system method object, it needs to be uploaded to the OSD where each policy object associated with it is located, and all method objects and policy objects are no longer partitioned to preserve their integrity. The storing process of the method object and the policy object is shown in fig. 3.
The uploading process is as follows: if the user method object is needed to be uploaded, the user method object is uploaded to a certain OSD at random, the information is stored in an external metadata server, when a client sends an associated command related to the user method object, the metadata server is searched, the OSD where the user method object and the corresponding user object are located is found, the method object is saved and copied to all the OSDs where the user object related to the method object is located, and the associated information is written in the information attribute pages of the method object and the user object. It should be noted that if a user object is deleted or migrated, the user method object associated therewith also needs to do the same.
If the system method object is needed to be uploaded, the system method object is uploaded to a certain OSD at random, the information is stored in a metadata server, when a client sends an associated command related to the system method object, the metadata server is searched, the OSD where the system method object and the corresponding policy object are located is found, the system method object is transferred and copied to the OSD where the policy object related to the system method object is located, and the associated information is written in information attribute pages of the system method object and the corresponding policy object. If the policy object is deleted, it is migrated, and the system method object associated with it also needs to do the same.
The method object is stored on different devices as a plurality of copies, which is helpful for improving the parallelism of the devices, reducing the response time of users, and greatly improving the performance of the storage devices although occupying a certain storage space. When data is distributed over a plurality of OSDs, a user requests data, and sequentially requests read/write of the usage method object to different OSDs according to (offset, len) thereof. On each OSD, the corresponding user object is read according to the (offset, len) of the relative object obtained by itself, and the final result is returned. In this way, the data are sequentially integrated in the client according to the reading sequence, and the system is not required to perform additional processing.
A policy object is a set of conditions. It is similar to the condition judgment statement in the C language, and can judge each condition of the countermeasure object and return a boolean value. The OSD monitors the system conditions according to the policy object conditions. The policy object also needs to be associated with a certain system method object, and when each condition of the policy object returns a true value, the policy object triggers the corresponding system method object to automatically execute. Policy objects are preconditions for the automatic execution of system method objects.
The interaction flow of the policy object handling module with the file interface VFS is shown in fig. 4. The strategy object processing module completes the registration and deletion of strategy objects according to the strategy request, and associates and de-associates corresponding method objects; after the policy object is associated with the method object, a kernel thread is run to read the system information in the root information attribute page and compare with its condition. Once the conditions are met, the method object associated therewith is invoked for execution. The implementation of the policy object is the basis for the automatic execution of the system method object. When a user needs to use a policy object to realize automatic execution of a system method object, the flow to be executed is as follows:
(1) Submitting a system method object to be executed to a system;
(2) Registering AND writing POLICY objects to the system using osd_create_and_write_policy commands;
(3) Using an OSD_ASSOCIATE_POLICY command, associating the strategy object with a system method object to be executed;
(4) After the user finishes the steps, the policy object processing module automatically reads information in the root object attribute page, monitors the running condition of the system, reads the attribute of the policy object attribute page to obtain a system method object ID (identity) associated with the attribute, and when the running condition of the system returns true conditions in the policy object, invokes the system method object to execute;
(5) When the user no longer needs to use the POLICY object, the osd_unassociate_policy command is used to disassociate the POLICY object from the system METHOD object, and the osd_remove_method command is used to delete the POLICY object.
It can be seen that the system of the present invention reduces the data transmission amount on the network by lowering part of the operation modules of the application program into the Object Storage Device (OSD) to utilize the redundant parallel computing capability in the storage system, reduces the requirement of the application program for the network bandwidth, and enhances the intelligence of the OSD. The object storage and the active storage are combined to form the active object storage system, so that the advantages of the object storage and the active storage are absorbed, and the performance of the storage system is improved. The intelligent active object storage system provided by the invention can flexibly realize the data preprocessing in the nodes of the object storage system, endow the nodes with certain autonomy and improve the performance of the storage system.
The foregoing is merely exemplary embodiments of the present application and is not intended to limit the scope of the present application, and various modifications and variations may be suggested to one skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.
Claims (9)
1. The method is characterized in that the method designs the system to comprise a client and an active storage node OSD, wherein the client is used for providing files, blocks and object interfaces for users, and the method also comprises an active object service and a communication service module; the OSD is positioned on the file, the block and the object interface, the OSD comprises an active storage module, an active object management module, a file interface VFS and a communication service module, the objects are stored in a local file system of the OSD through the file interface VFS at the bottom layer of the OSD, and each object in the active object storage system is finally mapped into one file of the local file system according to the ID;
the active storage module is positioned between an active object management module of the OSD and a file interface VFS at the bottom layer, and comprises a method object processing module and a strategy object processing module; the active object service and communication service module of the client comprises a package for actively storing related commands; the OSD communication service module is used for analyzing the command transmitted by the client, and if the command is irrelevant to the active storage, the command is processed according to the processing mode of the traditional object storage system; if the method is related to the active storage, the method object processing module and the strategy object processing module are transmitted to perform the active storage processing;
the method object processing module adopts a method object to realize active storage processing, the method object is a main implementation means of active storage, after the method object is introduced, a user can download required operation into the OSD, and the OSD is used as the method object for storage and management; the method object is divided into a user method object and a system method object, wherein the user method object is a method object for operating the user object, the system method object is a method object for realizing an OSD autonomous management function according to a strategy object, and the two triggering execution methods are different; when the method object is triggered to be executed, the OSD reads the content operation of the method object through the file interface VFS autonomously.
2. The implementation method according to claim 1, wherein the method object processing module completes registration and deletion of a method object according to a user method object related request, and associates and de-associates a corresponding user object; when a user sends a read command with an active storage mark to a system, the method object processing module can automatically read the content of the associated method object according to a given user object, schedule the user object as the input of the method object for execution, and return the executed result to the user; when a user sends a write command with an active storage mark to the system, the method object processing module can automatically read the content of the associated method object according to the given user object, input stream is used as the input of the method object for scheduling execution, and the executed result is stored in the corresponding user object.
3. The method of claim 2, wherein when the data is divided into a plurality of user objects and stored on different OSDs, the method objects are implemented with consideration of storage locations, and synchronization of operation results;
for the user method object, uploading the user method object to the OSD of each user object associated with the user method object, for the system method object, uploading the user method object to the OSD of each strategy object associated with the system method object, and all the method objects and the strategy objects are not segmented any more;
the uploading process is as follows: if the user method object is required to be uploaded, the user method object is firstly uploaded to an OSD at random, the position information of the user method object is stored in an external metadata server, when a client sends an associated command related to the user method object, the metadata server is searched, the OSD where the user method object and the corresponding user object are located is found, the method object is saved and copied to all the OSDs where the user object related to the user method object is located, and the associated information is written in information attribute pages of the method object and the user object; it should be noted that if a user object is deleted or migrated, then the user method object associated therewith also needs to do the same;
if the system method object is needed to be uploaded, the system method object is uploaded to an OSD at random, the position information of the system method object is stored in a metadata server, when a client sends an associated command related to the system method object, the metadata server is searched, the OSD where the system method object and the corresponding strategy object are located is found, the system method object is transferred and copied to the OSD where the strategy object related to the system method object is located, the associated information is written in information attribute pages of the system method object and the OSD, and if the strategy object is deleted and migrated, the system method object related to the strategy object also needs to do the same work.
4. A method according to claim 3, characterized in that the method objects are stored as multiple copies on different devices, when data are distributed on multiple OSDs, the user requests data, and in turn, requests for reading and writing the method objects are sent to different OSDs according to (offset, len), and on each OSD, the corresponding user objects are read according to the (offset, len) of the corresponding object obtained by the user, and the final result is returned, so that the data are sequentially integrated at the client in the order of reading.
5. The method of claim 4, wherein the OSD monitors system conditions according to the conditions of the policy objects, the policy objects are also associated with a system method object, and when each condition of the policy objects returns a true value, the policy objects trigger the corresponding system method object to automatically execute, and the policy objects are preconditions for the system method object to automatically execute.
6. The implementation method according to claim 5, wherein, when the policy object processing module interacts with the file interface VFS, the policy object processing module completes registration and deletion of the policy object according to the policy request, and associates and de-associates the corresponding method object; after the strategy object is associated with the method object, a kernel thread is operated to read the system information in the root information attribute page and compare with the conditions, and once the conditions are met, the method object associated with the strategy object is called to be executed, and the realization of the strategy object is the basis of the automatic execution of the system method object.
7. The implementation method according to claim 6, wherein when a user needs to implement automatic execution of a system method object using a policy object, the execution flow is as follows:
(1) Submitting a system method object to be executed to a system;
(2) Registering AND writing POLICY objects to the system using osd_create_and_write_policy commands;
(3) Using an OSD_ASSOCIATE_POLICY command, associating the strategy object with a system method object to be executed;
(4) After the user finishes the steps, the policy object processing module automatically reads information in the root object attribute page, monitors the running condition of the system, reads the attribute of the policy object attribute page to obtain a system method object ID (identity) associated with the attribute, and when the running condition of the system returns true conditions in the policy object, invokes the system method object to execute;
(5) When the user no longer needs to use the POLICY object, the osd_unassociate_policy command is used to disassociate the POLICY object from the system METHOD object, and the osd_remove_method command is used to delete the POLICY object.
8. An active object storage system designed by the method of any one of claims 1 to 7.
9. Use of the active object storage system of claim 8 in the field of network storage technology.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202011115392.8A CN112241243B (en) | 2020-10-19 | 2020-10-19 | Method for realizing active object storage system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202011115392.8A CN112241243B (en) | 2020-10-19 | 2020-10-19 | Method for realizing active object storage system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN112241243A CN112241243A (en) | 2021-01-19 |
CN112241243B true CN112241243B (en) | 2024-01-26 |
Family
ID=74169156
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202011115392.8A Active CN112241243B (en) | 2020-10-19 | 2020-10-19 | Method for realizing active object storage system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN112241243B (en) |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006178926A (en) * | 2004-10-18 | 2006-07-06 | Hitachi Ltd | Storage apparatus, system and method using a plurality of object-based storage devices |
WO2010040255A1 (en) * | 2008-10-07 | 2010-04-15 | 华中科技大学 | Method for managing object-based storage system |
US9002805B1 (en) * | 2012-12-14 | 2015-04-07 | Amazon Technologies, Inc. | Conditional storage object deletion |
CN105656952A (en) * | 2014-11-11 | 2016-06-08 | 田鹏 | Data exchange platform with reliable application level |
CN107920067A (en) * | 2017-11-10 | 2018-04-17 | 华中科技大学 | A kind of intrusion detection method in active objects storage system |
KR20190055009A (en) * | 2017-11-14 | 2019-05-22 | 성균관대학교산학협력단 | Method and apparatus for providing security service |
-
2020
- 2020-10-19 CN CN202011115392.8A patent/CN112241243B/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006178926A (en) * | 2004-10-18 | 2006-07-06 | Hitachi Ltd | Storage apparatus, system and method using a plurality of object-based storage devices |
WO2010040255A1 (en) * | 2008-10-07 | 2010-04-15 | 华中科技大学 | Method for managing object-based storage system |
CN101796514A (en) * | 2008-10-07 | 2010-08-04 | 华中科技大学 | The management method of object storage system |
US9002805B1 (en) * | 2012-12-14 | 2015-04-07 | Amazon Technologies, Inc. | Conditional storage object deletion |
CN105656952A (en) * | 2014-11-11 | 2016-06-08 | 田鹏 | Data exchange platform with reliable application level |
CN107920067A (en) * | 2017-11-10 | 2018-04-17 | 华中科技大学 | A kind of intrusion detection method in active objects storage system |
KR20190055009A (en) * | 2017-11-14 | 2019-05-22 | 성균관대학교산학협력단 | Method and apparatus for providing security service |
Also Published As
Publication number | Publication date |
---|---|
CN112241243A (en) | 2021-01-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11086725B2 (en) | Orchestration of heterogeneous multi-role applications | |
US11113158B2 (en) | Rolling back kubernetes applications | |
US10657008B2 (en) | Managing a redundant computerized database using a replicated database cache | |
CA2913036C (en) | Index update pipeline | |
US11347684B2 (en) | Rolling back KUBERNETES applications including custom resources | |
CN102981929B (en) | The management method of disk mirroring and system | |
CA3137857A1 (en) | Multi-language fusion query method and multi-model database system | |
CN103595797B (en) | Caching method for distributed storage system | |
US9183130B2 (en) | Data control system for virtual environment | |
CN109299056B (en) | A kind of method of data synchronization and device based on distributed file system | |
CN105243155A (en) | Big data extracting and exchanging system | |
CN105630418A (en) | Data storage method and device | |
US20090198703A1 (en) | Intelligent data storage system | |
WO2013143215A1 (en) | Concurrency control method and system in document library system | |
CN108491163B (en) | Big data processing method and device and storage medium | |
CN104881466A (en) | Method and device for processing data fragments and deleting garbage files | |
CN110135184B (en) | Method, device, equipment and storage medium for desensitizing static data | |
CN113377868A (en) | Offline storage system based on distributed KV database | |
CN103150225B (en) | Disk full abnormity fault tolerance method of object parallel storage system based on application level agent | |
KR101765725B1 (en) | System and Method for connecting dynamic device on mass broadcasting Big Data Parallel Distributed Processing | |
CN112965939A (en) | File merging method, device and equipment | |
CN109460345A (en) | The calculation method and system of real time data | |
CN112235396A (en) | Content processing link adjustment method, content processing link adjustment device, computer equipment and storage medium | |
US20140040191A1 (en) | Inventorying and copying file system folders and files | |
CN112241243B (en) | Method for realizing active object storage system |
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 |