CN104394142A - Method and device for achieving automatic Redis master-slave conversion - Google Patents
Method and device for achieving automatic Redis master-slave conversion Download PDFInfo
- Publication number
- CN104394142A CN104394142A CN201410679245.1A CN201410679245A CN104394142A CN 104394142 A CN104394142 A CN 104394142A CN 201410679245 A CN201410679245 A CN 201410679245A CN 104394142 A CN104394142 A CN 104394142A
- Authority
- CN
- China
- Prior art keywords
- redis
- master
- buffer control
- control center
- subsystem
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a method and a device for achieving automatic Redis master-slave conversion. The device includes a Redis cache control center, a broadcasting service framework, subsystems and Redis nodes. The Redis cache control center is used for storing configuration information, providing registration service for the broadcasting service framework, monitoring the Redis nodes, changing master-slave configuration information in a memory when a Redis master server is not alive and sending master-slave conversion commands to the broadcasting service framework. The broadcasting service framework is used for obtaining the broadcasting conversion commands of each subsystem of Redis linkage information from the Redis cache control center after receiving the master-slave conversion commands from the Redis cache control center. The subsystems are used for conducting master-slave conversion after receiving broadcasting of the broadcasting service framework. The Redis nodes serve as a cache layer between the subsystems and a database.
Description
Technical field
The present invention relates to a kind of method and system for realizing the automatic master-slave swap of Redis.
Background technology
Current web application system, in order to solve the high concurrent performance issue brought, all can take cache layer, the most widely used Redis of being exactly (Redis is the memory database of a key-Value Types in essence) between web application system and database.Redis, due to its high-performance and shirtsleeve operation order, as the cushioning effect between software and traditional database, when ensure that data validity, can also ensure that high-performance completely simultaneously.
Current Redis only supports master-slave back-up, but the version issued is not supported automatically to carry out master-slave swap after encountering problems, and mainly contains following two kinds at present to this solution:
The first scheme adopts Redis pair to write, and it writes two parts to carry out by application server.In this scenario, the comparison of coherence shortcoming of data, cannot use principal and subordinate's data Replica mechanism that Redis itself carries; After main frame is wherein hung, the follow-up difficulty cost compare adding new main frame is high; Current system must be stopped could continuing to add; Write the Redis of two-server simultaneously, alternately more more than once than normal condition, affect efficiency.
First scheme is by Redis and Keepalived combination of software.In this scenario, need to install Keepalived software separately, the script that allocation plan describes and configuration file, increase learning cost and easily make mistakes; All must open localization strategy at main frame with from machine, otherwise in the process automatically switched mutually, the data of the opposing party can be emptied by the side not opening localization, cause data to lose completely; The service logic of its own system cannot be implanted, stateless monitoring and master-slave swap can only be performed, such as, can not accomplish with the questions and prospect record when monitoring of concrete service logic and master-slave swap; Follow-up to add new Redis machine inconvenient, needs to change configuration file.
Therefore, expect to provide a kind of method and system more effectively realizing the automatic master-slave swap of Redis.
Summary of the invention
In order to solve in above-mentioned shortcoming of the prior art and problem at least one and the present invention is proposed.Based on the shortcoming that prior art exists, the invention provides a kind of method and system realizing the automatic master-slave swap of Redis of improvement, it carries out the broadcast of Redis master-slave swap order by broadcast service framework, thus realizes the object of master-slave swap.According to method and system of the present invention, do not need to build the living Redis environment of two covers, while cost-saving, therefore can not increase interaction times yet, lower efficiency; Without the need to configuring complicated Keepalived script and configuration file, reducing learning cost and reducing the possibility of makeing mistakes simultaneously; System that can not be out of service does not need to change configuration file yet, and the information of the Redis machine only needing simple typing to newly increase can complete newly-increased Redis machine function; Can dispose in any one operating system, no matter be windows platform or Linux platform; Existing system is got involved with the form of plug-in unit, very low to existing system transformation, and applicability is high.
According to an aspect, the present invention proposes a kind of system realizing the automatic master-slave swap of Redis, comprise: Redis buffer control center, send master-slave swap order for store configuration information, to the registration service of broadcast service framework, monitoring Redis node and principal and subordinate's configuration information of changing when Redis master server is not survived in internal memory to broadcast service framework; Broadcast service framework, for after from Redis buffer control receive centre to master-slave swap order, to each subsystem broadcast switching command obtaining Redis link information from Redis buffer control center; Subsystem, for carrying out master-slave swap after the broadcast receiving broadcast service framework; And Redis node, as the cache layer between subsystem and database.
Alternatively, the configuration information be stored in Redis buffer control in the heart comprises the IP of Redis master server and port information, Redis from the IP of server and port information and the Redis configuration information for each subsystem.
Alternatively, the IP of Redis master server and port information and Redis are stored in Redis configuration information table from the IP of server and port information, and the Redis configuration information being used for each subsystem is stored in subsystem Redis link information table.
Alternatively, broadcast service framework is Dubbo service framework.
Alternatively, by sending Ping order every predetermined amount of time to Redis master server, Redis buffer control center judges whether Redis master server survives.Described predetermined amount of time can be arranged as required,
Alternatively, when Redis buffer control center judges that Redis master server is not survived, Redis buffer control center judges whether Redis survives from server further, and when judging that Redis changes the principal and subordinate's configuration information preserved internal memory when surviving from server; And when judging that Redis reports to the police in a suitable form when server is not survived.
Alternatively, before Redis buffer control center sends master-slave swap order to broadcast service framework, the Redis principal and subordinate information of preserving in the Redis configuration information being used for each subsystem be stored in subsystem Redis link information table and internal memory compares by Redis buffer control center, and sends master-slave swap order when the Redis configuration information of at least one subsystem is different from the Redis principal and subordinate information of preserving in internal memory to broadcast service framework.
Alternatively, its Redis link information is returned to Redis buffer control center 110 by subsystem after carrying out master-slave swap.
According to another aspect, providing a kind of method for realizing the automatic master-slave swap of Redis, comprising: start Redis buffer control center, wherein according to the configuration information be stored in Redis buffer control in the heart, principal and subordinate's information is loaded in internal memory; By Redis buffer control center to the registration service of broadcast service framework; After succeeding in registration, Redis buffer control center is monitored Redis node; When judging that Redis master server is not survived, the principal and subordinate's configuration information preserved in internal memory is changed at Redis buffer control center; Redis buffer control center sends master-slave swap order to broadcast service framework; Broadcast service framework is to each subsystem broadcast switching command obtaining Redis link information from Redis buffer control center; And subsystem carries out master-slave swap.
Alternatively, the configuration information be stored in Redis buffer control in the heart can comprise the IP of Redis master server and port information, Redis from the IP of server and port information and the Redis configuration information for each subsystem.
Alternatively, the IP of Redis master server and port information and Redis are stored in Redis configuration information table from the IP of server and port information, and are stored in subsystem Redis link information table for the Redis configuration information of each subsystem.
Alternatively, broadcast service framework is Dubbo service framework.
Alternatively, by sending Ping order every predetermined amount of time to Redis master server, Redis buffer control center judges whether Redis master server survives.
Alternatively, when judging that Redis master server is not survived, Redis buffer control center judges whether Redis survives from server further, and when judging that Redis changes the principal and subordinate's configuration information preserved internal memory when surviving from server, otherwise report to the police in a suitable form.
Alternatively, before Redis buffer control center sends master-slave swap order to broadcast service framework, the Redis principal and subordinate information of preserving in the Redis configuration information being used for each subsystem be stored in subsystem Redis link information table and internal memory compares by Redis buffer control center 110, and sends master-slave swap order when the Redis configuration information of at least one subsystem is different from the Redis principal and subordinate information of preserving in internal memory to broadcast service framework.
Alternatively, its Redis link information is returned to Redis buffer control center by subsystem after carrying out master-slave swap.
Accompanying drawing explanation
By the description carried out below in conjunction with accompanying drawing, the above and other aspects, features and advantages of some one exemplary embodiment of the present invention will become apparent to those skilled in the art, wherein:
Fig. 1 is according to the Organization Chart realizing the system of the automatic master-slave swap of Redis of the present invention; And
Fig. 2 is according to the flow chart realizing the method for the automatic master-slave swap of Redis of the present invention.
Embodiment
There is provided with reference to accompanying drawing the following describes help complete understanding one exemplary embodiment of the present invention.It comprises various details to help understanding, and they should be thought it is only exemplary.Therefore, those of ordinary skill in the art will be appreciated that, can make various change and amendment, and can not deviate from scope and spirit of the present invention to the embodiments described herein.Equally, for clarity and conciseness, the description to known function and structure is eliminated.
Fig. 1 is the Organization Chart realizing the system of the automatic master-slave swap of Redis according to an embodiment of the invention.
Redis buffer control center 110 is for store configuration information, to broadcast service framework 120 registration service, monitoring Redis node 140 and change the principal and subordinate's configuration information in internal memory when Redis master server 140-1 is not survived and send master-slave swap order to broadcast service framework 120.
The configuration information be stored in Redis buffer control center 110 can comprise the IP of Redis master server 140-1 and port information, Redis from the IP of server 140-2 and port information and the Redis configuration information for each subsystem 130.Can as required, in a suitable form the IP of Redis master server 140-1 and port information, Redis are stored in Redis buffer control center 110 from the IP of server 140-2 and port information and the Redis configuration information that is used for each subsystem 130.Such as, the IP of Redis master server 140-1 and port information and Redis can be stored in Redis configuration information table from the IP of server 140-2 and port information, and the Redis configuration information being used for each subsystem 130 is stored in subsystem Redis link information table.Configuration information can be loaded in internal memory when Redis buffer control center starts.
When Redis buffer control center 110 starts, Redis buffer control center 110 is to broadcast service framework 120 registration service.Broadcast service framework 120 can for having the framework of broadcast capability arbitrarily.In one example, broadcast service framework 120 can be Dubbo service framework.
At Redis buffer control center 110 to after broadcast service framework 120 succeeds in registration, 110 pairs, Redis buffer control center Redis node 140 is monitored.Such as, by sending Ping order every predetermined amount of time to Redis master server 140-1, Redis buffer control center 110 can judge whether Redis master server 140-1 survives.Described predetermined amount of time can be arranged as required, such as, can be 5 seconds, 10 seconds, 12 seconds etc.In addition, each Redis node 140 can be monitored by starting multiple thread in Redis buffer control center 110.
When Redis buffer control center 110 judges that Redis master server 140-1 is not survived, the principal and subordinate's configuration information preserved in internal memory is changed at Redis buffer control center 110.That is, master server is become from server, and master server will be become from server.In addition, when Redis buffer control center 110 judges that Redis master server 140-1 is not survived, Redis buffer control center 110 can judge whether Redis survives from server 140-2, and changes when judging that Redis is survived from server 140-2 the principal and subordinate's configuration information preserved internal memory; And report to the police so that artificial treatment in a suitable form when judging that Redis is not survived from server 140-2.
Then Redis buffer control center 110 sends master-slave swap order to broadcast service framework 120.In addition, before Redis buffer control center 110 sends master-slave swap order to broadcast service framework 120, the Redis principal and subordinate information of such as, preserving in the Redis configuration information being used for each subsystem be stored in subsystem Redis link information table and internal memory can compare by Redis buffer control center 110, and sends master-slave swap order when the Redis configuration information of at least one subsystem is different from the Redis principal and subordinate information of preserving in internal memory to broadcast service framework 120.
Broadcast service framework 120, for after receiving master-slave swap order from Redis buffer control center 110, broadcasts switching command to each subsystem 130 obtaining Redis link information from Redis buffer control center 110.In one example, the principal and subordinate's configuration broadcast after change can be given each subsystem 130 by broadcast service framework 120.
Subsystem 130 for carrying out master-slave swap after the broadcast receiving broadcast service framework 120.And, its Redis link information can be returned to buffer control center, Redis buffer control center 110, Redis and change the Redis configuration information for corresponding subsystem be such as stored in subsystem Redis link information table wherein stored according to the Redis link information that subsystem 130 returns by subsystem 130 after carrying out master-slave swap.
After all subsystems 130 have switched, Redis master-slave swap has completed.Such as, Redis control centre 110 can to compare with the Redis link information stored in internal memory according to the Redis configuration information be such as stored in subsystem Redis link information table and judges whether that all subsystems 130 all complete switching.
In addition, Redis node 140 is used as the cache layer between subsystem and database.
Fig. 2 is the flow chart realizing the method for the automatic master-slave swap of Redis according to an embodiment of the invention.
System below with reference to Fig. 1 is described method.
In step 210, start Redis buffer control center 110, wherein according to the configuration information be stored in Redis buffer control in the heart, principal and subordinate's information is loaded in internal memory.
As described above, the configuration information be stored in Redis buffer control center 110 can comprise the IP of Redis master server 140-1 and port information, Redis from the IP of server 140-2 and port information and the Redis configuration information for each subsystem 130.Can as required, in a suitable form the IP of Redis master server 140-1 and port information, Redis are stored in Redis buffer control center 110 from the IP of server 140-2 and port information and the Redis configuration information that is used for each subsystem 130.Such as, the IP of Redis master server 140-1 and port information and Redis can be stored in Redis configuration information table from the IP of server 140-2 and port information, and the Redis configuration information being used for each subsystem 130 is stored in subsystem Redis link information table.
Such as, can before startup Redis buffer control center 110, create in Redis buffer control center 110 for the IP of record Redis master server and port information number, from the IP of server and port information, and by respective data storage in Redis configuration information table.
In a step 220, by Redis buffer control center 110 to broadcast service framework 120 registration service.As mentioned previously, broadcast service framework 120 can for having the framework of broadcast capability arbitrarily.In one example, broadcast service framework 120 can be Dubbo service framework.
In step 230, after succeeding in registration, 110 pairs, Redis buffer control center Redis node 140 is monitored.Such as, by sending Ping order every predetermined amount of time to Redis master server 140-1, Redis buffer control center 110 can judge whether Redis master server 140-1 survives.Described predetermined amount of time can be arranged as required, such as, can be 5 seconds, 10 seconds, 12 seconds etc.
In step 240, when judging that Redis master server 140-1 is not survived, the principal and subordinate's configuration information preserved in internal memory is changed at Redis buffer control center 110.That is, master server is become from server, and master server will be become from server.In addition, when judging that Redis master server 140-1 is not survived, Redis buffer control center 110 can judge whether Redis survives from server 140-2, and change when judging that Redis is survived from server 140-2 the principal and subordinate's configuration information preserved internal memory, otherwise report to the police so that artificial treatment in a suitable form.
In step 250, Redis buffer control center 110 sends master-slave swap order to broadcast service framework 120.In addition, before Redis buffer control center 110 sends master-slave swap order to broadcast service framework 120, the Redis principal and subordinate information of such as, preserving in the Redis configuration information being used for each subsystem be stored in subsystem Redis link information table and internal memory can compare by Redis buffer control center 110, and sends master-slave swap order when the Redis configuration information of at least one subsystem is different from the Redis principal and subordinate information of preserving in internal memory to broadcast service framework 120.
In step 260, broadcast service framework 120 broadcasts switching command to each subsystem 130 obtaining Redis link information from Redis buffer control center 110.In one example, the principal and subordinate's configuration broadcast after change can be given each system 130 by broadcast service framework 120.
In step 270, subsystem 130 carries out master-slave swap.And, its Redis link information can be returned to buffer control center, Redis buffer control center 110, Redis and change the Redis configuration information for corresponding subsystem be such as stored in subsystem Redis link information table wherein stored according to the Redis link information that subsystem 130 returns by subsystem 130 after carrying out master-slave swap.
After all subsystems 130 have switched, Redis master-slave swap has completed.Such as, Redis control centre 110 can to compare with the Redis link information stored in internal memory according to the Redis configuration information be such as stored in subsystem Redis link information table and judges whether that all subsystems 130 all complete switching.
Although this specification comprises many particular implementation details, but should not be the restriction of the scope to the content that any invention maybe can be advocated by these detailed explanation, and should be interpreted as can specific to the description of the feature of the specific embodiment of specific invention.Some Feature Combination described in the situation of the embodiment be separated in this manual can also be realized in single embodiment.On the contrary, also each character separation described in the situation of single execution mode can be realized or realizes in any suitable sub-portfolio in multiple execution mode.In addition, work in some combination although may describe feature as above, even initial opinion so, in some cases but the one or more features from advocated combination can be left out from combination, and advocated combination can be pointed to the variant of sub-portfolio or sub-portfolio.
Similarly, although depict operation with certain order in the accompanying drawings, this should be interpreted as and need with shown certain order or perform such operation with continuous order or need to perform the result that all illustrated operations just can reach expectation.In some cases, multitask and parallel processing can be favourable.In addition, the separation of various system components in the above-described embodiments should be interpreted as and all need such separation in all embodiments, and should be understood that, usually can by described program assembly and the system integration to together with become single software product or be encapsulated as multiple software product.
Computer program (also referred to as program, software, software application, script or code) can be write by programming language in any form, described programming language comprises compiling or interpretative code, in other words illustrated or procedural language, and it can be disposed in any form, comprise as stand-alone program or other unit of using in a computing environment as module, assembly, subprogram or be suitable for.Computer program there is no need to correspond to the file in file system.Program can be stored in the file of other program of maintenance or data (such as, be stored in the one or more scripts in marking language document) a part, the Single document being exclusively used in question program or multiple coordinative file (such as, storing the file of one or more module, subprogram or partial code) in.
Above-mentioned embodiment, does not form limiting the scope of the invention.It is to be understood that depend on designing requirement and other factors, various amendment, combination, sub-portfolio can be there is and substitute in those skilled in the art.Any amendment done within the spirit and principles in the present invention, equivalent replacement and improvement etc., all should be included within scope.
Claims (16)
1. realize a system for the automatic master-slave swap of Redis, comprising:
Redis buffer control center, sends master-slave swap order for store configuration information, to the registration service of broadcast service framework, monitoring Redis node and principal and subordinate's configuration information of changing when Redis master server is not survived in internal memory to broadcast service framework;
Broadcast service framework, for after from Redis buffer control receive centre to master-slave swap order, to each subsystem broadcast switching command obtaining Redis link information from Redis buffer control center;
Subsystem, for carrying out master-slave swap after the broadcast receiving broadcast service framework; And
Redis node, as the cache layer between subsystem and database.
2. system according to claim 1, wherein, the configuration information be stored in Redis buffer control in the heart comprises the IP of Redis master server and port information, Redis from the IP of server and port information and the Redis configuration information for each subsystem.
3. system according to claim 2, wherein, the IP of Redis master server and port information and Redis are stored in Redis configuration information table from the IP of server and port information, and the Redis configuration information being used for each subsystem is stored in subsystem Redis link information table.
4. system according to claim 1, wherein, broadcast service framework is Dubbo service framework.
5. system according to claim 1, wherein, by sending Ping order every predetermined amount of time to Redis master server, Redis buffer control center judges whether Redis master server survives.Described predetermined amount of time can be arranged as required,
6. system according to claim 1, wherein, when Redis buffer control center judges that Redis master server is not survived, Redis buffer control center judges whether Redis survives from server further, and when judging that Redis changes the principal and subordinate's configuration information preserved internal memory when surviving from server; And when judging that Redis reports to the police in a suitable form when server is not survived.
7. system according to claim 1, wherein, before Redis buffer control center sends master-slave swap order to broadcast service framework, the Redis principal and subordinate information of preserving in the Redis configuration information being used for each subsystem be stored in subsystem Redis link information table and internal memory compares by Redis buffer control center, and sends master-slave swap order when the Redis configuration information of at least one subsystem is different from the Redis principal and subordinate information of preserving in internal memory to broadcast service framework.
8. system according to claim 1, wherein, its Redis link information is returned to Redis buffer control center 110 by subsystem after carrying out master-slave swap.
9., for realizing a method for the automatic master-slave swap of Redis, comprising:
Start Redis buffer control center, wherein according to the configuration information be stored in Redis buffer control in the heart, principal and subordinate's information is loaded in internal memory;
By Redis buffer control center to the registration service of broadcast service framework;
After succeeding in registration, Redis buffer control center is monitored Redis node;
When judging that Redis master server is not survived, the principal and subordinate's configuration information preserved in internal memory is changed at Redis buffer control center;
Redis buffer control center sends master-slave swap order to broadcast service framework;
Broadcast service framework is to each subsystem broadcast switching command obtaining Redis link information from Redis buffer control center; And
Subsystem carries out master-slave swap.
10. method according to claim 9, wherein, the configuration information be stored in Redis buffer control in the heart can comprise the IP of Redis master server and port information, Redis from the IP of server and port information and the Redis configuration information for each subsystem.
11. methods according to claim 10, wherein, the IP of Redis master server and port information and Redis are stored in Redis configuration information table from the IP of server and port information, and are stored in subsystem Redis link information table for the Redis configuration information of each subsystem.
12. methods according to claim 9, wherein, broadcast service framework is Dubbo service framework.
13. methods according to claim 9, wherein, by sending Ping order every predetermined amount of time to Redis master server, Redis buffer control center judges whether Redis master server survives.
14. methods according to claim 9, wherein, when judging that Redis master server is not survived, Redis buffer control center judges whether Redis survives from server further, and when judging that Redis changes the principal and subordinate's configuration information preserved internal memory when surviving from server, otherwise report to the police in a suitable form.
15. methods according to claim 9, wherein, before Redis buffer control center sends master-slave swap order to broadcast service framework, the Redis principal and subordinate information of preserving in the Redis configuration information being used for each subsystem be stored in subsystem Redis link information table and internal memory compares by Redis buffer control center 110, and sends master-slave swap order when the Redis configuration information of at least one subsystem is different from the Redis principal and subordinate information of preserving in internal memory to broadcast service framework.
16. methods according to claim 9, wherein, its Redis link information is returned to Redis buffer control center by subsystem after carrying out master-slave swap.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410679245.1A CN104394142B (en) | 2014-11-24 | 2014-11-24 | For realizing the method and system of the automatic master-slave swaps of Redis |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410679245.1A CN104394142B (en) | 2014-11-24 | 2014-11-24 | For realizing the method and system of the automatic master-slave swaps of Redis |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104394142A true CN104394142A (en) | 2015-03-04 |
| CN104394142B CN104394142B (en) | 2018-02-16 |
Family
ID=52611978
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410679245.1A Active CN104394142B (en) | 2014-11-24 | 2014-11-24 | For realizing the method and system of the automatic master-slave swaps of Redis |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104394142B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106559267A (en) * | 2016-11-25 | 2017-04-05 | 聚好看科技股份有限公司 | The master-slave switching method of Redis, device and redis systems |
| CN107368485A (en) * | 2016-05-12 | 2017-11-21 | 苏宁云商集团股份有限公司 | The management method and Database Systems of a kind of database |
| CN109245908A (en) * | 2017-07-10 | 2019-01-18 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus of principal and subordinate's cluster switching |
| CN110324176A (en) * | 2019-05-29 | 2019-10-11 | 平安科技（深圳）有限公司 | Monitoring method, device and the storage medium of mqtt cluster based on Redis |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110238692A1 (en) * | 2010-03-24 | 2011-09-29 | Kddi Corporation | Apparatus and method for controlling devices in requested resource via network |
| CN102629260A (en) * | 2012-02-29 | 2012-08-08 | 浪潮(北京)电子信息产业有限公司 | Processing method, device and system for database collapse |
| CN102810111A (en) * | 2012-05-07 | 2012-12-05 | 互动在线（北京）科技有限公司 | Implementation method and system for keeping high availability of Oracle database service |
| CN102880475A (en) * | 2012-10-23 | 2013-01-16 | 上海普元信息技术股份有限公司 | Real-time event handling system and method based on cloud computing in computer software system |
| CN103199972A (en) * | 2013-03-25 | 2013-07-10 | 成都瑞科电气有限公司 | Double machine warm backup switching method and warm backup system achieved based on SOA and RS485 bus |
-
2014
- 2014-11-24 CN CN201410679245.1A patent/CN104394142B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110238692A1 (en) * | 2010-03-24 | 2011-09-29 | Kddi Corporation | Apparatus and method for controlling devices in requested resource via network |
| CN102629260A (en) * | 2012-02-29 | 2012-08-08 | 浪潮(北京)电子信息产业有限公司 | Processing method, device and system for database collapse |
| CN102810111A (en) * | 2012-05-07 | 2012-12-05 | 互动在线（北京）科技有限公司 | Implementation method and system for keeping high availability of Oracle database service |
| CN102880475A (en) * | 2012-10-23 | 2013-01-16 | 上海普元信息技术股份有限公司 | Real-time event handling system and method based on cloud computing in computer software system |
| CN103199972A (en) * | 2013-03-25 | 2013-07-10 | 成都瑞科电气有限公司 | Double machine warm backup switching method and warm backup system achieved based on SOA and RS485 bus |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107368485A (en) * | 2016-05-12 | 2017-11-21 | 苏宁云商集团股份有限公司 | The management method and Database Systems of a kind of database |
| CN106559267A (en) * | 2016-11-25 | 2017-04-05 | 聚好看科技股份有限公司 | The master-slave switching method of Redis, device and redis systems |
| CN109245908A (en) * | 2017-07-10 | 2019-01-18 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus of principal and subordinate's cluster switching |
| CN109245908B (en) * | 2017-07-10 | 2022-04-26 | 北京京东尚科信息技术有限公司 | Method and device for switching master cluster and slave cluster |
| CN110324176A (en) * | 2019-05-29 | 2019-10-11 | 平安科技（深圳）有限公司 | Monitoring method, device and the storage medium of mqtt cluster based on Redis |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104394142B (en) | 2018-02-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104735098B (en) | The control method and control system of session information | |
| US20160103845A1 (en) | Enhanced Handling Of Intermediate Data Generated During Distributed, Parallel Processing | |
| CN103345423B (en) | A kind of method and system processing asynchronous task | |
| CN105493474B (en) | System and method for supporting partition level logging for synchronizing data in a distributed data grid | |
| US20130246569A1 (en) | System and method for sharing global transaction identifier (gtrid) in a transactional middleware environment | |
| CN104394142A (en) | Method and device for achieving automatic Redis master-slave conversion | |
| US20150205688A1 (en) | Method for Migrating Memory and Checkpoints in a Fault Tolerant System | |
| CN103209210B (en) | Method for improving erasure code based storage cluster recovery performance | |
| CN104077199B (en) | Based on partition method and the system of the high-availability cluster of shared disk | |
| DE202015009784U1 (en) | Resource management systems | |
| CN102713854A (en) | Method and apparatus for saving and restoring container state | |
| US10305817B1 (en) | Provisioning system and method for a distributed computing environment using a map reduce process | |
| CN105205154A (en) | Data migration method and device | |
| CN102983996A (en) | Dynamic allocation method and system for high-availability cluster resource management | |
| US9356628B2 (en) | Dynamically reconfiguring rebuild agents for erasure code rebuild | |
| CN104486438A (en) | Disaster-tolerant method and disaster-tolerant device of distributed storage system | |
| CN103019626B (en) | Storage system, method and device for controlling cluster metadata | |
| CN104484167A (en) | Task processing method and device | |
| US10067841B2 (en) | Facilitating n-way high availability storage services | |
| CN114138568A (en) | Scheduling method and system for client fault transfer in Redis sentinel mode | |
| US10705971B2 (en) | Mapping logical blocks of a logical storage extent to a replacement storage device | |
| CN102436355A (en) | Data transmission method, device and system | |
| US20160011929A1 (en) | Methods for facilitating high availability storage services in virtualized cloud environments and devices thereof | |
| CN106371919B (en) | It is a kind of based on mapping-reduction computation model data cache method of shuffling | |
| CN105025104A (en) | Cloud desktop scheduling method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |