CN111400273A - Database capacity expansion method and device, electronic equipment and machine-readable storage medium - Google Patents
Database capacity expansion method and device, electronic equipment and machine-readable storage medium Download PDFInfo
- Publication number
- CN111400273A CN111400273A CN201911134095.5A CN201911134095A CN111400273A CN 111400273 A CN111400273 A CN 111400273A CN 201911134095 A CN201911134095 A CN 201911134095A CN 111400273 A CN111400273 A CN 111400273A
- Authority
- CN
- China
- Prior art keywords
- database
- sub
- data
- original
- databases
- 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
- 238000000034 method Methods 0.000 title claims abstract description 86
- 238000003860 storage Methods 0.000 title claims abstract description 33
- 230000005012 migration Effects 0.000 claims abstract description 99
- 238000013508 migration Methods 0.000 claims abstract description 99
- 230000002159 abnormal effect Effects 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 6
- 230000008569 process Effects 0.000 abstract description 35
- 238000013500 data storage Methods 0.000 abstract description 14
- 238000012545 processing Methods 0.000 abstract description 11
- 238000007726 management method Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000013523 data management Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000011065 in-situ storage Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 230000004044 response 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/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/214—Database migration support
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24552—Database cache management
-
- 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
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention provides a database capacity expansion method, a device, electronic equipment and a machine readable storage medium, wherein when the database capacity is expanded, a temporary cache library is established for caching newly written data and carrying out normal migration processing on historical data in an original database, after the historical data is migrated, the cached data in the temporary cache library is migrated to the expanded database, and the newly written data is cached by using the temporary cache library under the condition of not influencing the capacity expansion of the database, so that the data in the capacity expansion process of the database can be continuously written and stored, and the data storage efficiency is improved. And after the data stored in the temporary cache library is migrated, the temporary cache library is deleted, so that the temporary cache library can release the storage space in time, and the storage efficiency of the database is further improved.
Description
Technical Field
The present invention relates to the field of database technologies, and in particular, to a method and an apparatus for expanding a database, an electronic device, and a machine-readable storage medium.
Background
The database is a warehouse for organizing, storing and managing data established on computer storage equipment according to a data structure, and in brief, the database can be regarded as an electronic file cabinet, and a user can perform operations such as adding, intercepting, updating, deleting and the like on the data in the file cabinet.
With the rapid development of computer technology, communication technology and network technology, the amount of data to be stored increases explosively, and the capacity configured for a database cannot meet the actual data storage requirement, so that the capacity of the database needs to be expanded.
The corresponding expansion modes of the database mainly include two types: one is to backup the data in the database, add hard disk and partition again in the database server, and restore the original data to the database server by using the backup file; and the other method is that after the data in the database is backed up, a database server with a larger hard disk is directly replaced, and the original data is restored to a new database server by using the backup file.
However, in order to prevent a failure of writing new data due to the fact that the database server is adding a hard disk or replacing the database server, data writing needs to be interrupted during the expansion of the database, so that data storage discontinuity occurs during the expansion of the database, and data storage efficiency is reduced.
Disclosure of Invention
Embodiments of the present invention provide a method and an apparatus for expanding a database, an electronic device, and a machine-readable storage medium, so as to achieve the purpose of uninterrupted data storage in the process of expanding the database and improve the data storage efficiency. The specific technical scheme is as follows:
in a first aspect, an embodiment of the present invention provides a database capacity expansion method, where the method includes:
when the capacity expansion operation of the database is identified to be started, a temporary cache library is created;
storing the latest written data into the temporary cache library, and transferring the historical data stored in the original database into the database after expansion;
after the historical data migration is completed, migrating the data stored in the temporary cache library to the expanded database;
and after the data stored in the temporary cache library is migrated, deleting the temporary cache library.
Optionally, the expanded database includes: the database is composed of partial original sub-databases in the original database and sub-databases under a newly added database instance, the number of the sub-databases in the expanded database is equal to the number of the sub-databases in the original database, and the capacity of the sub-databases under the newly added database instance is larger than or equal to the capacity of the sub-databases in the original database;
the migrating the historical data stored in the original database to the database after the expansion includes:
and integrally transferring all historical data stored in a first sub-database in the original database to a sub-database under the newly added database instance, wherein the first sub-database is any sub-database except for the partial original sub-databases in the original database.
Optionally, the expanded database includes: a database composed of newly added sub-databases in the original database and original sub-databases, wherein the number of the newly added sub-databases is equal to the number of the original sub-databases;
the migrating the historical data stored in the original database to the database after the expansion includes:
and splitting the historical data stored in each original sub-database, and correspondingly migrating the split part of the historical data to each newly added sub-database.
Optionally, the expanded database includes: the database is composed of an original sub-database in the original database and sub-databases under newly added database instances, the number of the sub-databases under the newly added database instances is equal to the number of the original sub-databases, and the capacity of the sub-databases under the newly added database instances is larger than or equal to the capacity of the sub-databases in the original database;
the migrating the historical data stored in the original database to the database after the expansion includes:
and splitting the historical data stored in each sub-database in the original sub-database, and correspondingly migrating the split part of the historical data to each sub-database under the newly added database instance.
Optionally, in the migration process of the historical data, the method further includes:
detecting the state of the historical data in each sub-database, wherein the state comprises a finished state and an unfinished state;
recording the uncompleted sub-database when the capacity expansion operation of the database is abnormal;
and when the database capacity expansion operation returns to normal, continuing to perform the historical data migration on the uncompleted sub-database.
Optionally, in the migration process of the historical data, the method further includes:
when a data query instruction is received, querying the data to be queried from the original database and the temporary cache library according to the attribute information of the data to be queried carried by the data query instruction;
and returning the data to be queried from the original database and the temporary cache library.
Optionally, in the migration process of the historical data, the storing the latest written data in the temporary cache library includes:
receiving a data writing request, wherein the data writing request carries data to be written;
querying the original database for the presence of the data;
if the data does not exist in the original database, inquiring whether the data already exists in the temporary cache library;
and if the data does not exist in the temporary cache library, storing the data into the temporary cache library.
Optionally, in the process of migrating the data stored in the temporary cache library, the method further includes:
when a data query instruction is received, querying the data to be queried from the database after capacity expansion and the temporary cache library according to the attribute information of the data to be queried carried by the data query instruction;
and returning the data to be queried inquired from the database after the capacity expansion and the temporary cache library.
Optionally, in the process of migrating the data stored in the temporary cache library, the method further includes:
when a data writing request carrying data to be written is received, inquiring whether the data exists in the expanded database or not;
if the data does not exist in the expanded database, inquiring whether the data already exists in the temporary cache library;
and if the data does not exist in the temporary cache library, storing the data into the database after the expansion.
In a second aspect, an embodiment of the present invention provides a database capacity expansion apparatus, where the apparatus includes:
the creating module is used for creating a temporary cache library when the capacity expansion operation of the database is identified to be started;
the migration module is used for storing the latest written data into the temporary cache library and migrating the historical data stored in the original database into the expanded database;
the migration module is further configured to migrate the data stored in the temporary cache library to the expanded database after the historical data is migrated;
and the deleting module is used for deleting the temporary cache library after the data stored in the temporary cache library is migrated.
Optionally, the expanded database includes: the database is composed of partial original sub-databases in the original database and sub-databases under a newly added database instance, the number of the sub-databases in the expanded database is equal to the number of the sub-databases in the original database, and the capacity of the sub-databases under the newly added database instance is larger than or equal to the capacity of the sub-databases in the original database;
when the migration module is used for migrating the historical data stored in the original database to the expanded database, the migration module is specifically configured to:
and integrally transferring all historical data stored in a first sub-database in the original database to a sub-database under the newly added database instance, wherein the first sub-database is any sub-database except for the partial original sub-databases in the original database.
Optionally, the expanded database includes: a database composed of newly added sub-databases in the original database and original sub-databases, wherein the number of the newly added sub-databases is equal to the number of the original sub-databases;
when the migration module is used for migrating the historical data stored in the original database to the expanded database, the migration module is specifically configured to:
and splitting the historical data stored in each original sub-database, and correspondingly migrating the split part of the historical data to each newly added sub-database.
Optionally, the expanded database includes: the database is composed of an original sub-database in the original database and sub-databases under newly added database instances, the number of the sub-databases under the newly added database instances is equal to the number of the original sub-databases, and the capacity of the sub-databases under the newly added database instances is larger than or equal to the capacity of the sub-databases in the original database;
when the migration module is used for migrating the historical data stored in the original database to the expanded database, the migration module is specifically configured to:
and splitting the historical data stored in each sub-database in the original sub-database, and correspondingly migrating the split part of the historical data to each sub-database under the newly added database instance.
Optionally, the apparatus further comprises:
the detection module is used for detecting the state of the historical data in the sub-databases, wherein the state comprises a finished state and an unfinished state;
the recording module is used for recording the uncompleted sub-database when the capacity expansion operation of the database is abnormal;
and the migration module is further configured to continue to perform the historical data migration on the uncompleted sub-database when the database expansion operation returns to normal.
Optionally, the apparatus further comprises:
the query module is used for querying the data to be queried from the original database and the temporary cache library according to the attribute information of the data to be queried carried by the data query instruction when the data query instruction is received;
and the return module is used for returning the data to be inquired from the original database and the temporary cache library.
Optionally, in the migration process of the historical data, when the migration module is configured to store the latest written data in the temporary cache library, the migration module is specifically configured to:
receiving a data writing request, wherein the data writing request carries data to be written;
querying the original database for the presence of the data;
if the data does not exist in the original database, inquiring whether the data already exists in the temporary cache library;
and if the data does not exist in the temporary cache library, storing the data into the temporary cache library.
Optionally, the apparatus further comprises:
the query module is used for querying the data to be queried from the database after capacity expansion and the temporary cache library according to the attribute information of the data to be queried carried by the data query instruction when the data query instruction is received;
and the return module is used for returning the data to be inquired from the expanded database and the temporary cache library.
Optionally, the apparatus further comprises:
the query module is used for querying whether the data exists in the expanded database or not when a data write request carrying the data to be written is received;
the query module is further configured to query whether the data already exists in the temporary cache library if the data does not exist in the expanded database;
and the storage module is used for storing the data into the database after the capacity expansion if the data does not exist in the temporary cache library.
In a third aspect, an embodiment of the present invention provides an electronic device, which includes a processor and a memory, where the memory stores machine executable instructions that are executable by the processor, and the machine executable instructions are loaded and executed by the processor to implement the method provided in the first aspect of the embodiment of the present invention.
In a fourth aspect, the present invention provides a machine-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the computer program implements the method provided in the first aspect of the present invention.
The embodiment of the invention provides a database capacity expansion method, a device, electronic equipment and a machine readable storage medium, wherein the database capacity expansion method comprises the following steps: when the capacity expansion operation of the starting database is identified, a temporary cache library is created, the latest written data is stored in the temporary cache library, the historical data stored in the original database is migrated to the expanded database, the data stored in the temporary cache library is migrated to the expanded database after the migration of the historical data is completed, and the temporary cache library is deleted after the migration of the data stored in the temporary cache library is completed.
When the database expands, a temporary cache library is created for caching the latest written data and carrying out normal migration processing on the historical data in the original database, after the historical data migration is completed, the cached data in the temporary cache library is migrated to the expanded database, and the latest written data is cached by using the temporary cache library under the condition of not influencing the expansion of the database, so that the data in the database expansion process can be written and stored uninterruptedly, and the data storage efficiency is improved. And after the data stored in the temporary cache library is migrated, the temporary cache library is deleted, so that the temporary cache library can release the storage space in time, and the storage efficiency of the database is further improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a database capacity expansion method according to an embodiment of the present invention;
fig. 2 is a schematic expansion flow chart of a first expansion manner according to an embodiment of the present invention;
fig. 3 is a schematic expansion flow chart of a second expansion manner according to the embodiment of the present invention;
fig. 4 is a schematic expansion flow chart of a third expansion manner according to the embodiment of the present invention;
FIG. 5 is a flow chart illustrating data querying during migration of historical data according to an embodiment of the present invention;
FIG. 6 is a flow chart illustrating data writing during migration of historical data according to an embodiment of the present invention;
fig. 7 is a schematic flowchart illustrating a data query process during migration of data stored in a temporary cache according to an embodiment of the present invention;
fig. 8 is a schematic flow chart illustrating data writing during migration of data stored in a temporary cache library according to an embodiment of the present invention;
FIG. 9 is a schematic structural diagram of a database capacity expansion apparatus according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, 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 invention.
In order to achieve the purpose of uninterrupted data storage in the database expansion process and improve the data storage efficiency, embodiments of the present invention provide a database expansion method and apparatus, an electronic device, and a machine-readable storage medium. Next, a method for expanding a database according to an embodiment of the present invention is first described.
The execution main body of the database capacity expansion method provided by the embodiment of the invention is the electronic equipment with a data storage function, and the electronic equipment can be a distributed database system, a database server and the like. The method for expanding the capacity of the database provided by the embodiment of the present invention may be implemented by at least one of software, a hardware circuit, and a logic circuit provided in the electronic device.
As shown in fig. 1, a method for expanding a database according to an embodiment of the present invention may include the following steps.
S101, when the capacity expansion operation of the database is identified, a temporary cache library is created.
Under a normal condition (that is, the capacity of the database can meet the storage requirement of the user data volume), the written data can be stored in the database by using a data routing (a data routing function is generally implemented by a data management module (Master)), and the process can be understood as that the electronic device is operating in a normal service mode. Once the capacity of the database cannot meet the storage requirement of the user data volume, the user may select to perform a database capacity expansion operation (input operation may be performed through a database tool at the front end), and the electronic device may recognize a state of starting the database capacity expansion operation, or the electronic device may automatically start the database capacity expansion operation and recognize the state of starting the database capacity expansion operation.
The capacity expansion process can be divided into several different operation modes (in the embodiment of the invention, the operation modes are divided into a normal service mode, a historical data migration mode and a cache data migration mode), and the electronic equipment respectively operates in different modes in the capacity expansion process so as to realize the consistency of externally displayed data.
When the starting of the capacity expansion operation of the database is identified, a temporary cache library is automatically created on the electronic equipment, wherein the temporary cache library is a temporary storage space opened on the electronic equipment and used for storing the latest written data in the capacity expansion process of the database.
S102, storing the latest written data into a temporary cache library, and transferring the historical data stored in the original database into the expanded database.
After the temporary cache library is created, if the electronic device receives newly written data, the data is stored in the temporary cache library, and meanwhile, historical data is migrated from an original database to a database after capacity expansion.
Optionally, the expanded database may include: the database comprises a part of original sub-databases in the original database and sub-databases under newly added database instances, wherein the number of the sub-databases in the expanded database is equal to the number of the sub-databases in the original database, and the capacity of the sub-databases under the newly added database instances is larger than or equal to the capacity of the sub-databases in the original database.
Correspondingly, the step of migrating the historical data stored in the original database to the expanded database in S102 may specifically be: and integrally transferring all historical data stored in a first sub-database in the original database to a sub-database under the newly added database instance, wherein the first sub-database is any sub-database except part of the original sub-databases in the original database.
Optionally, the expanded database may further include: and the database is composed of a newly increased sub-database and an original sub-database in the original database, wherein the number of the newly increased sub-databases is equal to that of the original sub-databases.
Correspondingly, the step of migrating the historical data stored in the original database to the expanded database in S102 may specifically be: and splitting the historical data stored in each original sub-database, and correspondingly migrating the split part of the historical data to each newly added sub-database.
Optionally, the expanded database may further include: the database comprises an original sub-database in an original database and sub-databases under newly added database instances, wherein the number of the sub-databases under the newly added database instances is equal to that of the original sub-databases, and the capacity of the sub-databases under the newly added database instances is larger than or equal to that of the sub-databases in the original database.
Correspondingly, the step of migrating the historical data stored in the original database to the expanded database in S102 may specifically be:
and splitting historical data stored in each sub-database in the original sub-database, and correspondingly migrating the split part of historical data to each sub-database under the newly added database instance.
According to actual needs, there are three ways of database capacity expansion. The first is that only partial data of the database is migrated integrally by taking a sub-database DB as a unit and is migrated to a newly added database instance, the database instance is a main body for realizing the functions of the database, the database instance comprises a plurality of sub-databases, the capacity of the database is expanded according to the mode, and the quantity of the DB is unchanged; the second is that only the data in each DB of the database is split in situ, and the local database instance is still used for maintaining, the database capacity is expanded according to the mode, the number of the DBs is increased, and the current database instance independently maintains all the DBs; and thirdly, splitting the data, transferring a part of the data to other database examples, expanding the capacity of the database according to the mode, increasing the number of the DB, and maintaining the original number of the DB by the original database example and the newly-added database example.
The first capacity expansion mode is suitable for the situation that the performance of a machine is insufficient, a new machine expansion database instance needs to be added, but the single-table read-write capacity can still meet the requirement, the mode is simple to realize, a database instance is directly added, the capacity of a sub-database under the database instance is larger than or equal to that of a sub-database in an original database, therefore, historical data stored in the sub-database in the original database can be migrated in the whole database, then access configuration is updated, online loading is carried out again, and the capacity expansion of the database is completed under the condition that a client side does not sense. In the capacity expansion process, the electronic equipment is firstly switched from a normal service mode to a historical data migration mode, at the moment, newly written data are written into a temporary cache library, the whole historical data are migrated, after the database migration is finished, the database access configuration is updated and is loaded again on line, then the mode is switched to a cache data migration mode, the cache data are migrated from the temporary cache library to the expanded database, after the migration is finished, redundant historical data and cache data are deleted, and finally the mode is switched to the normal service mode, so that the capacity expansion operation is finished. The capacity expansion process of this capacity expansion mode is shown in fig. 2, in the normal service mode, data is distributed to two sub-databases DB1 and DB2 through data routing via a data access management module (Master), when the database is expanded, a database instance comprising DB3 is added, the capacity of DB3 is larger than that of DB2, DB3 replaces DB2 in the original database, DB1 is maintained in database instance 1, DB3 is maintained in database instance 2, at the same time, the electronic device creates a temporary cache library for recording the newly written data, the entire library of historical data in DB2 is migrated into DB3, after the migration of the historical data is completed, the data in the temporary cache library is migrated to the two sub-databases DB1 and DB3, after the migration of the cached data is completed, the electronic device is restored to a normal service state, and the data is distributed to the two sub-databases DB1 and DB3 through data routing via the data access management module.
The second expansion mode is suitable for being used when the machine performance is sufficient, but the single-table data volume is too large, so that the read-write performance is seriously reduced, and the service processing performance requirement cannot be met. In the capacity expansion mode, a new sub-database needs to be added to the original database, the number of the newly added sub-databases is equal to that of the original sub-databases, and the number of the sub-databases is twice of that of the original sub-databases before capacity expansion. The time of mode switching in the expansion process is the same as the first expansion mode, and through data splitting, the data volume required to be stored in each sub-database is approximately half of that before expansion, so that the read-write pressure of a single sub-database can be obviously reduced, and the response speed of database service is improved. As shown in fig. 3, in the normal service mode, data is distributed to two sub-databases DB1 and DB2 through data routing through a data access management module, when the database is expanded, two sub-databases DB3 and DB4 are newly added, DB1 splits stored data, part of the data is migrated to DB3, DB2 splits stored data, part of the data is migrated to DB4, at the same time, the electronic device creates a temporary buffer library for recording newly written data, after the history data migration is completed, the data in the temporary buffer library is migrated to four sub-databases DB1, DB2, DB3 and DB4, after the buffer data migration is completed, the electronic device returns to a normal service state, and the data is distributed to four sub-databases DB1, DB2, DB3 and DB4 through data routing through the data access management module.
The third capacity expansion mode is the combined use of the first capacity expansion mode and the second capacity expansion mode, and when the performance of the machine is insufficient, the single-table data volume in the database is large, the performance of the database is seriously reduced, and the service performance requirement cannot be met, the third capacity expansion mode can be used for carrying out the capacity expansion of the database. The capacity expansion process is the same as the first and second capacity expansion modes, but in the third capacity expansion mode, the original database is not only split and routed for the data stored in the sub-database, but also needs to be migrated to the newly built database, and the database has a certain free disk space and a relatively stable network environment when capacity expansion is needed. After the capacity expansion, each database instance and the data of the database are changed into half of the original ones, so that the performance pressure of the service node and the read-write pressure of the single table can be obviously reduced, and the data read-write processing capability of the database is improved. As shown in fig. 4, in the normal service mode, data is distributed to two sub-databases DB1 and DB2 through data routing by a data access management module, a database instance including DB3 and DB4 is newly added, the capacities of DB3 and DB4 are greater than those of DB1 and DB2, database instance 1 maintains DB1 and DB2, and database instance 2 maintains DB3 and DB4, at the same time, the electronic device creates a temporary buffer library for recording newly written data, DB1 splits stored data, migrates a part of data to DB3, DB2 splits stored data, a part of data to DB4, after the migration of history data is completed, the data in the temporary buffer library is migrated to four sub-databases DB1, DB2, DB3 and DB4, after the migration of buffer data is completed, the electronic device is restored to the normal service state, and the data is managed by the data access management module, distributed into four sub-databases DB1, DB2, DB3 and DB4 by data routing.
Optionally, in the migration process of the historical data, the method provided by the embodiment of the present invention may further perform the following steps:
detecting the state of historical data migrating in each sub-database, wherein the state comprises a finished state and an unfinished state; recording the uncompleted sub-database when the capacity expansion operation of the database is abnormal; and when the capacity expansion operation of the database is recovered to be normal, continuing to perform historical data migration on the uncompleted sub-database.
The capacity expansion operation needs a certain time, so that in the process of expanding the capacity of the database, the state of the historical data migrating in each sub-database needs to be detected in real time, and the state of the completed migration or the unfinished migration is recorded, so that the abnormal occurrence in the capacity expansion process of the database is allowed, if the abnormal occurrence occurs, the abnormal occurrence can be known by judging the unfinished migration state, and the historical data migration is directly continued on the sub-database in the unfinished state when the capacity expansion operation of the database is recovered to be normal, and the data migration does not need to be carried out again, so that the availability of the capacity expansion of the database is improved.
And S103, after the historical data is migrated, migrating the data stored in the temporary cache library to the database after capacity expansion.
The electronic device may determine whether the historical data is migrated completely by monitoring whether there is historical data in the original database, if the original database does not have historical data, it indicates that the historical data is migrated completely, and may switch to a cache data migration mode, in which data in the temporary cache table is migrated to the expanded database according to a data routing rule, and the electronic device may store newly written data to the expanded database according to a configured data routing, where the data routing may be implemented in a conventional manner such as hash, and details are not described here. The process of migrating the data stored in the temporary cache library to the expanded database can be understood as that the electronic device is working in the cache data migration mode.
Optionally, in the migration process of the historical data, the flow of the data query is as shown in fig. 5, and may include the following steps:
s501, when a data query instruction is received, querying the data to be queried from the original database and the temporary cache library according to the attribute information of the data to be queried carried by the data query instruction.
And S502, returning the data to be inquired from the original database and the temporary cache library.
When the data query device operates in the historical data migration mode, the database comprises the original database and the temporary cache library, so that when a data query instruction is received, the original database and the temporary cache library need to be queried simultaneously, and then query results of the two libraries are returned to the device initiating the data query.
Optionally, in the migration process of the historical data, the flow of data writing is shown in fig. 6, and may include the following steps:
s601, receiving a data writing request, wherein the data writing request carries data to be written.
S602, query whether the original database has the data, if yes, execute S605, otherwise execute S603.
S603, query whether the temporary cache library already contains the data, if yes, execute S605, otherwise execute S604.
S604, store the data in the temporary cache.
S605, the data is determined to exist and the writing fails.
When the data write-in device runs in a historical data migration mode, the original database and the temporary cache library are included in the database, so that the written-in data are not repeated in the database, the original database is firstly inquired when the data are written, the situation that new data do not exist in the original database is determined, then the temporary cache library is inquired, finally, the data are written in after the situation that the data do not exist in the whole database is confirmed, and the data are written in the temporary cache library.
And S104, deleting the temporary cache library after the data stored in the temporary cache library is migrated.
The electronic equipment can judge whether the cache data migration is completed or not by monitoring whether data exist in the temporary cache library or not, if the temporary cache library does not contain historical data, the data migration stored in the temporary cache library is completed, at the moment, the electronic equipment can be switched to a normal service mode to perform normal database service, the temporary cache library can be deleted, meanwhile, redundant historical data and cache data can be deleted, the cache space is released, and the storage efficiency of the database is guaranteed.
Optionally, in the process of migrating data stored in the temporary cache library, the flow of data query is shown in fig. 7, and may include the following steps:
and S701, when a data query instruction is received, querying the data to be queried from the database and the temporary cache library after capacity expansion according to the attribute information of the data to be queried carried by the data query instruction.
And S702, returning the data to be inquired from the database and the temporary cache library after capacity expansion.
When the data processing system operates in the cache data migration mode, because the database contains the data in the expanded database and the data in the temporary cache library, when a data query instruction is received, the expanded database and the temporary cache library need to be queried at the same time, and then query results of the two libraries are returned to the device initiating the data query.
Optionally, in the process of migrating the data stored in the temporary cache library, the flow of data writing is shown in fig. 8, and may include the following steps:
s801, when a data write request carrying data to be written is received, inquiring whether the data exists in the expanded database or not, if so, executing S804, otherwise, executing S802.
S802, inquiring whether the data exist in the temporary cache library, if so, executing S804, otherwise, executing S803.
And S803, storing the data into the expanded database.
S804, the data is determined to exist, and the writing fails.
When the data processing system operates in the cache data migration mode, because the database comprises the expanded database and the temporary cache library, in order to ensure that the written data is not repeated in the database, when the data is written, the expanded database is firstly inquired, the condition that new data does not exist in the expanded database is determined, then the temporary cache library is inquired, finally, the data is written after the condition that the data does not exist in the whole database is confirmed, and the data is written into the expanded database.
By applying the embodiment of the invention, when the starting of the capacity expansion operation of the database is identified, the temporary cache library is created, the latest written data is stored in the temporary cache library, the historical data stored in the original database is migrated to the expanded database, the data stored in the temporary cache library is migrated to the expanded database after the migration of the historical data is completed, and the temporary cache library is deleted after the migration of the data stored in the temporary cache library is completed. When the database expands, a temporary cache library is created for caching the latest written data and carrying out normal migration processing on the historical data in the original database, after the historical data migration is completed, the cached data in the temporary cache library is migrated to the expanded database, and the latest written data is cached by using the temporary cache library under the condition of not influencing the expansion of the database, so that the data in the database expansion process can be written and stored uninterruptedly, and the data storage efficiency is improved. And after the data stored in the temporary cache library is migrated, the temporary cache library is deleted, so that the temporary cache library can release the storage space in time, and the storage efficiency of the database is further improved.
Corresponding to the foregoing method embodiment, an embodiment of the present invention provides a database capacity expansion device, and as shown in fig. 9, the device may include:
a creating module 910, configured to create a temporary cache library when it is identified that a capacity expansion operation of the database is started;
a migration module 920, configured to store the latest written data in the temporary cache library, and migrate the historical data stored in the original database to the expanded database;
the migration module 920 is further configured to migrate the data stored in the temporary cache library to the expanded database after the historical data is migrated;
a deleting module 930, configured to delete the temporary cache library after the data stored in the temporary cache library is migrated.
Optionally, the expanded database may include: the database is composed of partial original sub-databases in the original database and sub-databases under a newly added database instance, the number of the sub-databases in the expanded database is equal to the number of the sub-databases in the original database, and the capacity of the sub-databases under the newly added database instance is larger than or equal to the capacity of the sub-databases in the original database;
when the migration module 920 is configured to migrate the historical data stored in the original database to the expanded database, specifically, the migration module may be configured to:
and integrally transferring all historical data stored in a first sub-database in the original database to a sub-database under the newly added database instance, wherein the first sub-database is any sub-database except for the partial original sub-databases in the original database.
Optionally, the expanded database may include: a database composed of newly added sub-databases in the original database and original sub-databases, wherein the number of the newly added sub-databases is equal to the number of the original sub-databases;
when the migration module 920 is configured to migrate the historical data stored in the original database to the expanded database, specifically, the migration module may be configured to:
and splitting the historical data stored in each original sub-database, and correspondingly migrating the split part of the historical data to each newly added sub-database.
Optionally, the expanded database may include: the database is composed of an original sub-database in the original database and sub-databases under newly added database instances, the number of the sub-databases under the newly added database instances is equal to the number of the original sub-databases, and the capacity of the sub-databases under the newly added database instances is larger than or equal to the capacity of the sub-databases in the original database;
when the migration module is configured to migrate the historical data stored in the original database to the expanded database, the migration module may be specifically configured to:
and splitting the historical data stored in each sub-database in the original sub-database, and correspondingly migrating the split part of the historical data to each sub-database under the newly added database instance.
Optionally, the apparatus may further include:
the detection module is used for detecting the state of the historical data in the sub-databases, wherein the state comprises a finished state and an unfinished state;
the recording module is used for recording the uncompleted sub-database when the capacity expansion operation of the database is abnormal;
the migration module 920 may be further configured to continue to perform the historical data migration on the uncompleted sub-database when the database expansion operation returns to normal.
Optionally, the apparatus may further include:
the query module is used for querying the data to be queried from the original database and the temporary cache library according to the attribute information of the data to be queried carried by the data query instruction when the data query instruction is received;
and the return module is used for returning the data to be inquired from the original database and the temporary cache library.
Optionally, in the migration process of the historical data, when the migration module 920 is configured to store the latest written data in the temporary cache library, it may specifically be configured to:
receiving a data writing request, wherein the data writing request carries data to be written;
querying the original database for the presence of the data;
if the data does not exist in the original database, inquiring whether the data already exists in the temporary cache library;
and if the data does not exist in the temporary cache library, storing the data into the temporary cache library.
Optionally, the apparatus may further include:
the query module is used for querying the data to be queried from the database after capacity expansion and the temporary cache library according to the attribute information of the data to be queried carried by the data query instruction when the data query instruction is received;
and the return module is used for returning the data to be inquired from the expanded database and the temporary cache library.
Optionally, the apparatus may further include:
the query module is used for querying whether the data exists in the expanded database or not when a data write request carrying the data to be written is received;
the query module may be further configured to query whether the data already exists in the temporary cache library if the data does not exist in the expanded database;
and the storage module is used for storing the data into the database after the capacity expansion if the data does not exist in the temporary cache library.
By applying the embodiment of the invention, when the starting of the capacity expansion operation of the database is identified, the temporary cache library is created, the latest written data is stored in the temporary cache library, the historical data stored in the original database is migrated to the expanded database, the data stored in the temporary cache library is migrated to the expanded database after the migration of the historical data is completed, and the temporary cache library is deleted after the migration of the data stored in the temporary cache library is completed. When the database expands, a temporary cache library is created for caching the latest written data and carrying out normal migration processing on the historical data in the original database, after the historical data migration is completed, the cached data in the temporary cache library is migrated to the expanded database, and the latest written data is cached by using the temporary cache library under the condition of not influencing the expansion of the database, so that the data in the database expansion process can be written and stored uninterruptedly, and the data storage efficiency is improved. And after the data stored in the temporary cache library is migrated, the temporary cache library is deleted, so that the temporary cache library can release the storage space in time, and the storage efficiency of the database is further improved.
An electronic device according to an embodiment of the present invention is further provided, as shown in fig. 10, and includes a processor 1001 and a memory 1002, where the memory 1002 stores machine executable instructions that can be executed by the processor 1001, and the machine executable instructions are loaded and executed by the processor 1001, so as to implement the database capacity expansion method provided in the embodiment of the present invention.
The Memory may include a RAM (Random Access Memory) or an NVM (Non-volatile Memory), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component.
Data transmission can be performed between the memory 1002 and the processor 1001 through a wired connection or a wireless connection, and communication between the chip and other devices can be performed through a wired communication interface or a wireless communication interface. Fig. 10 is a diagram illustrating an example of data transmission via a bus, and is not limited to a specific connection manner.
In the embodiment of the present invention, the processor can realize that: when the capacity expansion operation of the starting database is identified, a temporary cache library is created, the latest written data is stored in the temporary cache library, the historical data stored in the original database is migrated to the expanded database, the data stored in the temporary cache library is migrated to the expanded database after the migration of the historical data is completed, and the temporary cache library is deleted after the migration of the data stored in the temporary cache library is completed. When the database expands, a temporary cache library is created for caching the latest written data and carrying out normal migration processing on the historical data in the original database, after the historical data migration is completed, the cached data in the temporary cache library is migrated to the expanded database, and the latest written data is cached by using the temporary cache library under the condition of not influencing the expansion of the database, so that the data in the database expansion process can be written and stored uninterruptedly, and the data storage efficiency is improved. And after the data stored in the temporary cache library is migrated, the temporary cache library is deleted, so that the temporary cache library can release the storage space in time, and the storage efficiency of the database is further improved.
In addition, an embodiment of the present invention further provides a machine-readable storage medium, where a computer program is stored in the machine-readable storage medium, and when the computer program is executed by a processor, the method for expanding a database provided in the embodiment of the present invention is implemented.
In this embodiment of the present invention, the machine-readable storage medium stores machine-executable instructions for executing the database capacity expansion method provided in this embodiment of the present invention when running, so that it is possible to implement: when the capacity expansion operation of the starting database is identified, a temporary cache library is created, the latest written data is stored in the temporary cache library, the historical data stored in the original database is migrated to the expanded database, the data stored in the temporary cache library is migrated to the expanded database after the migration of the historical data is completed, and the temporary cache library is deleted after the migration of the data stored in the temporary cache library is completed. When the database expands, a temporary cache library is created for caching the latest written data and carrying out normal migration processing on the historical data in the original database, after the historical data migration is completed, the cached data in the temporary cache library is migrated to the expanded database, and the latest written data is cached by using the temporary cache library under the condition of not influencing the expansion of the database, so that the data in the database expansion process can be written and stored uninterruptedly, and the data storage efficiency is improved. And after the data stored in the temporary cache library is migrated, the temporary cache library is deleted, so that the temporary cache library can release the storage space in time, and the storage efficiency of the database is further improved.
For the embodiments of the electronic device and the machine-readable storage medium, since the contents of the related methods are substantially similar to those of the foregoing embodiments of the methods, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the embodiments of the methods.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, 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 identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus, the electronic device, and the machine-readable storage medium embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and in relation to the description, reference may be made to some portions of the method embodiments.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (15)
1. A method for expanding database, the method comprising:
when the capacity expansion operation of the database is identified to be started, a temporary cache library is created;
storing the latest written data into the temporary cache library, and transferring the historical data stored in the original database into the database after expansion;
after the historical data migration is completed, migrating the data stored in the temporary cache library to the expanded database;
and after the data stored in the temporary cache library is migrated, deleting the temporary cache library.
2. The method of claim 1, wherein the expanded database comprises: the database is composed of partial original sub-databases in the original database and sub-databases under a newly added database instance, the number of the sub-databases in the expanded database is equal to the number of the sub-databases in the original database, and the capacity of the sub-databases under the newly added database instance is larger than or equal to the capacity of the sub-databases in the original database;
the migrating the historical data stored in the original database to the database after the expansion includes:
and integrally transferring all historical data stored in a first sub-database in the original database to a sub-database under the newly added database instance, wherein the first sub-database is any sub-database except for the partial original sub-databases in the original database.
3. The method of claim 1, wherein the expanded database comprises: a database composed of newly added sub-databases in the original database and original sub-databases, wherein the number of the newly added sub-databases is equal to the number of the original sub-databases;
the migrating the historical data stored in the original database to the database after the expansion includes:
and splitting the historical data stored in each original sub-database, and correspondingly migrating the split part of the historical data to each newly added sub-database.
4. The method of claim 1, wherein the expanded database comprises: the database is composed of an original sub-database in the original database and sub-databases under newly added database instances, the number of the sub-databases under the newly added database instances is equal to the number of the original sub-databases, and the capacity of the sub-databases under the newly added database instances is larger than or equal to the capacity of the sub-databases in the original database;
the migrating the historical data stored in the original database to the database after the expansion includes:
and splitting the historical data stored in each sub-database in the original sub-database, and correspondingly migrating the split part of the historical data to each sub-database under the newly added database instance.
5. The method according to any of claims 2-4, wherein during the migration of the historical data, the method further comprises:
detecting the state of the historical data in each sub-database, wherein the state comprises a finished state and an unfinished state;
recording the uncompleted sub-database when the capacity expansion operation of the database is abnormal;
and when the database capacity expansion operation returns to normal, continuing to perform the historical data migration on the uncompleted sub-database.
6. The method of claim 1, wherein during the migration of the historical data, the method further comprises:
when a data query instruction is received, querying the data to be queried from the original database and the temporary cache library according to the attribute information of the data to be queried carried by the data query instruction;
and returning the data to be queried from the original database and the temporary cache library.
7. The method of claim 1, wherein during the migration of the historical data, the saving the latest written data in the temporary cache library comprises:
receiving a data writing request, wherein the data writing request carries data to be written;
querying the original database for the presence of the data;
if the data does not exist in the original database, inquiring whether the data already exists in the temporary cache library;
and if the data does not exist in the temporary cache library, storing the data into the temporary cache library.
8. The method of claim 1, wherein during the migration of data stored in the temporary cache library, the method further comprises:
when a data query instruction is received, querying the data to be queried from the database after capacity expansion and the temporary cache library according to the attribute information of the data to be queried carried by the data query instruction;
and returning the data to be queried inquired from the database after the capacity expansion and the temporary cache library.
9. The method of claim 1, wherein during the migration of data stored in the temporary cache library, the method further comprises:
when a data writing request carrying data to be written is received, inquiring whether the data exists in the expanded database or not;
if the data does not exist in the expanded database, inquiring whether the data already exists in the temporary cache library;
and if the data does not exist in the temporary cache library, storing the data into the database after the expansion.
10. A database capacity expansion apparatus, the apparatus comprising:
the creating module is used for creating a temporary cache library when the capacity expansion operation of the database is identified to be started;
the migration module is used for storing the latest written data into the temporary cache library and migrating the historical data stored in the original database into the expanded database;
the migration module is further configured to migrate the data stored in the temporary cache library to the expanded database after the historical data is migrated;
and the deleting module is used for deleting the temporary cache library after the data stored in the temporary cache library is migrated.
11. The apparatus of claim 10, wherein the expanded database comprises: the database is composed of partial original sub-databases in the original database and sub-databases under a newly added database instance, the number of the sub-databases in the expanded database is equal to the number of the sub-databases in the original database, and the capacity of the sub-databases under the newly added database instance is larger than or equal to the capacity of the sub-databases in the original database;
when the migration module is used for migrating the historical data stored in the original database to the expanded database, the migration module is specifically configured to:
and integrally transferring all historical data stored in a first sub-database in the original database to a sub-database under the newly added database instance, wherein the first sub-database is any sub-database except for the partial original sub-databases in the original database.
12. The apparatus of claim 10, wherein the expanded database comprises: a database composed of newly added sub-databases in the original database and original sub-databases, wherein the number of the newly added sub-databases is equal to the number of the original sub-databases;
when the migration module is used for migrating the historical data stored in the original database to the expanded database, the migration module is specifically configured to:
and splitting the historical data stored in each original sub-database, and correspondingly migrating the split part of the historical data to each newly added sub-database.
13. The apparatus of claim 10, wherein the expanded database comprises: the database is composed of an original sub-database in the original database and sub-databases under newly added database instances, the number of the sub-databases under the newly added database instances is equal to the number of the original sub-databases, and the capacity of the sub-databases under the newly added database instances is larger than or equal to the capacity of the sub-databases in the original database;
when the migration module is used for migrating the historical data stored in the original database to the expanded database, the migration module is specifically configured to:
and splitting the historical data stored in each sub-database in the original sub-database, and correspondingly migrating the split part of the historical data to each sub-database under the newly added database instance.
14. An electronic device comprising a processor and a memory, wherein the memory stores machine executable instructions executable by the processor, the machine executable instructions being loaded and executed by the processor to implement the method of any one of claims 1 to 9.
15. A machine readable storage medium, having stored therein a computer program which, when executed by a processor, implements the method of any of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911134095.5A CN111400273B (en) | 2019-11-19 | 2019-11-19 | Database capacity expansion method and device, electronic equipment and machine-readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911134095.5A CN111400273B (en) | 2019-11-19 | 2019-11-19 | Database capacity expansion method and device, electronic equipment and machine-readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111400273A true CN111400273A (en) | 2020-07-10 |
| CN111400273B CN111400273B (en) | 2024-02-02 |
Family
ID=71428370
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911134095.5A Active CN111400273B (en) | 2019-11-19 | 2019-11-19 | Database capacity expansion method and device, electronic equipment and machine-readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111400273B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111930716A (en) * | 2020-07-31 | 2020-11-13 | 中国工商银行股份有限公司 | Database capacity expansion method, device and system |
| CN113239011A (en) * | 2021-05-11 | 2021-08-10 | 京东数字科技控股股份有限公司 | Database capacity expansion method, device and system |
| WO2024212599A1 (en) * | 2023-12-13 | 2024-10-17 | 天翼云科技有限公司 | Method for implementing shard seamless expansion on basis of replication |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102930062A (en) * | 2012-11-30 | 2013-02-13 | 南京富士通南大软件技术有限公司 | Rapid horizontal extending method for databases |
| US20150331857A1 (en) * | 2014-05-15 | 2015-11-19 | Microsoft Corporation | Database migration |
| CN106933859A (en) * | 2015-12-30 | 2017-07-07 | 中国移动通信集团公司 | The moving method and device of a kind of medical data |
| CN106934048A (en) * | 2017-03-16 | 2017-07-07 | 北京搜狐新媒体信息技术有限公司 | Online data moving method, agent node |
| WO2018023497A1 (en) * | 2016-08-03 | 2018-02-08 | 深圳中兴力维技术有限公司 | Data migration method and device |
| CN108132949A (en) * | 2016-12-01 | 2018-06-08 | 腾讯科技（深圳）有限公司 | The method and device of Data Migration in data-base cluster |
| CN108268501A (en) * | 2016-12-30 | 2018-07-10 | 中国移动通信集团北京有限公司 | Method for processing business and device in a kind of online data transition process |
| CN108319596A (en) * | 2017-01-16 | 2018-07-24 | 阿里巴巴集团控股有限公司 | A kind of expansion method and device of database |
| CN109144977A (en) * | 2018-08-14 | 2019-01-04 | 五八有限公司 | A kind of data migration method, device, equipment and storage medium |
| CN109521943A (en) * | 2017-09-19 | 2019-03-26 | 腾讯科技（深圳）有限公司 | The distribution method and Related product of cloud database instance |
| US10346374B1 (en) * | 2014-03-14 | 2019-07-09 | Open Invention Network Llc | Optimized data migration application for database compliant data extraction, loading and transformation |
| CN110019125A (en) * | 2017-11-27 | 2019-07-16 | 北京京东尚科信息技术有限公司 | The method and apparatus of data base administration |
| CN110222030A (en) * | 2019-05-13 | 2019-09-10 | 福建天泉教育科技有限公司 | The method of Database Dynamic dilatation, storage medium |
-
2019
- 2019-11-19 CN CN201911134095.5A patent/CN111400273B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102930062A (en) * | 2012-11-30 | 2013-02-13 | 南京富士通南大软件技术有限公司 | Rapid horizontal extending method for databases |
| US10346374B1 (en) * | 2014-03-14 | 2019-07-09 | Open Invention Network Llc | Optimized data migration application for database compliant data extraction, loading and transformation |
| US20150331857A1 (en) * | 2014-05-15 | 2015-11-19 | Microsoft Corporation | Database migration |
| CN106933859A (en) * | 2015-12-30 | 2017-07-07 | 中国移动通信集团公司 | The moving method and device of a kind of medical data |
| WO2018023497A1 (en) * | 2016-08-03 | 2018-02-08 | 深圳中兴力维技术有限公司 | Data migration method and device |
| CN108132949A (en) * | 2016-12-01 | 2018-06-08 | 腾讯科技（深圳）有限公司 | The method and device of Data Migration in data-base cluster |
| CN108268501A (en) * | 2016-12-30 | 2018-07-10 | 中国移动通信集团北京有限公司 | Method for processing business and device in a kind of online data transition process |
| CN108319596A (en) * | 2017-01-16 | 2018-07-24 | 阿里巴巴集团控股有限公司 | A kind of expansion method and device of database |
| CN106934048A (en) * | 2017-03-16 | 2017-07-07 | 北京搜狐新媒体信息技术有限公司 | Online data moving method, agent node |
| CN109521943A (en) * | 2017-09-19 | 2019-03-26 | 腾讯科技（深圳）有限公司 | The distribution method and Related product of cloud database instance |
| CN110019125A (en) * | 2017-11-27 | 2019-07-16 | 北京京东尚科信息技术有限公司 | The method and apparatus of data base administration |
| CN109144977A (en) * | 2018-08-14 | 2019-01-04 | 五八有限公司 | A kind of data migration method, device, equipment and storage medium |
| CN110222030A (en) * | 2019-05-13 | 2019-09-10 | 福建天泉教育科技有限公司 | The method of Database Dynamic dilatation, storage medium |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111930716A (en) * | 2020-07-31 | 2020-11-13 | 中国工商银行股份有限公司 | Database capacity expansion method, device and system |
| CN113239011A (en) * | 2021-05-11 | 2021-08-10 | 京东数字科技控股股份有限公司 | Database capacity expansion method, device and system |
| WO2024212599A1 (en) * | 2023-12-13 | 2024-10-17 | 天翼云科技有限公司 | Method for implementing shard seamless expansion on basis of replication |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111400273B (en) | 2024-02-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US12117911B2 (en) | Remote data replication method and system | |
| KR101597384B1 (en) | Partition management in a partitioned, scalable, and available structured storage | |
| CN109729129B (en) | Configuration modification method of storage cluster system, storage cluster and computer system | |
| US7840536B1 (en) | Methods and apparatus for dynamic journal expansion | |
| US10838829B2 (en) | Method and apparatus for loading data from a mirror server and a non-transitory computer readable storage medium | |
| US20060047926A1 (en) | Managing multiple snapshot copies of data | |
| US10126946B1 (en) | Data protection object store | |
| CN102158540A (en) | System and method for realizing distributed database | |
| CN111400273B (en) | Database capacity expansion method and device, electronic equipment and machine-readable storage medium | |
| CN103324582A (en) | Memory migration method, memory migration device and equipment | |
| CN109271376A (en) | Database upgrade method, apparatus, equipment and storage medium | |
| US20230281167A1 (en) | Hybrid synchronization using a shadow component | |
| CN113806300B (en) | Data storage method, system, device, equipment and storage medium | |
| CN112256650B (en) | Storage space management method, device, equipment and storage medium | |
| CN105740049B (en) | A kind of control method and device | |
| CN111198845A (en) | Data migration method, readable storage medium and computing device | |
| CN113239012A (en) | Database migration method and device, electronic equipment and storage medium | |
| CN107943412B (en) | Method, device and system for splitting partition and deleting data file in partition | |
| CN104517067A (en) | Method, device and system for data access | |
| CN112083885B (en) | Data migration method and device, electronic equipment and storage medium | |
| US20050262033A1 (en) | Data recording apparatus, data recording method, program for implementing the method, and program recording medium | |
| US10671482B2 (en) | Providing consistency in a distributed data store | |
| JP4512386B2 (en) | Backup system and method | |
| CN111984598A (en) | High-performance metadata log file management method, system, medium and terminal | |
| US7949632B2 (en) | Database-rearranging program, database-rearranging method, and database-rearranging apparatus |
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 |