WO2017220033A1 - 服务器集群及适用于该集群的数据库资源组切换控制方法 - Google Patents

服务器集群及适用于该集群的数据库资源组切换控制方法 Download PDF

Info

Publication number
WO2017220033A1
WO2017220033A1 PCT/CN2017/089876 CN2017089876W WO2017220033A1 WO 2017220033 A1 WO2017220033 A1 WO 2017220033A1 CN 2017089876 W CN2017089876 W CN 2017089876W WO 2017220033 A1 WO2017220033 A1 WO 2017220033A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
restart
switching
current
node
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.)
Ceased
Application number
PCT/CN2017/089876
Other languages
English (en)
French (fr)
Inventor
汪洋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Publication of WO2017220033A1 publication Critical patent/WO2017220033A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
    • H04L41/0661—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities by reconfiguring faulty entities
    • 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

Definitions

  • the invention relates to a server cluster management technology, in particular to a server cluster and a database resource group switching control method applicable to the server cluster.
  • Server clustering refers to bringing together many servers to perform the same service. It seems to the client that there is only one server. Clusters can use multiple computers for parallel computing to achieve high computing speeds, and can also be backed up by multiple computers, so that any one machine can break the whole system and still function properly. Once the cluster service is installed and running on the server, the server can join the cluster. Clustering can reduce the number of single points of failure and achieve high availability of clustered resources.
  • the database management software used by each server is commercialized software, and the procurement cost is high.
  • the existing database resource group applicable to the server cluster is used.
  • the database storage requirements of each server must use the file system, so that the performance of the database IO is reduced.
  • the database storage corresponding to each server involves the unloading and loading of the file system volume, and the switching time is long.
  • a database resource group switching control method suitable for a server cluster comprising:
  • step B If there is no resource in the resource group, return to step A above. If the resource in the resource group fails, analyze whether the failed resource is allowed to restart.
  • step E If the failed resource restarts successfully, return to step A above. If the failed resource restart fails, the failed resource is switched to another node for operation.
  • analyzing whether the failed resource is allowed to restart includes:
  • the first dynamic attribute value RESTART_COUNT and the first static attribute value RESTART_ATTEMPTS are used to analyze whether to restart the failed resource, wherein:
  • the current value of the first static attribute value RESTART_ATTEMPTS is 0, it means that the current resource is not allowed to restart. If the first static attribute value RESTART_ATTEMPTS is defined as N, the number of times the current resource is allowed to be restarted is N, and if the current number is A dynamic attribute value RESTART_COUNT is n, indicating that the resource has been restarted n times;
  • n ⁇ N confirm that the resource can still be restarted at the local node, try to restart the resource, and increase the dynamic attribute value n by one;
  • the step C includes:
  • the resource is allowed to switch, the resource is switched to a switching node of a predetermined preset number of switching nodes according to a preset switching rule;
  • the resource fails to run on a predetermined preset number of switching nodes, the resource is processed offline and the monitoring of the resource is stopped.
  • the preset switching rule is:
  • the resource fails to run on the currently switched switching node, and the current number of handovers corresponding to the resource is less than the number of allowed handovers, the resource is switched to a predetermined other handover node, and the current handover corresponding to the resource is switched. Add 1 to the number of times; and
  • the node switching operation is ended.
  • the method further comprises:
  • the resource is processed offline and monitoring of the resource is stopped.
  • a server cluster includes a plurality of servers, each of which includes a storage device and a processor, wherein:
  • the storage device is configured to store a database resource group switching control suitable for a server cluster system
  • the processor is configured to invoke and execute the database resource group switching control system applicable to the server cluster to perform the following steps:
  • step B If there is no resource in the resource group, return to step A above. If the resource in the resource group fails, analyze whether the failed resource is allowed to restart.
  • step E If the failed resource restarts successfully, return to step A above. If the failed resource restart fails, the failed resource is switched to another node for operation.
  • analyzing whether the failed resource is allowed to restart includes:
  • the first dynamic attribute value RESTART_COUNT and the first static attribute value RESTART_ATTEMPTS are analyzed based on the current resource to allow restarting the failed resource, wherein:
  • the current value of the first static attribute value RESTART_ATTEMPTS is 0, it means that the current resource is not allowed to restart. If the first static attribute value RESTART_ATTEMPTS is defined as N, the number of times the current resource is allowed to be restarted is N, and if the current number is A dynamic attribute value RESTART_COUNT is n, indicating that the resource has been restarted n times;
  • n ⁇ N confirm that the resource can still be restarted at the local node, try to restart the resource, and increase the dynamic attribute value n by one;
  • the database resource group switching control system confirms that the resource cannot be restarted at the local node.
  • the step C includes:
  • the resource is allowed to switch, the resource is switched to a switching node of a predetermined preset number of switching nodes according to a preset switching rule;
  • the resource fails to run on a predetermined preset number of switching nodes, the resource is processed offline and the monitoring of the resource is stopped.
  • the preset switching rule is:
  • the resource fails to run on the currently switched switching node, and the current number of handovers corresponding to the resource is less than the number of allowed handovers, the resource is switched to a predetermined other handover node, and the current handover corresponding to the resource is switched. Add 1 to the number of times; and
  • the node switching operation is ended.
  • the processor performs the following steps in calling and executing the database resource group switching control system applicable to the server cluster:
  • the resource is processed offline and monitoring of the resource is stopped.
  • the database resource group switching control method and system applicable to the server cluster of the present invention can reduce the switching time of the database resource group switching.
  • FIG. 1 is a flow chart of a method for a preferred embodiment of a database resource group switching control method for a server cluster according to the present invention.
  • FIG. 2 is a detailed flowchart of one step of the database resource group switching control method applicable to the server cluster shown in FIG. 1.
  • FIG. 3 is a system architecture diagram of a preferred embodiment of a database resource group switching control system applicable to a server cluster of the present invention.
  • FIG. 4 is a configuration diagram of each database resource group in a preferred embodiment of the database resource group switching control system applicable to the server cluster of the present invention.
  • FIG. 5 is a functional block diagram of a preferred embodiment of a database resource group switching control system applicable to a server cluster of the present invention.
  • FIG. 1 it is a flowchart of a method for a preferred embodiment of a database resource group switching control method for a server cluster.
  • the database resource group switching control method applicable to the server cluster in this embodiment is not limited to the steps shown in the flowchart. In addition, in the steps shown in the flowchart, some steps may be omitted, and the order between the steps may be changed.
  • Step S10 The database resource group switching control system installed in each server of the server cluster performs fault checking on each resource in each database resource group every preset time (for example, 2 minutes).
  • step S11 the database resource group switching control system determines whether there is a resource failure in the resource group.
  • step S12 is performed, and the database resource group switching control system analyzes whether the failed resource is allowed to restart.
  • step 13 is performed, and the database resource group switching control system switches the failed resource to another node for running.
  • step S14 is executed, and the database resource group switching control system controls the failed resource to restart, and increases the current restart number corresponding to the resource by one.
  • whether to allow the current resource to be restarted and the number of restarts of the current resource is concluded by analyzing the first dynamic attribute value RESTART_COUNT of the current resource and the first static attribute value RESTART_ATTEMPTS. Specifically, if the current value of RESTART_ATTEMPTS is 0, it means that the current resource does not allow restart. If the defined value of RESTART_ATTEMPTS is N, it means that the current resource is allowed to restart and the number of restarts allowed is N. If RESTART_COUNT is n, then The resource has been restarted n times.
  • n ⁇ N it is confirmed that the resource can still be restarted at the local node, and the database resource group switching control system may try to restart the resource and increase the RESTART_COUNT value n by 1; when n ⁇ N, the database resource group switching control The system confirms that the resource cannot continue to restart at the local node. It can be understood that the above-mentioned plus 1 operation can be performed before, during, or after the restart of the resource, and no limitation is imposed in the present application.
  • RESTART_ATTEMPTS For example, if the defined value of RESTART_ATTEMPTS is 3, it means that the number of times the current resource is allowed to be restarted is 3, and if the current RESTART_COUNT is 2 (indicating that the resource has been restarted 2 times), the database resource group switching control system confirms that the resource can still be Restarting the local node will attempt to restart the resource and increment the RESTART_COUNT value by one; if the RESTART_ATTEMPTS has a defined value of 3, and if the current RESTART_COUNT is 3 (indicating that the resource has been restarted 3 times), then the database resource group The handover control system confirms that the resource cannot continue to restart at the local node.
  • Step S15 The database resource group switching control system determines whether the failed resource is successfully restarted.
  • step 10 If the failed resource restarts successfully, the process returns to step 10; if the failed resource restart fails, the above-mentioned step S13 is performed, and the database resource group switching control system switches the failed resource to another node for operation.
  • step S13 in FIG. 1 it is a refinement implementation flowchart of step S13 in FIG. 1, that is, a refinement implementation flow chart in which a faulty resource is switched to another node.
  • the resource that will fail in this embodiment The method of switching to operation on other nodes is not limited to the steps shown in the flowchart, and in addition, some of the steps shown in the flowchart may be omitted, and the order between the steps may be changed.
  • Step S20 the database resource group switching control system analyzes whether the resource allows switching.
  • analyzing whether the handover is allowed is performed based on the second static attribute value FAILURE_THRESHOLD of the current resource. If the second static attribute value FAILURE_THRESHOLD defines a value of zero, it means that the current resource does not allow switching; if the second static attribute value FAILURE_THRESHOLD defines a value of P, the number of times the current resource is allowed to be switched is P, and the P is greater than 0. Integer.
  • step S21 is performed, and the database resource group switching control system switches the resource to a switching node of a predetermined preset number of switching nodes according to a preset switching rule.
  • Step S22 the database resource group switching control system further determines whether the resource runs successfully on a switched node.
  • the database resource group switching control system clears the current restart number corresponding to the resource, and returns to step S10 in FIG. 1 .
  • step S23 if the resource fails to run on a predetermined preset number of switching nodes, step S23 is performed, the database resource group switching control system processes the resource offline, and stops monitoring the resource. .
  • step S20 the database resource group switching control system analyzes that the resource does not allow handover, and also performs step S23, the database resource group switching control system processes the resource offline, and stops monitoring the resource.
  • the preset switching rule is: switching the resource to the next switching node one by one according to a predetermined switching sequence of the preset number of nodes; if the resource is in the currently switched node If the operation succeeds, the current restart number corresponding to the resource is cleared, and the node switching operation ends. If the resource fails to run on the currently switched switching node, and the current number of handovers corresponding to the resource is less than the number of allowed handovers, the resource is switched to run on a predetermined other switching node, and the current resource corresponding to the resource is The number of switchings is increased by 1.
  • the node handover operation is terminated; it can be understood that the foregoing addition operation may be performed before, during, or after the handover of the node, which is not Make restrictions.
  • the resource may be switched to run on other nodes according to the node order defined in HOSTING_MEMBERS or SERVER_POOLS, and the current number of handovers corresponding to the resource is incremented by one before, during, or after each node switch, for example
  • the current resource switching number control is controlled by the second dynamic attribute FAILURE_COUNT and the second static attribute FAILURE_THRESHOLD of the current resource, for example, the current FAILURE_COUNT is 2 (indicating that the resource has been switched 2 times), and the defined value of FAILURE_THRESHOLD is 4
  • the database resource group switching control system for the server cluster confirms that the resource can still be switched at other nodes, tries to continue switching the running node of the resource, and increments the FAILURE_COUNT value by 1).
  • FIG. 3 it is a system architecture diagram of a preferred embodiment of a database resource group switching control system applicable to a server cluster of the present invention.
  • the system architecture diagram structure of the database resource group switching control system is: multiple service servers 1 (three in the figure as an example), and the plurality of service servers 1 are communicatively connected through a network 3 (for example, a fiber optic network).
  • a plurality of storage devices 2 (two in the figure).
  • Each service server 1 includes a processor 1a for supporting the operation of the entire service server 1, and a storage device 1b for storing various data and computer instructions.
  • the data resource group 10, the database resource switching control system 11, the cluster management system 12, and the operating system 13 are stored on the storage device.
  • the storage device 1b may include one or more non-volatile storage media, such as a ROM, an EPROM, or a Flash Memory, etc., which may be built in the corresponding service server 1 or may be configured as a service server in the form of an external storage device. Part of 1.
  • non-volatile storage media such as a ROM, an EPROM, or a Flash Memory, etc.
  • the database resource group 10 includes a database resource group identifier 11. Further, the database resource group 10 further includes three resources: a listener 12, a virtual IP address 13, and a database 14. The three resources of the listener 12, the virtual IP address 13 and the database 14 of each database resource group 10 are integrally designed and configured together. Referring to FIG. 2, the technical benefits of this are as follows: 1. The listener 12 is dependent on For the virtual IP address 13, the database 14 is relatively independent, thus ensuring switching or starting data. The startup sequence of each resource in the process of the library resource group 10 is correct; secondly, the three key resources of the listener 12, the virtual IP address 13 and the database 14 are switched as a whole, and the database resource group 10 can be switched after the node is Provide external services.
  • the cluster management system 12 can be used to manage a set of mutually independent service servers 1 interconnected by a high speed network in a single system mode, which form a group.
  • the operating system 13 is a Linux operating system, a Windows operating system, or any other suitable operating system.
  • the database resource control system 11 includes at least one computer instruction executable by the processor 1a to implement the database resource group switching control method of various embodiments of the present application.
  • These computer instructions can be divided into a plurality of functional modules, such as resource group monitoring module 110 and resource group management module 111, depending on the functions performed by different portions of these computer instructions.
  • the resource group monitoring module 110 is configured to perform a fault check on each resource in each database resource group 10 every predetermined time (for example, 2 minutes) to determine whether there is a resource failure in the resource group 10.
  • the resource group management module 111 is configured to perform a restart on the failed resource or switch the failed resource to another node when the resource in the resource group 10 fails.
  • the resource group management module 111 switches the failed resource to another node for running; or if the failed resource allows the restart, the resource group management module 111 controls the failure.
  • the resource is restarted, and the current number of restarts corresponding to the resource is increased by one. It can be understood that the addition operation can be performed before, during, or after the restart of the resource, which is not limited in this application.
  • the restart number control of the current resource is controlled by the first dynamic attribute value RESTART_COUNT of the current resource and the first static attribute value RESTART_ATTEMPTS. If the current RESTART_ATTEMPTS has a defined value of 0, it means that the current resource does not allow restart. If the defined value of RESTART_ATTEMPTS is N, the number of times the current resource is allowed to be restarted is N. If RESTART_COUNT is n, the resource has been restarted n times. .
  • n ⁇ N it is confirmed that the resource can still be restarted at the local node, and will try to restart the resource, and RESTART_COUNT value n plus 1; when n ⁇ N, the database resource group switching control system confirms that the resource cannot continue to restart at the local node.
  • the resource group management module 111 confirms that the resource can still be The local node restarts, attempts to restart the resource, and increments the RESTART_COUNT value; if the RESTART_ATTEMPTS has a defined value of 3, and if the current RESTART_COUNT is 3 (indicating that the resource has been restarted 3 times), the resource group management module 111 confirms that the resource cannot continue to restart at the local node.
  • the resource group management module 111 further determines whether the failed resource is successfully restarted.
  • the resource group monitoring module 110 continues to perform fault checking on each resource in each database resource group 10 every predetermined time (for example, 2 minutes) to determine whether there is a resource group. The resource in 10 has failed.
  • the resource group management module 111 further switches the failed resource to another node for operation.
  • the resource group management module 111 first analyzes whether the resource allows switching. In this embodiment, it is analyzed whether the handover is allowed to be performed based on the second static attribute value FAILURE_THRESHOLD of the current resource. If the second static attribute value FAILURE_THRESHOLD defines a value of zero, it means that the current resource does not allow switching; if the second static attribute value FAILURE_THRESHOLD defines a value of P, the number of times the current resource is allowed to be switched is P, and the P is greater than 0. A positive integer.
  • the resource group management module 111 processes the resource offline and stops monitoring the resource.
  • the resource group management module 111 switches the resource to a handover node of a predetermined preset number of handover nodes according to a preset handover rule. If the resource runs successfully on a switched node, the resource group management module 111 clears the current restart number corresponding to the resource. If the resource fails to run on a predetermined preset number of switching nodes, Then, the resource group management module 111 processes the resource offline and stops monitoring the resource.
  • the preset switching rule is: switching the resource to the next switching node one by one according to a predetermined switching sequence of the preset number of nodes; if the resource is in the currently switched node If the operation succeeds, the current restart number corresponding to the resource is cleared, and the node switching operation ends. If the resource fails to run on the currently switched switching node, and the current number of handovers corresponding to the resource is less than the number of allowed handovers, the resource is switched to a predetermined other handover node, and the current handover corresponding to the resource is switched. Add 1 to the number of times.
  • the node switching operation ends; it can be understood that the foregoing adding operation may be before, during, or after the handover. This is done after the handover, and this application does not limit this.
  • the resource may be switched to run on other nodes according to the node order defined in HOSTING_MEMBERS or SERVER_POOLS, and the current number of handovers corresponding to the resource is incremented by one before, during, or after each node switch, for example
  • the current resource switching number control is controlled by the second dynamic attribute FAILURE_COUNT and the second static attribute FAILURE_THRESHOLD of the current resource, for example, the current FAILURE_COUNT is 2 (indicating that the resource has been switched 2 times), and the defined value of FAILURE_THRESHOLD is 4
  • the database resource group switching control system for the server cluster confirms that the resource can still be switched at other nodes, tries to continue switching the running node of the resource, and increments the FAILURE_COUNT value by 1).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Hardware Redundancy (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种适用于服务器集群的数据库资源组切换控制方法，包括：每隔预设时间对各个资源组中的各个资源进行故障检查；若有资源组中的资源发生故障，则分析发生故障的资源是否允许重启；若发生故障的资源不允许重启，则将发生故障的资源切换至其他节点上运行；若发生故障的资源允许重启，则控制发生故障的资源进行重启，并将该资源对应的当前重启次数加1；及若发生故障的资源重启失败，则将发生故障的资源切换至其他节点上运行。本发明还提供一种服务器集群。本发明可以减少数据库资源组切换的切换时间。

Description

服务器集群及适用于该集群的数据库资源组切换控制方法
优先权申明
本申请基于巴黎公约申明享有2016年6月24日递交的申请号为CN2016104665056、名称为“服务器集群及适用于该集群的数据库资源组切换控制方法”中国专利申请的优先权，该中国专利申请的整体内容以参考的方式结合在本申请中。
技术领域
本发明涉及服务器集群管理技术，特别是一种服务器集群以及适用于该服务器集群的数据库资源组切换控制方法。
背景技术
服务器集群是指将很多服务器集中起来一起进行同一种服务，在客户端看来就像是只有一个服务器。集群可以利用多个计算机进行并行计算从而获得很高的计算速度，也可以用多个计算机做备份，从而使得任何一个机器坏了整个系统还是能正常运行。一旦在服务器上安装并运行了集群服务，该服务器即可加入群集。集群化操作可以减少单点故障数量，并且实现了群集化资源的高可用性。
目前，业界使用的现有适用于服务器集群的数据库资源组切换控制系统中，各个服务器使用的数据库管理软件是商业化软件，采购成本较高，另外，在现有适用于服务器集群的数据库资源组切换控制系统中，各个服务器对应的数据库存储要求必须使用文件系统，使得数据库IO性能会降低，同时，各个服务器对应的数据库存储涉及文件系统卷的卸载和加载，切换时间长。
发明内容
鉴于以上内容，有必要提供一种适用于服务器集群的数据库资源组切换控 制方法，其可以减少数据库资源组切换的切换时间。
一种适用于服务器集群的数据库资源组切换控制方法，包括：
A、每隔预设时间对各个资源组中的各个资源进行故障检查；
B、若没有资源组中的资源发生故障，则返回执行上述步骤A，若有资源组中的资源发生故障，则分析发生故障的资源是否允许重启；
C、若发生故障的资源不允许重启，则将发生故障的资源切换至其他节点上运行；
D、若发生故障的资源允许重启，则控制发生故障的资源进行重启，并将该资源对应的当前重启次数加1；及
E、若发生故障的资源重启成功，则返回执行上述步骤A，若发生故障的资源重启失败，则将发生故障的资源切换至其他节点上运行。
优选地，所述步骤B中分析发生故障的资源是否允许重启包括：
基于当前资源的第一动态属性值RESTART_COUNT和第一静态属性值RESTART_ATTEMPTS分析是否重启发生故障的资源，其中：
若当前第一静态属性值RESTART_ATTEMPTS的定义值为0，则代表当前资源不允许重启，若第一静态属性值RESTART_ATTEMPTS的定义值为N，则代表当前资源允许重启的次数为N，同时若当前第一动态属性值RESTART_COUNT是n，代表该资源已经重启了n次；
若n<N，则确认该资源仍然可以在本地节点进行重启，尝试重启该资源，并将动态属性值n加1；
若n≥N，则确认该资源不可以在本地节点重启。
优选地，所述步骤C包括：
F、基于当前资源的第二静态属性值FAILURE_THRESHOLD分析该资源是否允许切换，其中，若第二静态属性值FAILURE_THRESHOLD定义值为0，则代表当前资源不允许切换，如果第二静态属性值FAILURE_THRESHOLD定义 值为P，则代表当前资源允许切换的次数为P；
G、若该资源允许切换，则将该资源按预设的切换规则切换至预先确定的预设数量的切换节点中的一个切换节点上运行；
H、若该资源在一个切换的节点上运行成功，则将该资源对应的当前重启次数清零，并返回执行上述步骤A；及
I、若该资源在预先确定的预设数量的切换节点上均运行失败，则将该资源离线处理，并停止监控该资源。
优选地，所述预设的切换规则为：
按照预先确定的预设数量节点的切换顺序，逐个将该资源切换至下一切换节点上运行；
若该资源在当前切换的节点上运行成功，则将该资源对应的当前重启次数清零并结束节点切换操作；
若该资源在当前切换的切换节点上运行失败，且该资源对应的当前切换次数小于允许切换的次数，则将该资源切换至预先确定的其他切换节点上运行，并将该资源对应的当前切换次数加1；及
若该资源在当前切换的切换节点上运行失败，且该资源对应的当前切换次数大于等于允许切换的次数，则结束节点切换操作。
优选地，该方法还包括：
若该资源不允许切换，则将该资源离线处理，并停止监控该资源。
鉴于以上内容，还有必要提供一种适用于上述方法的服务器集群，其可以减少数据库资源组切换的切换时间。
一种服务器集群，包括多个服务器，每个服务器包括存储设备以及处理器，其中：
所述存储设备，用于存储一个适用于服务器集群的数据库资源组切换控制 系统；
所述处理器，用于调用并执行所述适用于服务器集群的数据库资源组切换控制系统，以执行如下步骤：
A、每隔预设时间对各个资源组中的各个资源进行故障检查；
B、若没有资源组中的资源发生故障，则返回执行上述步骤A，若有资源组中的资源发生故障，则分析发生故障的资源是否允许重启；
C、若发生故障的资源不允许重启，则将发生故障的资源切换至其他节点上运行；
D、若发生故障的资源允许重启，则控制发生故障的资源进行重启，并将该资源对应的当前重启次数加1；及
E、若发生故障的资源重启成功，则返回执行上述步骤A，若发生故障的资源重启失败，则将发生故障的资源切换至其他节点上运行。
优选地，所述步骤B中分析发生故障的资源是否允许重启包括：
基于当前资源的第一动态属性值RESTART_COUNT和第一静态属性值RESTART_ATTEMPTS分析是否允许重启发生故障的资源，其中：
若当前第一静态属性值RESTART_ATTEMPTS的定义值为0，则代表当前资源不允许重启，若第一静态属性值RESTART_ATTEMPTS的定义值为N，则代表当前资源允许重启的次数为N，同时若当前第一动态属性值RESTART_COUNT是n，代表该资源已经重启了n次；
若n<N，则确认该资源仍然可以在本地节点进行重启，尝试重启该资源，并将动态属性值n加1；
若n≥N，则数据库资源组切换控制系统确认该资源不可以在本地节点重启。
优选地，所述步骤C包括：
F、基于当前资源的第二静态属性值FAILURE_THRESHOLD分析该资源是否允许切换，其中，如果第二静态属性值FAILURE_THRESHOLD定义值为0， 则代表当前资源不允许切换，如果第二静态属性值FAILURE_THRESHOLD定义值为P，则代表当前资源允许切换的次数为P；
G、若该资源允许切换，则将该资源按预设的切换规则切换至预先确定的预设数量的切换节点中的一个切换节点上运行；
H、若该资源在一个切换的节点上运行成功，则将该资源对应的当前重启次数清零，并返回执行上述步骤A；及
I、若该资源在预先确定的预设数量的切换节点上均运行失败，则将该资源离线处理，并停止监控该资源。
优选地，所述预设的切换规则为：
按照预先确定的预设数量节点的切换顺序，逐个将该资源切换至下一切换节点上运行；
若该资源在当前切换的节点上运行成功，则将该资源对应的当前重启次数清零，并结束节点切换操作；
若该资源在当前切换的切换节点上运行失败，且该资源对应的当前切换次数小于允许切换的次数，则将该资源切换至预先确定的其他切换节点上运行，并将该资源对应的当前切换次数加1；及
若该资源在当前切换的切换节点上运行失败，且该资源对应的当前切换次数大于等于允许切换的次数，则结束节点切换操作。
优选地，所述处理器在调用并执行所述适用于服务器集群的数据库资源组切换控制系统还执行如下步骤：
若该资源不允许切换，则将该资源离线处理，并停止监控该资源。
相较于现有技术，本发明所述适用于服务器集群的数据库资源组切换控制方法及系统，可以减少数据库资源组切换的切换时间。
附图说明
图1是本发明适用于服务器集群的数据库资源组切换控制方法较佳实施例的方法流程图。
图2是图1所示适用于服务器集群的数据库资源组切换控制方法中其中一个步骤的细化流程图。
图3是本发明适用于服务器集群的数据库资源组切换控制系统较佳实施例的系统架构图。
图4是本发明适用于服务器集群的数据库资源组切换控制系统较佳实施例中每个数据库资源组的配置图。
图5是本发明适用于服务器集群的数据库资源组切换控制系统较佳实施例的功能模块图。
具体实施方式
参阅图1所示，是本发明适用于服务器集群的数据库资源组切换控制方法较佳实施例的方法流程图。本实施例所述适用于服务器集群的数据库资源组切换控制方法并不限于流程图中所示步骤，此外流程图中所示步骤中，某些步骤可以省略、步骤之间的顺序可以改变。
步骤S10，安装于服务器集群的每个服务器中的数据库资源组切换控制系统每隔预设时间(例如，2分钟)，对各个数据库资源组中的各个资源进行故障检查。
步骤S11，所述数据库资源组切换控制系统判断有没有资源组中的资源发生故障。
若没有资源发生故障，则返回执行上述步骤S10。
或者，若有资源组中的资源发生故障，则执行步骤S12，所述数据库资源组切换控制系统分析发生故障的资源是否允许重启。
若发生故障的资源不允许重启，则执行步骤13，所述数据库资源组切换控制系统将发生故障的资源切换至其他节点上运行。
若发生故障的资源允许重启，则执行步骤S14，所述数据库资源组切换控制系统控制发生故障的资源进行重启，并将该资源对应的当前重启次数加1。
本发明其中一个实施例中，是否允许当前资源重启以及当前资源的重启次数是通过分析当前资源的第一动态属性值RESTART_COUNT和第一静态属性值RESTART_ATTEMPTS来得出结论的。具体而言，若当前RESTART_ATTEMPTS的定义值为0，则代表当前资源不允许重启，若RESTART_ATTEMPTS的定义值为N，则代表当前资源允许重启且允许重启的次数为N，若RESTART_COUNT是n，则说明该资源已经重启了n次。当n<N时，则确认该资源仍然可以在本地节点进行重启，数据库资源组切换控制系统可尝试重启该资源，并将RESTART_COUNT值n加1；当n≥N时，则数据库资源组切换控制系统确认该资源不可以在本地节点继续进行重启。可以理解，上述加1操作可在资源重启之前、重启之中或重启之后进行，在本申请中并不做任何限制。
例如：若RESTART_ATTEMPTS的定义值为3，则代表当前资源允许重启的次数为3，同时若当前RESTART_COUNT是2(说明该资源已经重启了2次)，则数据库资源组切换控制系统确认该资源仍然可以在本地节点进行重启，会尝试重启该资源，并将RESTART_COUNT值加1；若RESTART_ATTEMPTS的定义值为3，同时若当前RESTART_COUNT是3(说明该资源已经重启了3次)，则所述数据库资源组切换控制系统确认该资源不可以在本地节点继续进行重启。
步骤S15，所述数据库资源组切换控制系统判断发生故障的资源是否重启成功。
若发生故障的资源重启成功，则返回执行上述步骤10；若发生故障的资源重启失败，执行上述的步骤S13，所述数据库资源组切换控制系统将发生故障的资源切换至其他节点上运行。
参阅图2所示，是图1中步骤S13的细化实施流程图，即将发生故障的资源切换至其他节点上运行的细化实施流程图。本实施例所述将发生故障的资源 切换至其他节点上运行的方法并不限于流程图中所示步骤，此外流程图中所示步骤中，某些步骤可以省略、步骤之间的顺序可以改变。
步骤S20，所述数据库资源组切换控制系统分析该资源是否允许切换。
本发明其中一个实施例中，分析是否允许切换是基于当前资源的第二静态属性值FAILURE_THRESHOLD来进行分析的。若第二静态属性值FAILURE_THRESHOLD定义值为零，则代表当前资源不允许切换；如果第二静态属性值FAILURE_THRESHOLD定义值为P，则代表当前资源允许切换的次数为P，所述P为大于0的整数。
若该资源允许切换，则执行步骤S21，所述数据库资源组切换控制系统将该资源按预设的切换规则切换至预先确定的预设数量的切换节点中的一个切换节点上运行。
步骤S22，所述数据库资源组切换控制系统进一步判断该资源在一个切换的节点上是否运行成功。
若该资源在一个切换的节点上运行成功，则所述数据库资源组切换控制系统将该资源对应的当前重启次数清零，并返回执行图1中的步骤S10。
在本发明其他实施例中，若该资源在预先确定的预设数量的切换节点上均运行失败，则执行步骤S23，所述数据库资源组切换控制系统将该资源离线处理，并停止监控该资源。
此外，步骤S20中，所述数据库资源组切换控制系统分析该资源不允许切换，则也是执行步骤S23，所述数据库资源组切换控制系统将该资源离线处理，并停止监控该资源。
本发明较佳实施例中，所述预设的切换规则为：按照预先确定的预设数量节点的切换顺序，逐个将该资源切换至下一切换节点上运行；若该资源在当前切换的节点上运行成功，则将该资源对应的当前重启次数清零，节点切换操作结束。若该资源在当前切换的切换节点上运行失败，且该资源对应的当前切换次数小于允许切换的次数，则将该资源切换至预先确定的其他切换节点上运行，并在将该资源对应的当前切换次数加1。若该资源在当前切换的切换节点上运行 失败，且该资源对应的当前切换次数大于等于允许切换的次数，则结束节点切换操作；可以理解，上述加1操作可在节点切换之前、切换之中或者切换之后进行，本申请对此并不做限制。(例如，可以按照在HOSTING_MEMBERS或者SERVER_POOLS中定义的节点次序切换该资源到其他的节点上运行，并在每次节点切换之前、切换之中或者切换之后将该资源对应的当前切换次数加1，例如，当前资源的切换次数控制是通过当前资源的第二动态属性FAILURE_COUNT和第二静态属性FAILURE_THRESHOLD来进行控制的，例如当前FAILURE_COUNT是2(说明该资源已经切换了2次)，FAILURE_THRESHOLD的定义值为4，则适用于服务器集群的数据库资源组切换控制系统确认该资源仍然可以在其他节点进行切换，会尝试继续切换该资源的运行节点，并将FAILURE_COUNT值加1)。
参阅图3所示，是本发明适用于服务器集群的数据库资源组切换控制系统较佳实施例的系统架构图。
所述数据库资源组切换控制系统的系统架构图统架构为：多个业务服务器1(图中以3个为例)，和所述多个业务服务器1通过网络3(例如，光纤网络)通信连接的多个存储装置2(图中以2个为例)。每个业务服务器1包括处理器1a及存储设备1b，处理器1a用于支撑整个业务服务器1的运行，存储设备1b用于存储各种数据及计算机指令。在本实施例中，存储设备上存储有数据资源组10、数据库资源切换控制系统11、集群管理系统12、操作系统13。
可以理解，存储设备1b可以包括一个或多个非易失性存储介质，如ROM、EPROM或Flash Memory等，其可以内置在对应的业务服务器1中，也可以以外界存储设备的形式构成业务服务器1的一部分。
其中，所述数据库资源组10包括数据库资源组标识11。进一步地，所述数据库资源组10还包括监听器12、虚拟IP地址13和数据库14三个资源。每个数据库资源组10的监听器12、虚拟IP地址13和数据库14这三个资源整体设计配置在一起，请参见图2所示，这样做的技术益处是：一、监听器12是依赖于虚拟IP地址13的，数据库14是相对独立的，这样就保证切换或者启动数据 库资源组10过程中各个资源的启动顺序是正确无误的；二、使得监听器12、虚拟IP地址13及数据库14这三个关键资源作为一个整体进行切换，确保数据库资源组10切换节点后可以对外提供服务。
所述集群管理系统12可以用于以单一系统的模式管理一组相互独立的、通过高速网络互联的业务服务器1，它们构成了一个组。
所述操作系统13为Linux操作系统、Windows操作系统或者其他任意适用的操作系统。
在本实施例中，数据库资源控制系统11包括至少一个计算机指令，该计算机指令可被处理器1a执行以实现本申请各实施例的数据库资源组切换控制方法。根据这些计算机指令的不同部分所执行的功能，这些计算机指令可被划分为多个功能模块，如资源组监控模块110以及资源组管理模块111。
所述资源组监控模块110用于每隔预设时间(例如，2分钟)，对各个数据库资源组10中的各个资源进行故障检查，以判断有没有资源组10中的资源发生故障。
所述资源组管理模块111用于当有资源组10中的资源发生故障时，对发生故障的资源执行重启或者将发生故障的资源切换至其他节点上运行。
详细地，若发生故障的资源不允许重启，所述资源组管理模块111将发生故障的资源切换至其他节点上运行；或者若发生故障的资源允许重启，所述资源组管理模块111控制发生故障的资源进行重启，并将该资源对应的当前重启次数加1。可以理解，该加1操作可在资源重启之前、重启之中或重启之后进行，本申请对此并无限制。
本发明其中一个实施例中，当前资源的重启次数控制是通过当前资源的第一动态属性值RESTART_COUNT和第一静态属性值RESTART_ATTEMPTS来进行控制的。若当前RESTART_ATTEMPTS的定义值为0，则代表当前资源不允许重启，若RESTART_ATTEMPTS的定义值为N，则代表当前资源允许重启的次数为N，若RESTART_COUNT是n，则说明该资源已经重启了n次。当n<N时，则确认该资源仍然可以在本地节点进行重启，会尝试重启该资源，并将 RESTART_COUNT值n加1；当n≥N时，则数据库资源组切换控制系统确认该资源不可以在本地节点继续进行重启。
例如：若RESTART_ATTEMPTS的定义值为3，则代表当前资源允许重启的次数为3，同时若当前RESTART_COUNT是2(说明该资源已经重启了2次)，则资源组管理模块111确认该资源仍然可以在本地节点进行重启，会尝试重启该资源，并将RESTART_COUNT值加1；若RESTART_ATTEMPTS的定义值为3，同时若当前RESTART_COUNT是3(说明该资源已经重启了3次)，则所述资源组管理模块111确认该资源不可以在本地节点继续进行重启。
本发明其他实施例中，所述资源组管理模块111进一步判断发生故障的资源是否重启成功。
若发生故障的资源重启成功，则由所述资源组监控模块110继续每隔预设时间(例如，2分钟)，对各个数据库资源组10中的各个资源进行故障检查，以判断有没有资源组10中的资源发生故障。
或者，若发生故障的资源重启失败，所述资源组管理模块111进一步将发生故障的资源切换至其他节点上运行。
在对发生故障的资源切换至其他节点上运行时，所述资源组管理模块111首先分析该资源是否允许切换。本实施例中，分析是否允许切换是基于当前资源的第二静态属性值FAILURE_THRESHOLD来进行分析的。若第二静态属性值FAILURE_THRESHOLD定义值为零，则代表当前资源不允许切换；如果第二静态属性值FAILURE_THRESHOLD定义值为P，则代表当前资源允许切换的次数为P，所述P为大于0的正整数。
若该资源不允许切换，则所述资源组管理模块111将该资源离线处理，并停止监控该资源。
若该资源允许切换，则所述资源组管理模块111将该资源按预设的切换规则切换至预先确定的预设数量的切换节点中的一个切换节点上运行。若该资源在一个切换的节点上运行成功，则所述资源组管理模块111将该资源对应的当前重启次数清零。若该资源在预先确定的预设数量的切换节点上均运行失败， 则所述资源组管理模块111将该资源离线处理，并停止监控该资源。
本发明较佳实施例中，所述预设的切换规则为：按照预先确定的预设数量节点的切换顺序，逐个将该资源切换至下一切换节点上运行；若该资源在当前切换的节点上运行成功，则将该资源对应的当前重启次数清零，节点切换操作结束。若该资源在当前切换的切换节点上运行失败，且该资源对应的当前切换次数小于允许切换的次数，则将该资源切换至预先确定的其他切换节点上运行，并将该资源对应的当前切换次数加1。若该资源在当前切换的切换节点上运行失败，且该资源对应的当前切换次数大于等于允许切换的次数，则结束节点切换操作；可以理解，上述加1操作可在切换之前、切换之中或者切换之后进行，本申请对此并不进行限制。(例如，可以按照在HOSTING_MEMBERS或者SERVER_POOLS中定义的节点次序切换该资源到其他的节点上运行，并在每次节点切换之前、切换之中或者切换之后将该资源对应的当前切换次数加1，例如，当前资源的切换次数控制是通过当前资源的第二动态属性FAILURE_COUNT和第二静态属性FAILURE_THRESHOLD来进行控制的，例如当前FAILURE_COUNT是2(说明该资源已经切换了2次)，FAILURE_THRESHOLD的定义值为4，则适用于服务器集群的数据库资源组切换控制系统确认该资源仍然可以在其他节点进行切换，会尝试继续切换该资源的运行节点，并将FAILURE_COUNT值加1)。
最后所应说明的是，以上实施例仅用以说明本发明的技术方案而非限制，尽管参照较佳实施例对本发明进行了详细说明，本领域的普通技术人员应当理解，可以对本发明的技术方案进行修改或等同替换，而不脱离本发明技术方案的精神和范围。

Claims (10)

  1. 一种适用于服务器集群的数据库资源组切换控制方法，其特征在于，该方法包括以下步骤：
    A、每隔预设时间对各个资源组中的各个资源进行故障检查；
    B、若没有资源组中的资源发生故障，则返回执行上述步骤A，若有资源组中的资源发生故障，则分析发生故障的资源是否允许重启；
    C、若发生故障的资源不允许重启，则将发生故障的资源切换至其他节点上运行；
    D、若发生故障的资源允许重启，则控制发生故障的资源进行重启，并将该资源对应的当前重启次数加1；及
    E、若发生故障的资源重启成功，则返回执行上述步骤A，若发生故障的资源重启失败，则将发生故障的资源切换至其他节点上运行。
  2. 如权利要求1所述的方法，其特征在于，所述步骤B中分析发生故障的资源是否允许重启包括：
    基于当前资源的第一动态属性值RESTART_COUNT和第一静态属性值RESTART_ATTEMPTS分析是否重启发生故障的资源，其中：
    若当前第一静态属性值RESTART_ATTEMPTS的定义值为0，则代表当前资源不允许重启，若第一静态属性值RESTART_ATTEMPTS的定义值为N，则代表当前资源允许重启的次数为N，同时若当前第一动态属性值RESTART_COUNT是n，代表该资源已经重启了n次；
    若n<N，则确认该资源仍然可以在本地节点进行重启，尝试重启该资源，并将动态属性值n加1；
    若n≥N，则确认该资源不可以在本地节点重启。
  3. 如权利要求1所述的方法，其特征在于，所述步骤C包括：
    F、基于当前资源的第二静态属性值FAILURE_THRESHOLD分析该资源是 否允许切换，其中，若第二静态属性值FAILURE_THRESHOLD定义值为0，则代表当前资源不允许切换，如果第二静态属性值FAILURE_THRESHOLD定义值为P，则代表当前资源允许切换的次数为P；
    G、若该资源允许切换，则将该资源按预设的切换规则切换至预先确定的预设数量的切换节点中的一个切换节点上运行；
    H、若该资源在一个切换的节点上运行成功，则将该资源对应的当前重启次数清零，并返回执行上述步骤A；及
    I、若该资源在预先确定的预设数量的切换节点上均运行失败，则将该资源离线处理，并停止监控该资源。
  4. 如权利要求3所述的方法，其特征在于，所述预设的切换规则为：
    按照预先确定的预设数量节点的切换顺序，将该资源切换至下一切换节点上运行；
    若该资源在当前切换的节点上运行成功，则将该资源对应的当前重启次数清零并结束节点切换操作；
    若该资源在当前切换的切换节点上运行失败，且该资源对应的当前切换次数小于允许切换的次数，则将该资源切换至预先确定的其他切换节点上运行，并将该资源对应的当前切换次数加1；及
    若该资源在当前切换的切换节点上运行失败，且该资源对应的当前切换次数大于等于允许切换的次数，则结束节点切换操作。
  5. 如权利要求3所述的方法，其特征在于，该方法还包括：
    若该资源不允许切换，则将该资源离线处理，并停止监控该资源。
  6. 一种服务器集群，包括多个服务器，其特征在于，每个服务器包括存储设备以及处理器，其中：
    所述存储设备，用于存储一个适用于服务器集群的数据库资源组切换控制 系统；
    所述处理器，用于执行所述适用于服务器集群的数据库资源组切换控制系统，以执行如下步骤：
    A、每隔预设时间对各个资源组中的各个资源进行故障检查；
    B、若没有资源组中的资源发生故障，则返回执行上述步骤A，若有资源组中的资源发生故障，则分析发生故障的资源是否允许重启；
    C、若发生故障的资源不允许重启，则将发生故障的资源切换至其他节点上运行；
    D、若发生故障的资源允许重启，则控制发生故障的资源进行重启，并将该资源对应的当前重启次数加1；及
    E、若发生故障的资源重启成功，则返回执行上述步骤A，若发生故障的资源重启失败，则将发生故障的资源切换至其他节点上运行。
  7. 如权利要求6所述的服务器集群，其特征在于，所述步骤B中分析发生故障的资源是否允许重启包括：
    基于当前资源的第一动态属性值RESTART_COUNT和第一静态属性值RESTART_ATTEMPTS分析是否允许重启发生故障的资源，其中：
    若当前第一静态属性值RESTART_ATTEMPTS的定义值为0，则代表当前资源不允许重启，若第一静态属性值RESTART_ATTEMPTS的定义值为N，则代表当前资源允许重启的次数为N，同时若当前第一动态属性值RESTART_COUNT是n，代表该资源已经重启了n次；
    若n<N，则确认该资源仍然可以在本地节点进行重启，尝试重启该资源，并将动态属性值n加1；
    若n≥N，则数据库资源组切换控制系统确认该资源不可以在本地节点重启。
  8. 如权利要求6所述的服务器集群，其特征在于，所述步骤C包括：
    F、基于当前资源的第二静态属性值FAILURE_THRESHOLD分析该资源是 否允许切换，其中，如果第二静态属性值FAILURE_THRESHOLD定义值为0，则代表当前资源不允许切换，如果第二静态属性值FAILURE_THRESHOLD定义值为P，则代表当前资源允许切换的次数为P；
    G、若该资源允许切换，则将该资源按预设的切换规则切换至预先确定的预设数量的切换节点中的一个切换节点上；
    H、若该资源在一个切换的节点上运行成功，则将该资源对应的当前重启次数清零，并返回执行上述步骤A；及
    I、若该资源在预先确定的预设数量的切换节点上均运行失败，则将该资源离线处理，并停止监控该资源。
  9. 如权利要求8所述的服务器集群，其特征在于，所述预设的切换规则为：
    按照预先确定的预设数量节点的切换顺序，将该资源切换至下一切换节点上运行；
    若该资源在当前切换的节点上运行成功，则将该资源对应的当前重启次数清零并结束节点切换操作；
    若该资源在当前切换的切换节点上运行失败，且该资源对应的当前切换次数小于允许切换的次数，则将该资源切换至预先确定的其他切换节点上运行，并将该资源对应的当前切换次数加1；及
    若该资源在当前切换的切换节点上运行失败，且该资源对应的当前切换次数大于等于允许切换的次数，则结束节点切换操作。
  10. 如权利要求8所述的服务器集群，其特征在于，所述处理器在调用并执行所述适用于服务器集群的数据库资源组切换控制系统还执行如下步骤：
    若该资源不允许切换，则将该资源离线处理，并停止监控该资源。
PCT/CN2017/089876 2016-06-24 2017-06-23 服务器集群及适用于该集群的数据库资源组切换控制方法 Ceased WO2017220033A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610466505.6 2016-06-24
CN201610466505.6A CN106130763A (zh) 2016-06-24 2016-06-24 服务器集群及适用于该集群的数据库资源组切换控制方法

Publications (1)

Publication Number Publication Date
WO2017220033A1 true WO2017220033A1 (zh) 2017-12-28

Family

ID=57268107

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/089876 Ceased WO2017220033A1 (zh) 2016-06-24 2017-06-23 服务器集群及适用于该集群的数据库资源组切换控制方法

Country Status (2)

Country Link
CN (1) CN106130763A (zh)
WO (1) WO2017220033A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110569149A (zh) * 2019-09-16 2019-12-13 上海新炬网络技术有限公司 基于故障探测触发Oracle容灾自动应急切换的方法
CN114546427A (zh) * 2022-02-21 2022-05-27 江苏苏宁银行股份有限公司 一种基于DNS和MGR的MySQL高可用实现方法
CN115484267A (zh) * 2022-09-15 2022-12-16 中国联合网络通信集团有限公司 多集群部署处理方法、装置、电子设备和存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106130763A (zh) * 2016-06-24 2016-11-16 平安科技（深圳）有限公司 服务器集群及适用于该集群的数据库资源组切换控制方法
CN107092690A (zh) * 2017-04-24 2017-08-25 广东浪潮大数据研究有限公司 一种数据库僵死的检测方法及装置
CN107911230B (zh) * 2017-10-24 2020-08-28 丹露成都网络技术有限公司 基于metaq集群的自动监控恢复方法
CN110162428A (zh) * 2019-05-17 2019-08-23 中国铁道科学研究院集团有限公司 数据同步方法及装置、电子设备和计算机可读存储介质
CN111008097A (zh) * 2019-12-06 2020-04-14 深圳震有科技股份有限公司 基于服务信息的服务器自动处理方法及系统、计算机设备
CN112751782B (zh) * 2020-12-29 2022-09-30 微医云(杭州)控股有限公司 基于多活数据中心的流量切换方法、装置、设备及介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103152419A (zh) * 2013-03-08 2013-06-12 中标软件有限公司 一种云计算平台的高可用集群管理方法
CN105357038A (zh) * 2015-10-26 2016-02-24 北京百度网讯科技有限公司 监控虚拟机集群的方法和系统
CN105517030A (zh) * 2015-11-24 2016-04-20 广东欧珀移动通信有限公司 网络通信功能异常的处理方法、调制解调器及移动终端
CN106130763A (zh) * 2016-06-24 2016-11-16 平安科技（深圳）有限公司 服务器集群及适用于该集群的数据库资源组切换控制方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7925761B2 (en) * 2009-06-30 2011-04-12 Novell, Inc. System and method for implementing a dead man dependency technique for cluster resources
CN104660386A (zh) * 2015-03-03 2015-05-27 浪潮电子信息产业股份有限公司 一种基于安腾平台下提高db2容灾高可用性的方法
CN105183591A (zh) * 2015-09-07 2015-12-23 浪潮(北京)电子信息产业有限公司 一种高可用集群的实现方法及系统
CN105391790A (zh) * 2015-11-26 2016-03-09 国家电网公司 类RAC One Node的数据库高可用方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103152419A (zh) * 2013-03-08 2013-06-12 中标软件有限公司 一种云计算平台的高可用集群管理方法
CN105357038A (zh) * 2015-10-26 2016-02-24 北京百度网讯科技有限公司 监控虚拟机集群的方法和系统
CN105517030A (zh) * 2015-11-24 2016-04-20 广东欧珀移动通信有限公司 网络通信功能异常的处理方法、调制解调器及移动终端
CN106130763A (zh) * 2016-06-24 2016-11-16 平安科技（深圳）有限公司 服务器集群及适用于该集群的数据库资源组切换控制方法

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110569149A (zh) * 2019-09-16 2019-12-13 上海新炬网络技术有限公司 基于故障探测触发Oracle容灾自动应急切换的方法
CN110569149B (zh) * 2019-09-16 2023-07-25 上海新炬网络技术有限公司 基于故障探测触发Oracle容灾自动应急切换的方法
CN114546427A (zh) * 2022-02-21 2022-05-27 江苏苏宁银行股份有限公司 一种基于DNS和MGR的MySQL高可用实现方法
CN115484267A (zh) * 2022-09-15 2022-12-16 中国联合网络通信集团有限公司 多集群部署处理方法、装置、电子设备和存储介质

Also Published As

Publication number Publication date
CN106130763A (zh) 2016-11-16

Similar Documents

Publication Publication Date Title
WO2017220033A1 (zh) 服务器集群及适用于该集群的数据库资源组切换控制方法
US10983880B2 (en) Role designation in a high availability node
EP4083786A1 (en) Cloud operating system management method and apparatus, server, management system, and medium
US9960963B2 (en) Dynamic client fail-over during a rolling patch installation based on temporal server conditions
CN103201724B (zh) 在高可用性虚拟机环境中提供高可用性应用程序
US10924538B2 (en) Systems and methods of monitoring software application processes
WO2010122709A1 (ja) 若化処理装置、若化処理システム、コンピュータプログラムおよびデータ処理方法
CN103152419A (zh) 一种云计算平台的高可用集群管理方法
EP3550436A1 (en) Method and apparatus for detecting and recovering fault of virtual machine
CN105095001A (zh) 分布式环境下虚拟机异常恢复方法
WO2017215430A1 (zh) 一种集群内的节点管理方法及节点设备
CN110865907A (zh) 在主服务器与从服务器之间提供服务冗余的方法和系统
KR20150111608A (ko) 가상화 서버의 이중화를 위한 제어 방법 및 이를 위한 가상화 제어 장치
WO2017049912A1 (zh) 一种jslee容器的业务处理方法及系统
CN117407219A (zh) 针对模型训练任务的异常处理系统、集群、设备和介质
US10789129B1 (en) Rolling restoration of enterprise business services following service disruption
US10193744B1 (en) Mass restoration of enterprise business services following service disruption
CN114130035B (zh) 一种用户匹配方法、装置、设备及存储介质
CN103118121B (zh) 一种高可用集群在虚拟化技术中的应用方法
US12386649B2 (en) Server maintenance control device, server maintenance system, server maintenance control method, and program
CN113377702A (zh) 两节点集群启动的方法及装置、电子设备和存储介质
CN105187482B (zh) 一种PaaS平台故障自愈实现的方法及消息服务器
US10365934B1 (en) Determining and reporting impaired conditions in a multi-tenant web services environment
CN112612652A (zh) 分布式存储系统异常节点重启方法及系统
CN112433860B (zh) 一种事件管理的方法、系统、设备及介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17814770

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 9.04.2019)

122 Ep: pct application non-entry in european phase

Ref document number: 17814770

Country of ref document: EP

Kind code of ref document: A1