Differentiating connectivity issues from server failures
First Claim
Patent Images
1. A method to be executed at least in part in a computing device for differentiating connectivity issues from server failures, the method comprising:
- determining an interruption in a connectivity status of a server of a server group;
determining connectivity status of at least one other server within the same server group;
inferring one of a server failure and a network failure based on the connectivity statuses of the servers in the server group; and
routing messages to the server based on the inference bysuppressing resubmission of redundant messages until a decision is made whether the inference is one of a server failure and a network failure;
re-routing messages intended for the server to the at least one other server if the inference is server failure; and
queuing the messages for later delivery if the inference is network failure.
2 Assignments
0 Petitions
Accused Products
Abstract
A status of connectivity between servers of different sites (locations) is used to infer whether a network or a server failure has occurred such that data between the servers can be routed more efficiently reducing unnecessary network traffic due to duplicate messages. Servers may be grouped based on location or other characteristics and connectivity status determined based on the communication status of individual servers and their respective groups.
-
Citations
19 Claims
-
1. A method to be executed at least in part in a computing device for differentiating connectivity issues from server failures, the method comprising:
-
determining an interruption in a connectivity status of a server of a server group; determining connectivity status of at least one other server within the same server group; inferring one of a server failure and a network failure based on the connectivity statuses of the servers in the server group; and routing messages to the server based on the inference by suppressing resubmission of redundant messages until a decision is made whether the inference is one of a server failure and a network failure; re-routing messages intended for the server to the at least one other server if the inference is server failure; and queuing the messages for later delivery if the inference is network failure. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A computing system for differentiating connectivity issues from server failures, the system comprising:
-
a first site comprising a plurality of servers grouped based on one of;
a location of the servers and a function of the servers;a first server part of a second site comprising a plurality of servers coupled to the servers of the first site via a network, the first server configured to; detect an interruption in a connectivity status of a server of the first site based on a heartbeat network connection; determine connectivity status of remaining servers of the first site; infer one of a server failure and a network failure based on the connectivity statuses of the servers of the first site; suppress resubmission of redundant messages until a decision is made whether the inference is one of a server failure and a network failure; re-route messages intended for the server to at least one the remaining servers of the first site if the inference is server failure; and queue the messages at the first server for later delivery if the inference is network failure. - View Dependent Claims (12, 13, 14, 15)
-
-
16. A computer-readable storage medium with instructions stored thereon for differentiating connectivity issues from server failures, the instructions comprising:
-
detecting an interruption in a connectivity status of a primary server of a site comprising a plurality of high availability servers based on one of;
a number of heartbeat checks and a period of no-response;determining connectivity status of remaining servers of the site; inferring one of a server failure and a network failure based on the connectivity statuses of the servers of the site; re-routing the messages intended for the primary server to at least one the remaining servers of the site if the inference is server failure; queuing the messages for later delivery if the inference is network failure; checking to determine whether the primary server is reconnected; and if the primary server is reconnected, continuing to route the messages intended for the primary server to the primary server. - View Dependent Claims (17, 18, 19)
-
Specification