CN111258954A - Data migration method, device, equipment and storage medium - Google Patents
Data migration method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN111258954A CN111258954A CN202010025782.XA CN202010025782A CN111258954A CN 111258954 A CN111258954 A CN 111258954A CN 202010025782 A CN202010025782 A CN 202010025782A CN 111258954 A CN111258954 A CN 111258954A
- Authority
- CN
- China
- Prior art keywords
- data
- migrated
- migration
- data migration
- current stage
- 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
- 238000013508 migration Methods 0.000 title claims abstract description 290
- 230000005012 migration Effects 0.000 title claims abstract description 290
- 238000000034 method Methods 0.000 title claims abstract description 261
- 230000008569 process Effects 0.000 claims abstract description 200
- 238000012795 verification Methods 0.000 claims abstract description 37
- 238000004140 cleaning Methods 0.000 claims abstract description 14
- 230000015654 memory Effects 0.000 claims description 20
- 238000005096 rolling process Methods 0.000 claims description 10
- 238000001514 detection method Methods 0.000 claims description 6
- 239000000126 substance Substances 0.000 claims description 2
- 238000013461 design Methods 0.000 description 29
- 238000004590 computer program Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 101100217298 Mus musculus Aspm gene Proteins 0.000 description 4
- 238000004891 communication Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 238000013524 data verification Methods 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 230000000903 blocking effect Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001151 other effect Effects 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
- G06F16/119—Details of migration of file systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a data migration method, a data migration device, data migration equipment and a storage medium, and relates to the technical field of data migration. The specific implementation scheme is as follows: acquiring first verification information by verifying data to be migrated; establishing a hard link for the data to be migrated in the target directory to obtain a new directory entry of the data to be migrated; acquiring second check-up information according to the data corresponding to the new directory entry in the target directory; and checking whether the data corresponding to the new directory entry is consistent with the data to be migrated or not by the first checking information and the second checking information, and if so, cleaning the source directory entry of the data to be migrated before migration. According to the data migration method and device, data migration on the single computer is achieved through the mode of establishing the hard link, a mobile interface of a data system does not need to be called in the data migration process, the data migration process is simple, efficient, safe and reliable, and risks in the data migration process are reduced. In addition, the data migration process can be reentrant, can be rolled back, can be asynchronous, and is suitable for the migration of a large number of files, and has higher security.
Description
Technical Field
The application relates to the technical field of computers, in particular to the technical field of data migration.
Background
Services are increasingly becoming mainstream when running in containers, and distributed storage systems are no exception. However, for the physical machine storage service that has stored mass data, usability, stability, user insensitivity, and the like need to be considered, and the switching process is complex. At this time, it is often more efficient (avoiding cross-network movement of data) to switch a single machine in place from the physical machine mode of operation to in-container operation. While the storage system is used as a stateful service, this single machine switching process usually needs to: migration of services and migration of service states (data). For the migration of the service, the start-stop operation of the physical machine and the container mode service process is usually required; whereas for migration of service state (data) it is usually necessary to move data within a single machine scope. For a cluster with many nodes, there is usually a central coordinator that schedules stand-alone switching tasks using rpc (Remote Procedure Call) commands. In the single machine switching process, the single machine data migration relates to a plurality of data, which is important. This puts some requirements on stand-alone data migration:
a large number of online data nodes are involved in the cluster, and the emergency rollback can be realized in the single machine migration process; a large amount of user data is involved in a single data node, and data migration is required to be safe and reliable; single point migration may have failure, and the migration process needs to be reentrant; the central coordinator and the data nodes communicate through the remote rpc, network jitter occurs with probability, and synchronous blocking calling is easy to fail, and on the other hand, the coordinator needs to operate numerous nodes, so that an asynchronous mode needs to be supported.
In the prior art, for data migration on a single computer, a mobile interface of a file system is usually called to perform data movement operations. The existing data migration method is low in safety and migration efficiency, and the risk coefficient of data on an operation line is high when a large number of files need to be migrated.
Disclosure of Invention
The application provides a data migration method, a data migration device, data migration equipment and a storage medium, so that the safety and the migration efficiency of a data migration process on a single machine are improved.
A first aspect of the present application provides a data migration method, including:
verifying the data to be migrated to acquire first verification information;
establishing a hard link for the data to be migrated in a target directory to obtain a new directory entry of the data to be migrated;
acquiring second check-up information according to the data corresponding to the new directory entry in the target directory; checking whether the data corresponding to the new directory entry is consistent with the data to be migrated or not for the first checking information and the second checking information;
and if the data corresponding to the new directory entry is consistent with the data to be migrated, cleaning the source directory entry of the data to be migrated before migration.
In the embodiment, data migration on the single computer is realized by establishing the hard link, a mobile interface of a data system is not required to be called in the data migration process, the data migration process is simple, efficient, safe and reliable, and the risk of the data migration process is reduced.
In a possible design, the first check information includes a storage structure and/or a check code before the data to be migrated is migrated, where the check code is an inode number corresponding to a source directory entry before migration or a check code acquired by a check algorithm for the data to be migrated;
the second check information comprises a storage structure and/or check codes after the data to be migrated is migrated, and the check codes are index node numbers corresponding to new directory entries or check codes acquired from data corresponding to the new directory entries through a check algorithm;
the verifying whether the data corresponding to the new directory entry is consistent with the data to be migrated for the first and second verification information includes:
and comparing whether the first check information is the same as the second check information.
In a possible design, before verifying the data to be migrated, the method further includes:
detecting a data migration environment;
and judging whether the data migration environment meets a preset condition or not.
In one possible design, the method further includes:
and recording the current stage in the data migration process in real time through a state machine.
In one possible design, the method further includes:
and when the data migration process is interrupted and a re-entry instruction is received, re-entry is carried out on the data migration process according to the current stage of the interruption moment in the state machine.
In one possible design, the reentry of the data migration process according to the current stage of the interrupt time in the state machine includes:
if the current stage is before the hard link is established, the whole data migration process is executed repeatedly;
if the current stage is in the process of establishing the hard link or the verification process after the hard link is established, deleting the new directory entry of the data to be migrated and then re-starting to execute the whole data migration process;
if the current stage is in the process of clearing the source directory entries, the process of clearing the source directory entries is continuously executed;
and if the current stage is in the process of finishing clearing the source directory entry, returning a prompt message of successful migration.
In one possible design, the method further includes:
and when a rollback instruction is received, rolling back the data migration process according to the current stage in the state machine.
In one possible design, the rolling back the data migration process according to the current stage in the state machine includes:
if the current stage is before the hard link is created, returning a prompt message of completion of rollback;
if the current stage is in the process of establishing the hard link or the verification process after the hard link is established, deleting the new directory entry of the data to be migrated;
and if the current stage is in the process of clearing the source directory entries or the process of clearing the source directory entries is completed, re-creating the source directory entries in the source directory before the migration of the data to be migrated through creating hard links, and deleting the new directory entries of the data to be migrated after the verification process.
In one possible design, the data to be migrated includes a plurality of data, and the method further includes:
performing data migration processes on a plurality of data in an asynchronous mode, and acquiring the state of each data migration process by scheduling equipment in a polling mode;
and controlling any data migration process according to the state of the data migration process.
A second aspect of the present application provides a data migration apparatus, comprising:
the verification module is used for verifying the data to be migrated to acquire first verification information;
the migration module is used for establishing a hard link for the data to be migrated in the target directory to obtain a new directory entry of the data to be migrated;
the checking module is further used for acquiring second checking information according to the data corresponding to the new directory entry in the target directory; checking whether the data corresponding to the new directory entry is consistent with the data to be migrated or not for the first checking information and the second checking information;
and the clearing module is used for clearing the source directory entry of the data to be migrated before migration if the data corresponding to the new directory entry is consistent with the data to be migrated.
In a possible design, the first check information includes a storage structure and/or a check code before the data to be migrated is migrated, where the check code is an inode number corresponding to a source directory entry before migration or a check code acquired by a check algorithm for the data to be migrated;
the second check information comprises a storage structure and/or check codes after the data to be migrated is migrated, and the check codes are index node numbers corresponding to new directory entries or check codes acquired from data corresponding to the new directory entries through a check algorithm;
when the checking module checks whether the data corresponding to the new directory entry is consistent with the data to be migrated for the first checking information and the second checking information, the checking module is configured to:
and comparing whether the first check information is the same as the second check information.
In one possible design, the apparatus further includes a detection module to:
before verifying data to be migrated, detecting a data migration environment;
and judging whether the data migration environment meets a preset condition or not.
In one possible design, the apparatus further includes a status logging module to:
and recording the current stage in the data migration process in real time through a state machine.
In one possible design, the apparatus further includes a reentry control module to:
and when the data migration process is interrupted and a re-entry instruction is received, re-entry is carried out on the data migration process according to the current stage of the interruption moment in the state machine.
In one possible design, when the reentry control module reenters the data migration process according to the current stage of the interruption time in the state machine, the reentry control module is configured to:
if the current stage is before the hard link is established, the whole data migration process is executed repeatedly;
if the current stage is in the process of establishing the hard link or the verification process after the hard link is established, deleting the new directory entry of the data to be migrated and then re-starting to execute the whole data migration process;
if the current stage is in the process of clearing the source directory entries, the process of clearing the source directory entries is continuously executed;
and if the current stage is in the process of finishing clearing the source directory entry, returning a prompt message of successful migration.
In one possible design, the apparatus further includes a rollback control module to:
and when a rollback instruction is received, rolling back the data migration process according to the current stage in the state machine.
In one possible design, when the rollback control module rolls back the data migration process according to the current stage in the state machine, the rollback control module is configured to:
if the current stage is before the hard link is created, returning a prompt message of completion of rollback;
if the current stage is in the process of establishing the hard link or the verification process after the hard link is established, deleting the new directory entry of the data to be migrated;
and if the current stage is in the process of clearing the source directory entries or the process of clearing the source directory entries is completed, re-creating the source directory entries in the source directory before the migration of the data to be migrated through creating hard links, and deleting the new directory entries of the data to be migrated after the verification process.
In one possible design, the data to be migrated includes a plurality of data, and the apparatus further includes a scheduling module to:
performing data migration processes on a plurality of data in an asynchronous mode, and acquiring the state of each data migration process by scheduling equipment in a polling mode;
and controlling any data migration process according to the state of the data migration process.
A third aspect of the present application provides an electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of the first aspect.
A fourth aspect of the present application provides a non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of the first aspect.
A fifth aspect of the application provides a computer program comprising program code for performing the method according to the first aspect when the computer program is run by a computer.
A sixth aspect of the present application provides a data migration method, including:
establishing a hard link for data to be migrated in a target directory to obtain a new directory entry of the data to be migrated;
and cleaning the source directory entry of the data to be migrated before migration.
One embodiment in the above application has the following advantages or benefits: acquiring first verification information by verifying data to be migrated; establishing a hard link for the data to be migrated in a target directory to obtain a new directory entry of the data to be migrated; acquiring second check-up information according to the data corresponding to the new directory entry in the target directory; and checking whether the data corresponding to the new directory entry is consistent with the data to be migrated or not for the first check information and the second check information, and if so, cleaning the source directory entry of the data to be migrated before migration. According to the data migration method and device, data migration on the single computer is achieved through the mode of establishing the hard link, a mobile interface of a data system does not need to be called in the data migration process, the data migration process is simple, efficient, safe and reliable, and risks in the data migration process are reduced. In addition, the data migration process can be reentrant, rollback and asynchronous, and is suitable for the migration of a large number of files, so that the scheme design of the cluster node data migration is greatly simplified, and the problems of service stability, scheduling node and migration node rpc call failure and the like in the migration process do not need to be frequently considered.
Other effects of the above-described alternative will be described below with reference to specific embodiments.
Drawings
The drawings are included to provide a better understanding of the present solution and are not intended to limit the present application. Wherein:
FIG. 1 is a flow chart of a data migration method provided by an embodiment of the present application;
FIG. 2 is a flow chart of a data migration method according to another embodiment of the present application;
FIG. 3 is a flow chart of a data migration method provided by another embodiment of the present application;
FIG. 4 is a block diagram of a data migration apparatus according to an embodiment of the present application;
FIG. 5 is a block diagram of a data migration apparatus according to another embodiment of the present application;
fig. 6 is a block diagram of an electronic device for implementing the data migration method according to the embodiment of the present application.
Detailed Description
The following description of the exemplary embodiments of the present application, taken in conjunction with the accompanying drawings, includes various details of the embodiments of the application for the understanding of the same, which are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
In the single-machine switching process, the single-machine data migration involves a lot of data, which is important. This puts some requirements on stand-alone data migration: a large number of online data nodes are involved in the cluster, and the emergency rollback can be realized in the single machine migration process; a large amount of user data is involved in a single data node, and data migration is required to be safe and reliable; single point migration may have failure, and the migration process needs to be reentrant; the central coordinator and the data nodes communicate through the remote rpc, network jitter occurs with probability, and synchronous blocking calling is easy to fail, and on the other hand, the coordinator needs to operate numerous nodes, so that an asynchronous mode needs to be supported.
However, in the prior art, the data migration on the single machine is realized by calling the mobile interface of the file system, and the above requirements cannot be usually met, so that the data migration method provided in the embodiment realizes the data migration on the single machine by creating a hard link, the mobile interface of the data system does not need to be called in the data migration process, the data migration process is simple, efficient, safe and reliable, the risk of the data migration process is reduced, and in addition, the data migration process can be reentrant, rollback can be realized, asynchronization can be realized, and the method is suitable for the migration of a large number of files. The data migration process will be described in detail with reference to specific embodiments.
An embodiment of the present application provides a data migration method, and fig. 1 is a flowchart of the data migration method provided in the embodiment of the present invention. As shown in fig. 1, the data migration method specifically includes the following steps:
s101, verifying the data to be migrated, and acquiring first verification information.
In this embodiment, before data is migrated, data to be migrated may be checked first to obtain first check information, where the first check information is used to subsequently check the migrated data to verify that the migrated data is consistent with the original data of the data to be migrated, and may include content consistency and/or storage structure consistency.
Optionally, the first check information may include a storage structure and/or a check code before migration of the data to be migrated, where the check code is an iNode number (iNode) corresponding to a source directory entry before migration or a check code acquired by a check algorithm for the data to be migrated.
In this embodiment, the storage structure specifically includes, for example, a storage directory tree of the data to be migrated, including relationships among parent nodes, child nodes, sibling nodes, and the like; the check code may be an iNode number corresponding to a source directory entry in a source directory before the data to be migrated is migrated, where the iNode is used to store the data to be migrated and basic information (such as data byte number, read-write permission, storage location, etc.) of the directory where the data to be migrated is located, and if the iNode numbers of two data are the same, it indicates that the two data are the same data; the check code may also be a check code obtained by processing the data to be migrated through a check algorithm such as MD5, SHA1, SHA256, or the like, that is, an MD5 value, an SHA1 value, and an SHA256 value, and if an MD5 value, an SHA1 value, or an SHA256 value of two data is the same, it indicates that the two data contents are the same. Of course, other verification methods may also be adopted in this embodiment, and are not described herein again.
S102, establishing a hard link for the data to be migrated in a target directory to obtain a new directory entry of the data to be migrated.
In this embodiment, when data to be migrated needs to be migrated to a certain container or other location, a data directory corresponding to the container or other location is used as a target directory, and in this embodiment, a hard link is created in the target directory for the data to be migrated, so as to obtain a new directory entry of the data to be migrated, where the concept of the hard link is that a plurality of data names that are not in or in the same directory can be modified at the same time, and after one modification, all data with the hard link are modified together, that is, in this embodiment, the data to be migrated can be linked to the target directory through the new directory entry, and at this time, a source directory entry of the data to be migrated in a source directory is not affected. In the embodiment, data migration is performed in a hard link mode, and the storage position of the data to be migrated on the physical disk does not need to be changed.
S103, acquiring second check-up information according to the data corresponding to the new directory entry in the target directory; and checking whether the data corresponding to the new directory entry is consistent with the data to be migrated or not for the first check information and the second check information.
In this embodiment, after the creation of the hard link is completed, if the hard link is correct, the data corresponding to the new directory entry should be the data to be migrated, at this time, reference may be made to S101 to obtain second check information for the data corresponding to the new directory entry, similarly, the second check information may include a storage structure and/or a check code after the data to be migrated is corresponding to the first check information, and the check code is an inode number corresponding to the new directory entry or a check code obtained by using a check algorithm for the data corresponding to the new directory entry, which is not described herein again.
In this embodiment, if the second check information matches the first check information, it may be indicated that the data corresponding to the new directory entry is consistent with the data to be migrated, that is, it is determined whether the migrated data is consistent with the data before migration. In this embodiment, whether the first check information is the same as the second check information may be compared, and if so, it indicates that the two data are the same, and optionally, in this embodiment, by comparing the iNode numbers of the two data, it may be quickly and efficiently determined whether the data are the same, or by comparing the MD5 value, the SHA1 value, or the SHA256 value of the two data, it may be more accurately determined whether the data contents are the same.
And S104, if the data corresponding to the new directory entry is consistent with the data to be migrated, cleaning the source directory entry of the data to be migrated before migration.
In this embodiment, when it is determined that the data corresponding to the new directory entry is consistent with the data to be migrated, the source directory entry of the data to be migrated before migration is cleared, so that the whole data migration process is completed, and the security and reliability of data migration are improved.
In the data migration method provided by this embodiment, first verification information is obtained by verifying data to be migrated; establishing a hard link for the data to be migrated in a target directory to obtain a new directory entry of the data to be migrated; acquiring second check-up information according to the data corresponding to the new directory entry in the target directory; and checking whether the data corresponding to the new directory entry is consistent with the data to be migrated or not for the first check information and the second check information, and if so, cleaning the source directory entry of the data to be migrated before migration. In the embodiment, data migration on the single computer is realized by establishing the hard link, a mobile interface of a data system is not required to be called in the data migration process, the data migration process is simple, efficient, safe and reliable, and the risk of the data migration process is reduced.
Another embodiment of the present application provides a data migration method, as shown in fig. 2, based on the foregoing embodiment, the data migration method includes the following specific steps:
s201, detecting a data migration environment; and judging whether the data migration environment meets a preset condition or not.
In this embodiment, first, a basic environment is checked, for example, whether a state of a storage node where data to be migrated is located (whether the data to be migrated can work normally) and whether a current storage service has stopped is checked, so that in order to avoid that the data to be migrated changes during a migration process, the current storage service needs to be stopped to perform data migration. When the storage node state is in accordance with expectation and the current storage service is stopped, the subsequent S202-S205 can be directly executed; when the storage node state is expected but the current storage service is not stopped, the state saving can be performed, the current storage service is stopped, and then the subsequent S202-S205 are performed.
S202, when the data migration environment meets a preset condition, verifying data to be migrated to acquire first verification information;
s203, establishing a hard link for the data to be migrated in a target directory to obtain a new directory entry of the data to be migrated;
s204, acquiring second check-up information according to the data corresponding to the new directory entry in the target directory; checking whether the data corresponding to the new directory entry is consistent with the data to be migrated or not for the first checking information and the second checking information;
s205, if the data corresponding to the new directory entry is consistent with the data to be migrated, cleaning the source directory entry of the data to be migrated before migration.
In the present embodiment, S202 to S205 are the same as S101 to S104 in the above embodiments, and the principle and technical effects thereof are not described herein again.
On the basis of any of the above embodiments, the method further comprises:
and recording the current stage in the data migration process in real time through a state machine.
In this embodiment, when each step in the data migration process of the foregoing embodiments S101 to S104 or S201 to S205 is performed, the current stage in the data migration process may be recorded in real time by the state machine, for example, when the current stage is executed to S101, the current stage may be recorded as a data verification stage before migration; when the step S102 is executed, the current stage can be recorded as a hard link creating stage; when the step S103 is executed, the current stage can be recorded as a verification process stage after the hard link is created; when executing to S104, it may be recorded that the current stage is a clean source directory entry process stage.
On the basis of the foregoing embodiment, this embodiment further provides a scheme for reentry after an interruption (or migration failure) occurs in the data migration process, which is specifically as follows:
and when the data migration process is interrupted and a re-entry instruction is received, re-entry is carried out on the data migration process according to the current stage of the interruption moment in the state machine.
In this embodiment, when the data migration process is interrupted, the user may control the data migration process to be reentrant, and after receiving a reentry instruction of the user, the current stage of the interruption time may be obtained from the state machine, and then different reentry modes may be adopted according to the difference of the current stages of the interruption time.
Optionally, if the current stage is before the creation of the hard link, the whole data migration process is executed again. Before the creation of the hard link, a data verification stage before migration and/or a data migration environment detection stage are included, that is, a new directory entry is not created before interruption, and when the new directory entry is reset, the whole data migration process can be directly executed from the beginning, that is, the steps S101 to S104 or S201 to S205 are executed again.
Optionally, if the current stage is in the process of creating a hard link or verifying after creating a hard link, the whole data migration process is executed after deleting the new directory entry of the data to be migrated. Because the data to be migrated during the relocation may have changed and is different from the data to be migrated before the interruption, the whole data migration process needs to be re-executed after deleting the new directory entry of the data to be migrated, that is, re-executed in S101-S104 or S201-S205, so as to ensure that the data before and after the migration are the same.
Optionally, if the current stage is in the process of clearing the source directory entry, the process of clearing the source directory entry is continuously executed. Since the hard link has been created before the interruption, the new directory entry can already be linked to the data location, at which point the clean-up step need only be continued.
Optionally, if the current stage is in the process of completing clearing the source directory entry, a prompt message that the migration is successful is returned. When the process of cleaning the source directory entry is completed before the interruption, that is, the process of executing S101-S104 or S201-S205 is completed, at this time, the re-entry does not need to execute any step of S101-S104 or S201-S205 again, and the prompt information that the migration is successful can be directly returned.
On the basis of any of the above embodiments, this embodiment further provides a rollback scheme, which is specifically as follows:
and when a rollback instruction is received, rolling back the data migration process according to the current stage in the state machine.
In this embodiment, during or after the data migration, if rollback is required, the current stage may be acquired in the state machine, and different rollback modes may be adopted according to the difference of the current stage.
Optionally, if the current stage is before the hard link is created, a prompt message indicating that the rollback is completed is returned. Before the hard link is created, a data verification stage before migration and/or a data migration environment detection stage are included, namely, a new directory entry is not created at the moment, and only prompt information of completion of rollback needs to be returned during rollback.
Optionally, if the current stage is in the process of creating a hard link or verifying after creating a hard link, deleting the new directory entry of the data to be migrated. Because the new directory entry is created at this time, but the source directory entry before migration is not deleted, the new directory entry of the data to be migrated is deleted when rollback is performed.
Optionally, if the current stage is in the process of clearing the source directory entry or the process of clearing the source directory entry is completed, the source directory entry is created again in the source directory before the data to be migrated is migrated by creating a hard link, and the new directory entry of the data to be migrated is deleted after the verification process. Because a new directory entry is created and the source directory entry before migration is deleted, the migrated data may be migrated again and migrated back to the original location with reference to the process of S101-S104 or S201-S205, that is, the source directory entry of the data is created again in the source directory by creating a hard link, and the new directory entry of the data to be migrated in the target directory is deleted after the verification process.
On the basis of any of the foregoing embodiments, the data to be migrated includes a plurality of data, and as shown in fig. 3, the method further includes:
s301, performing data migration processes on a plurality of data in an asynchronous mode, and acquiring the state of each data migration process by scheduling equipment in a polling mode;
s302, controlling any data migration process according to the state of the data migration process.
In this embodiment, when there are multiple data migration tasks, the data migration tasks can be sequentially started by one central coordinator (scheduling device), the data migration processes are carried out in an asynchronous mode, the state of the migration process is recorded in real time in each data migration process, the state of each data migration process is acquired by scheduling equipment in a polling mode, wherein the state of the migration process can include migration process, migration success and migration failure, and further any data migration process can be controlled according to the state of the data migration process, for example, if the state of a certain data migration process is in the migration process for a long time (exceeds a preset threshold), the method can be suspended or re-entered after interruption, thereby improving the network jitter resistance in the migration process, avoiding synchronous blockage and facilitating the efficient management and scheduling of a plurality of migration tasks.
The data migration method provided by any embodiment can realize data migration on a single machine, does not need to call a mobile interface of a data system in the data migration process, is simple, efficient, safe and reliable in the data migration process, and reduces the risk of the data migration process. In addition, the data migration process can be reentrant, rollback and asynchronous, and is suitable for the migration of a large number of files, so that the scheme design of the cluster node data migration is greatly simplified, and the problems of service stability, scheduling node and migration node rpc call failure and the like in the migration process do not need to be frequently considered.
Fig. 4 is a structural diagram of a data migration apparatus according to an embodiment of the present invention. As shown in fig. 4, the data migration apparatus 400 specifically includes: a verification module 401, a migration module 402, and a cleaning module 403.
The verification module is used for verifying the data to be migrated to acquire first verification information;
the migration module is used for establishing a hard link for the data to be migrated in the target directory to obtain a new directory entry of the data to be migrated;
the checking module is further used for acquiring second checking information according to the data corresponding to the new directory entry in the target directory; checking whether the data corresponding to the new directory entry is consistent with the data to be migrated or not for the first checking information and the second checking information;
and the clearing module is used for clearing the source directory entry of the data to be migrated before migration if the data corresponding to the new directory entry is consistent with the data to be migrated.
In a possible design, the first check information includes a storage structure and/or a check code before the data to be migrated is migrated, where the check code is an inode number corresponding to a source directory entry before migration or a check code acquired by a check algorithm for the data to be migrated;
the second check information comprises a storage structure and/or check codes after the data to be migrated is migrated, and the check codes are index node numbers corresponding to new directory entries or check codes acquired from data corresponding to the new directory entries through a check algorithm;
when the checking module checks whether the data corresponding to the new directory entry is consistent with the data to be migrated for the first checking information and the second checking information, the checking module is configured to:
and comparing whether the first check information is the same as the second check information.
In one possible design, as shown in fig. 5, the data migration apparatus 400 further includes a detection module 404 configured to:
before verifying data to be migrated, detecting a data migration environment;
and judging whether the data migration environment meets a preset condition or not.
In one possible design, as shown in fig. 5, the data migration apparatus 400 further includes a status recording module 405 configured to:
and recording the current stage in the data migration process in real time through a state machine.
In one possible design, the data migration apparatus further includes a reentry control module 406 configured to:
and when the data migration process is interrupted and a re-entry instruction is received, re-entry is carried out on the data migration process according to the current stage of the interruption moment in the state machine.
In one possible design, the reentrant control module 406, when reentrying the data migration process according to the current stage of the interrupt time in the state machine, is configured to:
if the current stage is before the hard link is established, the whole data migration process is executed repeatedly;
if the current stage is in the process of establishing the hard link or the verification process after the hard link is established, deleting the new directory entry of the data to be migrated and then re-starting to execute the whole data migration process;
if the current stage is in the process of clearing the source directory entries, the process of clearing the source directory entries is continuously executed;
and if the current stage is in the process of finishing clearing the source directory entry, returning a prompt message of successful migration.
In one possible design, as shown in fig. 5, the data migration apparatus 400 further includes a rollback control module 407 configured to:
and when a rollback instruction is received, rolling back the data migration process according to the current stage in the state machine.
In one possible design, when rolling back the data migration process according to the current stage in the state machine, the rollback control module 407 is configured to:
if the current stage is before the hard link is created, returning a prompt message of completion of rollback;
if the current stage is in the process of establishing the hard link or the verification process after the hard link is established, deleting the new directory entry of the data to be migrated;
and if the current stage is in the process of clearing the source directory entries or the process of clearing the source directory entries is completed, re-creating the source directory entries in the source directory before the migration of the data to be migrated through creating hard links, and deleting the new directory entries of the data to be migrated after the verification process.
In one possible design, the data to be migrated includes a plurality of data, and as shown in fig. 5, the data migration apparatus 400 further includes a scheduling module 408 configured to:
performing data migration processes on a plurality of data in an asynchronous mode, and acquiring the state of each data migration process by scheduling equipment in a polling mode;
and controlling any data migration process according to the state of the data migration process.
The data migration apparatus provided in this embodiment may be specifically configured to execute the method embodiments provided in fig. 1 to 3, and specific functions are not described herein again.
The data migration apparatus provided in this embodiment obtains first verification information by verifying data to be migrated; establishing a hard link for the data to be migrated in a target directory to obtain a new directory entry of the data to be migrated; acquiring second check-up information according to the data corresponding to the new directory entry in the target directory; and checking whether the data corresponding to the new directory entry is consistent with the data to be migrated or not for the first check information and the second check information, and if so, cleaning the source directory entry of the data to be migrated before migration. In the embodiment, data migration on the single computer is realized by establishing the hard link, a mobile interface of a data system is not required to be called in the data migration process, the data migration process is simple, efficient, safe and reliable, and the risk of the data migration process is reduced. In addition, the data migration process can be reentrant, rollback and asynchronous, and is suitable for the migration of a large number of files, so that the scheme design of the cluster node data migration is greatly simplified, and the problems of service stability, scheduling node and migration node rpc call failure and the like in the migration process do not need to be frequently considered.
According to an embodiment of the present application, an electronic device and a readable storage medium are also provided.
Fig. 6 is a block diagram of an electronic device according to the data migration method in the embodiment of the present application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular telephones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application that are described and/or claimed herein.
As shown in fig. 6, the electronic apparatus includes: one or more processors 601, memory 602, and interfaces for connecting the various components, including a high-speed interface and a low-speed interface. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions for execution within the electronic device, including instructions stored in or on the memory to display graphical information of a GUI on an external input/output apparatus (such as a display device coupled to the interface). In other embodiments, multiple processors and/or multiple buses may be used, along with multiple memories and multiple memories, as desired. Also, multiple electronic devices may be connected, with each device providing portions of the necessary operations (e.g., as a server array, a group of blade servers, or a multi-processor system). In fig. 6, one processor 601 is taken as an example.
The memory 602 is a non-transitory computer readable storage medium as provided herein. The memory stores instructions executable by at least one processor to cause the at least one processor to perform the data migration method provided herein. The non-transitory computer readable storage medium of the present application stores computer instructions for causing a computer to perform the data migration method provided herein.
The memory 602, as a non-transitory computer readable storage medium, may be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules corresponding to the data migration method in the embodiments of the present application (for example, the checking module 401, the migration module 402, and the cleaning module 403 shown in fig. 4, and further, the detection module 404, the state recording module 405, the reentry control module 406, the rollback control module 407, and the scheduling module 408 shown in fig. 5). The processor 601 executes various functional applications of the server and data processing by running non-transitory software programs, instructions, and modules stored in the memory 602, that is, implementing the data migration method in the above method embodiment.
The memory 602 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created from use of the data migration electronic device, and the like. Further, the memory 602 may include high speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 602 optionally includes memory located remotely from the processor 601, and these remote memories may be connected to the data migration electronics via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The electronic device of the data migration method may further include: an input device 603 and an output device 604. The processor 601, the memory 602, the input device 603 and the output device 604 may be connected by a bus or other means, and fig. 6 illustrates the connection by a bus as an example.
The input device 603 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the data migration electronic device, such as a touch screen, keypad, mouse, track pad, touch pad, pointer stick, one or more mouse buttons, track ball, joystick, or other input device. The output devices 604 may include a display device, auxiliary lighting devices (e.g., LEDs), and tactile feedback devices (e.g., vibrating motors), among others. The display device may include, but is not limited to, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and a plasma display. In some implementations, the display device can be a touch screen.
Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, application specific ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
These computer programs (also known as programs, software applications, or code) include machine instructions for a programmable processor, and may be implemented using high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.
The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
According to the technical scheme of the embodiment of the application, first verification information is obtained by verifying the data to be migrated; establishing a hard link for the data to be migrated in a target directory to obtain a new directory entry of the data to be migrated; acquiring second check-up information according to the data corresponding to the new directory entry in the target directory; and checking whether the data corresponding to the new directory entry is consistent with the data to be migrated or not for the first check information and the second check information, and if so, cleaning the source directory entry of the data to be migrated before migration. In the embodiment, data migration on the single computer is realized by establishing the hard link, a mobile interface of a data system is not required to be called in the data migration process, the data migration process is simple, efficient, safe and reliable, and the risk of the data migration process is reduced. In addition, the data migration process can be reentrant, rollback and asynchronous, and is suitable for the migration of a large number of files, so that the scheme design of the cluster node data migration is greatly simplified, and the problems of service stability, scheduling node and migration node rpc call failure and the like in the migration process do not need to be frequently considered.
The present application also provides a computer program comprising program code means for performing the above-described embodiments when said computer program is run by a computer
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present application may be executed in parallel, sequentially, or in different orders, and the present invention is not limited thereto as long as the desired results of the technical solutions disclosed in the present application can be achieved.
The above-described embodiments should not be construed as limiting the scope of the present application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (21)
1. A method of data migration, comprising:
verifying the data to be migrated to acquire first verification information;
establishing a hard link for the data to be migrated in a target directory to obtain a new directory entry of the data to be migrated;
acquiring second check-up information according to the data corresponding to the new directory entry in the target directory; checking whether the data corresponding to the new directory entry is consistent with the data to be migrated or not for the first checking information and the second checking information;
and if the data corresponding to the new directory entry is consistent with the data to be migrated, cleaning the source directory entry of the data to be migrated before migration.
2. The method according to claim 1, wherein the first check information includes a storage structure and/or a check code before the data to be migrated is migrated, where the check code is an inode number corresponding to a source directory entry before migration or a check code acquired by a check algorithm for the data to be migrated;
the second check information comprises a storage structure and/or check codes after the data to be migrated is migrated, and the check codes are index node numbers corresponding to new directory entries or check codes acquired from data corresponding to the new directory entries through a check algorithm;
the verifying whether the data corresponding to the new directory entry is consistent with the data to be migrated for the first and second verification information includes:
and comparing whether the first check information is the same as the second check information.
3. The method according to claim 1, wherein before checking the data to be migrated, the method further comprises:
detecting a data migration environment;
and judging whether the data migration environment meets a preset condition or not.
4. The method according to any one of claims 1-3, further comprising:
and recording the current stage in the data migration process in real time through a state machine.
5. The method of claim 4, further comprising:
and when the data migration process is interrupted and a re-entry instruction is received, re-entry is carried out on the data migration process according to the current stage of the interruption moment in the state machine.
6. The method according to claim 5, wherein said re-entering the data migration process according to the current stage of the interrupt time in the state machine comprises:
if the current stage is before the hard link is established, the whole data migration process is executed repeatedly;
if the current stage is in the process of establishing the hard link or the verification process after the hard link is established, deleting the new directory entry of the data to be migrated and then re-starting to execute the whole data migration process;
if the current stage is in the process of clearing the source directory entries, the process of clearing the source directory entries is continuously executed;
and if the current stage is in the process of finishing clearing the source directory entry, returning a prompt message of successful migration.
7. The method of claim 4, further comprising:
and when a rollback instruction is received, rolling back the data migration process according to the current stage in the state machine.
8. The method of claim 7, wherein rolling back the data migration process according to the current stage in the state machine comprises:
if the current stage is before the hard link is created, returning a prompt message of completion of rollback;
if the current stage is in the process of establishing the hard link or the verification process after the hard link is established, deleting the new directory entry of the data to be migrated;
and if the current stage is in the process of clearing the source directory entries or the process of clearing the source directory entries is completed, re-creating the source directory entries in the source directory before the migration of the data to be migrated through creating hard links, and deleting the new directory entries of the data to be migrated after the verification process.
9. The method of claim 1, wherein the data to be migrated comprises a plurality of data, the method further comprising:
performing data migration processes on a plurality of data in an asynchronous mode, and acquiring the state of each data migration process by scheduling equipment in a polling mode;
and controlling any data migration process according to the state of the data migration process.
10. A data migration apparatus, comprising:
the verification module is used for verifying the data to be migrated to acquire first verification information;
the migration module is used for establishing a hard link for the data to be migrated in the target directory to obtain a new directory entry of the data to be migrated;
the checking module is further used for acquiring second checking information according to the data corresponding to the new directory entry in the target directory; checking whether the data corresponding to the new directory entry is consistent with the data to be migrated or not for the first checking information and the second checking information;
and the clearing module is used for clearing the source directory entry of the data to be migrated before migration if the data corresponding to the new directory entry is consistent with the data to be migrated.
11. The apparatus according to claim 10, wherein the first check information includes a storage structure and/or a check code before the data to be migrated is migrated, where the check code is an inode number corresponding to a source directory entry before migration or a check code obtained by a check algorithm for the data to be migrated;
the second check information comprises a storage structure and/or check codes after the data to be migrated is migrated, and the check codes are index node numbers corresponding to new directory entries or check codes acquired from data corresponding to the new directory entries through a check algorithm;
when the checking module checks whether the data corresponding to the new directory entry is consistent with the data to be migrated for the first checking information and the second checking information, the checking module is configured to:
and comparing whether the first check information is the same as the second check information.
12. The apparatus of claim 10, further comprising a detection module to:
before verifying data to be migrated, detecting a data migration environment;
and judging whether the data migration environment meets a preset condition or not.
13. The apparatus according to any one of claims 10-12, further comprising a status logging module to:
and recording the current stage in the data migration process in real time through a state machine.
14. The apparatus of claim 13, further comprising a reentry control module to:
and when the data migration process is interrupted and a re-entry instruction is received, re-entry is carried out on the data migration process according to the current stage of the interruption moment in the state machine.
15. The apparatus of claim 14, wherein the reentrant control module, when reentrying the data migration process according to the current stage of the interrupt time in the state machine, is configured to:
if the current stage is before the hard link is established, the whole data migration process is executed repeatedly;
if the current stage is in the process of establishing the hard link or the verification process after the hard link is established, deleting the new directory entry of the data to be migrated and then re-starting to execute the whole data migration process;
if the current stage is in the process of clearing the source directory entries, the process of clearing the source directory entries is continuously executed;
and if the current stage is in the process of finishing clearing the source directory entry, returning a prompt message of successful migration.
16. The apparatus of claim 13, further comprising a rollback control module to:
and when a rollback instruction is received, rolling back the data migration process according to the current stage in the state machine.
17. The apparatus of claim 16, wherein the rollback control module, when rolling back the data migration process according to the current stage in the state machine, is configured to:
if the current stage is before the hard link is created, returning a prompt message of completion of rollback;
if the current stage is in the process of establishing the hard link or the verification process after the hard link is established, deleting the new directory entry of the data to be migrated;
and if the current stage is in the process of clearing the source directory entries or the process of clearing the source directory entries is completed, re-creating the source directory entries in the source directory before the migration of the data to be migrated through creating hard links, and deleting the new directory entries of the data to be migrated after the verification process.
18. The apparatus of claim 10, wherein the data to be migrated comprises a plurality of data, the apparatus further comprising a scheduling module configured to:
performing data migration processes on a plurality of data in an asynchronous mode, and recording the state of each data migration process by scheduling equipment;
and controlling any data migration process according to the state of the data migration process.
19. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-9.
20. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-9.
21. A method of data migration, comprising:
establishing a hard link for data to be migrated in a target directory to obtain a new directory entry of the data to be migrated;
and cleaning the source directory entry of the data to be migrated before migration.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010025782.XA CN111258954B (en) | 2020-01-10 | 2020-01-10 | Data migration method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010025782.XA CN111258954B (en) | 2020-01-10 | 2020-01-10 | Data migration method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111258954A true CN111258954A (en) | 2020-06-09 |
| CN111258954B CN111258954B (en) | 2023-12-05 |
Family
ID=70948627
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010025782.XA Active CN111258954B (en) | 2020-01-10 | 2020-01-10 | Data migration method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111258954B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104603774A (en) * | 2012-10-11 | 2015-05-06 | 株式会社日立制作所 | Migration-destination file server and file system migration method |
| CN105978952A (en) * | 2016-04-28 | 2016-09-28 | 中国科学院计算技术研究所 | Virtualization scene flow migration method based on network function and system thereof |
| US9563628B1 (en) * | 2012-12-11 | 2017-02-07 | EMC IP Holding Company LLC | Method and system for deletion handling for incremental file migration |
| CN108228813A (en) * | 2017-12-29 | 2018-06-29 | 北京奇虎科技有限公司 | The delet method and device of replica database in distributed system |
| CN109901786A (en) * | 2017-12-08 | 2019-06-18 | 腾讯科技（深圳）有限公司 | Data migration method, system, device and computer readable storage medium |
| CN110532225A (en) * | 2019-09-03 | 2019-12-03 | 北京百度网讯科技有限公司 | Storage engines switching method, device, electronic equipment and medium |
| CN110597609A (en) * | 2019-09-17 | 2019-12-20 | 深圳市及响科技有限公司 | Cluster migration and automatic recovery method and system |
-
2020
- 2020-01-10 CN CN202010025782.XA patent/CN111258954B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104603774A (en) * | 2012-10-11 | 2015-05-06 | 株式会社日立制作所 | Migration-destination file server and file system migration method |
| US9563628B1 (en) * | 2012-12-11 | 2017-02-07 | EMC IP Holding Company LLC | Method and system for deletion handling for incremental file migration |
| CN105978952A (en) * | 2016-04-28 | 2016-09-28 | 中国科学院计算技术研究所 | Virtualization scene flow migration method based on network function and system thereof |
| CN109901786A (en) * | 2017-12-08 | 2019-06-18 | 腾讯科技（深圳）有限公司 | Data migration method, system, device and computer readable storage medium |
| CN108228813A (en) * | 2017-12-29 | 2018-06-29 | 北京奇虎科技有限公司 | The delet method and device of replica database in distributed system |
| CN110532225A (en) * | 2019-09-03 | 2019-12-03 | 北京百度网讯科技有限公司 | Storage engines switching method, device, electronic equipment and medium |
| CN110597609A (en) * | 2019-09-17 | 2019-12-20 | 深圳市及响科技有限公司 | Cluster migration and automatic recovery method and system |
Non-Patent Citations (2)
| Title |
|---|
| YANG CHEN，JIE WU: "Link-based fine granularity flow migration in SDNs to reduce packet loss" * |
| 刘志宽: "分级存储系统中元数据管理的设计与实现" * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111258954B (en) | 2023-12-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10592237B2 (en) | Efficient detection of architecture related bugs during the porting process | |
| CN112925651A (en) | Application resource deployment method, device, electronic equipment and medium | |
| CN112540914A (en) | Execution method, execution device, server and storage medium for unit test | |
| CN111290768A (en) | Updating method, device, equipment and medium for containerization application system | |
| US10372701B2 (en) | Transaction processor | |
| CN111510480B (en) | Request sending method and device and first server | |
| CN114089974A (en) | Cloud code development system, method, device, equipment and storage medium | |
| CN111339187A (en) | Data processing method, device, equipment and storage medium based on intelligent contract | |
| CN111782147A (en) | Method and apparatus for cluster scale-up | |
| CN111625949A (en) | Simulation engine system, simulation processing method, device and medium | |
| CN111782357B (en) | Label control method and device, electronic equipment and readable storage medium | |
| CN111782341A (en) | Method and apparatus for managing clusters | |
| CN111966471A (en) | Access method, device, electronic equipment and computer storage medium | |
| CN112069137A (en) | Method and device for generating information, electronic equipment and computer readable storage medium | |
| CN111966877A (en) | Front-end service method, device, equipment and storage medium | |
| CN111884847A (en) | Method and apparatus for handling faults | |
| US10223089B1 (en) | Partial redundancy elimination with a fixed number of temporaries | |
| CN111835857B (en) | Method and apparatus for accessing data | |
| CN111258954B (en) | Data migration method, device, equipment and storage medium | |
| US20220276901A1 (en) | Batch processing management | |
| CN115639953A (en) | Data migration method and device | |
| CN110515622B (en) | Button state control method and device, electronic equipment and storage medium | |
| CN110750419B (en) | Offline task processing method and device, electronic equipment and storage medium | |
| CN113821232A (en) | Model updating method and device | |
| CN112667255A (en) | Updating method, updating device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |