CN105306566A - Method and system for electing master control node in cloud storage system - Google Patents
Method and system for electing master control node in cloud storage system Download PDFInfo
- Publication number
- CN105306566A CN105306566A CN201510690214.0A CN201510690214A CN105306566A CN 105306566 A CN105306566 A CN 105306566A CN 201510690214 A CN201510690214 A CN 201510690214A CN 105306566 A CN105306566 A CN 105306566A
- Authority
- CN
- China
- Prior art keywords
- controlling vertex
- node
- main controlled
- controlled node
- basic platform
- 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
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/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Abstract
The invention discloses a method for electing a master control node in a cloud storage system. The method comprises the following steps: maintaining data update state identifiers of control nodes on a foundation platform of the cloud storage system; when no master control node exists in the cloud storage system, obtaining the data update state identifiers of other control nodes by the control nodes from the foundation platform, judging whether the data of a current control node are updated according to the obtained data update state identifiers, if so, changing the current control node into the master control node, and notifying the other control nodes that the current control node is elected as the master control node. The invention further discloses a cloud storage system.
Description
Technical field
The application relates to the Internet cloud computing and cloud deposits technical field, particularly relates to the method and system of electing main controlled node in a kind of cloud storage system.
Background technology
Along with computer network, the particularly fast development of Internet, increasing data by datumization, the annual sharp increase of global information memory space.Traditional information system concept there occurs huge change, and these changes show the revolutionary change that the storage of information, transmission, issue and obtain manner occur highlightedly.Meanwhile, mass data intensive applications, as video monitoring, radio, TV and film industries, digital library, medical video image procossing, massive video online editing etc., to the capacity of storage system, performance, fail safe, extensibility and availability propose requirements at the higher level.Traditional direct memory module can not satisfy the demands gradually, and the complexity of the demand that information stores and application proposes new memory module.
Cloud storage is in the conceptive extension of cloud computing and the new concept of development out one, refer to by functions such as cluster application, grid or distributed file systems, various dissimilar memory device a large amount of in network is gathered collaborative work by application software, a system of data storage and Operational Visit function is externally provided jointly.Compared with traditional memory device, cloud storage system is not only a hardware, but the complication system of multiple part composition such as the network equipment, memory device, server, application software, public access interface, Access Network and a client-side program.Each several part take memory device as core, externally provides data to store and Operational Visit service by application software.
Cloud storage system is a kind of typical distributed system, wherein there is multiple Controlling vertex.Therefore, need to elect a main controlled node between multiple Controlling vertex, other Controlling vertex are as backup node.The main controlled node made new advances can be elected fast after system start-up or after the inefficacy of former main controlled node.To the solution of this neither one maturation in prior art.
Summary of the invention
This application provides the method and system of electing main controlled node in a kind of cloud storage system, can in cloud storage system without main controlled node time, elect the main controlled node made new advances fast.
This application provides a kind of method of electing main controlled node in cloud storage system, comprising:
A, safeguard the Data Update status indicator of each Controlling vertex at the basic platform of cloud storage system;
B, when in cloud storage system without main controlled node time, each Controlling vertex obtains the Data Update status indicator of other Controlling vertex from basic platform, whether the data judging this Controlling vertex according to obtained Data Update status indicator are up-to-date, if, this Controlling vertex is changed to main controlled node, and notifies that other this Controlling vertex of Controlling vertex is elected as main controlled node.
Alternatively, steps A comprises:
Respective handling is carried out in the request that main controlled node receives client and back end, according to standby host list by data syn-chronization to each standby host node, the Data Update status indicator of each main controlled node of the corresponding renewal of basic platform or standby host node.
Alternatively, steps A comprises: Controlling vertex registers the node descriptor of this Controlling vertex on basic platform when starting, described node descriptor comprises Data Update status indicator.
Alternatively, described node descriptor comprises further: node identification and master control/standby host node identification.
Alternatively, the method comprises further:
Main controlled node obtains the event of reaching the standard grade of Controlling vertex at basic platform registered callbacks interface, and is added in standby host list by the Controlling vertex of newly reaching the standard grade.
Alternatively, step B comprises:
B1, Controlling vertex obtain the node descriptor of other Controlling vertex by basic platform registered callbacks interface;
B2, Controlling vertex judge whether to there is main controlled node according to obtained node descriptor, if exist, process ends, otherwise, perform step B3;
According to node descriptor, B3, Controlling vertex judge whether the Data Update status indicator of this Controlling vertex is up-to-date, if so, perform step B4, otherwise process ends;
B4, Controlling vertex send request to basic platform, and the standby host node identification of this Controlling vertex is revised as main controlled node mark, and sends notice to other Controlling vertex in cloud storage system, this Controlling vertex is elected as main controlled node.
Alternatively, before step B1, comprise further:
Controlling vertex detects main controlled node failure event by basic platform registered callbacks interface, then trigger performing described B1.
Alternatively, comprise further after step B4: other Controlling vertex are added standby host list by described main controlled node.
The embodiment of the present application additionally provides a kind of cloud storage system, and described cloud storage system comprises basic platform and multiple Controlling vertex,
Described basic platform is for safeguarding the Data Update status indicator of each Controlling vertex;
Described Controlling vertex comprises:
Whether sensing module, for existing main controlled node in perception cloud storage system;
Acquisition module, during for perceiving without main controlled node at sensing module, obtains the Data Update status indicator of other Controlling vertex from basic platform;
Judge module, for judging according to obtained Data Update status indicator whether the data of this Controlling vertex are up-to-date;
Election module, for when described judge module judged result is for being, changes to main controlled node by this Controlling vertex, and notifies that other this Controlling vertex of Controlling vertex is elected as main controlled node.
Alternatively, described Controlling vertex comprises further:
Data simultaneous module, for when this Controlling vertex is main controlled node, after respective handling is carried out in the request receiving client and back end when this Controlling vertex, according to standby host list by data syn-chronization to each standby host node, and send data syn-chronization notification message to basic platform; When this Controlling vertex is standby host node, receives the data from main controlled node and upgrade the data of this Controlling vertex, and sending data syn-chronization notification message to basic platform;
Described basic platform is further used for, according to the data syn-chronization notification message from each Controlling vertex, upgrading the Data Update status indicator of corresponding Controlling vertex.
As can be seen from the above technical solutions, the Data Update status indicator of each Controlling vertex is safeguarded at the basic platform of cloud storage system; When in cloud storage system without main controlled node time, each Controlling vertex obtains the Data Update status indicator of other Controlling vertex from basic platform, whether the data judging this Controlling vertex according to obtained Data Update status indicator are up-to-date, if so, notify that other this Controlling vertex of Controlling vertex is elected as main controlled node.When the application's scheme can lose efficacy without main controlled node or former main controlled node when cloud storage system starts, select main controlled node rapidly, ensure that cloud storage system normally runs.
Accompanying drawing explanation
When having main controlled node in the cloud storage system that Fig. 1 provides for the embodiment of the present application, schematic flow sheet when new Controlling vertex starts;
Fig. 2 for the embodiment of the present application provide without main controlled node when, the handling process schematic diagram of wherein any one Controlling vertex when cloud storage system starts;
After main controlled node lost efficacy in the cloud storage system that Fig. 3 provides for the embodiment of the present application, elected the handling process schematic diagram of new main controlled node.
Embodiment
The application provides a kind of method of electing main controlled node in cloud storage system, can elect main controlled node quickly and efficiently from multiple Controlling vertex.The design of its basic fundamental comprises: the Data Update status indicator safeguarding each Controlling vertex at the basic platform of cloud storage system; When in cloud storage system without main controlled node time, each Controlling vertex obtains the Data Update status indicator of other Controlling vertex from basic platform, whether the data judging this Controlling vertex according to obtained Data Update status indicator are up-to-date, if so, notify that other this Controlling vertex of Controlling vertex is elected as main controlled node.Node receives the request from client and back end after being elected to main controlled node, and by data syn-chronization to standby host.
For making the know-why of technical scheme, feature and technique effect clearly, below in conjunction with specific embodiment, technical scheme is described in detail.
When Fig. 1 shows in the cloud storage system that the embodiment of the present application provides and has main controlled node, handling process when new Controlling vertex starts, comprises the steps:
Step 101: Controlling vertex, when starting, basic platform is registered the node descriptor of this Controlling vertex.
Described node descriptor at least needs to comprise node identification, master control/standby host node identification, Data Update status indicator.
Wherein, node identification is for distinguishing each Controlling vertex, and the node identification of each Controlling vertex is unique in cloud storage system.Master control/standby host node identification is used for showing that this Controlling vertex is main controlled node or standby host node, and Controlling vertex is defaulted as standby host node when starting.Data Update status indicator is for showing the data newness degree of this Controlling vertex, and the concrete form of Data Update status indicator can be the time of the last Data Update of this main controlled node.
In addition, node descriptor also comprises the necessary information such as IP address, node status information (internal memory, CPU).
Step 102: main controlled node obtains the event of reaching the standard grade of Controlling vertex at basic platform registered callbacks interface, and is added in standby host list by this Controlling vertex.
Meanwhile, the new Controlling vertex started also can obtain the node descriptor of other Controlling vertex by basic platform registered callbacks interface.And judge whether to there is main controlled node according to described node descriptor.
Step 103: respective handling is carried out in the request that main controlled node receives client and back end, according to standby host list by data syn-chronization to each standby host node, the Data Update status indicator of each main controlled node of the corresponding renewal of basic platform or standby host node.
Fig. 2 show that the embodiment of the present application provides without main controlled node when, when cloud storage system starts, the handling process of wherein any one Controlling vertex, comprises the steps:
Step 201: Controlling vertex registers the node descriptor of this Controlling vertex on basic platform when starting.
Step 202: Controlling vertex obtains the node descriptor of other Controlling vertex by basic platform registered callbacks interface.
Step 203: Controlling vertex judges whether to there is main controlled node according to obtained node descriptor, if exist, process ends, otherwise, perform step 204.
Step 204: according to node descriptor, Controlling vertex judges whether the Data Update status indicator of this Controlling vertex is up-to-date, if so, performs step 205, otherwise process ends.
Step 205: Controlling vertex sends request to basic platform, the standby host node identification of this Controlling vertex is revised as main controlled node mark, and sends notice to other Controlling vertex in cloud storage system, this Controlling vertex is elected as main controlled node.
Step 206: other Controlling vertex is added standby host list by main controlled node.
Step 207: respective handling is carried out in the request that main controlled node receives client and back end, according to standby host list by data syn-chronization to each standby host node, the Data Update status indicator of each main controlled node of the corresponding renewal of basic platform or standby host node.
Except needing to elect main controlled node when cloud storage system starts, breaking down when main controlled node or because after certain reason off-line, needing to elect the main controlled node made new advances.
Fig. 3 shows after in the cloud storage system that the embodiment of the present application provides, main controlled node lost efficacy, and elects the handling process of new main controlled node, comprises the steps:
Step 301: standby host node detects main controlled node failure event by basic platform registered callbacks interface.
Step 302: standby host node obtains the node descriptor of other standby host node by basic platform registered callbacks interface.
Step 303: according to node descriptor, standby host node judges whether the Data Update status indicator of this standby host node is up-to-date, if so, performs step 304, otherwise process ends.
Step 304: standby host node sends request to basic platform, the standby host node identification of this standby host node is revised as main controlled node mark, and sends notice to other standby host node in cloud storage system, this Controlling vertex is elected as main controlled node.
Step 305: other standby host node is added standby host list by new elected main controlled node.
Step 306: respective handling is carried out in the request that described main controlled node receives client and back end, according to standby host list by data syn-chronization to each standby host node, the Data Update status indicator of each main controlled node of the corresponding renewal of basic platform or standby host node.
The embodiment of the present application additionally provides a kind of cloud storage system, and described cloud storage system comprises basic platform, back end (haveing nothing to do with technical scheme) and multiple Controlling vertex,
Described basic platform is for safeguarding the Data Update status indicator of each Controlling vertex;
Described Controlling vertex comprises:
Whether sensing module, for existing main controlled node in perception cloud storage system;
Acquisition module, during for perceiving without main controlled node at sensing module, obtains the Data Update status indicator of other Controlling vertex from basic platform;
Judge module, for judging according to obtained Data Update status indicator whether the data of this Controlling vertex are up-to-date;
Election module, for when described judge module judged result is for being, changes to main controlled node by this Controlling vertex, and notifies that other this Controlling vertex of Controlling vertex is elected as main controlled node.
Alternatively, described Controlling vertex comprises further:
Data simultaneous module, for when this Controlling vertex is main controlled node, after respective handling is carried out in the request receiving client and back end when this Controlling vertex, according to standby host list by data syn-chronization to each standby host node, and send data syn-chronization notification message to basic platform; When this Controlling vertex is standby host node, receives the data from main controlled node and upgrade the data of this Controlling vertex, and sending data syn-chronization notification message to basic platform;
Described basic platform is further used for, according to the data syn-chronization notification message from each Controlling vertex, upgrading the Data Update status indicator of corresponding Controlling vertex.
Alternatively, Controlling vertex comprises further: Registering modules, and for registering the node descriptor of this Controlling vertex on basic platform when starting, described node descriptor comprises Data Update status indicator.
Preferably, described node descriptor comprises further: node identification and master control/standby host node identification.
Alternatively, described acquisition module is further used for: when this Controlling vertex is main controlled node, obtains the event of reaching the standard grade of Controlling vertex, and added in standby host list by the Controlling vertex of newly reaching the standard grade at basic platform registered callbacks interface.
Alternatively, described acquisition module is used for the node descriptor being obtained other Controlling vertex by basic platform registered callbacks interface;
Described sensing module is used for judging whether to there is main controlled node according to obtained node descriptor;
According to node descriptor, described judge module judges whether the Data Update status indicator of this Controlling vertex is up-to-date;
Described election module is used for sending request to basic platform, and the standby host node identification of this Controlling vertex is revised as main controlled node mark, and sends notice to other Controlling vertex in cloud storage system, this Controlling vertex is elected as main controlled node.
Alternatively, described acquisition module detects main controlled node failure event by basic platform registered callbacks interface, then obtain the node descriptor of other Controlling vertex further.
Alternatively, Controlling vertex comprises further: standby host administration module, for when this Controlling vertex is main controlled node, other Controlling vertex is added standby host list.
The application's scheme can realize following technique effect: (just started or the inefficacy of former main controlled node) when not having main controlled node in cloud storage system, elect unique main controlled node in a short period of time, thus ensure the continuation of application system, substantially increase availability and the low delay of system; Whole switching is to application system transparent, and application system does not need to do extra process.Data syn-chronization between Controlling vertex ensures validity and the integrality of data.
Be to be understood that, although this specification describes according to each execution mode, but not each execution mode only comprises an independently technical scheme, this narrating mode of specification is only for clarity sake, those skilled in the art should by specification integrally, technical scheme in each execution mode also through appropriately combined, can form other execution modes that it will be appreciated by those skilled in the art that.
The foregoing is only the preferred embodiment of the application; not in order to limit the protection range of the application; within all spirit in technical scheme and principle, any amendment made, equivalent replacements, improvement etc., all should be included within scope that the application protects.
Claims (10)
1. elect a method for main controlled node in cloud storage system, it is characterized in that, comprising:
A, safeguard the Data Update status indicator of each Controlling vertex at the basic platform of cloud storage system;
B, when in cloud storage system without main controlled node time, each Controlling vertex obtains the Data Update status indicator of other Controlling vertex from basic platform, whether the data judging this Controlling vertex according to obtained Data Update status indicator are up-to-date, if, this Controlling vertex is changed to main controlled node, and notifies that other this Controlling vertex of Controlling vertex is elected as main controlled node.
2. method according to claim 1, is characterized in that, steps A comprises:
Respective handling is carried out in the request that main controlled node receives client and back end, according to standby host list by data syn-chronization to each standby host node, the Data Update status indicator of each main controlled node of the corresponding renewal of basic platform or standby host node.
3. method according to claim 2, is characterized in that, steps A comprises: Controlling vertex registers the node descriptor of this Controlling vertex on basic platform when starting, described node descriptor comprises Data Update status indicator.
4. method according to claim 3, is characterized in that, described node descriptor comprises further: node identification and master control/standby host node identification.
5. method according to claim 3, is characterized in that, the method comprises further:
Main controlled node obtains the event of reaching the standard grade of Controlling vertex at basic platform registered callbacks interface, and is added in standby host list by the Controlling vertex of newly reaching the standard grade.
6. method according to claim 4, is characterized in that, step B comprises:
B1, Controlling vertex obtain the node descriptor of other Controlling vertex by basic platform registered callbacks interface;
B2, Controlling vertex judge whether to there is main controlled node according to obtained node descriptor, if exist, process ends, otherwise, perform step B3;
According to node descriptor, B3, Controlling vertex judge whether the Data Update status indicator of this Controlling vertex is up-to-date, if so, perform step B4, otherwise process ends;
B4, Controlling vertex send request to basic platform, and the standby host node identification of this Controlling vertex is revised as main controlled node mark, and sends notice to other Controlling vertex in cloud storage system, this Controlling vertex is elected as main controlled node.
7. method according to claim 4, is characterized in that, before step B1, comprises further:
Controlling vertex detects main controlled node failure event by basic platform registered callbacks interface, then trigger performing described B1.
8. method according to claim 6, is characterized in that, comprises further after step B4: other Controlling vertex are added standby host list by described main controlled node.
9. a cloud storage system, described cloud storage system comprises basic platform and multiple Controlling vertex, it is characterized in that,
Described basic platform is for safeguarding the Data Update status indicator of each Controlling vertex;
Described Controlling vertex comprises:
Whether sensing module, for existing main controlled node in perception cloud storage system;
Acquisition module, during for perceiving without main controlled node at sensing module, obtains the Data Update status indicator of other Controlling vertex from basic platform;
Judge module, for judging according to obtained Data Update status indicator whether the data of this Controlling vertex are up-to-date;
Election module, for when described judge module judged result is for being, changes to main controlled node by this Controlling vertex, and notifies that other this Controlling vertex of Controlling vertex is elected as main controlled node.
10. cloud storage system according to claim 9, is characterized in that, described Controlling vertex comprises further:
Data simultaneous module, for when this Controlling vertex is main controlled node, after respective handling is carried out in the request receiving client and back end when this Controlling vertex, according to standby host list by data syn-chronization to each standby host node, and send data syn-chronization notification message to basic platform; When this Controlling vertex is standby host node, receives the data from main controlled node and upgrade the data of this Controlling vertex, and sending data syn-chronization notification message to basic platform;
Described basic platform is further used for, according to the data syn-chronization notification message from each Controlling vertex, upgrading the Data Update status indicator of corresponding Controlling vertex.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510690214.0A CN105306566A (en) | 2015-10-22 | 2015-10-22 | Method and system for electing master control node in cloud storage system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510690214.0A CN105306566A (en) | 2015-10-22 | 2015-10-22 | Method and system for electing master control node in cloud storage system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105306566A true CN105306566A (en) | 2016-02-03 |
Family
ID=55203309
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510690214.0A Pending CN105306566A (en) | 2015-10-22 | 2015-10-22 | Method and system for electing master control node in cloud storage system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105306566A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106657117A (en) * | 2016-12-31 | 2017-05-10 | 广州佳都信息技术研发有限公司 | Method and device for managing subway integrated monitoring authority |
| CN110290159A (en) * | 2018-03-19 | 2019-09-27 | 中移(苏州)软件技术有限公司 | A kind of method and apparatus of management and running |
| CN111093220A (en) * | 2019-11-14 | 2020-05-01 | 中国人民解放军军事科学院国防科技创新研究院 | Autonomous unmanned cluster dynamic management method and management platform |
| CN111400112A (en) * | 2020-03-18 | 2020-07-10 | 深圳市腾讯计算机系统有限公司 | Writing method and device of storage system of distributed cluster and readable storage medium |
| WO2021078294A1 (en) * | 2019-10-25 | 2021-04-29 | 北京金山云网络技术有限公司 | Service coordination method and apparatus for distributed storage system, and electronic device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1645862A (en) * | 2005-02-01 | 2005-07-27 | 北京北方烽火科技有限公司 | Self adaptable electing algorithm for main controlled node in group |
| CN101984632A (en) * | 2010-11-15 | 2011-03-09 | 中兴通讯股份有限公司 | Load distributing method, device and server in distributed cache system |
| US20130278412A1 (en) * | 2012-04-20 | 2013-10-24 | Detcon, Inc. | Networked system and methods for detection of hazardous conditions |
| CN103580915A (en) * | 2013-09-26 | 2014-02-12 | 东软集团股份有限公司 | Method and device for determining main control node of trunking system |
| CN104468163A (en) * | 2013-09-18 | 2015-03-25 | 腾讯科技（北京）有限公司 | Method and device for disaster tolerant network construction, and disaster tolerant network |
| CN104753994A (en) * | 2013-12-27 | 2015-07-01 | 杭州海康威视系统技术有限公司 | Method and device for data synchronization based on cluster server system |
-
2015
- 2015-10-22 CN CN201510690214.0A patent/CN105306566A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1645862A (en) * | 2005-02-01 | 2005-07-27 | 北京北方烽火科技有限公司 | Self adaptable electing algorithm for main controlled node in group |
| CN101984632A (en) * | 2010-11-15 | 2011-03-09 | 中兴通讯股份有限公司 | Load distributing method, device and server in distributed cache system |
| US20130278412A1 (en) * | 2012-04-20 | 2013-10-24 | Detcon, Inc. | Networked system and methods for detection of hazardous conditions |
| CN104468163A (en) * | 2013-09-18 | 2015-03-25 | 腾讯科技（北京）有限公司 | Method and device for disaster tolerant network construction, and disaster tolerant network |
| CN103580915A (en) * | 2013-09-26 | 2014-02-12 | 东软集团股份有限公司 | Method and device for determining main control node of trunking system |
| CN104753994A (en) * | 2013-12-27 | 2015-07-01 | 杭州海康威视系统技术有限公司 | Method and device for data synchronization based on cluster server system |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106657117A (en) * | 2016-12-31 | 2017-05-10 | 广州佳都信息技术研发有限公司 | Method and device for managing subway integrated monitoring authority |
| CN110290159A (en) * | 2018-03-19 | 2019-09-27 | 中移(苏州)软件技术有限公司 | A kind of method and apparatus of management and running |
| CN110290159B (en) * | 2018-03-19 | 2022-06-28 | 中移(苏州)软件技术有限公司 | Method and equipment for scheduling management |
| WO2021078294A1 (en) * | 2019-10-25 | 2021-04-29 | 北京金山云网络技术有限公司 | Service coordination method and apparatus for distributed storage system, and electronic device |
| CN111093220A (en) * | 2019-11-14 | 2020-05-01 | 中国人民解放军军事科学院国防科技创新研究院 | Autonomous unmanned cluster dynamic management method and management platform |
| CN111400112A (en) * | 2020-03-18 | 2020-07-10 | 深圳市腾讯计算机系统有限公司 | Writing method and device of storage system of distributed cluster and readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106331098B (en) | Server cluster system | |
| CN105306566A (en) | Method and system for electing master control node in cloud storage system | |
| US9367261B2 (en) | Computer system, data management method and data management program | |
| CN110830283B (en) | Fault detection method, device, equipment and system | |
| US9952947B2 (en) | Method and system for processing fault of lock server in distributed system | |
| CN103581276A (en) | Cluster management device and system, service client side and corresponding method | |
| CN104468150A (en) | Method for realizing fault migration through virtual host and virtual host service device | |
| CN110825698B (en) | Metadata management method and related device | |
| CN105069152B (en) | data processing method and device | |
| CN111600794B (en) | Server switching method, terminal, server and storage medium | |
| CN103188098B (en) | A kind of disaster tolerance switching method, system and device | |
| CN103731290A (en) | Server failure switching method | |
| CN111294391A (en) | Configuration synchronization method, device, equipment and readable storage medium | |
| CN112732702B (en) | Database engine file processing method and device | |
| CN109257396B (en) | Distributed lock scheduling method and device | |
| CN113190620A (en) | Method, device, equipment and storage medium for synchronizing data between Redis clusters | |
| CN105323271A (en) | Cloud computing system, and processing method and apparatus thereof | |
| CN107087021B (en) | Master-slave server determination method and device | |
| CN111797352A (en) | Method and device for sealing account and sealing system | |
| CN111488247A (en) | High-availability method and device for managing and controlling multiple fault tolerance of nodes | |
| CN105338058A (en) | Application updating method and device | |
| JP6085266B2 (en) | Server resource management device | |
| CN115145782A (en) | Server switching method, mooseFS system and storage medium | |
| CN112612652A (en) | Distributed storage system abnormal node restarting method and system | |
| CN111444062A (en) | Method and device for managing master node and slave node of cloud database |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160203 |