技术领域technical field
本发明涉及一种高可用性和强一致性的数据库集群系统的节点管理方法。The invention relates to a node management method of a database cluster system with high availability and strong consistency.
背景技术Background technique
RAC（Real Application Cluster，真正应用集群）是Oracle的并行集群，位于不同节点的Oracle实例同时访问同一个Oracle数据库，节点之间通过私有网络进行通信，所有的控制文件、联机日志和数据文件存放在共享的存储设备上，能够被集群中的所有节点读写；这种集群方法主要有以下两个局限：RAC (Real Application Cluster, real application cluster) is a parallel cluster of Oracle. Oracle instances located on different nodes access the same Oracle database at the same time. Nodes communicate through a private network. All control files, online logs and data files are stored in On the shared storage device, it can be read and written by all nodes in the cluster; this cluster method mainly has the following two limitations:
1）实例间的数据同步1) Data synchronization between instances
RAC提供多个实例，RAC会将写入的数据先缓存在实例的内存，再同步到共享的存储中，有时在数据的同步上花费的时间较大。例如：当多个实例同时写入数据后立即查询新写入的数据时，写在各个实例中的数据还未同步到共享的存储中，为了保证读取的数据的正确性，必须通过复杂的同步过程维护各个实例中数据的一致性。当数据量小时，所需时间可以接受；但当数据量大时，维持一致性所花费的时间可能无法接受。RAC provides multiple instances. RAC will first cache the written data in the memory of the instance, and then synchronize it to the shared storage. Sometimes it takes a long time to synchronize the data. For example: when multiple instances write data at the same time and immediately query the newly written data, the data written in each instance has not been synchronized to the shared storage. In order to ensure the correctness of the read data, complex The synchronization process maintains the consistency of data in each instance. When the amount of data is small, the time required is acceptable; but when the amount of data is large, the time it takes to maintain consistency may not be acceptable.
另一方面，当实例故障时，若该实例中缓存的数据还未同步到共享存储中，则这部分数据将丢失，无法恢复。On the other hand, when an instance fails, if the data cached in the instance has not been synchronized to the shared storage, this part of the data will be lost and cannot be recovered.
2）数据库单点故障2) Database single point of failure
RAC中数据文件只有一份，当共享存储出现故障时，将无法提供服务。There is only one data file in the RAC. When the shared storage fails, the service cannot be provided.
Data Guard是Oracle推出的一种数据库方案，在主节点与备用节点间通过日志同步来保证数据的同步，可以实现数据库快速切换与灾难性恢复。但是，这种模式下的主库和备库的切换必须人工操作，带来了很大的不便。Data Guard is a database solution introduced by Oracle. It uses log synchronization between the primary node and the standby node to ensure data synchronization, enabling rapid database switching and disaster recovery. However, the switching between the main library and the standby library in this mode must be manually operated, which brings great inconvenience.
发明内容Contents of the invention
本发明的目的在于克服现有技术的不足，提供一种高可用性和强一致性的数据库集群系统及其节点管理方法，能够进行节点管理,在节点增加、宕机节点处理和宕机节点重新接入的过程中，保证数据库集群系统的运行和节点数据的同步一致，进而节点故障不会造成数据损失，节点故障处理方便有效。The purpose of the present invention is to overcome the deficiencies of the prior art, to provide a highly available and strongly consistent database cluster system and its node management method, capable of node management, node increase, downtime node processing and downtime node reconnection During the entry process, the operation of the database cluster system is guaranteed to be consistent with the synchronization of node data, so that node failure will not cause data loss, and node failure handling is convenient and effective.
本发明的目的是通过以下技术方案来实现的：一种高可用性和强一致性的数据库集群系统，包括节点规则设置单元、初始配置单元和多个节点，所述多个节点之间通过私有网络连接；The purpose of the present invention is achieved through the following technical solutions: a database cluster system with high availability and strong consistency, including a node rule setting unit, an initial configuration unit and a plurality of nodes, between the plurality of nodes through a private network connect;
每个所述的节点均能够提供完整的存储、访问和节点管理服务，且存储的数据同步一致；Each of the described nodes can provide complete storage, access and node management services, and the stored data is synchronized and consistent;
所述初始配置单元用于提供配置接口，进而通过手动配置的方式从所述多个节点中确定主节点和副节点；The initial configuration unit is used to provide a configuration interface, and then determine the primary node and the secondary node from the plurality of nodes through manual configuration;
所述节点规则设置单元用于设定节点管理规则，保证节点管理过程中数据库集群系统的运行和各个节点数据的同步一致。The node rule setting unit is used to set node management rules to ensure that the operation of the database cluster system and the synchronization of each node data are consistent during the node management process.
所述的节点规则设置单元包括：The node rule setting unit includes:
节点增加规则设置模块，用于设置节点增加的规则，保证新增节点与数据库集群系统中其他节点的数据同步一致；The node increase rule setting module is used to set the rules for node increase to ensure that the data synchronization between the newly added node and other nodes in the database cluster system is consistent;
宕机规则设置模块，用于设置节点宕机时对节点进行处理的规则，保证节点宕机不会影响整个数据库集群系统的工作；The downtime rule setting module is used to set the rules for processing nodes when the node is down, so as to ensure that the downtime of the node will not affect the work of the entire database cluster system;
宕机重连规则设置模块，用于设置节点宕机重连的规则，保证宕机重连的节点与数据库集群系统其他节点的数据同步一致。The downtime reconnection rule setting module is used to set the rules for node downtime reconnection to ensure that the data synchronization between the downtime reconnected node and other nodes of the database cluster system is consistent.
所述的多个节点还连接统一的地址访问集群，为用户组访问服务接口。The plurality of nodes are also connected to a unified address to access the cluster, and access the service interface for the user group.
每个所述的节点均包括存储模块、数据服务模块和节点管理模块；所述存储模块用于对节点数据进行存储；所述数据服务模块用于为用户提供服务；所述节点管理模块用于根据节点管理规则，保证节点管理过程中各个节点数据的同步一致。Each of the nodes includes a storage module, a data service module and a node management module; the storage module is used to store node data; the data service module is used to provide services for users; the node management module is used to According to the node management rules, the data synchronization and consistency of each node during the node management process are guaranteed.
所述的一种高可用性和强一致性的数据库集群系统的节点管理方法，包括以下步骤：The described node management method of a database cluster system with high availability and strong consistency comprises the following steps:
S1.通过手动配置的方式从所述多个节点选择一个节点作为主节点，其余所有节点均为副节点；S1. Select a node from the multiple nodes as the primary node through manual configuration, and all other nodes are secondary nodes;
S2.根据设定的节点管理规则对数据库集群中的节点进行管理，包括节点增加、宕机节点处理和宕机节点重新接入。S2. Manage the nodes in the database cluster according to the set node management rules, including node addition, downtime node processing and downtime node reconnection.
所述的节点增加包括以下子步骤：The described node increase comprises the following substeps:
S201.在数据库集群系统中加入新的节点；S201. Add a new node to the database cluster system;
S202.以新增节点加入的时间作为分界线；S202. Use the time when the new node joins as the dividing line;
S203.新增节点从主节点中同步该时间分界线之前的数据；S203. The newly added node synchronizes the data before the time boundary from the master node;
S204.根据主节点保留的日志文件，依次对该时间分界线之后新增节点的数据进行恢复；S204. According to the log file retained by the master node, the data of the newly added node after the time boundary is sequentially restored;
S205.当新增节点与主节点数据一致时，新增节点加入成功，对用户可见，且能够为用户提供服务。S205. When the data of the newly added node is consistent with that of the master node, the newly added node is added successfully, visible to the user, and able to provide services for the user.
所述的宕机节点处理包括以下子步骤：Described downtime node processing comprises the following substeps:
S211.判断宕机节点的类型：S211. Determine the type of downtime node:
（1）如果宕机节点为主节点，进入步骤S212；(1) If the downtime node is the master node, go to step S212;
（2）如果宕机节点为副节点，主节点断开宕机节点连接，并其踢出集群，其余节点照常工作；(2) If the downtime node is a secondary node, the master node disconnects the downtime node and kicks it out of the cluster, and the rest of the nodes work as usual;
S212.根据各个副节点的工作情况,从副节点中选取新的主节点，并将宕机节点踢出集群。S212. Select a new master node from the slave nodes according to the working conditions of each slave node, and kick the down node out of the cluster.
所述副节点的工作情况包括但不限于副节点的活跃度、负载量和连接数。The working condition of the secondary node includes but not limited to activity, load and connection number of the secondary node.
所述的宕机节点重新接入包括以下子步骤：The re-access of the downtime node includes the following sub-steps:
S221.宕机节点重新接入时，提取宕机节点宕掉时的时间戳；S221. When the downtime node reconnects, extract the time stamp when the downtime node is down;
S222.以宕掉时的时间戳为基准，根据主节点的日志文件，恢复重新接入的节点在时间戳之后的所有数据；S222. Taking the time stamp at the time of failure as a benchmark, according to the log file of the master node, restore all the data of the reconnected node after the time stamp;
S222.重新接入的节点与主节点数据一致时，接入成功，对用户可见，且能够为用户提供服务。S222. When the data of the reconnected node is consistent with that of the master node, the access is successful, visible to the user, and able to provide services for the user.
本发明的有益效果是：在数据库集群系统中各个节点数据同步一致,每个节点均能够提供完整存储访问服务的基础上,还能够通过节点管理，在节点增加、宕机节点处理和宕机节点重新接入的过程中，进一步保证数据库集群系统的运行和节点数据的同步一致，进而节点故障不会造成数据损失，节点故障处理方便有效；在节点增加和宕机节点重新接入的过程中，数据与主节点一致后，节点才能对用户可见和提供服务，更加方便于数据库集群系统中的节点管理。The beneficial effects of the present invention are: in the database cluster system, the data of each node is synchronized and consistent, and each node can provide a complete storage access service, and can also manage nodes through node increase, downtime node processing and downtime node In the process of re-connection, further ensure the operation of the database cluster system and the synchronization of node data, so that node failure will not cause data loss, and node failure processing is convenient and effective; during the process of node addition and downtime node re-connection, After the data is consistent with the master node, the node can be visible to users and provide services, which is more convenient for node management in the database cluster system.
附图说明Description of drawings
图1为本发明的数据库集群系统原理框图；Fig. 1 is a functional block diagram of the database cluster system of the present invention;
图2为本发明数据库集群系统的节点管理方法流程图。Fig. 2 is a flow chart of the node management method of the database cluster system of the present invention.
具体实施方式detailed description
下面结合附图进一步详细描述本发明的技术方案，但本发明的保护范围不局限于以下所述。The technical solution of the present invention will be further described in detail below in conjunction with the accompanying drawings, but the protection scope of the present invention is not limited to the following description.
如图1所示，一种高可用性和强一致性的数据库集群系统，包括节点规则设置单元、初始配置单元和多个节点，所述多个节点之间通过私有网络连接；As shown in Figure 1, a database cluster system with high availability and strong consistency includes a node rule setting unit, an initial configuration unit and a plurality of nodes, and the plurality of nodes are connected through a private network;
每个所述的节点均能够提供完整的存储、访问和节点管理服务，且存储的数据同步一致；Each of the described nodes can provide complete storage, access and node management services, and the stored data is synchronized and consistent;
所述初始配置单元用于提供配置接口，进而通过手动配置的方式从所述多个节点中确定主节点和副节点；The initial configuration unit is used to provide a configuration interface, and then determine the primary node and the secondary node from the plurality of nodes through manual configuration;
所述节点规则设置单元用于设定节点管理规则，保证节点管理过程中数据库集群系统的运行和各个节点数据的同步一致。The node rule setting unit is used to set node management rules to ensure that the operation of the database cluster system and the synchronization of each node data are consistent during the node management process.
所述的节点规则设置单元包括：The node rule setting unit includes:
节点增加规则设置模块，用于设置节点增加的规则，保证新增节点与数据库集群系统中其他节点的数据同步一致；The node increase rule setting module is used to set the rules for node increase to ensure that the data synchronization between the newly added node and other nodes in the database cluster system is consistent;
在本申请中,所述节点增加的规则包括: 以新增节点加入的时间作为分界线；从主节点中同步该时间分界线之前的数据；并根据主节点保留的日志文件，依次对该时间分界线之后新增节点的数据进行恢复；当新增节点与主节点数据一致时，新增节点加入成功，才对用户可见。In this application, the rules for adding nodes include: taking the time when the new node joins as the dividing line; synchronizing the data before the time dividing line from the master node; The data of the newly added node after the dividing line is restored; when the data of the newly added node is consistent with the data of the main node, the newly added node is successfully added and is visible to the user.
宕机规则设置模块，用于设置节点宕机时对节点进行处理的规则，保证节点宕机不会影响整个数据库集群系统的工作；The downtime rule setting module is used to set the rules for processing nodes when the node is down, so as to ensure that the downtime of the node will not affect the work of the entire database cluster system;
在本申请中，节点宕机时对节点进行处理的规则包括：如果宕机节点为主节点，根据各个副节点的工作情况,从副节点中选取新的主节点，并将宕机节点踢出集群；如果宕机节点时副节点，主节点断开宕机节点连接，并其踢出集群，其余节点照常工作；In this application, the rules for processing nodes when a node is down include: if the downtime node is the master node, according to the working conditions of each slave node, select a new master node from the slave nodes, and kick out the downtime node Cluster; if the downtime node is a secondary node, the master node disconnects the downtime node and kicks it out of the cluster, and the rest of the nodes work as usual;
宕机重连规则设置模块，用于设置节点宕机重连的规则，保证宕机重连的节点与数据库集群系统其他节点的数据同步一致。The downtime reconnection rule setting module is used to set the rules for node downtime reconnection to ensure that the data synchronization between the downtime reconnected node and other nodes of the database cluster system is consistent.
本申请中，节点宕机重连的规则包括：以宕掉时的时间戳为基准，根据主节点的日志文件，恢复重新接入的节点在时间戳之后的所有数据；重新接入的节点与主节点数据一致时，才能对用户可见和提供服务。In this application, the rules for node downtime reconnection include: based on the time stamp at the time of downtime, according to the log file of the master node, restore all the data of the reconnected node after the time stamp; Only when the master node data is consistent can it be visible and provide services to users.
在本申请的实施例中，设定的节点管理规则（节点增加规则、宕机规则、宕机重连规则）等实质上是节点之间的协议。In the embodiment of the present application, the set node management rules (node addition rules, downtime rules, downtime reconnection rules) etc. are essentially agreements between nodes.
在本申请中，初始配置单元用于进行初始配置,需要通过私有网络与每个所述的节点连接；节点规则设置单元用于对节点之间的规则（协议）进行设置，也需要通过私有网络与每个所述的节点连接。In this application, the initial configuration unit is used for initial configuration and needs to be connected to each of the nodes through a private network; the node rule setting unit is used to set the rules (protocols) between nodes and also needs to be connected through a private network Connect with each of the described nodes.
所述的多个节点还连接统一的地址访问集群，为用户组访问服务接口。The plurality of nodes are also connected to a unified address to access the cluster, and access the service interface for the user group.
每个所述的节点均包括存储模块、数据服务模块和节点管理模块；所述存储模块用于对节点数据进行存储；所述数据服务模块用于为用户提供服务；所述节点管理模块用于根据节点管理规则，保证节点管理过程中各个节点数据的同步一致。Each of the nodes includes a storage module, a data service module and a node management module; the storage module is used to store node data; the data service module is used to provide services for users; the node management module is used to According to the node management rules, the data synchronization and consistency of each node during the node management process are guaranteed.
在本申请的实施例中，除了保证节点管理过程中数据的同步一致外，还需要保证命令执行过程中，各个节点的数据同步，具体地，为用户提供服务过程中，接收到数据增加、删除、修改类命令时，所有节点同时执行，均执行成功时，整个命令执行成功，若一个节点执行失败，则全部节点回滚回命令执行前的状态，保证存储的数据同步一致。In the embodiment of this application, in addition to ensuring the synchronization and consistency of data in the process of node management, it is also necessary to ensure that the data of each node is synchronized in the process of command execution. 1. When modifying a command, all nodes execute it at the same time. If all of them execute successfully, the entire command executes successfully. If one node fails to execute, all nodes roll back to the state before the command execution to ensure that the stored data is synchronized and consistent.
如图2所示,所述的一种高可用性和强一致性的数据库集群系统的节点管理方法，包括以下步骤：As shown in Figure 2, the described node management method of a database cluster system with high availability and strong consistency comprises the following steps:
S1.通过手动配置的方式从所述多个节点选择一个节点作为主节点，其余所有节点均为副节点；S1. Select a node from the multiple nodes as the primary node through manual configuration, and all other nodes are secondary nodes;
S2.根据设定的节点管理规则对数据库集群中的节点进行管理，包括节点增加、宕机节点处理和宕机节点重新接入。S2. Manage the nodes in the database cluster according to the set node management rules, including node addition, downtime node processing and downtime node reconnection.
所述的节点增加包括以下子步骤：The described node increase comprises the following substeps:
S201.在数据库集群系统中加入新的节点；S201. Add a new node to the database cluster system;
S202.以新增节点加入的时间作为分界线；S202. Use the time when the new node joins as the dividing line;
S203.新增节点从主节点中同步该时间分界线之前的数据；S203. The newly added node synchronizes the data before the time boundary from the master node;
S204.根据主节点保留的日志文件，依次对该时间分界线之后新增节点的数据进行恢复；S204. According to the log file retained by the master node, the data of the newly added node after the time boundary is sequentially restored;
S205.当新增节点与主节点数据一致时，新增节点加入成功，对用户可见，且能够为用户提供服务。S205. When the data of the newly added node is consistent with that of the master node, the newly added node is added successfully, visible to the user, and able to provide services for the user.
所述的宕机节点处理包括以下子步骤：Described downtime node processing comprises the following substeps:
S211.判断宕机节点的类型：S211. Determine the type of downtime node:
（1）如果宕机节点为主节点，进入步骤S212；(1) If the downtime node is the master node, go to step S212;
（2）如果宕机节点为副节点，主节点断开宕机节点连接，并其踢出集群，其余节点照常工作；(2) If the downtime node is a secondary node, the master node disconnects the downtime node and kicks it out of the cluster, and the rest of the nodes work as usual;
S212.根据各个副节点的工作情况,从副节点中选取新的主节点，并将宕机节点踢出集群。S212. Select a new master node from the slave nodes according to the working conditions of each slave node, and kick the down node out of the cluster.
所述副节点的工作情况包括但不限于副节点的活跃度、负载量和连接数。The working condition of the secondary node includes but not limited to activity, load and connection number of the secondary node.
所述的宕机节点重新接入包括以下子步骤：The re-access of the downtime node includes the following sub-steps:
S221.宕机节点重新接入时，提取宕机节点宕掉时的时间戳；S221. When the downtime node reconnects, extract the time stamp when the downtime node is down;
S222.以宕掉时的时间戳为基准，根据主节点的日志文件，恢复重新接入的节点在时间戳之后的所有数据；S222. Taking the time stamp at the time of failure as a benchmark, according to the log file of the master node, restore all the data of the reconnected node after the time stamp;
S222.重新接入的节点与主节点数据一致时，接入成功，对用户可见，且能够为用户提供服务。S222. When the data of the reconnected node is consistent with that of the master node, the access is successful, visible to the user, and able to provide services for the user.
本发明中，每个节点都能提供完整的服务，能够有效提升工作效率；同时，该数据库集群能够自动管理节点主从关系，当副节点宕掉时，主节点会将其踢出集群，该副节点对外不可见；当主节点宕掉时，能自动选出新的主节点，再将宕掉的主节点踢出集群；由于数据库集群自动管理，对于用户来说，没有节点没有主副之分（看不到主节点和副节点之分），也不需要手动选择执行命令或任务的节点。相较于Data Guard手动切换主备库的方式，该数据库集群自动管理节点主从关系将大大缩短维护时间，对故障的处理方便有效；并且该数据库集群中每个节点都具存储模块、数据服务模块，整个集群中存在多份数据，避免了RAC方式中故障导致的数据丢失问题。In the present invention, each node can provide complete services, which can effectively improve work efficiency; at the same time, the database cluster can automatically manage the master-slave relationship of nodes. When the secondary node fails, the master node will kick it out of the cluster. The secondary node is invisible to the outside world; when the primary node goes down, a new primary node can be automatically selected, and then the downed primary node will be kicked out of the cluster; due to the automatic management of the database cluster, for users, there is no node without primary and secondary nodes (I can't see the difference between the primary node and the secondary node), and there is no need to manually select the node to execute the command or task. Compared with Data Guard's method of manually switching the master-slave database, the database cluster automatically manages the master-slave relationship of nodes, which will greatly shorten the maintenance time, and handle faults conveniently and effectively; and each node in the database cluster has storage modules, data service Module, there are multiple copies of data in the entire cluster, which avoids the problem of data loss caused by failures in the RAC mode.
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610721028.3ACN106301938A (en) | 2016-08-25 | 2016-08-25 | A kind of high availability and the data base cluster system of strong consistency and node administration method thereof |
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610721028.3ACN106301938A (en) | 2016-08-25 | 2016-08-25 | A kind of high availability and the data base cluster system of strong consistency and node administration method thereof |
| Publication Number | Publication Date |
|---|---|
| CN106301938Atrue CN106301938A (en) | 2017-01-04 |
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610721028.3APendingCN106301938A (en) | 2016-08-25 | 2016-08-25 | A kind of high availability and the data base cluster system of strong consistency and node administration method thereof |
| Country | Link |
|---|---|
| CN (1) | CN106301938A (en) |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106960060A (en)* | 2017-04-10 | 2017-07-18 | 聚好看科技股份有限公司 | The management method and device of a kind of data-base cluster |
| CN107846318A (en)* | 2017-11-15 | 2018-03-27 | 郑州云海信息技术有限公司 | A kind of distributed type assemblies and distributed type assemblies management method |
| CN108900331A (en)* | 2018-06-26 | 2018-11-27 | 郑州云海信息技术有限公司 | A kind of distributed type assemblies management method and distributed type assemblies |
| CN108984602A (en)* | 2018-06-05 | 2018-12-11 | 网易（杭州）网络有限公司 | A database control method and database system |
| CN109254880A (en)* | 2017-07-12 | 2019-01-22 | 苏宁云商集团股份有限公司 | A kind of method and device handling database delay machine |
| CN109298976A (en)* | 2018-10-17 | 2019-02-01 | 成都索贝数码科技股份有限公司 | Heterogeneous database cluster backup system and method |
| CN109347906A (en)* | 2018-08-30 | 2019-02-15 | 腾讯科技（深圳）有限公司 | A kind of data transmission method, device and server |
| CN109981459A (en)* | 2019-02-28 | 2019-07-05 | 联想(北京)有限公司 | A kind of method for sending information, client and computer readable storage medium |
| CN110162428A (en)* | 2019-05-17 | 2019-08-23 | 中国铁道科学研究院集团有限公司 | Method of data synchronization and device, electronic equipment and computer readable storage medium |
| CN110333986A (en)* | 2019-06-19 | 2019-10-15 | 上海二三四五网络科技有限公司 | A method of ensureing redis cluster availability |
| CN112134887A (en)* | 2020-09-23 | 2020-12-25 | 哈尔滨海能达科技有限公司 | Data synchronization method and device for nodes in distributed cluster |
| CN112190924A (en)* | 2020-12-04 | 2021-01-08 | 腾讯科技（深圳）有限公司 | Data disaster tolerance method, device and computer readable medium |
| CN112612854A (en)* | 2020-12-29 | 2021-04-06 | 天津南大通用数据技术股份有限公司 | Method for ensuring data consistency of cluster database during power failure or downtime |
| CN113297173A (en)* | 2021-05-24 | 2021-08-24 | 阿里巴巴新加坡控股有限公司 | Distributed database cluster management method and device and electronic equipment |
| CN115883575A (en)* | 2022-11-23 | 2023-03-31 | 紫光云技术有限公司 | High-availability cluster optimization method based on B tree |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7290015B1 (en)* | 2003-10-02 | 2007-10-30 | Progress Software Corporation | High availability via data services |
| CN102521297A (en)* | 2011-11-30 | 2012-06-27 | 北京人大金仓信息技术股份有限公司 | Method for achieving system dynamic expansion in shared-nothing database cluster |
| CN104993940A (en)* | 2015-05-11 | 2015-10-21 | 广东小天才科技有限公司 | Method and device for reducing data loss in main/standby node fault switching process |
| CN105095486A (en)* | 2015-08-17 | 2015-11-25 | 浪潮(北京)电子信息产业有限公司 | Cluster database disaster recovery method and device |
| CN105138441A (en)* | 2015-06-30 | 2015-12-09 | 中标软件有限公司 | HAC system, warning method based on HAC system and warning system based on HAC system |
| CN105159943A (en)* | 2015-08-07 | 2015-12-16 | 北京思特奇信息技术股份有限公司 | Automatic backup method and system for distributed database |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7290015B1 (en)* | 2003-10-02 | 2007-10-30 | Progress Software Corporation | High availability via data services |
| CN102521297A (en)* | 2011-11-30 | 2012-06-27 | 北京人大金仓信息技术股份有限公司 | Method for achieving system dynamic expansion in shared-nothing database cluster |
| CN104993940A (en)* | 2015-05-11 | 2015-10-21 | 广东小天才科技有限公司 | Method and device for reducing data loss in main/standby node fault switching process |
| CN105138441A (en)* | 2015-06-30 | 2015-12-09 | 中标软件有限公司 | HAC system, warning method based on HAC system and warning system based on HAC system |
| CN105159943A (en)* | 2015-08-07 | 2015-12-16 | 北京思特奇信息技术股份有限公司 | Automatic backup method and system for distributed database |
| CN105095486A (en)* | 2015-08-17 | 2015-11-25 | 浪潮(北京)电子信息产业有限公司 | Cluster database disaster recovery method and device |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106960060B (en)* | 2017-04-10 | 2020-07-31 | 聚好看科技股份有限公司 | Database cluster management method and device |
| CN106960060A (en)* | 2017-04-10 | 2017-07-18 | 聚好看科技股份有限公司 | The management method and device of a kind of data-base cluster |
| CN109254880A (en)* | 2017-07-12 | 2019-01-22 | 苏宁云商集团股份有限公司 | A kind of method and device handling database delay machine |
| CN109254880B (en)* | 2017-07-12 | 2022-07-19 | 苏宁易购集团股份有限公司 | Method and device for processing database downtime |
| CN107846318A (en)* | 2017-11-15 | 2018-03-27 | 郑州云海信息技术有限公司 | A kind of distributed type assemblies and distributed type assemblies management method |
| CN108984602A (en)* | 2018-06-05 | 2018-12-11 | 网易（杭州）网络有限公司 | A database control method and database system |
| CN108984602B (en)* | 2018-06-05 | 2021-04-16 | 网易（杭州）网络有限公司 | A database control method and database system |
| CN108900331A (en)* | 2018-06-26 | 2018-11-27 | 郑州云海信息技术有限公司 | A kind of distributed type assemblies management method and distributed type assemblies |
| CN109347906A (en)* | 2018-08-30 | 2019-02-15 | 腾讯科技（深圳）有限公司 | A kind of data transmission method, device and server |
| CN109298976A (en)* | 2018-10-17 | 2019-02-01 | 成都索贝数码科技股份有限公司 | Heterogeneous database cluster backup system and method |
| CN109981459A (en)* | 2019-02-28 | 2019-07-05 | 联想(北京)有限公司 | A kind of method for sending information, client and computer readable storage medium |
| CN110162428A (en)* | 2019-05-17 | 2019-08-23 | 中国铁道科学研究院集团有限公司 | Method of data synchronization and device, electronic equipment and computer readable storage medium |
| CN110333986A (en)* | 2019-06-19 | 2019-10-15 | 上海二三四五网络科技有限公司 | A method of ensureing redis cluster availability |
| CN110333986B (en)* | 2019-06-19 | 2023-12-29 | 上海二三四五网络科技有限公司 | Method for guaranteeing availability of redis cluster |
| CN112134887A (en)* | 2020-09-23 | 2020-12-25 | 哈尔滨海能达科技有限公司 | Data synchronization method and device for nodes in distributed cluster |
| CN112134887B (en)* | 2020-09-23 | 2022-08-09 | 哈尔滨海能达科技有限公司 | Data synchronization method and device for nodes in distributed cluster |
| CN112190924A (en)* | 2020-12-04 | 2021-01-08 | 腾讯科技（深圳）有限公司 | Data disaster tolerance method, device and computer readable medium |
| CN112612854A (en)* | 2020-12-29 | 2021-04-06 | 天津南大通用数据技术股份有限公司 | Method for ensuring data consistency of cluster database during power failure or downtime |
| CN113297173A (en)* | 2021-05-24 | 2021-08-24 | 阿里巴巴新加坡控股有限公司 | Distributed database cluster management method and device and electronic equipment |
| CN113297173B (en)* | 2021-05-24 | 2023-10-31 | 阿里巴巴新加坡控股有限公司 | Distributed database cluster management method and device, electronic equipment |
| CN115883575A (en)* | 2022-11-23 | 2023-03-31 | 紫光云技术有限公司 | High-availability cluster optimization method based on B tree |
| Publication | Publication Date | Title |
|---|---|---|
| CN106301938A (en) | A kind of high availability and the data base cluster system of strong consistency and node administration method thereof | |
| CN103346903B (en) | Dual-machine backup method and device | |
| WO2019154394A1 (en) | Distributed database cluster system, data synchronization method and storage medium | |
| CN104504062B (en) | Master/slave data storehouse method of data synchronization and device | |
| CN102142008B (en) | Method and system for implementing distributed memory database, token controller and memory database | |
| CN113987064B (en) | Data processing method, system and device | |
| CN109491609B (en) | Cache data processing method, device and equipment and readable storage medium | |
| CN110807064B (en) | Data recovery device in RAC distributed database cluster system | |
| Ronstrom et al. | MySQL cluster architecture overview | |
| CN102938705B (en) | Method for managing and switching high availability multi-machine backup routing table | |
| CN105224637A (en) | A kind of based on PostgreSQL database active and standby/the comprehensive method of cluster application | |
| CN105069160A (en) | Autonomous controllable database based high-availability method and architecture | |
| CN109189860A (en) | A kind of active and standby increment synchronization method of MySQL based on Kubernetes system | |
| CN105471622A (en) | High-availability method and system for main/standby control node switching based on Galera | |
| JP2011530127A (en) | Method and system for maintaining data integrity between multiple data servers across a data center | |
| CN108173959A (en) | A cluster storage system | |
| CN111639132B (en) | Log synchronization method and device | |
| CN117827544B (en) | Hot backup system, method, electronic device and storage medium | |
| CN103473328A (en) | MYSQL (my structured query language)-based database cloud and construction method for same | |
| CN106156318A (en) | A kind of system and method realizing multinode data base's High Availabitity | |
| CN110377487A (en) | A kind of method and device handling high-availability cluster fissure | |
| CN107220104A (en) | A kind of virtual machine preparedness method and apparatus | |
| WO2020233001A1 (en) | Distributed storage system comprising dual-control architecture, data reading method and device, and storage medium | |
| CN107357800A (en) | A kind of database High Availabitity zero loses solution method | |
| CN106612314A (en) | System for realizing software-defined storage based on virtual machine |
| 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:20170104 |