CN112328573A - Database migration method and system in kubernets cluster - Google Patents
Database migration method and system in kubernets cluster Download PDFInfo
- Publication number
- CN112328573A CN112328573A CN202011208456.9A CN202011208456A CN112328573A CN 112328573 A CN112328573 A CN 112328573A CN 202011208456 A CN202011208456 A CN 202011208456A CN 112328573 A CN112328573 A CN 112328573A
- Authority
- CN
- China
- Prior art keywords
- database
- access pressure
- controller
- instance
- service
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000013508 migration Methods 0.000 title claims description 35
- 230000005012 migration Effects 0.000 title claims description 35
- 238000004590 computer program Methods 0.000 claims description 11
- 230000000694 effects Effects 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 16
- 230000008569 process Effects 0.000 description 5
- 238000012423 maintenance Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000008602 contraction Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000003068 static 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/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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- 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/25—Integrating or interfacing systems involving database management systems
- G06F16/256—Integrating or interfacing systems involving database management systems in federated or virtual 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Abstract
The application relates to a method and a system for migrating a database in a kubernets cluster, wherein the method for migrating the database in the kubernets cluster comprises the following steps: the flow monitor judges whether the access pressure value of the database is greater than a set threshold value; if so, the flow monitor sends request information for migrating the database to a database controller; newly adding a database instance by the database controller, and transferring a database table of the database to the newly added database instance; the database controller locks the database and modifies the direction of the database Service, and through the application, the problem that a single instance cannot support large concurrent access is solved, so that the effect of effectively supporting the large concurrent access of the database instance is achieved.
Description
Technical Field
The application relates to the technical field of cloud computing, in particular to a method and a system for migrating a database in a kubernets cluster.
Background
In the related technology, when the Service scale is small, multiple databases of a kubernet cluster can also meet the access needs of the databases when running on the same instance, but with the continuous increase of the Service scale, the database table is increased, with more and more frequent database accesses, finally, a single instance cannot support the access needs of the multiple databases, the processing mode is that the pressure of the databases is manually detected by operation and maintenance personnel, the databases are manually migrated, the Service is suspended after migration, and the switching of Service direction is manually completed, which is time-consuming and labor-consuming.
An effective solution is not provided for the problem that a single instance cannot support large concurrent access in the related art.
Disclosure of Invention
The embodiment of the application provides a database migration method and a database migration system in a kubernets cluster, and aims to at least solve the problem that a single instance cannot support large concurrent access in the related technology.
In a first aspect, an embodiment of the present application provides a method for migrating a database in a kubernets cluster, where the method includes:
the flow monitor judges whether an access pressure value of a database is greater than a set threshold value, wherein the access pressure value comprises the frequency and/or the flow size of the database accessed by a Service system through a database Service;
if so, the flow monitor sends request information for migrating the database to a database controller;
after receiving the request information, the database controller adds a database instance and migrates a database table of the database to the added database instance;
and after the database table migration is completed, the database controller locks the database and modifies the direction of the database Service corresponding to the database, so that the database Service points to the newly added database instance.
In some embodiments, before the flow monitor determines whether the access pressure value of the database is greater than the set threshold, the method includes: the flow monitor calculates an access pressure value of the database.
In some embodiments, after the traffic monitor calculates the access pressure value of the database within the current window, if yes, before the traffic monitor sends the request information for migrating the database to the database controller, the method includes: and in a plurality of continuous window periods, calculating to obtain a plurality of access pressure values of the database, and judging whether the plurality of access pressure values are all larger than the set threshold value by the flow monitor.
In some embodiments, after the database Service points to the newly added database instance, the method includes: the database controller unlocks the database.
In a second aspect, an embodiment of the present application provides a database migration system in a kubernets cluster, where the system includes a traffic monitor and a database controller;
the flow monitor judges whether an access pressure value of a database is greater than a set threshold value, wherein the access pressure value comprises the frequency and/or the flow size of the database accessed by a Service system through a database Service;
if so, the flow monitor sends request information for migrating the database to the database controller;
after receiving the request information, the database controller adds a database instance and migrates a database table of the database to the added database instance;
and after the database table migration is completed, the database controller locks the database and modifies the direction of the database Service corresponding to the database, so that the database Service points to the newly added database instance.
In some embodiments, before the flow monitor determines whether the access pressure value of the database is greater than the set threshold: the flow monitor calculates the access pressure of the database.
In some embodiments, after the traffic monitor calculates the access pressure of the database within the current window, if yes, before the traffic monitor sends the request information for migrating the database to the database controller: and in a plurality of continuous window periods, calculating to obtain a plurality of access pressure values of the database, and judging whether the plurality of access pressure values are all larger than the set threshold value by the flow monitor.
In some embodiments, after the database Service points to the newly added database instance: the database controller unlocks the database.
In a third aspect, an embodiment of the present application provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements a database migration method in the kubernets cluster when executing the computer program.
In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a method for migrating a database in a kubernets cluster.
Compared with the related art, the database migration method in the kubernets cluster provided by the embodiment of the application judges whether the access pressure value of the database is greater than a set threshold value or not through the flow monitor, wherein the access pressure value comprises the frequency and/or the flow size of the Service system accessing the database through the database Service; if so, the flow monitor sends request information for migrating the database to a database controller; after the database controller receives the request information, newly adding a database instance, and migrating a database table of the database to the newly added database instance; after the database table migration is completed, the database controller locks the database and modifies the direction of the database Service corresponding to the database, so that the database Service points to the newly added database instance, the problem that a single instance cannot support large concurrent access is solved, and the effect of providing effective support for the large concurrent access of the database instance is achieved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a schematic diagram of an application environment of a database migration method in a kubernets cluster according to an embodiment of the present application;
FIG. 2 is a flow chart of a method of database migration in a kubernets cluster according to an embodiment of the present application;
FIG. 3 is a flow chart of a flow monitor calculating an access pressure value for a database according to an embodiment of the present application;
FIG. 4 is a flow chart of a method of comparing an access pressure value to a set threshold value according to an embodiment of the application;
FIG. 5 is a flow diagram of a database controller unlocking a database according to an embodiment of the present application;
FIG. 6 is a system architecture diagram illustrating a database migration scenario according to an embodiment of the present application;
FIG. 7 is a system architecture diagram during database migration according to an embodiment of the present application;
FIG. 8 is a block diagram of a database migration system in a kubernets cluster according to an embodiment of the present application;
fig. 9 is an internal structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be described and illustrated below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments provided in the present application without any inventive step are within the scope of protection of the present application.
It is obvious that the drawings in the following description are only examples or embodiments of the present application, and that it is also possible for a person skilled in the art to apply the present application to other similar contexts on the basis of these drawings without inventive effort. Moreover, it should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another.
Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the specification. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of ordinary skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments without conflict.
Unless defined otherwise, technical or scientific terms referred to herein shall have the ordinary meaning as understood by those of ordinary skill in the art to which this application belongs. Reference to "a," "an," "the," and similar words throughout this application are not to be construed as limiting in number, and may refer to the singular or the plural. The present application is directed to the use of the terms "including," "comprising," "having," and any variations thereof, which are intended to cover non-exclusive inclusions; for example, a process, method, system, article, or apparatus that comprises a list of steps or modules (elements) is not limited to the listed steps or elements, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Reference to "connected," "coupled," and the like in this application is not intended to be limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The term "plurality" as referred to herein means two or more. "and/or" describes an association relationship of associated objects, meaning that three relationships may exist, for example, "A and/or B" may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. Reference herein to the terms "first," "second," "third," and the like, are merely to distinguish similar objects and do not denote a particular ordering for the objects.
The database migration method in the kubernets cluster provided by the application can be applied to an application environment shown in fig. 1, fig. 1 is an application environment schematic diagram of the database migration method in the kubernets cluster according to the embodiment of the application, fig. 1 is a server 101, and the server 101 can be implemented by an independent server or a server cluster formed by a plurality of servers. The server 101 is internally deployed with a kubernets cluster and a database migration system in the kubernets cluster, wherein the database migration system in the kubernets cluster comprises a traffic monitor and a database controller; the flow monitor judges whether the access pressure value of the database is greater than a set threshold value, wherein the access pressure value comprises the frequency and/or the flow size of the Service system accessing the database through the database Service; if so, the flow monitor sends request information for migrating the database to the database controller; after the database controller receives the request information, newly adding a database instance, and migrating a database table of the database to the newly added database instance; after the database table migration is completed, the database controller locks the database and modifies the direction of the database Service corresponding to the database to enable the database Service to point to the newly added database instance; the kubernets are an open-source platform for automatic container operation, and can realize the functions of automatic deployment, automatic expansion and contraction of container clusters, maintenance and the like; pod is the smallest resource scheduling unit on kubernets, but Pod may be destroyed and rebuilt frequently, and Pod IP may change; the Service is a resource provided by kubernets and is used for solving the problem that the pod IP is changed frequently, the Service can provide a uniform entrance (IP address), and even if the pod associated with the Service is changed, the Service can correctly forward the request to the available pod.
The present embodiment provides a method for migrating a database in a kubernets cluster, and fig. 2 is a flowchart of the method for migrating a database in a kubernets cluster according to the embodiment of the present application, and as shown in fig. 2, the flowchart includes the following steps:
step S201, the flow monitor judges whether the access pressure value of the database is greater than a set threshold value, wherein the access pressure value comprises the frequency and/or the flow size of the Service system accessing the database through the database Service;
step S202, if yes, the flow monitor sends request information for migrating the database to a database controller; if not, the database is not migrated, and a next monitoring window is entered;
step S203, after the database controller receives the request information, newly adding a database instance, and migrating the database table of the database to the newly added database instance;
step S204, after the database table migration is completed, the database controller locks the database and modifies the direction of the database Service corresponding to the database, so that the database Service points to the newly added database instance.
Through the above steps S201 to S204, compared to the problem that a single instance in the prior art cannot support large concurrent access, the present embodiment adds a new traffic monitor based on the original kubernets, adds a new database controller, the traffic monitor mainly detects database traffic, the database controller mainly takes charge of migrating the database table and redirecting the database accessed by the Service, the present embodiment cooperates with the database access tag of the Service system to automatically determine the database instance pressure, when the single instance cannot support large concurrent access, the traffic monitor determines that the access pressure of the database is greater than the set threshold, and timely sends the request information for migrating the database to the database controller, after the database controller receives the request information, adds a new database instance, migrates the database with high access amount to a new instance, and finally directs the database Service access to the new instance, the problem that a single instance cannot support large concurrent access is solved, and effective support is provided for the large concurrent access of the database instance.
It should be noted that, the databases in the cluster all provide external services in the form of Service, and the business system accesses the databases in the form of Service discovery, and even if the database instance changes, the business system is not sensitive to the change.
In some embodiments, fig. 3 is a flowchart of a flow monitor calculating an access pressure value of a database according to an embodiment of the present application, and as shown in fig. 3, before the flow monitor determines whether the access pressure value of the database is greater than a set threshold, the method includes the following steps:
in step S301, the flow monitor calculates an access pressure value of the database.
Through the step S301, the flow monitor obtains the access pressure value of the database, and compared with the prior art that the pressure of the database is manually detected by operation and maintenance personnel, the database migration requirement can be timely found through detection of the flow monitor, and the problem that a single instance cannot support large concurrent access is avoided.
In some embodiments, fig. 4 is a flowchart of a method for comparing an access pressure value with a set threshold according to an embodiment of the present application, and as shown in fig. 4, after the traffic monitor calculates the access pressure value of the database in a current window period, if yes, before the traffic monitor sends request information for migrating the database to the database controller, the method includes the following steps:
step S401, in a plurality of consecutive window periods, calculating a plurality of access pressure values of the database, and the flow monitor determining whether the plurality of access pressure values are all greater than the set threshold.
In step 401, the traffic monitor calculates the access pressure value of the database by sliding the window, and reports a request for migrating the database to the database controller when the pressure of the database in a plurality of consecutive monitoring windows exceeds a set threshold, because a single access pressure value is greater than the set threshold, it may indicate that the database has a temporary busy access, and the access pressure values of the current database calculated for a plurality of consecutive times are greater than the set threshold, which can reflect the necessity of actually having a newly added database instance.
In some embodiments, fig. 5 is a flowchart of a database controller unlocking a database according to an embodiment of the present application, and as shown in fig. 5, after the database Service points to the newly added database instance, the method includes the following steps:
in step S501, the database controller unlocks the database.
After the migration of the database table is completed (the Service does not need to be interrupted during the migration), in the process of switching the pointing direction of the database Service, in order to ensure the accuracy of the migrated data, the database needs to be locked, and the writing operation cannot be performed, at this time, the suspended Service is more secure, and after the locking is released in step S501, the Service system can continue to operate.
In some embodiments, fig. 6 is a schematic diagram of a system architecture when a database is not migrated according to an embodiment of the present application, as shown in fig. 6, a Service system and a database become Service providers by way of Service, the Service system accesses the database through an IP provided by the database Service, a request arriving at the database Service is forwarded to a database instance, and a traffic monitor continuously monitors traffic conditions of the database Service.
In some embodiments, fig. 7 is a schematic diagram of a system architecture during database migration according to an embodiment of the present application, and as shown in fig. 7, when a traffic monitor detects that an access pressure value of a certain database is continuously and multiple times greater than a set threshold, a request for database migration is initiated to a database controller; the database controller performs database migration, as shown in the figure, the database on the right side in the database example on the upper right side is migrated to the newly added database example on the lower right side; and finally, the database controller can temporarily lock the original database and modify the direction of the database Service so that the database Service points to the newly added database instance.
It should be noted that the steps illustrated in the above-described flow diagrams or in the flow diagrams of the figures may be performed in a computer system, such as a set of computer-executable instructions, and that, although a logical order is illustrated in the flow diagrams, in some cases, the steps illustrated or described may be performed in an order different than here.
Fig. 8 is a block diagram illustrating a structure of a database migration system in a kubernets cluster according to an embodiment of the present disclosure, and as shown in fig. 8, the system includes a traffic monitor 81 and a database controller 82; the flow monitor 81 determines whether an access pressure value of the database is greater than a set threshold, wherein the access pressure value includes the frequency and/or the flow size of the Service system accessing the database through the database Service; if yes, the traffic monitor 81 sends a request message for migrating the database to the database controller 82; after receiving the request information, the database controller 82 adds a new database instance, and migrates the database table of the database to the added database instance; after the database table migration is completed, the database controller 82 locks the database, and modifies the direction of the database Service corresponding to the database, so that the database Service points to the newly added database instance.
In some embodiments, before the flow monitor 81 determines whether the access pressure value of the database is greater than the set threshold: the flow monitor 81 calculates the access pressure of the database.
In some embodiments, after the traffic monitor 81 calculates the access pressure of the database during the current window, if yes, the traffic monitor 81 sends the request information for migrating the database to the database controller 82 before: in a plurality of consecutive window periods, a plurality of access pressure values of the database are calculated, and the flow monitor 81 determines whether the plurality of access pressure values are all greater than the set threshold value.
In some embodiments, the database Service points to the new database instance after: the database controller 82 unlocks the database.
In an embodiment, fig. 9 is a schematic internal structure diagram of an electronic device according to an embodiment of the present application, and as shown in fig. 9, there is provided an electronic device, which may be a server, and its internal structure diagram may be as shown in fig. 9. The electronic device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the electronic device is configured to provide computing and control capabilities. The memory of the electronic equipment comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the electronic device is used for storing data. The network interface of the electronic device is used for connecting and communicating with an external terminal through a network. The computer program is executed by a processor to implement a method of game data push.
Those skilled in the art will appreciate that the configuration shown in fig. 9 is a block diagram of only a portion of the configuration relevant to the present application, and does not constitute a limitation on the electronic device to which the present application is applied, and a particular electronic device may include more or less components than those shown in the drawings, or combine certain components, or have a different arrangement of components.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
It should be understood by those skilled in the art that various features of the above-described embodiments can be combined in any combination, and for the sake of brevity, all possible combinations of features in the above-described embodiments are not described in detail, but rather, all combinations of features which are not inconsistent with each other should be construed as being within the scope of the present disclosure.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method for migrating a database in a kubernets cluster is characterized by comprising the following steps:
the flow monitor judges whether an access pressure value of a database is greater than a set threshold value, wherein the access pressure value comprises the frequency and/or the flow size of the database accessed by a Service system through a database Service;
if so, the flow monitor sends request information for migrating the database to a database controller;
after receiving the request information, the database controller adds a database instance and migrates a database table of the database to the added database instance;
and after the database table migration is completed, the database controller locks the database and modifies the direction of the database Service corresponding to the database, so that the database Service points to the newly added database instance.
2. The method of claim 1, wherein before the flow monitor determines whether the access pressure value of the database is greater than the set threshold, the method comprises: the flow monitor calculates an access pressure value of the database.
3. The method of claim 2, wherein after the traffic monitor calculates the access pressure value of the database within the current window, if yes, before the traffic monitor sends a request message for migrating the database to a database controller, the method comprises: and in a plurality of continuous window periods, calculating to obtain a plurality of access pressure values of the database, and judging whether the plurality of access pressure values are all larger than the set threshold value by the flow monitor.
4. The method of claim 1, wherein after the database Service points to the newly added database instance, the method comprises: the database controller unlocks the database.
5. A database migration system in a kubernets cluster is characterized by comprising a traffic monitor and a database controller;
the flow monitor judges whether an access pressure value of a database is greater than a set threshold value, wherein the access pressure value comprises the frequency and/or the flow size of the database accessed by a Service system through a database Service;
if so, the flow monitor sends request information for migrating the database to the database controller;
after receiving the request information, the database controller adds a database instance and migrates a database table of the database to the added database instance;
and after the database table migration is completed, the database controller locks the database and modifies the direction of the database Service corresponding to the database, so that the database Service points to the newly added database instance.
6. The system of claim 5, wherein the flow monitor is configured to determine whether the access pressure value of the database is greater than a predetermined threshold value by: the flow monitor calculates the access pressure of the database.
7. The system of claim 6, wherein after the traffic monitor calculates the access pressure of the database within the current window, if yes, before the traffic monitor sends the database controller the request information for migrating the database: and in a plurality of continuous window periods, calculating to obtain a plurality of access pressure values of the database, and judging whether the plurality of access pressure values are all larger than the set threshold value by the flow monitor.
8. The system of claim 5, wherein the database Service points to after the newly added database instance: the database controller unlocks the database.
9. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of database migration in a kubernets cluster according to any of claims 1 to 4 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out a method of database migration in a kubernets cluster according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011208456.9A CN112328573A (en) | 2020-11-03 | 2020-11-03 | Database migration method and system in kubernets cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011208456.9A CN112328573A (en) | 2020-11-03 | 2020-11-03 | Database migration method and system in kubernets cluster |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112328573A true CN112328573A (en) | 2021-02-05 |
Family
ID=74323136
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011208456.9A Pending CN112328573A (en) | 2020-11-03 | 2020-11-03 | Database migration method and system in kubernets cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112328573A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112685390A (en) * | 2021-03-22 | 2021-04-20 | 阿里云计算有限公司 | Database instance management method and device and computing equipment |
| CN113093995A (en) * | 2021-04-12 | 2021-07-09 | 杭州朗澈科技有限公司 | Cloud disk data migration method and system |
| CN113688182A (en) * | 2021-10-26 | 2021-11-23 | 深圳市明源云科技有限公司 | Database automatic switching method and device and computer readable storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102508718A (en) * | 2011-11-22 | 2012-06-20 | 杭州华三通信技术有限公司 | Method and device for balancing load of virtual machine |
| CN110245125A (en) * | 2019-05-20 | 2019-09-17 | 中国平安人寿保险股份有限公司 | Data migration method, device, computer equipment and storage medium |
| CN110780998A (en) * | 2019-09-29 | 2020-02-11 | 武汉大学 | Kubernetes-based dynamic load balancing resource scheduling method |
| CN111190883A (en) * | 2019-12-03 | 2020-05-22 | 腾讯科技（深圳）有限公司 | Data migration method and device, computer readable storage medium and computer equipment |
| CN111367887A (en) * | 2020-03-03 | 2020-07-03 | 威海新北洋数码科技有限公司 | Multi-tenant data sharing system, management method thereof and database deployment method |
| US20200326876A1 (en) * | 2017-12-28 | 2020-10-15 | Huawei Technologies Co., Ltd. | Object Migration Method, Device, and System |
-
2020
- 2020-11-03 CN CN202011208456.9A patent/CN112328573A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102508718A (en) * | 2011-11-22 | 2012-06-20 | 杭州华三通信技术有限公司 | Method and device for balancing load of virtual machine |
| US20200326876A1 (en) * | 2017-12-28 | 2020-10-15 | Huawei Technologies Co., Ltd. | Object Migration Method, Device, and System |
| CN110245125A (en) * | 2019-05-20 | 2019-09-17 | 中国平安人寿保险股份有限公司 | Data migration method, device, computer equipment and storage medium |
| CN110780998A (en) * | 2019-09-29 | 2020-02-11 | 武汉大学 | Kubernetes-based dynamic load balancing resource scheduling method |
| CN111190883A (en) * | 2019-12-03 | 2020-05-22 | 腾讯科技（深圳）有限公司 | Data migration method and device, computer readable storage medium and computer equipment |
| CN111367887A (en) * | 2020-03-03 | 2020-07-03 | 威海新北洋数码科技有限公司 | Multi-tenant data sharing system, management method thereof and database deployment method |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112685390A (en) * | 2021-03-22 | 2021-04-20 | 阿里云计算有限公司 | Database instance management method and device and computing equipment |
| CN112685390B (en) * | 2021-03-22 | 2021-12-21 | 阿里云计算有限公司 | Database instance management method and device and computing equipment |
| CN113093995A (en) * | 2021-04-12 | 2021-07-09 | 杭州朗澈科技有限公司 | Cloud disk data migration method and system |
| CN113093995B (en) * | 2021-04-12 | 2023-05-26 | 深圳软通动力信息技术有限公司 | Cloud disk data migration method and system |
| CN113688182A (en) * | 2021-10-26 | 2021-11-23 | 深圳市明源云科技有限公司 | Database automatic switching method and device and computer readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112328573A (en) | Database migration method and system in kubernets cluster | |
| CN111464355A (en) | Method and device for controlling expansion capacity of Kubernetes container cluster and network equipment | |
| CN110602169B (en) | Service calling method and device, computer equipment and storage medium | |
| WO2022057231A1 (en) | Method and apparatus for accessing server, device, and storage medium | |
| CN105069152B (en) | data processing method and device | |
| WO2019128382A1 (en) | Method for deleting container, and related device | |
| CN107992491A (en) | A kind of method and device of distributed file system, data access and data storage | |
| CN112422610A (en) | Intelligent gateway method and system based on distributed object storage | |
| CN112532687A (en) | Method and system for capacity expansion of kubernets load balancer | |
| CN110557398B (en) | Service request control method, device, system, computer equipment and storage medium | |
| CN112905556A (en) | Directory lease management method, device, equipment and storage medium for distributed system | |
| CN113900774B (en) | Virtual machine control method and device of cloud operating system and storage medium | |
| CN112115167A (en) | Cache system hot spot data access method, device, equipment and storage medium | |
| US11159608B2 (en) | Method and control node for managing cloud resources in a communications network | |
| CN112671945A (en) | Method, device, computer equipment and storage medium for managing IP proxy pool | |
| CN109857344B (en) | Heartbeat state judgment method and device based on shared memory and computer equipment | |
| CN109831521B (en) | Cache instance management method and device, computer equipment and storage medium | |
| CN114564153B (en) | Volume mapping relieving method, device, equipment and storage medium | |
| CN110650132A (en) | Access method and device of edge computing node, computer equipment and storage medium | |
| CN114172903A (en) | Node capacity expansion method, device, equipment and medium of slarm scheduling system | |
| CN114546591A (en) | Mirror image file sharing method, container cluster management system and related equipment | |
| CN114422530A (en) | Flow control method and device, computer equipment and storage medium | |
| EP3255542A1 (en) | Service management method and the device | |
| CN108834087B (en) | Short message sending method and device, computer equipment and storage medium | |
| CN113093995A (en) | Cloud disk data migration method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220808 Address after: 100094 Room 502, floor 5, building 16, East District, yard 10, northwest Wangdong Road, Haidian District, Beijing Applicant after: Softcom power information technology (Group) Co.,Ltd. Address before: 311100 Room 802, building 12, 1818-2, Wenyi West Road, Yuhang street, Yuhang District, Hangzhou City, Zhejiang Province Applicant before: HANGZHOU LANGCHE TECHNOLOGY Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220905 Address after: 518000 floor 2-24, building a, Zhongshe Plaza, No.1028, Buji Road, Dongxiao street, Luohu District, Shenzhen City, Guangdong Province Applicant after: Shenzhen Softcom Power Information Technology Co.,Ltd. Address before: 100094 Room 502, floor 5, building 16, East District, yard 10, northwest Wangdong Road, Haidian District, Beijing Applicant before: Softcom power information technology (Group) Co.,Ltd. |
|
| TA01 | Transfer of patent application right |