Method for controlling operations of server cluster

• US 20150143157A1
• Filed: 08/05/2014
• Published: 05/21/2015
• Est. Priority Date: 11/19/2013
• Status: Active Grant

• Current Assignee: Synology Incorporated
• Original Assignee: Synology Incorporated
• Inventors: Chen, Kan-Yueh, Liu, Jia-Yu
• Granted Patent: US 9,354,995 B2
• Time in Patent Office: Days
• US Class Current: 714/4.3
• CPC Class Codes: G06F 11/203 using migration
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• CPC Class Codes: H04L 67/1048 Departure or maintenance mechanisms
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

A server cluster has a plurality of application servers. During failover of a failed node of the application servers, right to use of internet protocol (IP) address of the failed node is transferred to a surviving node of the server cluster according to a failed-link index of the failed node, the total number of surviving nodes of the server cluster, and successful link indexes of the surviving nodes.

Claims

1. A method of controlling operations of a server cluster, the server cluster comprising m application servers, the method comprising:

setting surviving nodes of the m application servers to successful-link indexes of different values;

setting failed nodes of the m application servers to failed-link indexes of different values; and

when an s^th application server of the m application servers is a failed node and failover is performed on the s^th application server, transferring right to use of an internet protocol (IP) address of the s^th application server to a t^th application server of the m application servers according to a failed-link index of the s^th application server, a number of the surviving nodes of the m application servers, and a successful-link index of each of the surviving nodes;

wherein m>

1, m≧

s>

0, m≧

t>

0, and m, s, and t are positive integers.

2. The method of claim 1, wherein transferring the right to use of the internet protocol address of the s^th application server to the t^th application server of the m application servers according to the failed-link index of the s^th application server, the number of the surviving nodes of the m application servers, and the successful-link index of each of the surviving nodes comprises:

transferring the right to use of the internet protocol address of the s^th application server to the t^th application server of the m application servers according to a remainder of the failed-link index of the s^th application server divided by the number of surviving nodes and the successful-link index of each of the surviving nodes;

wherein the successful-link index of the t^th application server is equal to the remainder.

3. The method of claim 1, further comprising:

setting a sequence of the m application servers;

wherein the successful-link index of each of the surviving nodes and a failed-link index of each of the failed nodes are set according to the sequence.

4. The method of claim 3, wherein the sequence is set according to internet protocol addresses of the m application servers.

5. The method of claim 3, wherein the sequence is set according to media access control (MAC) addresses of the m application servers.

6. The method of claim 1, further comprising:

the m application servers issuing Packet Internet Groper (PING) commands to one another so as to individually establish a surviving node table and a failed node table, wherein the surviving node table is used to record each of the successful-link indexes, and the failed node table is used to record each of the failed-link indexes.

7. The method of claim 1, further comprising:

each application server determining whether links between the each application server and other application servers are interrupted based on TCP/IP connections among the m application servers so as to establish a surviving node table and a failed node table of the each application server, wherein the surviving node table is used to record each of the successful-link indexes, and the failed node table is used to record each of the failed-link indexes.