CN110807013A - Data migration method and device for distributed data storage cluster - Google Patents
Data migration method and device for distributed data storage cluster Download PDFInfo
- Publication number
- CN110807013A CN110807013A CN201810877478.0A CN201810877478A CN110807013A CN 110807013 A CN110807013 A CN 110807013A CN 201810877478 A CN201810877478 A CN 201810877478A CN 110807013 A CN110807013 A CN 110807013A
- Authority
- CN
- China
- Prior art keywords
- data
- migration
- wal
- working node
- target
- 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
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the application provides a data migration method and device for a distributed data storage cluster, wherein the method comprises the following steps: the method comprises the steps of obtaining a pre-written log WAL of a working node of a source cluster, wherein the WAL is used for recording stored data of the working node, reading the content of the WAL so as to obtain target migration data from the stored data of the working node, and sending the target migration data to a message middleware, and the message middleware is used for providing the target migration data for a target data cluster.
Description
Technical Field
The present application relates to the field of computers, and in particular, to a data migration method and apparatus for a distributed data storage cluster.
Background
In a distributed data storage cluster, it is often necessary to synchronize data stored by a database to other databases. Taking the HBase as an example, it is usually necessary to synchronize data in the HBase to other databases, for example, synchronize data in the HBase to other databases for data analysis, or synchronize data in the HBase to other databases to create a search index. Based on this, it is necessary to provide a technical solution to migrate data stored in the distributed data storage cluster.
Disclosure of Invention
The embodiment of the application aims to provide a data migration method and device for a distributed data storage cluster, so as to migrate data stored by the distributed data storage cluster.
To achieve the above purpose, the embodiments of the present application are implemented as follows:
the embodiment of the application provides a data migration method for a distributed data storage cluster, which comprises the following steps: acquiring a pre-written log WAL of a working node of a source cluster, wherein the WAL is used for recording stored data of the working node; reading the content of the WAL to acquire target migration data from the stored data of the working node; and sending the target migration data to a message middleware, wherein the message middleware is used for providing the target migration data for a target data cluster.
An embodiment of the present application provides a data migration apparatus for a distributed data storage cluster, including: the acquisition module is used for acquiring a pre-written log WAL of a working node of a source cluster, wherein the WAL is used for recording stored data of the working node; a reading module, configured to read the content of the WAL, so as to obtain target migration data from the stored data of the working node; and the migration module is used for sending the target migration data to a message middleware, and the message middleware is used for providing the target migration data for a target data cluster.
An embodiment of the present application provides a data migration device for a distributed data storage cluster, including: a processor; and a memory arranged to store computer executable instructions that, when executed, cause the processor to implement the data migration method described above.
The embodiment of the application provides a storage medium for storing computer executable instructions, and the executable instructions realize the data migration method when being executed.
In this embodiment, by obtaining a pre-written log WAL of a working node of a source cluster, where the WAL is used to record stored data of the working node, read content of the WAL, obtain target migration data from the stored data of the working node, and send the target migration data to middleware for providing target migration data message to a target data cluster, data stored in the source cluster can be migrated, and the data stored in the source cluster is imported into the target data cluster. Because the data storage operation of the distributed data storage cluster does not need to be monitored, the target migration data can be obtained by reading the content of the WAL, so that the data migration flow and the data storage flow do not interfere with each other, the system resources are saved, and the data migration efficiency is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.
FIG. 1 is a schematic diagram of a distributed data storage cluster according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a data migration method according to an embodiment of the present application;
FIG. 3 is a schematic diagram of data migration according to an embodiment of the present application;
FIG. 4a is a schematic diagram of data migration according to an embodiment of the present application;
FIG. 4b is a schematic diagram of data migration according to an embodiment of the present application;
FIG. 5 is a block diagram illustrating a data migration apparatus according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of a data migration apparatus according to an embodiment of the present application.
Detailed Description
The embodiment of the application provides a data migration method and device for a distributed data storage cluster, so that data stored by the distributed data storage cluster is migrated.
In order to make those skilled in the art better understand the technical solutions in the present application, 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, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. 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 application.
Fig. 1 is a schematic diagram of a distributed data storage cluster provided in an embodiment of the present application, and as shown in fig. 1, the cluster includes a working node, a management node, and a common storage space, where the working node may be multiple, and may be 101, 102, and 103 shown in fig. 1. There are at least 1 policing node, which may be 104 as shown in fig. 1. As shown in fig. 1, the cluster further includes a common storage space 105, and the common storage space 105 is a storage space that each of the working nodes and the management node can access.
In an embodiment, the distributed data storage cluster is an Hbase cluster, the working node includes a RegionServers node, the managing node includes a Master node, and the public storage space includes a ZooKeeper.
By the method in the embodiment, data stored in the source cluster can be imported into the Message middleware, and the Message middleware can be a Message Queue (MQ) and provides data to the target data cluster through the Message middleware.
Fig. 2 is a schematic flowchart of a data migration method according to an embodiment of the present application, where the method can be applied to a source cluster and executed by a specific process in a work node of the source cluster. As shown in fig. 2, the method includes:
step S202, obtaining a WAL (Write-ahead logging) of a working node of a source cluster, wherein the WAL is used for recording stored data of the working node;
step S204, reading the content of the WAL to acquire target migration data from the stored data of the working node;
step S206, the target migration data is sent to a message middleware, and the message middleware is used for providing the target migration data for the target data cluster.
In this embodiment, by obtaining a pre-written log WAL of a working node of a source cluster, where the WAL is used to record stored data of the working node, read content of the WAL, obtain target migration data from the stored data of the working node, and send the target migration data to middleware for providing target migration data message to a target data cluster, data stored in the source cluster can be migrated, and the data stored in the source cluster is imported into the target data cluster. Because the data storage operation of the distributed data storage cluster does not need to be monitored, the target migration data can be obtained by reading the content of the WAL, so that the data migration flow and the data storage flow do not interfere with each other, the system resources are saved, and the data migration efficiency is improved.
The method in this embodiment can be applied to a source cluster and executed by a specific process in a working node of the source cluster, and after the working node of the source cluster is started to operate, the specific process in the working node for taking charge of data migration continuously executes the method flow in fig. 2, and the incremental data of the working node is exported in real time by reading the WAL content, so as to achieve the purpose of data real-time migration.
In this embodiment, a path queue is stored in the work node, where the path queue is configured to store a log path of the WAL of the work node, and the path queue may store the log path of each WAL according to a generation time sequence of each WAL, and the log path of the WAL may be used to indicate a specific storage address of the WAL. In one example, after the work node starts running, a new WAL is created, a log path of the WAL is saved in a path queue, the work node records the stored data in the new WAL, and after one WAL is recorded fully, the work node creates the next WAL again.
Correspondingly, in step S202, obtaining the pre-written log WAL of the working node of the source cluster may be: and acquiring a log path of the WAL from the path queue of the working node, and acquiring the corresponding WAL according to the acquired log path.
In this embodiment, the WAL is used to record the stored data of the working node. The contents of the WAL include the following fields: < sequence number > < time > < table > < operation 1> < operation 2>, each operation including the following fields: < operation type > < row > < column > < value >, wherein when the operation type is "write operation", a row field and a column field indicate storage locations of data in the database, and a value field indicates stored data contents.
In step S204, the reading of the content of the WAL to obtain the target migration data from the stored data of the working node may be: all stored data of the working nodes recorded in the WAL are used as target migration data, or the target migration data are extracted from the stored data of the working nodes recorded in the WAL according to preset data migration configuration information.
In one case, after the contents of the WAL are read, all stored data of the working nodes recorded in the WAL are set as target migration data. In another case, preset data migration configuration information is obtained, for example, data migration configuration information is obtained from a public storage space of the distributed data storage cluster, where the configuration information is used to indicate a row position, a column position, and the like of the target migration data in the database. And extracting target migration data from the stored data of the working nodes recorded in the WAL according to the data migration configuration information and the fields contained in the content of the WAL.
For example, according to the data migration configuration information, it is determined that the target migration data is located in X rows and Y columns in the database, and then, in the content of the read WAL, data stored in X rows and Y columns in the database is extracted, and the data is used as the target migration data.
In this embodiment, the data migration configuration information is set in the public storage space of the distributed data storage cluster, so that each working node in the cluster can conveniently acquire the configuration information, and if the configuration information is changed, each working node can acquire the changed configuration information.
In this embodiment, through the step S206, the target migration data can be sent to the message middleware, and the message middleware can provide the target migration data to the target data cluster, for example, the target data cluster may actively obtain the target migration data from the message middleware, or the message middleware writes the target migration data into the target data cluster. The target data cluster refers to a cluster that ultimately acquires the target migration data.
In a specific embodiment, the working node includes a content reading offset, and the content reading offset is used to indicate a reading position for reading the content of the WAL, and the content can be read at the position indicated by the content reading offset in the WAL. For example, the content reading offset is a, which indicates the position of the nth log in the WAL, so that the nth log is read in the WAL according to the content reading offset.
In this embodiment, the specific implementation process of the method in fig. 2 may be: and acquiring the WAL of the source cluster working node, acquiring a content reading offset, and reading the content of the acquired WAL according to the content reading offset. In a specific example, the path queue includes multiple log paths, a log path at the head of the queue is obtained from the path queue, the content in the WAL corresponding to the log path is read according to the content read offset, after the content of the WAL is read, the content read offset may be updated according to a preset offset update rule, for example, after each log is read, the content read offset is increased by a specific value, such as by 1, so as to read the next log, and after all the content of one WAL is read, the content read offset value is initialized, so as to read the content of the next WAL.
In this embodiment, if it is determined that the content read from the WAL includes the target migration data according to the preset data migration configuration information, a content read offset corresponding to the read content is inserted into the data sending queue. The data sending queue may include one or more content reading offsets, and the logs corresponding to the content reading offsets included in the data sending queue all include the target migration data. In this embodiment, the target migration data in the log corresponding to each content reading offset in the data sending queue may be sequentially sent to the message middleware, so that the message middleware provides the target migration data to the target data cluster. In this embodiment, in the data sending queue, each time one piece of target migration data is sent, the corresponding content reading offset may be deleted.
Specifically, a target offset may be determined in each content reading offset in the data sending queue, for example, the content reading offset at the head of the queue is determined as the target offset, if the data sending queue includes a WAL identifier associated with the target offset, the WAL corresponding to the WAL identifier is determined as the WAL corresponding to the target offset, otherwise, the WAL currently read in the path queue is determined as the WAL corresponding to the target offset, then, in the WAL corresponding to the target offset, the content is obtained according to the target offset, the obtained target migration data in the content is sent to the message middleware as the target migration data corresponding to the target offset, and thus, according to this process, the target migration data corresponding to each content reading offset in the data sending queue is all sent to the message middleware.
Fig. 3 is a schematic diagram of data migration according to an embodiment of the present application, and as shown in fig. 3, the data migration apparatus includes a path queue and a data sending queue, where the path queue includes a plurality of log paths, obtains a log path from a head of the path queue, reads content from a WAL corresponding to the log path according to a content read offset, and writes the content read offset into the data sending queue, for example, writes into a tail of the data sending queue, if the read content includes target migration data. The data sending queue may include a plurality of content reading offsets, and target migration data corresponding to each content reading offset included in the data sending queue is sent to the message middleware to complete data migration. In this embodiment, the log path of the WAL whose content is completely read may be removed from the path queue, for example, when the content of the WAL corresponding to the log path located at the head of the path queue is completely read, the log path is deleted from the path queue.
In the embodiment, the data migration is realized by using the data sending queue, the next piece of target migration data can be directly sent after the last piece of target migration data is sent, and the next piece of target migration data is sent without waiting for the message middleware to send the successful response information or the failed response information of the last piece of target migration data, so that the data migration efficiency is improved.
In this embodiment, before sending the target migration data to the message middleware, the format of the target migration data may be converted into a format allowed by the message middleware, so that the format of the target migration data meets the format requirement of the message middleware.
Further, the method in this embodiment further includes: and determining the position of the target migration data in the WAL, and if the target migration data fails to be sent to the message middleware, reading the content of the WAL again from the determined position so as to repeatedly send the target migration data to the message middleware.
In this embodiment, after the target migration data is sent to the message middleware, a response message returned by the message middleware may be received, and if the message middleware does not return a response message after exceeding a set duration, it is determined that the target migration data is failed to be sent, and otherwise, it is determined that the target migration data is successfully sent. In this embodiment, when the position of the target migration data in the WAL is determined, the line number where the target migration data is located in the WAL may be determined. In this embodiment, when the content of the WAL is read, a line-by-line reading mode may be adopted, so that if the target migration data fails to be sent to the message middleware, the content of the WAL may be read again from the determined position, thereby achieving an effect of repeatedly obtaining the target migration data, and repeatedly sending the target migration data to the message middleware through the flow in fig. 2.
Taking the scenario shown in fig. 3 as an example, when sending of the target migration data to the message middleware fails, the log path corresponding to the target migration data may be removed from the path queue or not removed. If the log path corresponding to the target migration data which is failed to be sent is removed from the path queue, the log path corresponding to the target migration data which is failed to be sent can be inserted into the head of the path queue, and the current content reading offset is modified to be the content reading offset corresponding to the target migration data which is failed to be sent, so that the effect of re-obtaining the target migration data and migrating the target migration data is achieved. Or, if the log path corresponding to the target migration data that has failed to be sent is not removed from the path queue, the current content reading offset may be modified to be the content reading offset corresponding to the target migration data that has failed to be sent, so as to achieve the effect of reacquiring and migrating the target migration data.
Fig. 4a is a schematic diagram of data migration according to an embodiment of the present application, and as shown in fig. 4a, a path queue includes three log paths, and a WAL corresponding to a log path at the head of the queue includes target migration data in both a first log and a second log, so that a content read offset 1 corresponding to the first log and a content read offset 2 corresponding to the second log are sent to a data sending queue, and a content read offset is modified to 3, so that a third log in the WAL corresponding to the log path at the head of the queue is read according to the modified content read offset. In the data sending queue, if the target migration data corresponding to the content reading offset 1 fails to be sent, because the log path corresponding to the target migration data which fails to be sent is not removed from the path queue, the content reading offset is modified to 1, so that a first log is read from the WAL corresponding to the log path at the head of the queue according to the modified content reading offset, the content reading offset corresponding to the first log is repeatedly sent to the data queue, and the target migration data is resent in a log rollback mode. After the first log is repeatedly sent, the content reading offset can be updated to 2, so that the second log is continuously read.
Fig. 4b is a schematic diagram of data migration provided in an embodiment of the present application, and is different from fig. 4a, when target migration data corresponding to a content reading offset 1 fails to be sent, a WAL corresponding to a log path located at the head of a queue in a path queue in fig. 4b is not a WAL corresponding to the content reading offset 1, so that a log path of the WAL corresponding to the content reading offset 1 is determined, the determined log path is inserted at the head of the path queue, and the content reading offset is modified to 1, so that a first log is read from the WAL corresponding to the log path located at the head of the queue according to the modified content reading offset, and the content reading offset corresponding to the first log is repeatedly sent to the data queue, and resending of the target migration data is achieved in a log rollback manner.
Therefore, according to the embodiment, when the target migration data is failed to be sent, data rollback can be achieved, and the target migration data is sent to the message middleware again, so that data cannot be missed during data migration.
In this embodiment, the location of the target migration data in the WAL may also be determined, and if the target migration data is successfully sent to the message middleware, the data migration progress of the working node is determined according to the determined location, and the data migration progress of the working node is backed up in the public storage space of the source cluster.
Specifically, the data migration progress of the work node is used to indicate which WALs of the work node have all target migration data in migration completed, and which position is read in the WAL currently being read. In the structure shown in fig. 1, each working node can access the common storage space, and therefore, in the common storage space, each working node can back up a corresponding data migration progress.
Taking the scenario shown in fig. 3 as an example, the path queue and the data sending queue may both be set in the memory space of the working node, and in consideration of the situation that the working node runs, in this embodiment, each working node backs up its data migration progress by setting a backup path queue in the common storage space. Each working node creates a backup path queue in a public storage space of the distributed data storage cluster, the backup path queue is used for storing the log paths of the WALs of the corresponding working nodes, the storage sequence of each log path in the backup path queue can be the same as that of each log path in the path queue, and each time a new WAL is created by a working node, the corresponding log path is written into the backup path queue.
After the target migration data is successfully sent to the message middleware, the working node determines that all the target migration data contained in the target migration data is successfully sent to the WAL of the message middleware, deletes the log path of the WAL in the backup path queue corresponding to the working node, determines the read-completed part in the currently read WAL, and marks the read-completed part in the backup path queue corresponding to the working node, for example, marks the previous ten pieces of content in the currently read WAL.
In one example, the working node may periodically delete all log paths of target migration data after migration completion in a backup path queue of the common storage space according to the migration progress of the target migration data, and periodically mark the contents of read completion in the WAL currently being read in the backup path queue.
In this embodiment, the management and control node may further obtain a data migration progress of each working node in the common storage space, and determine, according to the migration progress, target migration data that has not been migrated by each working node. When deleting the WAL of each working node, the management and control node deletes the WAL of each working node according to the target migration data which is not migrated by each working node, so that the WAL where the target migration data which is not migrated by the working node is located is not deleted.
For example, when a managed node of the distributed data storage cluster needs to delete the WAL of a certain working node in the storage space, it may read a remaining log path in the backup path queue of the working node, where the WAL corresponding to the remaining log path is the WAL to which the corresponding target migration data is not migrated, and the WAL is not deleted by the managed node.
In the embodiment, the data migration progress of the working node is backed up in the public storage space of the source cluster, so that the data migration progress is not lost after the working node is crashed, and the data migration efficiency is improved.
In this embodiment, each working node may backup the data migration progress in the common storage space, and the method in this embodiment further includes: determining a working node with abnormal data migration in a source cluster, starting a data migration recovery thread for the abnormal working node, acquiring the data migration progress of the abnormal working node in a public storage space of the source cluster through the data migration recovery thread, and migrating data for the abnormal working node according to the data migration progress of the abnormal working node through the data migration recovery thread.
Specifically, when data migration of each working node is abnormal, for example, when the data migration is abnormally crashed, a notification message is sent to other working nodes, and based on the notification message, the working node can determine the working node with the abnormal data migration in the source cluster, and then start a data migration recovery thread for the abnormal working node. Then, through the thread, obtaining the data migration progress of the abnormal working node in the public storage space of the source cluster, wherein the data migration progress can be used for indicating which WALs of the abnormal working node are not migrated. And finally, migrating data for the abnormal working node through the data migration recovery thread according to the data migration progress of the abnormal working node.
Migrating data for the abnormal working node according to the data migration progress of the abnormal working node through the data migration recovery thread, which may specifically be: and determining the WAL which is not migrated by the abnormal working node according to the data migration progress of the abnormal working node, acquiring the target migration data of the abnormal working node from the non-migrated WAL, and sending the target migration data of the abnormal working node to a message middleware to migrate the data for the abnormal working node.
Specifically, the WAL which is not migrated to the abnormal working node is determined according to the data migration progress of the abnormal working node, where the WAL which is not migrated may include the WAL whose content is not read completely and the WAL which is being read when the abnormality occurs, and a specific process of obtaining the target migration data of the abnormal working node from the WAL which is not migrated may refer to the foregoing description, and is not repeated here, and finally, the target migration data of the abnormal working node is sent to the message middleware to migrate the data for the abnormal working node.
Taking the scenario in fig. 3 as an example, when a path queue and a data transmission queue of a certain working node are abnormal, such as the path queue and the data transmission queue are abnormally empty, the execution main body in the present solution can acquire a backup path queue of the abnormal working node from the common storage space, and migrate the remaining target migration data of the abnormal working node according to the acquired backup path queue.
The migration of the remaining target migration data of the abnormal working node according to the obtained backup path queue may be: obtaining a log path from the obtained backup path queue of the abnormal working node, generating a content reading offset, reading content from the WAL corresponding to the obtained log path according to the generated content reading offset, creating a data sending queue, writing the content reading offset into the created data sending queue if the read content contains target migration data, and sequentially sending the target migration data corresponding to each content reading offset in the created data sending queue to a message middleware to migrate the remaining target migration data of the abnormal working node. The marking condition in the backup path queue may be obtained, where the marking condition is used to mark a read-completed part in a WAL currently being read when an abnormality occurs in a working node, and a content read offset is generated according to the marking condition.
In this embodiment, since data is migrated to an abnormal working node through a separate data migration recovery thread, the data migration flow of the execution main body and the working flow of the data migration recovery thread are independent of each other and do not affect each other, so that the data migration efficiency of the execution main body is improved.
Therefore, according to the embodiment, data migration can be performed for the working node of the user, data migration can be performed for the abnormal working node, and the effect that the data migration is not affected when the working node is abnormal is achieved.
In the foregoing, a data migration method is introduced, and based on the method, this embodiment further provides a data migration apparatus for a distributed data storage cluster, fig. 5 is a schematic diagram of module composition of the data migration apparatus provided in this embodiment of the present application, and as shown in fig. 5, the apparatus includes an obtaining module 51, a reading module 52, and a migration module 53.
Specifically, the obtaining module 51 is configured to obtain a pre-written log WAL of a working node of a source cluster, the WAL is configured to record stored data of the working node, the reading module 52 is configured to read content of the WAL to obtain target migration data from the stored data of the working node, and the migration module 53 is configured to send the target migration data to a message middleware, where the message middleware is configured to provide the target migration data to a target data cluster.
Optionally, the reading module 52 is specifically configured to: all stored data of the working nodes recorded in the WAL are used as target migration data, or the target migration data are extracted from the stored data of the working nodes recorded in the WAL according to preset data migration configuration information.
Optionally, the apparatus further comprises: the device comprises a first position determining module used for determining the position of target migration data in the WAL, and a rollback reading module used for reading the content of the WAL again from the determined position to repeatedly send the target migration data to the message middleware if the target migration data fails to be sent to the message middleware.
Optionally, the apparatus further comprises: and the progress backup module is used for determining the data migration progress of the working node according to the determined position and backing up the data migration progress of the working node in the public storage space of the source cluster if the target migration data is successfully sent to the message middleware.
Optionally, the apparatus further comprises: the system comprises a thread starting module, a progress acquiring module and a migration recovery module, wherein the thread starting module is used for determining a working node with abnormal data migration in a source cluster and starting a data migration recovery thread for the abnormal working node, the progress acquiring module is used for acquiring the data migration progress of the abnormal working node in a public storage space of the source cluster through the data migration recovery thread, and the migration recovery module is used for migrating data for the abnormal working node according to the data migration progress of the abnormal working node through the data migration recovery thread.
Optionally, the migration recovery module is specifically configured to: determining the WAL of the abnormal working node which is not migrated according to the data migration progress of the abnormal working node, acquiring the target migration data of the abnormal working node from the WAL which is not migrated, and sending the target migration data of the abnormal working node to a message middleware to migrate the data for the abnormal working node.
In this embodiment, by obtaining a pre-written log WAL of a working node of a source cluster, where the WAL is used to record stored data of the working node, read content of the WAL, obtain target migration data from the stored data of the working node, and send the target migration data to middleware for providing target migration data message to a target data cluster, data stored in the source cluster can be migrated, and the data stored in the source cluster is imported into the target data cluster. Because the data storage operation of the distributed data storage cluster does not need to be monitored, the target migration data can be obtained by reading the content of the WAL, so that the data migration flow and the data storage flow do not interfere with each other, the system resources are saved, and the data migration efficiency is improved.
The device in this embodiment can implement each process in the data migration method described above, and achieve a corresponding effect, which is not repeated here.
Further, an embodiment of the present application also provides a data migration device for a distributed data storage cluster, fig. 6 is a schematic structural diagram of the data migration device provided in an embodiment of the present application, as shown in fig. 6, the data migration device may generate a relatively large difference due to different configurations or performances, and may include one or more processors 901 and a memory 902, where the memory 902 may store one or more storage applications or data. Memory 902 may be, among other things, transient storage or persistent storage. The application stored in memory 902 may include one or more modules (not shown), each of which may include a series of computer-executable instructions for the data migration device. Still further, the processor 901 may be configured to communicate with the memory 902 to execute a series of computer-executable instructions in the memory 902 on the data migration device. The data migration apparatus may also include one or more power supplies 903, one or more wired or wireless network interfaces 904, one or more input-output interfaces 905, one or more keyboards 906, and the like.
In one particular embodiment, a data migration apparatus includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the data migration apparatus, and configured for execution by one or more processors the one or more programs include computer-executable instructions for:
acquiring a pre-written log WAL of a working node of a source cluster, wherein the WAL is used for recording stored data of the working node;
reading the content of the WAL to acquire target migration data from the stored data of the working node;
and sending the target migration data to a message middleware, wherein the message middleware is used for providing the target migration data for a target data cluster.
Optionally, when executed, the computer executable instructions read the content of the WAL to obtain target migration data from the stored data of the working node, including:
all stored data of the working nodes recorded in the WAL are used as target migration data;
alternatively, the first and second electrodes may be,
and extracting target migration data from the stored data of the working nodes recorded in the WAL according to preset data migration configuration information.
Optionally, the computer executable instructions, when executed, further comprise:
determining a location of the target migration data in the WAL;
and if the target migration data fails to be sent to the message middleware, reading the content of the WAL again from the determined position so as to repeatedly send the target migration data to the message middleware.
Optionally, the computer executable instructions, when executed, further comprise:
determining a location of the target migration data in the WAL;
and if the target migration data is successfully sent to the message middleware, determining the data migration progress of the working node according to the determined position, and backing up the data migration progress of the working node in the public storage space of the source cluster.
Optionally, the computer executable instructions, when executed, further comprise:
determining a working node with abnormal data migration in the source cluster, and starting a data migration recovery thread for the abnormal working node;
acquiring the data migration progress of the abnormal working node in the public storage space of the source cluster through the data migration recovery thread;
and migrating data for the abnormal working node according to the data migration progress of the abnormal working node through the data migration recovery thread.
Optionally, when executed, the computer-executable instructions migrate data for the abnormal working node according to the data migration progress of the abnormal working node, including:
determining the WAL which is not migrated by the abnormal working node according to the data migration progress of the abnormal working node;
acquiring target migration data of the abnormal working node from the non-migrated WAL;
and sending the target migration data of the abnormal working node to message middleware to migrate the data for the abnormal working node.
In this embodiment, by obtaining a pre-written log WAL of a working node of a source cluster, where the WAL is used to record stored data of the working node, read content of the WAL, obtain target migration data from the stored data of the working node, and send the target migration data to middleware for providing target migration data message to a target data cluster, data stored in the source cluster can be migrated, and the data stored in the source cluster is imported into the target data cluster. Because the data storage operation of the distributed data storage cluster does not need to be monitored, the target migration data can be obtained by reading the content of the WAL, so that the data migration flow and the data storage flow do not interfere with each other, the system resources are saved, and the data migration efficiency is improved.
The device in this embodiment can implement each process in the data migration method described above, and achieve a corresponding effect, which is not repeated here.
Further, embodiments of the present application also provide a storage medium for storing computer-executable instructions, in a specific embodiment, the storage medium may be a usb disk, an optical disk, a hard disk, and the like, and the storage medium stores computer-executable instructions that, when executed by a processor, implement the following processes:
acquiring a pre-written log WAL of a working node of a source cluster, wherein the WAL is used for recording stored data of the working node;
reading the content of the WAL to acquire target migration data from the stored data of the working node;
and sending the target migration data to a message middleware, wherein the message middleware is used for providing the target migration data for a target data cluster.
Optionally, when executed, the computer executable instructions read the content of the WAL to obtain target migration data from the stored data of the working node, including:
all stored data of the working nodes recorded in the WAL are used as target migration data;
alternatively, the first and second electrodes may be,
and extracting target migration data from the stored data of the working nodes recorded in the WAL according to preset data migration configuration information.
Optionally, the computer executable instructions, when executed, further comprise:
determining a location of the target migration data in the WAL;
and if the target migration data fails to be sent to the message middleware, reading the content of the WAL again from the determined position so as to repeatedly send the target migration data to the message middleware.
Optionally, the computer executable instructions, when executed, further comprise:
determining a location of the target migration data in the WAL;
and if the target migration data is successfully sent to the message middleware, determining the data migration progress of the working node according to the determined position, and backing up the data migration progress of the working node in the public storage space of the source cluster.
Optionally, the computer executable instructions, when executed, further comprise:
determining a working node with abnormal data migration in the source cluster, and starting a data migration recovery thread for the abnormal working node;
acquiring the data migration progress of the abnormal working node in the public storage space of the source cluster through the data migration recovery thread;
and migrating data for the abnormal working node according to the data migration progress of the abnormal working node through the data migration recovery thread.
Optionally, when executed, the computer-executable instructions migrate data for the abnormal working node according to the data migration progress of the abnormal working node, including:
determining the WAL which is not migrated by the abnormal working node according to the data migration progress of the abnormal working node;
acquiring target migration data of the abnormal working node from the non-migrated WAL;
and sending the target migration data of the abnormal working node to message middleware to migrate the data for the abnormal working node.
In this embodiment, by obtaining a pre-written log WAL of a working node of a source cluster, where the WAL is used to record stored data of the working node, read content of the WAL, obtain target migration data from the stored data of the working node, and send the target migration data to middleware for providing target migration data message to a target data cluster, data stored in the source cluster can be migrated, and the data stored in the source cluster is imported into the target data cluster. Because the data storage operation of the distributed data storage cluster does not need to be monitored, the target migration data can be obtained by reading the content of the WAL, so that the data migration flow and the data storage flow do not interfere with each other, the system resources are saved, and the data migration efficiency is improved.
The device in this embodiment can implement each process in the data migration method described above, and achieve a corresponding effect, which is not repeated here.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardsradware (Hardware Description Language), vhjhd (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (14)
1. A method of data migration for a distributed data storage cluster, the method comprising:
acquiring a pre-written log WAL of a working node of a source cluster, wherein the WAL is used for recording stored data of the working node;
reading the content of the WAL to acquire target migration data from the stored data of the working node;
and sending the target migration data to a message middleware, wherein the message middleware is used for providing the target migration data for a target data cluster.
2. The method of claim 1, wherein reading the contents of the WAL to obtain target migration data from the stored data of the worker node comprises:
all stored data of the working nodes recorded in the WAL are used as target migration data;
alternatively, the first and second electrodes may be,
and extracting target migration data from the stored data of the working nodes recorded in the WAL according to preset data migration configuration information.
3. The method of claim 1, wherein the method further comprises:
determining a location of the target migration data in the WAL;
and if the target migration data fails to be sent to the message middleware, reading the content of the WAL again from the determined position so as to repeatedly send the target migration data to the message middleware.
4. The method according to any one of claims 1-3, wherein the method further comprises:
determining a location of the target migration data in the WAL;
and if the target migration data is successfully sent to the message middleware, determining the data migration progress of the working node according to the determined position, and backing up the data migration progress of the working node in the public storage space of the source cluster.
5. The method of claim 4, wherein the method further comprises:
determining a working node with abnormal data migration in the source cluster, and starting a data migration recovery thread for the abnormal working node;
acquiring the data migration progress of the abnormal working node in the public storage space of the source cluster through the data migration recovery thread;
and migrating data for the abnormal working node according to the data migration progress of the abnormal working node through the data migration recovery thread.
6. The method of claim 5, wherein migrating data for the abnormal work node according to the data migration progress of the abnormal work node comprises:
determining the WAL which is not migrated by the abnormal working node according to the data migration progress of the abnormal working node;
acquiring target migration data of the abnormal working node from the non-migrated WAL;
and sending the target migration data of the abnormal working node to message middleware to migrate the data for the abnormal working node.
7. A data migration apparatus for a distributed data storage cluster, the apparatus comprising:
the acquisition module is used for acquiring a pre-written log WAL of a working node of a source cluster, wherein the WAL is used for recording stored data of the working node;
a reading module, configured to read the content of the WAL, so as to obtain target migration data from the stored data of the working node;
and the migration module is used for sending the target migration data to a message middleware, and the message middleware is used for providing the target migration data for a target data cluster.
8. The apparatus of claim 7, wherein the reading module is specifically configured to:
all stored data of the working nodes recorded in the WAL are used as target migration data;
alternatively, the first and second electrodes may be,
and extracting target migration data from the stored data of the working nodes recorded in the WAL according to preset data migration configuration information.
9. The apparatus of claim 7, wherein the apparatus further comprises:
a first location determination module, configured to determine a location of the target migration data in the WAL;
and a rollback reading module, configured to, if the target migration data fails to be sent to the message middleware, start to read the content of the WAL again from the determined position, so as to repeatedly send the target migration data to the message middleware.
10. The apparatus of any of claims 7-9, wherein the apparatus further comprises:
a second location determining module, configured to determine a location of the target migration data in the WAL;
and the progress backup module is used for determining the data migration progress of the working node according to the determined position and backing up the data migration progress of the working node in the public storage space of the source cluster if the target migration data is successfully sent to the message middleware.
11. The apparatus of claim 10, wherein the apparatus further comprises:
the thread starting module is used for determining the working node with abnormal data migration in the source cluster and starting a data migration recovery thread for the abnormal working node;
the progress acquisition module is used for acquiring the data migration progress of the abnormal working node in the public storage space of the source cluster through the data migration recovery thread;
and the migration recovery module is used for migrating data for the abnormal working node according to the data migration progress of the abnormal working node through the data migration recovery thread.
12. The apparatus according to claim 11, wherein the migration recovery module is specifically configured to:
determining the WAL which is not migrated by the abnormal working node according to the data migration progress of the abnormal working node;
acquiring target migration data of the abnormal working node from the non-migrated WAL;
and sending the target migration data of the abnormal working node to message middleware to migrate the data for the abnormal working node.
13. A data migration apparatus for a distributed data storage cluster, comprising: a processor; and a memory arranged to store computer executable instructions that when executed cause the processor to implement the data migration method of any one of claims 1 to 6 above.
14. A storage medium storing computer-executable instructions which, when executed, implement the data migration method of any one of claims 1 to 6 above.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810877478.0A CN110807013B (en) | 2018-08-03 | 2018-08-03 | Data migration method and device for distributed data storage cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810877478.0A CN110807013B (en) | 2018-08-03 | 2018-08-03 | Data migration method and device for distributed data storage cluster |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110807013A true CN110807013A (en) | 2020-02-18 |
| CN110807013B CN110807013B (en) | 2023-07-18 |
Family
ID=69486864
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810877478.0A Active CN110807013B (en) | 2018-08-03 | 2018-08-03 | Data migration method and device for distributed data storage cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110807013B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112000292A (en) * | 2020-08-21 | 2020-11-27 | 北京金山云网络技术有限公司 | Data migration method and device, electronic equipment and computer storage medium |
| CN112416884A (en) * | 2020-11-23 | 2021-02-26 | 中国移动通信集团江苏有限公司 | Data synchronization method and system |
| CN113032385A (en) * | 2021-05-31 | 2021-06-25 | 北京江融信科技有限公司 | Easily-extensible configurable data backup system and method |
| CN113438275A (en) * | 2021-05-27 | 2021-09-24 | 众安在线财产保险股份有限公司 | Data migration method and device, storage medium and data migration equipment |
| CN114610817A (en) * | 2022-05-12 | 2022-06-10 | 恒生电子股份有限公司 | Data synchronization method and device, multi-active system, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103514274A (en) * | 2013-09-17 | 2014-01-15 | 宁波东冠科技有限公司 | Method for data migration of non-relational database HBase |
| CN104424283A (en) * | 2013-08-30 | 2015-03-18 | 阿里巴巴集团控股有限公司 | Data migration system and data migration method |
| CN104504062A (en) * | 2014-12-22 | 2015-04-08 | 浙江宇视科技有限公司 | Data synchronization method and device of primary and standby databases |
| CN104778225A (en) * | 2015-03-27 | 2015-07-15 | 浙江大学 | Method for synchronizing data in unstructured data multi-storage system |
| US20180176016A1 (en) * | 2016-12-15 | 2018-06-21 | Nutanix, Inc. | Intent framework |
-
2018
- 2018-08-03 CN CN201810877478.0A patent/CN110807013B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104424283A (en) * | 2013-08-30 | 2015-03-18 | 阿里巴巴集团控股有限公司 | Data migration system and data migration method |
| CN103514274A (en) * | 2013-09-17 | 2014-01-15 | 宁波东冠科技有限公司 | Method for data migration of non-relational database HBase |
| CN104504062A (en) * | 2014-12-22 | 2015-04-08 | 浙江宇视科技有限公司 | Data synchronization method and device of primary and standby databases |
| CN104778225A (en) * | 2015-03-27 | 2015-07-15 | 浙江大学 | Method for synchronizing data in unstructured data multi-storage system |
| US20180176016A1 (en) * | 2016-12-15 | 2018-06-21 | Nutanix, Inc. | Intent framework |
Non-Patent Citations (3)
| Title |
|---|
| CHAO-TUNG YANG 等: "Implementation of Data Transform Method into NoSQL Database for Healthcare Data", 《2013 INTERNATIONAL CONFERENCE ON PARALLEL AND DISTRIBUTED COMPUTING, APPLICATIONS AND TECHNOLOGIES》, pages 198 - 205 * |
| 曾文英: "面向移动环境的数据存储管理方法关键技术研究", 《中国博士学位论文全文数据库 信息科技辑》, no. 06, pages 137 - 4 * |
| 李钟隽: "基于XML数据迁移中间件的研究", vol. 2007, no. 04, pages 138 - 366 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112000292A (en) * | 2020-08-21 | 2020-11-27 | 北京金山云网络技术有限公司 | Data migration method and device, electronic equipment and computer storage medium |
| CN112416884A (en) * | 2020-11-23 | 2021-02-26 | 中国移动通信集团江苏有限公司 | Data synchronization method and system |
| CN113438275A (en) * | 2021-05-27 | 2021-09-24 | 众安在线财产保险股份有限公司 | Data migration method and device, storage medium and data migration equipment |
| CN113032385A (en) * | 2021-05-31 | 2021-06-25 | 北京江融信科技有限公司 | Easily-extensible configurable data backup system and method |
| CN114610817A (en) * | 2022-05-12 | 2022-06-10 | 恒生电子股份有限公司 | Data synchronization method and device, multi-active system, electronic equipment and storage medium |
| CN114610817B (en) * | 2022-05-12 | 2022-09-27 | 恒生电子股份有限公司 | Data synchronization method and device, multi-activity system, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110807013B (en) | 2023-07-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110807013B (en) | Data migration method and device for distributed data storage cluster | |
| US10896157B2 (en) | Clone file backup and restore | |
| CN107239324B (en) | Service flow processing method, device and system | |
| CN107066519B (en) | Task detection method and device | |
| CN108628688B (en) | Message processing method, device and equipment | |
| US10055299B2 (en) | Clone file backup and restore | |
| CN107577697B (en) | Data processing method, device and equipment | |
| CN109104327B (en) | Service log generation method, device and equipment | |
| CN109284066B (en) | Data processing method, device, equipment and system | |
| CN111752633A (en) | Code loading method, device and equipment | |
| CN110633096A (en) | Node control method and device, version control method and device and distributed system | |
| CN114529417A (en) | Method for executing transaction, block chain, main node and slave node | |
| CN110895545B (en) | Shared data synchronization method and device | |
| CN111459724A (en) | Node switching method, device, equipment and computer readable storage medium | |
| CN111158858A (en) | Cloning method and device of virtual machine and computer readable storage medium | |
| CN108595315B (en) | Log collection method, device and equipment | |
| CN111399780B (en) | Data writing method, device and equipment | |
| CN110083602B (en) | Method and device for data storage and data processing based on hive table | |
| CN116048977B (en) | Test method and device based on data reduction | |
| CN110019975B (en) | Random walk, random walk method based on cluster, random walk device and equipment | |
| CN110908429A (en) | Timer operation method and device | |
| CN115391337A (en) | Database partitioning method and device, storage medium and electronic equipment | |
| CN112084171A (en) | Operation log writing method, device, equipment and medium based on Cassandra database | |
| CN111339117A (en) | Data processing method, device and equipment | |
| CN108121719B (en) | Method and device for realizing data extraction conversion loading ETL |
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 |