CN108959533A - The snapshot update management method and system of Metadata Service cluster - Google Patents
The snapshot update management method and system of Metadata Service cluster Download PDFInfo
- Publication number
- CN108959533A CN108959533A CN201810697880.0A CN201810697880A CN108959533A CN 108959533 A CN108959533 A CN 108959533A CN 201810697880 A CN201810697880 A CN 201810697880A CN 108959533 A CN108959533 A CN 108959533A
- Authority
- CN
- China
- Prior art keywords
- snapshot
- update
- meta data
- server
- data server
- 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
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a kind of snapshot update management methods of Metadata Service cluster, comprising: is based on snapshot update management system, system includes multiple meta data servers and management server；This method comprises: transmission snapshot update is requested to management server, the interior metadata information comprising snapshot update of snapshot update request after meta data server carries out the update of snapshot table；Management server is cached after receiving the snapshot update request that meta data server is sent, and updates the snapshot table of itself accordingly；After receiving snapshot acquisition request, corresponding snapshot table data are sent to corresponding object side.The present invention is saved the snapshot update data of whole meta data servers in cluster by management server, any to apply when needing snapshot data, it is only necessary to obtain out of management server, simplify operating procedure when snapshot applications；The snapshot update management system based on the above method that the invention also discloses a kind of.
Description
Technical field
The present invention relates to cluster management technical fields, more particularly to a kind of snapshot update management of Metadata Service cluster
Method and system.
Background technique
It include one in each meta data server mds in the Metadata Service cluster of distributed file system
Snaptable, i.e., a kind of snapshot table, the sequence number and SNAPSHOT INFO, newest primary deletion/creation etc. for saving snapshot are fast
According to metadata.
Currently, after snapshot table of some mds to itself is updated, such as mds1 updates, if other mds are needed
If synchronizing update, need to directly transmit the update snapshot data that request obtains mds1 to mds1.Make in this way,
Under certain business for needing to obtain a large amount of snapshot datas, it is desirable to if obtaining the snapshot data of demand, need each mds in cluster
Between repeatedly interact, complicated for operation, the business deadline is long.
Therefore, the snapshot update management method and system for how providing a kind of Metadata Service cluster easy to operate are these
The current problem to be solved of field technical staff.
Summary of the invention
The object of the present invention is to provide a kind of snapshot update management method of Metadata Service cluster and system, a kind of member number
According to the snapshot update management method of service cluster, the snapshot update of whole meta data servers in cluster is saved by management server
Data facilitate follow-up business application to obtain snapshot data.
In order to solve the above technical problems, the present invention provides a kind of snapshot update management method of Metadata Service cluster,
Based on snapshot update management system, the system comprises multiple meta data servers and management servers；The described method includes:
Transmission snapshot update is requested to the management server after the meta data server carries out the update of snapshot table, described
It include the metadata information of snapshot update in snapshot update request；
The management server is cached after receiving the snapshot update request that the meta data server is sent, accordingly more
The newly snapshot table of itself；After receiving snapshot acquisition request, corresponding snapshot table data are sent to corresponding object side.
Preferably, further includes:
After the management server receives the snapshot update request, sends snapshot update and notify to cluster, except progress
In whole meta data servers other than the meta data server of snapshot update；Hair is carried in the snapshot update notice
The mark of the meta data server of raw snapshot update.
Preferably, further includes:
The meta data server sends snapshot synchronized update and requests to the management server, the snapshot synchronized update
The mark of the meta data server as synchronization object is carried in request；
After the management server receives the snapshot synchronized update request, according to being taken in snapshot synchronized update request
The corresponding snapshot update request of the identifier lookup of band, and lookup result is back to the member for sending the snapshot synchronized update request
Data server.
Preferably, further includes:
After the management server sends the snapshot update notice, the sound of each meta data server return is waited
It answers；
The management server receives whole metadata clothes in addition to the meta data server for carrying out snapshot update
It is engaged in after the response that device returns, sending allows to instruct to the meta data server for carrying out the update of snapshot table；
It is described carry out the update of snapshot table meta data server receive it is described allow instruction after, by itself snapshot table update number
According in write-in log.
Preferably, further includes:
If the management server does not receive whole responses after preset time, transmission carries non-returning response
The mark of meta data server allows to instruct to the meta data server for carrying out the update of snapshot table；
The meta data server for carrying out the update of snapshot table is by the mark of the meta data server of the non-returning response
It is written in itself log.
Preferably, log is written in itself snapshot table more new data by the meta data server for carrying out the update of snapshot table
Afterwards, further includes:
It is described carry out the update of snapshot table meta data server send submit completion notice to the cluster in except itself with
Outer whole meta data servers.
Preferably, the meta data server for carrying out the update of snapshot table also wraps before sending the snapshot update request
It includes:
The meta data server for carrying out the update of snapshot table obtains lock, locks itself list of meta data；
Correspondingly, log is written in itself snapshot table more new data by the meta data server for carrying out the update of snapshot table
Afterwards, further includes:
The meta data server for carrying out the update of snapshot table discharges lock, discharges itself list of meta data.
Preferably, the metadata information of the snapshot update specifically includes:
Snapshot update operation content, snapshot update operation catalogue and snapshot update operating time.
In order to solve the above technical problems, the present invention also provides a kind of snapshot update management systems of Metadata Service cluster
System, including multiple meta data servers and management server；
The meta data server is requested for transmission snapshot update after carrying out snapshot table update to the management service
Device, the interior metadata information comprising snapshot update of snapshot update request；
The management server updates accordingly after receiving the snapshot update request that the meta data server is sent
The snapshot table of itself；After receiving snapshot acquisition request, corresponding snapshot table data are sent to corresponding object side.
The present invention provides a kind of snapshot update management method of Metadata Service cluster and systems, when some metadata
After server carries out the update of snapshot table, which, which can be sent to snapshot update information in management server, delays
Deposit update, so that the snapshot update data comprising meta data servers whole in cluster in management server, any business
Apply when needing snapshot data, it is only necessary to out of management server obtain, without each meta data server it
Between repeatedly interacted, facilitate service application obtain snapshot data, simplify behaviour of the service application when obtaining snapshot data
Make step, reduces the processing time of service application.
Detailed description of the invention
It to describe the technical solutions in the embodiments of the present invention more clearly, below will be to institute in the prior art and embodiment
Attached drawing to be used is needed to be briefly described, it should be apparent that, the accompanying drawings in the following description is only some implementations of the invention
Example, for those of ordinary skill in the art, without creative efforts, can also obtain according to these attached drawings
Obtain other attached drawings.
Fig. 1 is a kind of flow chart of the process of the snapshot update management method of Metadata Service cluster provided by the invention；
Fig. 2 is the process of the process of the snapshot update management method of another Metadata Service cluster provided by the invention
Figure.
Specific embodiment
Core of the invention is to provide the snapshot update management method and system of a kind of Metadata Service cluster, is taken by management
Business device saves the snapshot update data of whole meta data servers in cluster, and follow-up business application is facilitated to obtain snapshot data.
In order to make the object, technical scheme and advantages of the embodiment of the invention clearer, below in conjunction with the embodiment of the present invention
In attached drawing, technical scheme in the embodiment of the invention is clearly and completely described, it is clear that described embodiment is
A part of the embodiment of the present invention, instead of all the embodiments.Based on the embodiments of the present invention, those of ordinary skill in the art
Every other embodiment obtained without making creative work, shall fall within the protection scope of the present invention.
The present invention provides a kind of snapshot update management methods of Metadata Service cluster, are based on snapshot update management system
System, system includes multiple meta data servers and management server；Shown in Figure 1, Fig. 1 is a kind of member provided by the invention
The flow chart of the process of the snapshot update management method of data service cluster；This method comprises:
Step s1: transmission snapshot update is requested to management server, snapshot after meta data server carries out the update of snapshot table
Update the metadata information in request comprising snapshot update；
Wherein, it can select a meta data server as management server in Metadata Service cluster, execute some pipes
Reason operation.This operation is updated for snapshot table, it is believed that management server is snapserver (i.e. snapshot service side), pipe
It manages server and other meta data servers is snapclient (snapshot customer), because management server itself also belongs to
Meta data server, therefore management server includes two kinds of identity of snapserver and snapclient.
After being updated in certain meta-data server to snapshot table, snapshot update can be sent and requested to management server.
At this point, since the meta data server for carrying out snapshot update is only to have carried out updating operation, and will not update result and write with a brush dipped in Chinese ink to magnetic
It in disk, therefore is lost to avoid updating result, needs to cache this snapshot update in the meta data server for carrying out snapshot update
Metadata information.
Step s2: management server is cached after receiving the snapshot update request that meta data server is sent, accordingly more
The newly snapshot table of itself；After receiving snapshot acquisition request, corresponding snapshot table data are sent to corresponding object side.
Here snapshot acquisition request can be what extraneous server was sent, it is also possible to some metadata in cluster
What server was sent, this is not limited by the present invention.
Since management server itself also belongs to one kind of meta data server, the snapshot table in management server
It needs to carry out snapshot table and updates synchronization, therefore, after management server receives snapshot update request, need to update itself accordingly first
Snapshot table.
In a kind of specific implementation, this method further include:
After management server receives snapshot update request, sends snapshot update and notify to cluster, except progress snapshot update
Meta data server other than whole meta data servers in；First number that snapshot update occurs is carried in snapshot update notice
According to the mark of server.
It is understood that other meta data servers may be deposited after having meta data server to carry out snapshot update
In the demand synchronized to the snapshot update, therefore, after having meta data server to carry out snapshot update, management service is needed
Device notifies entire cluster, other meta data servers is facilitated to carry out data acquisition.
It is further known that this method further include:
Meta data server sends snapshot synchronized update and requests to management server, carries in the request of snapshot synchronized update
The mark of meta data server as synchronization object；
After management server receives the request of snapshot synchronized update, according to the identifier lookup carried in the request of snapshot synchronized update
Corresponding snapshot update request, and lookup result is back to the meta data server for sending the request of snapshot synchronized update.
It is understood that part meta data server can have a synchronous demand of data, therefore these meta data servers
After having learnt that snapshot update occurs for meta data server, it can send and request to management server, to obtain snapshot update request,
Synchronize update.
In a kind of specific implementation, this method further include:
After management server sends snapshot update notice, the response of each meta data server return is waited；
Management server receives whole meta data servers in addition to the meta data server for carrying out snapshot update and returns
Response after, send allow instruct to carry out the update of snapshot table meta data server；
The meta data server for carrying out the update of snapshot table receives after allowing instruction, and day is written in itself snapshot table more new data
In will.
Here the purpose for waiting returning response, is to confirm whether each meta data server receives notice.
Wherein, since management server cannot can generally be arranged a preset time, sentence without wait-for-response in limited time
Whole responses whether are received in disconnected preset time.Certainly, the numerical value present invention of preset time is not construed as limiting.
It is understood that under normal circumstances, management server can receive the whole metadata clothes for itself sending notice
The response that business device returns.Receive all response after, can acknowledgement notification complete, at this point, reinform carry out the update of snapshot table
Meta data server carry out log write-in.In Metadata Service cluster, log be for being recorded to operation content, after
Extended meeting periodically writes with a brush dipped in Chinese ink log to disk, and therefore, it is necessary to guarantee the correctness of log and integrality.If carrying out snapshot table
The meta data server of update then can not in log once completion snapshot update record i.e. in log updates if completing
The case where including snapshot update notice, so that the subsequent notice feelings that can not be learnt this log according to the content of log recording and update
Condition.Therefore, receive management server transmission allow instruction after, then carry out log write-in, then can guarantee day as far as possible
The correctness and integrality of will.In addition, it is fashionable in log write, can be synchronous by the information of this snapshot update and snapshot update
Information is recorded into log, and meta data server the log segment of record can be committed in the whole log of itself into
Row saves, and writes with a brush dipped in Chinese ink whole log to disk for subsequent.
In addition, meta data server can periodically write with a brush dipped in Chinese ink log to disk, therefore, in order to avoid writing with a brush dipped in Chinese ink to disk
Interior log content repeats, it is only necessary to log write-in is carried out in the meta data server for carrying out the update of snapshot table.
Although, it is generally the case that management server should be able to receive all first number for itself sending snapshot update notice
It, may be due to some meta data server failures or communication issue according to the response that server returns, but under partial picture
Appearance only receives the case where part response, at this time this method further include:
If management server does not receive whole responses after preset time, the first number for carrying non-returning response is sent
According to the meta data server for allowing to instruct to the update of snapshot table is carried out of the mark of server；
Itself is written in the mark of the meta data server of non-returning response by the meta data server for carrying out the update of snapshot table
In log.
It is understood that if part meta data server is not within a preset time if returning response, it will usually think
The part meta data server there are failure, at this point, management server needs to filter out the metadata of this some notifications failure
The mark of server, and it is sent to the meta data server for carrying out the update of snapshot table, make the metadata clothes for carrying out the update of snapshot table
This portion identification can be written in log for business device, which part Metadata Service when subsequent user being facilitated to learn this snapshot update
Device notice failure.
In a specific embodiment, the meta data server for carrying out the update of snapshot table writes itself snapshot table more new data
After entering log, further includes:
The meta data server for carrying out the update of snapshot table sends the whole submitted in completion notice to cluster in addition to itself
Meta data server.
It is understood that by send submit completion notice, it is possible to notify that other meta data servers this time snapshot more
New operation has been written into log, and snapshot update process is completed.
In a specific embodiment, the meta data server for carrying out the update of snapshot table sends snapshot update request before also
Include:
The meta data server for carrying out the update of snapshot table obtains lock, locks itself list of meta data；
Correspondingly, after log is written in itself snapshot table more new data by the meta data server for carrying out the update of snapshot table, also
Include:
The meta data server for carrying out the update of snapshot table discharges lock, discharges itself list of meta data.
It is understood that meta data server belongs to server-side for actual client, accordingly, it is possible to have
Some clients access to meta data server, if if meta data server is carrying out snapshot update at this time, not only
The access of client may influence the snapshot update of meta data server, and the snapshot update of meta data server may also influence visitor
The access at family end is as a result, therefore, in order to avoid such case is locked when meta data server carries out snapshot update using lock
The list of meta data of the fixed meta data server, is that external client can not access at this moment, after snapshot update, then
Release lock.
In addition, the lock that meta data server obtains is provided with corresponding lock permission, different lock permissions allows to execute difference
Operation, the lock permission for the lock that meta data server obtains in the present invention is required to allow to execute snapshot operation.
Wherein, the metadata information of snapshot update of the present invention specifically includes:
Snapshot update operation content, snapshot update operation catalogue and snapshot update operating time.
Certainly, metadata information also may include other content, and the present invention is not particularly limited this.
Shown in Figure 2, Fig. 2 is the snapshot update management method of another Metadata Service cluster provided by the invention
The flow chart of process.
The present invention provides a kind of snapshot update management methods of Metadata Service cluster, when some meta data server
After carrying out the update of snapshot table, which can be sent to snapshot update information in management server and be cached more
Newly, so that the snapshot update data comprising meta data servers whole in cluster in management server, any service application
When needing snapshot data, it is only necessary to out of management server obtain, without between each meta data server into
Row repeatedly interaction, facilitates service application and obtains snapshot data, simplifies operation step of the service application when obtaining snapshot data
Suddenly, reduce the processing time of service application.
The present invention also provides a kind of snapshot update management systems of Metadata Service cluster, including multiple Metadata Services
Device and management server；
Meta data server is requested for transmission snapshot update after carrying out snapshot table update to management server, and snapshot is more
It include the metadata information of snapshot update in new request；
Management server updates the fast of itself after the snapshot update request for receiving meta data server transmission accordingly
According to table；After receiving snapshot acquisition request, corresponding snapshot table data are sent to corresponding object side.
Above several specific embodiments are only the preferred embodiment of the present invention, and above several specific embodiments can be with
Any combination, the embodiment obtained after combination is also within protection scope of the present invention.It should be pointed out that for the art
For those of ordinary skill, relevant speciality technical staff deduced out in the case where not departing from spirit of that invention and concept thereof other change
Into and variation, should all be included in the protection scope of the present invention.
Each embodiment in this specification is described in a progressive manner, the highlights of each of the examples are with other
The difference of embodiment, the same or similar parts in each embodiment may refer to each other.For device disclosed in embodiment
For, since it is corresponded to the methods disclosed in the examples, so being described relatively simple, related place is said referring to method part
It is bright.
It should also be noted that, in the present specification, relational terms such as first and second and the like be used merely to by
One entity or operation are distinguished with another entity or operation, without necessarily requiring or implying these entities or operation
Between there are any actual relationship or orders.Moreover, the terms "include", "comprise" or its any other variant meaning
Covering non-exclusive inclusion, so that the process, method, article or equipment for including a series of elements not only includes that
A little elements, but also including other elements that are not explicitly listed, or further include for this process, method, article or
The intrinsic element of equipment.In the absence of more restrictions, the element limited by sentence "including a ...", is not arranged
Except there is also other identical elements in the process, method, article or apparatus that includes the element.
The foregoing description of the disclosed embodiments enables those skilled in the art to implement or use the present invention.
Various modifications to these embodiments will be readily apparent to those skilled in the art, as defined herein
General Principle can be realized in other embodiments without departing from the spirit or scope of the present invention.Therefore, of the invention
It is not intended to be limited to the embodiments shown herein, and is to fit to and the principles and novel features disclosed herein phase one
The widest scope of cause.
Claims (9)
1. a kind of snapshot update management method of Metadata Service cluster, which is characterized in that be based on snapshot update management system, institute
The system of stating includes multiple meta data servers and management server；The described method includes:
Transmission snapshot update is requested to the management server, the snapshot after the meta data server carries out the update of snapshot table
Update the metadata information in request comprising snapshot update；
The management server is cached after receiving the snapshot update request that the meta data server is sent, and is updated accordingly certainly
The snapshot table of body；After receiving snapshot acquisition request, corresponding snapshot table data are sent to corresponding object side.
2. the method according to claim 1, wherein further include:
After the management server receives the snapshot update request, sends snapshot update and notify to cluster, except progress snapshot
In whole meta data servers other than the meta data server updated；It is fast that generation is carried in the snapshot update notice
According to the mark of the meta data server of update.
3. according to the method described in claim 2, it is characterized by further comprising:
The meta data server sends snapshot synchronized update and requests to the management server, the snapshot synchronized update request
Inside carry the mark of the meta data server as synchronization object；
After the management server receives the snapshot synchronized update request, interior carrying is requested according to the snapshot synchronized update
The corresponding snapshot update request of identifier lookup, and lookup result is back to the metadata for sending the snapshot synchronized update request
Server.
4. the method according to claim 1, wherein further include:
After the management server sends the snapshot update notice, the response of each meta data server return is waited；
The management server receives whole meta data servers in addition to the meta data server for carrying out snapshot update
After the response of return, sending allows to instruct to the meta data server for carrying out the update of snapshot table；
It is described carry out the update of snapshot table meta data server receive it is described allow instruction after, itself snapshot table more new data is write
Enter in log.
5. according to the method described in claim 4, it is characterized by further comprising:
If the management server does not receive whole responses after preset time, the first number for carrying non-returning response is sent
According to server mark allow to instruct to it is described carry out the update of snapshot table meta data server；
The mark of the meta data server of the non-returning response is written the meta data server for carrying out the update of snapshot table
In itself log.
6. method according to claim 4 or 5, which is characterized in that the meta data server for carrying out the update of snapshot table
After log is written in itself snapshot table more new data, further includes:
The meta data server for carrying out the update of snapshot table, which is sent, to be submitted in completion notice to the cluster in addition to itself
Whole meta data servers.
7. according to the method described in claim 6, it is characterized in that, the meta data server for carrying out the update of snapshot table is sent
Before the snapshot update request further include:
The meta data server for carrying out the update of snapshot table obtains lock, locks itself list of meta data；
Correspondingly, after log is written in itself snapshot table more new data by the meta data server for carrying out the update of snapshot table, also
Include:
The meta data server for carrying out the update of snapshot table discharges lock, discharges itself list of meta data.
8. the method according to claim 1, wherein the metadata information of the snapshot update specifically includes:
Snapshot update operation content, snapshot update operation catalogue and snapshot update operating time.
9. a kind of snapshot update management system of Metadata Service cluster, which is characterized in that including multiple meta data servers with
And management server；
The meta data server is requested for transmission snapshot update after carrying out snapshot table update to the management server, institute
State the metadata information comprising snapshot update in snapshot update request；
The management server updates itself after receiving the snapshot update request that the meta data server is sent accordingly
Snapshot table；After receiving snapshot acquisition request, corresponding snapshot table data are sent to corresponding object side.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810697880.0A CN108959533A (en) | 2018-06-29 | 2018-06-29 | The snapshot update management method and system of Metadata Service cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810697880.0A CN108959533A (en) | 2018-06-29 | 2018-06-29 | The snapshot update management method and system of Metadata Service cluster |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN108959533A true CN108959533A (en) | 2018-12-07 |
Family
ID=64484351
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810697880.0A Pending CN108959533A (en) | 2018-06-29 | 2018-06-29 | The snapshot update management method and system of Metadata Service cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108959533A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111339117A (en) * | 2020-03-19 | 2020-06-26 | 支付宝(杭州)信息技术有限公司 | Data processing method, device and equipment |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060053139A1 (en) * | 2004-09-03 | 2006-03-09 | Red Hat, Inc. | Methods, systems, and computer program products for implementing single-node and cluster snapshots |
| CN107071005A (en) * | 2017-03-24 | 2017-08-18 | 厦门中控生物识别信息技术有限公司 | A kind of method of data synchronization and system |
-
2018
- 2018-06-29 CN CN201810697880.0A patent/CN108959533A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060053139A1 (en) * | 2004-09-03 | 2006-03-09 | Red Hat, Inc. | Methods, systems, and computer program products for implementing single-node and cluster snapshots |
| CN107071005A (en) * | 2017-03-24 | 2017-08-18 | 厦门中控生物识别信息技术有限公司 | A kind of method of data synchronization and system |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111339117A (en) * | 2020-03-19 | 2020-06-26 | 支付宝(杭州)信息技术有限公司 | Data processing method, device and equipment |
| CN111339117B (en) * | 2020-03-19 | 2023-09-01 | 支付宝(杭州)信息技术有限公司 | Data processing method, device and equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11379428B2 (en) | Synchronization of client machines with a content management system repository | |
| CA2790734C (en) | Data synchronization between a data center environment and a cloud computing environment | |
| CN107256178B (en) | Container management platform | |
| US10635658B2 (en) | Asynchronous shared application upgrade | |
| US10379963B2 (en) | Methods and apparatus for managing a large-scale environment of copy data management appliances | |
| CN109542865A (en) | Distributed cluster system configuration file synchronous method, device, system and medium | |
| US10216589B2 (en) | Smart data replication recoverer | |
| WO2012137262A1 (en) | Information processing system and data processing method | |
| US20090030952A1 (en) | Global asset management | |
| US10726042B2 (en) | Replication control using eventually consistent meta-data | |
| KR20040077566A (en) | Method and system for synchronizing data shared among peer computing devices | |
| CN112069265A (en) | Configuration data synchronization method, service data system, computer system and medium | |
| EP2382564A1 (en) | Selective database replication | |
| US10289383B2 (en) | Cross object synchronization | |
| CN108156030B (en) | Method and device for synchronizing configuration strategies | |
| CN103701913A (en) | Data synchronization method and device | |
| CN109144785A (en) | Method and apparatus for Backup Data | |
| CN106325768B (en) | A kind of two-shipper storage system and method | |
| US11321193B2 (en) | Database restoration across cloud environments | |
| US20180150312A1 (en) | Data-persisting temporary virtual machine environments | |
| CN108959533A (en) | The snapshot update management method and system of Metadata Service cluster | |
| US9201685B2 (en) | Transactional cache versioning and storage in a distributed data grid | |
| CN111198805B (en) | Abnormality monitoring method and device | |
| US9524312B2 (en) | Prioritized, incremental data retrieval from a database, with an event listener | |
| US11630814B2 (en) | Automated online upgrade of database replication |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20181207 |
|
| RJ01 | Rejection of invention patent application after publication |