CN107066348B - Method and device for realizing high-availability NAS cluster - Google Patents
Method and device for realizing high-availability NAS cluster Download PDFInfo
- Publication number
- CN107066348B CN107066348B CN201710011485.8A CN201710011485A CN107066348B CN 107066348 B CN107066348 B CN 107066348B CN 201710011485 A CN201710011485 A CN 201710011485A CN 107066348 B CN107066348 B CN 107066348B
- Authority
- CN
- China
- Prior art keywords
- local
- record
- node
- database
- data
- 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 32
- 230000005012 migration Effects 0.000 claims abstract description 33
- 238000013508 migration Methods 0.000 claims abstract description 33
- 238000012545 processing Methods 0.000 claims abstract description 12
- 230000004044 response Effects 0.000 claims abstract description 12
- 230000008569 process Effects 0.000 claims description 8
- 238000004422 calculation algorithm Methods 0.000 claims description 7
- 238000006243 chemical reaction Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 1
- 238000004883 computer application Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000002360 explosive Substances 0.000 description 1
- 230000010076 replication Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- 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
- G06F16/1824—Distributed file systems implemented using Network-attached Storage [NAS] architecture
- G06F16/1827—Management specifically adapted to NAS
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/80—Database-specific techniques
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to the technical field of computer storage, in particular to a method and a device for realizing a high-availability NAS cluster. The invention discloses a method for realizing a high-availability NAS cluster, which comprises the following steps: a recording request end sends a recording request to a server-side node of a local database; the local main node of the record in other databases judges whether the data in the data main node of the record in other databases needs forced migration according to the attribute of the record request; and after receiving the response of the forced data migration, the service end node of the local database sets the local database as the database where the recorded data main node is located. The invention also discloses a device for realizing the high-availability NAS cluster, which comprises the following steps: a recording request sending and processing module, a second judging module and a resetting module. The invention realizes the data migration redundancy backup on the NAS layer, ensures that the data cannot be lost under the condition that the node fails, and realizes the high availability of the NAS cluster.
Description
Technical Field
The invention relates to the technical field of computer storage, in particular to a method and a device for realizing a high-availability NAS cluster.
Background
With the rapid development of computer applications and network technologies, digital information is in an explosive growth trend, users put higher requirements on the availability and expandability of a storage system, and a single NAS cannot meet the needs of the users, resulting in the emergence of an NAS clustering technology. The NAS cluster system combines the advantages of the NAS cluster system in two aspects: when one subsystem in the NAS cluster fails, the cluster system quickly makes a response and distributes the tasks of the subsystem to other working similar subsystems in the cluster for execution; when the total work flow exceeds the capacity of the systems in a cluster, other subsystems will be added to the cluster.
The traditional high-availability NAS cluster is realized by the problem of depending on a bottom layer file system, so that the coupling of the NAS and the bottom layer file system is very high; the decoupled NAS cluster cannot guarantee that data is not lost. Therefore, a new method is needed to solve the problem of data migration redundancy backup of the NAS cluster and improve the high availability of the NAS cluster.
Disclosure of Invention
In view of the above technical problems, an object of the present invention is to provide a method and an apparatus for implementing data migration redundancy based on a high-availability NAS cluster, so as to implement data migration redundancy backup on an NAS layer, ensure that data is not lost when a node fails, and implement high availability of the NAS cluster.
In order to achieve the purpose, the invention is realized by the following technical scheme:
the invention provides a method for realizing a high-availability NAS cluster, which comprises the following steps:
a: a recording request end sends a recording request to a server-side node of a local database;
b: the local main node of the record in other databases judges whether the data in the data main node of the record in other databases needs forced migration according to the attribute of the record request;
c: and after receiving the response of the forced data migration, the service end node of the local database sets the local database as the database where the recorded data main node is located.
Preferably, before step a, the method further comprises: the recording request end presets the attribute of the recording request as read-only and read-write.
Preferably, after step a, the method further comprises: the local main node of the record in the local database judges whether the local database has the local record node of the record by searching the local database, if so, the record request end starts to process the record in the local database; if not, the record request is sent to the local master node of the record in the other database.
Preferably, after sending the record request to the local master node of the record in the other database, the method further includes: and initializing other databases.
Preferably, step C comprises: if not, copying the data in the data main node recorded in the other database and sending the data to the service end node of the local database; if so, the local main node recorded in the other database records the node number of the data main node recorded in the other database, and the data in the data main node recorded in the other database is migrated to the local main node recorded in the other database and then migrated to the service end node of the local database.
Preferably, the local database and the other databases are both Key-value databases.
The invention also provides a device for realizing the high-availability NAS cluster, which comprises the following components:
the recording request sending and processing module is used for sending a recording request to a server node of the local database by a recording request end and processing the record;
the second judgment module is used for judging whether the data in the data main node recorded in the other databases needs to be forcibly migrated or not according to the attribute of the recording request, and if not, copying the data in the data main node recorded in the other databases and sending the data to the service end node of the local database; if so, the local main node recorded in the other database records the node number of the data main node recorded in the other database, and the data in the data main node recorded in the other database is migrated to the local main node recorded in the other database and then migrated to the service end node of the local database;
and the resetting module is used for setting the local database as the database where the recorded data main node is located after the server-side node of the local database receives the response of the forced data migration.
Preferably, the method further comprises the following steps: and the preset module is used for presetting the attribute of the recording request as read-only and read-write by the recording request end.
Preferably, the method further comprises the following steps: the first judging module is used for judging whether the local main node of the record in the local database has the local record node of the record by searching the local database, if so, the record requesting terminal starts to process the record in the local database; if not, the record request is sent to the local master node of the record in the other database.
Preferably, the method further comprises the following steps: and the initialization module is used for initializing other databases after the record request is sent to the local master node of the record in other databases.
Compared with the prior art, the method for realizing the high-availability NAS cluster has the following beneficial effects:
1. according to the invention, each record in the Key-value database is used as a basic data synchronization point, and each record realizes data migration redundancy backup on an NAS layer through conversion of different identities, so that the dependence of a record request on a bottom storage system is reduced, the data cannot be lost under the condition that a node fails, and the high availability of an NAS cluster is realized;
2. the invention endows each record in each database of the NAS cluster with three different identities, and when each database is in an initial state, the local main node and the data main node of each record are the same node number. When a recording request end sends a recording request to a service end node of a local database and the local database does not have the record, the local database determines the node numbers of the local main node and the data main node recorded in other databases of the NAS cluster through a Hash and remainder algorithm according to a Key, then sends the recording request to the local main node recorded in the other databases, the local main node recorded in the other databases judges whether the data in the data main node recorded in the other databases needs to be forcibly migrated or not according to the attribute of the recording request, and if the data needs to be forcibly migrated, the local main node recorded in the local database records the latest node number of the data main node. Therefore, when data migration occurs in the database of the NAS cluster, the local main node and the data main node of each record are different node numbers, so that conversion of different identities of each record is realized, redundant backup of data migration and real-time updating of the database in the NAS cluster are realized, and data cannot be lost under the condition that the nodes fail.
The beneficial effects of the implementation apparatus of a high-availability NAS cluster are similar to those of the implementation method of a high-availability NAS cluster, and are not described herein again.
Drawings
Fig. 1 is a schematic flow chart of a method for implementing a high-availability NAS cluster according to the present invention.
Fig. 2 is a schematic flow chart of data migration in the implementation method of the high-availability NAS cluster of the present invention.
Fig. 3 is a second flowchart illustrating an implementation method of a high-availability NAS cluster according to the present invention.
Fig. 4 is a schematic flow chart of data replication in the implementation method of the high-availability NAS cluster according to the present invention.
Fig. 5 is a schematic structural diagram of an implementation apparatus of a high availability NAS cluster according to the present invention.
Fig. 6 is a second schematic structural diagram of an implementation apparatus of a high-availability NAS cluster according to the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terms and concepts appearing in the following examples are explained below:
in a highly available NAS cluster, any one record in each database has three different identities, namely a local record node (local register node), a local master node (local master node), and a data master node (data master node).
The local recording node: the English is called Local record node, and records of common identities stored in the Local record node.
Local master node: the node number of the local master node can be obtained by calculating the Key value of each record. Therefore, any node can be guaranteed, the value of the local main node of each record does not need to be stored, and the node number of the local main node of each record can be known through calculation of the Key value of each record.
A data main node: the English full-name data master node is characterized in that in a cluster database, for one record, a data master node is unique, but is not fixed, and can be converted among a plurality of nodes in a cluster; the data master node is more like a right to have a modification right to a record, so in the clustered database, the data of the record in the data master node is always up-to-date.
The following describes a method and an apparatus for implementing a high-availability NAS cluster according to the present invention with reference to the accompanying drawings and embodiments:
example 1
As shown in fig. 1, an implementation method of a high-availability NAS cluster includes the following steps:
step S101: a recording request end sends a recording request to a service end node of a local database, and the attribute of the recording request is set to be read-only and read-write;
step S102: the local main node of the record in the local database judges whether the local database has the local record node of the record by searching the local database, if so, the S106 is carried out, and the record request end starts to process the record in the local database; if not, the recording request is sent to the local master node of the record in other databases, and step S103 is performed;
step S103: initializing the Head of the record in other databases;
step S104: the local main node of the record in other databases judges whether the data in the data main node of the record in other databases needs forced migration according to the attribute of the record request, if not, the data in the data main node of the record in other databases is copied and sent to the service end node of the local database; if so, the local main node recorded in the other database records the node number of the data main node recorded in the other database, and the data in the data main node recorded in the other database is migrated to the local main node recorded in the other database and then migrated to the service end node of the local database;
step S105: after receiving a response of the forced data migration, a service end node of the local database sets the local database as a database where the recorded data main node is located;
step S106: the record requestor begins processing the record in the local database.
Referring to fig. 2, as an implementation manner, the databases in the NAS cluster are all Key-Value databases, each record in each database has three different identities, namely a local record node (local record node), a local master node (local master node), and a data master node (data master node), and the Value is found and processed by retrieving through Key, where the Value includes two parts, namely, a Head and a Value, and a node number (ID) of the local master node (local master node) and a node number (ID) of the data master node of the record are recorded in the Head. And the local database determines the node numbers (IDs) of the local master node and the data master node recorded in other databases of the NAS cluster through a Hash remainder algorithm according to the Key.
When a record request end (NAS APP) cannot find a record in a local database, sending a record request to a service end node (local dispatcher node) of the local database, and setting the attribute of the record request as read-write; the local master node (local master node) of the record in the local database finds out that the local database does not have the local recording node (local record node) of the record by searching the local database, the local database initializes and stores the Head of the record, and then determines the node numbers (IDs) of the local master node (local master node) and the data master node (data master node) of the record in other databases of the NAS cluster according to Key through a Hash remainder algorithm, and then sends the record request to the local master node (local master node) of the record in other databases; after receiving the recording request, the local master node (local master node) of the record in other databases initializes the Head of the record in other databases, and when the other databases are in an initial state, the node numbers (IDs) of the local master node (local master node) and the data master node (data master node) of each record are the same; because the record request is a read-write attribute, forced migration is required, the local master node (local master node) of the record in the other database needs to record the node number (ID) of the data master node (data master node) of the record in the other database, and the data in the data master node (data master node) of the record in the other database is migrated to the local master node (local master node) of the record in the other database, and then migrated to the service end node (local dispatcher node) of the local database, at this time, the node numbers (IDs) of the local master node (local master node) and the data master node (data master node) of the record in the other database are different, so that the conversion of different identities of each record and the redundancy of data migration are realized; after receiving the response of the forced migration of the data, a service end node (local dispatcher node) of the local database sets the local database as a database where the data master node (data master node) of the record is located, that is, the node number (ID) of the data master node (data master node) of the record in the local database is always the latest; the record request side (NAS APP) starts processing the record in the local database.
Example 2
As shown in fig. 3, a method for implementing a high-availability NAS cluster includes the following steps:
step S201: the recording request end presets the attribute of the recording request as read-only and read-write;
step S202: a recording request end sends a recording request to a server-side node of a local database;
step S203: the local master node of the record in the local database judges whether the local database has the local record node of the record by searching the local database, if so, the S207 is carried out, and the record request end starts to process the record in the local database; if not, the local database initializes and stores the recorded Head, and then determines the node numbers of the local main node and the data main node recorded in other databases of the NAS cluster through a Hash remainder algorithm according to the Key, and sends the recording request to the local main node recorded in other databases, and the step S204 is performed;
step S204: initializing the Head of the record in other databases;
step S205: the local main node of the record in other databases judges whether the data in the data main node of the record in other databases needs forced migration according to the attribute of the record request, if not, the data in the data main node of the record in other databases is copied and sent to the service end node of the local database; if so, the local main node recorded in the other database records the node number of the data main node recorded in the other database, and the data in the data main node recorded in the other database is migrated to the local main node recorded in the other database and then migrated to the service end node of the local database;
step S206: after receiving a response of the forced data migration, a service end node of the local database sets the local database as a database where the recorded data main node is located;
step S207: the record requestor begins processing the record in the local database.
Referring to fig. 4, as an implementation manner, the databases in the NAS cluster are all Key-Value databases, each record in each database has three different identities, that is, a local record node (local record node), a local master node (local master node), and a data master node (data master node), and the Value is found and processed by retrieving through Key, where the Value includes two parts, namely, a Head and a Value, and a node number (ID) of the local master node (local master node) and a node number (ID) of the data master node of the record are recorded in the Head. And the local database determines the node numbers (IDs) of the local master node and the data master node recorded in other databases of the NAS cluster through a Hash remainder algorithm according to the Key.
When a record request end (NAS APP) cannot find a record in a local database, sending a record request to a service end node (local dispatcher node) of the local database, and setting the attribute of the record request as read-only; the local master node (local master node) of the record in the local database finds out that the local database does not have the local recording node (local record node) of the record by searching the local database, the local database initializes and stores the Head of the record, and then determines the node numbers (IDs) of the local master node (local master node) and the data master node (data master node) of the record in other databases of the NAS cluster according to Key through a Hash remainder algorithm, and then sends the record request to the local master node (local master node) of the record in other databases; after receiving the recording request, the local master node (local master node) of the record in other databases initializes the Head of the record in other databases, and when the other databases are in an initial state, the node numbers (IDs) of the local master node (local master node) and the data master node (data master node) of each record are the same; because the record request is read-only attribute, forced migration is not needed, and only the data in the data master node of the record in other databases needs to be copied and sent to the service end node (local dispatcher node) of the local database; after receiving the response of the forced migration of the data, a service end node (local dispatcher node) of the local database sets the local database as a database where the data master node (data master node) of the record is located, that is, the node number (ID) of the data master node (data master node) of the record in the local database is always the latest; the record request side (NAS APP) starts processing the record in the local database.
Example 3
As shown in fig. 5, an apparatus for implementing a high availability NAS cluster includes the following modules:
a record request sending and processing module 302, configured to send a record request to a server node in a local database and process the record, where attributes of the record request are set to be read-only and read-write in advance;
a second determining module 305, where the local master node of the record in the other database is used to determine whether forced migration of the data in the data master node of the record in the other database is needed according to the attribute of the record request, and if forced migration is not needed, the data in the data master node of the record in the other database is copied and sent to the service end node of the local database; if the forced migration is needed, the local main node recorded in the other database records the node number of the data main node recorded in the other database, and the data in the data main node recorded in the other database is migrated to the local main node recorded in the other database and then migrated to the service end node of the local database;
and a resetting module 306, configured to set the local database as the database where the recorded data master node is located after the server-side node of the local database receives the response of the forced data migration.
Wherein the recording request sending module 302 is sequentially connected with the second judging module 305 and the resetting module 306.
Example 4
As shown in fig. 6, an apparatus for implementing a high availability NAS cluster includes the following modules:
the preset module 301 is configured to preset, by the recording request end, attributes of the recording request to be read-only and read-write.
A record request sending and processing module 302, configured to send a record request to a server node in the local database and process the record;
a first judging module 303, configured to judge, by retrieving the local database, a local master node (local master node) of the record in the local database, whether the local database has a local record node of the record, and if the local database has the record, start processing the record in the local database by the record requesting terminal; and if the record does not exist in the local database, sending the record request to the local main node of the record in other databases.
The initialization module 304 is configured to initialize another database after sending the record request to the local master node of the record in the another database.
A second determining module 305, where the local master node of the record in the other database is used to determine whether forced migration of the data in the data master node of the record in the other database is needed according to the attribute of the record request, and if forced migration is not needed, the data in the data master node of the record in the other database is copied and sent to the service end node of the local database; if the forced migration is needed, the local main node recorded in the other database records the node number of the data main node recorded in the other database, and the data in the data main node recorded in the other database is migrated to the local main node recorded in the other database and then migrated to the service end node of the local database;
and a resetting module 306, configured to set the local database as the database where the recorded data master node is located after the server-side node of the local database receives the response of the forced data migration.
The presetting module 301 is sequentially connected to the recording request sending module 302, the first judging module 303, the initializing module 304, the second judging module 305 and the resetting module 306.
The above description is only an exemplary embodiment of the present invention, and should not be taken as limiting the scope of the present invention, and any equivalent changes and modifications made by those skilled in the art without departing from the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (2)
1. A method for implementing a high-availability NAS cluster is characterized by comprising the following steps:
the recording request end presets the attributes of the recording request as read-only and read-write;
a recording request end sends a recording request to a server-side node of a local database;
the local main node of the record in the local database judges whether the local database has the local record node of the record by searching the local database, if so, the record request end starts to process the record in the local database; if not, the record request is sent to the local main node of the record in other databases;
initializing other databases;
the local main node of the record in other databases judges whether the data in the data main node of the record in other databases needs forced migration according to the attribute of the record request, if not, the data in the data main node of the record in other databases is copied and sent to the service end node of the local database; if so, the local main node recorded in the other database records the node number of the data main node recorded in the other database, and the data in the data main node recorded in the other database is migrated to the local main node recorded in the other database and then migrated to the service end node of the local database;
after receiving a response of the forced data migration, a service end node of the local database sets the local database as a database where the recorded data main node is located;
the local database and other databases are both Key-value databases, and any record in each database has three different identities, namely a local record node, a local main node and a data main node; and the local database determines the node numbers of the local main node and the data main node recorded in other databases of the NAS cluster through a Hash remainder algorithm according to the Key.
2. An apparatus for implementing a high-availability NAS cluster, comprising:
the preset module is used for recording the attribute of the preset recording request of the request end as read-only and read-write;
the recording request sending and processing module is used for sending a recording request to a server node of the local database by a recording request end and processing the record;
the first judging module is used for judging whether the local main node of the record in the local database has the local record node of the record by searching the local database, if so, the record requesting terminal starts to process the record in the local database; if not, the record request is sent to the local main node of the record in other databases;
the initialization module is used for initializing other databases after sending the record request to the local main node of the record in other databases;
the second judgment module is used for judging whether the data in the data main node recorded in the other databases needs to be forcibly migrated or not according to the attribute of the recording request, and if not, copying the data in the data main node recorded in the other databases and sending the data to the service end node of the local database; if so, the local main node recorded in the other database records the node number of the data main node recorded in the other database, and the data in the data main node recorded in the other database is migrated to the local main node recorded in the other database and then migrated to the service end node of the local database;
and the resetting module is used for setting the local database as the database where the recorded data main node is located after the server-side node of the local database receives the response of the forced data migration.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710011485.8A CN107066348B (en) | 2017-01-07 | 2017-01-07 | Method and device for realizing high-availability NAS cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710011485.8A CN107066348B (en) | 2017-01-07 | 2017-01-07 | Method and device for realizing high-availability NAS cluster |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107066348A CN107066348A (en) | 2017-08-18 |
| CN107066348B true CN107066348B (en) | 2021-03-02 |
Family
ID=59623339
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710011485.8A Active CN107066348B (en) | 2017-01-07 | 2017-01-07 | Method and device for realizing high-availability NAS cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107066348B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101030946A (en) * | 2007-04-12 | 2007-09-05 | 华为技术有限公司 | Method and system for realizing data service |
| CN102158540A (en) * | 2011-02-18 | 2011-08-17 | 广州从兴电子开发有限公司 | System and method for realizing distributed database |
| CN105141456A (en) * | 2015-08-25 | 2015-12-09 | 山东超越数控电子有限公司 | Method for monitoring high-availability cluster resource |
-
2017
- 2017-01-07 CN CN201710011485.8A patent/CN107066348B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101030946A (en) * | 2007-04-12 | 2007-09-05 | 华为技术有限公司 | Method and system for realizing data service |
| CN102158540A (en) * | 2011-02-18 | 2011-08-17 | 广州从兴电子开发有限公司 | System and method for realizing distributed database |
| CN105141456A (en) * | 2015-08-25 | 2015-12-09 | 山东超越数控电子有限公司 | Method for monitoring high-availability cluster resource |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107066348A (en) | 2017-08-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11741048B2 (en) | Distributed write journals that support fast snapshotting for a distributed file system | |
| US20190188190A1 (en) | Scaling stateful clusters while maintaining access | |
| US10725691B1 (en) | Dynamic recycling algorithm to handle overlapping writes during synchronous replication of application workloads with large number of files | |
| CN101334797B (en) | Distributed file systems and its data block consistency managing method | |
| US9305072B2 (en) | Information storage system and data replication method thereof | |
| US11321291B2 (en) | Persistent version control for data transfer between heterogeneous data stores | |
| CN106776130B (en) | Log recovery method, storage device and storage node | |
| US20070061379A1 (en) | Method and apparatus for sequencing transactions globally in a distributed database cluster | |
| CN104580439B (en) | Method for uniformly distributing data in cloud storage system | |
| CN107180113B (en) | Big data retrieval platform | |
| WO2019001017A1 (en) | Inter-cluster data migration method and system, server, and computer storage medium | |
| JP2013544386A (en) | System and method for managing integrity in a distributed database | |
| US11093446B2 (en) | Duplicate request checking for file system interfaces | |
| US11768624B2 (en) | Resilient implementation of client file operations and replication | |
| JP2016521427A (en) | Method, device and system for peer-to-peer data replication and method, device and system for master node switching | |
| WO2018136760A1 (en) | Systems and methods for reconstructing cache loss | |
| CN106873902B (en) | File storage system, data scheduling method and data node | |
| KR101527634B1 (en) | Method and apparatus for providing sharding service | |
| WO2014107901A1 (en) | Data storage method, database storage node failure processing method and apparatus | |
| US20160139996A1 (en) | Methods for providing unified storage for backup and disaster recovery and devices thereof | |
| US20170315869A1 (en) | Fault-tolerant Enterprise Object Storage System for Small Objects | |
| CN107566341B (en) | Data persistence storage method and system based on federal distributed file storage system | |
| US11442894B2 (en) | Methods for scalable file backup catalogs and devices thereof | |
| US20210397599A1 (en) | Techniques for generating a consistent view of an eventually consistent database | |
| EP3349416B1 (en) | Relationship chain processing method and system, and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201231 Address after: 215000 Building 9, No.1 guanpu Road, Guoxiang street, Wuzhong Economic Development Zone, Suzhou City, Jiangsu Province Applicant after: SUZHOU LANGCHAO INTELLIGENT TECHNOLOGY Co.,Ltd. Address before: Room 1601, 16 / F, 278 Xinyi Road, Zhengdong New District, Zhengzhou City, Henan Province, 450000 Applicant before: ZHENGZHOU YUNHAI INFORMATION TECHNOLOGY Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |