| US20170026468A1 | 2017-01-26 |
| Claims Following is the claim for this invention: - 1. In this invention we have various groups of virtual machines or nodes in the cloud forming different clusters. We will use Gossip-based protocols for diffusing information or object in large-scale distributed group of virtual machines or cluster. Nodes in the cloud might use multiple objects and hence might belong to multiple gossip groups or clusters. General observation is that gossip messages are frequently short, perhaps containing just a few tens of bytes. Hence like other gossip systems we push only object version numbers to optimise message exchanges in the cluster, so if the destination node does not have the latest version of the object, it can request a copy from the exchange node (or source node having the latest version of object copy). An individual object version number can be as short as 12 to 16 bytes in total. The second observation is that there is negligible difference in network overhead between a UDP datagram packet containing 15 bytes or 1500 bytes, as long as the datagram is not fragmented and hence stacking multiple object version numbers in a single datagram packet from node s to node d is possible and imposes practically no additional network overhead. Hence we include in a single datagram packet from node s to node d, object version numbers of all new objects of gossip groups or clusters for which both nodes s and d belong available for dissemination from node s (or invoked by an outside client service by providing object, it’s version and cluster or gossip groups). We can take a step further by including object version numbers for objects that node d is not interested in but present in gossip groups or clusters for which both nodes s and d belong, node d might in turn propagate these object version numbers to nodes that will benefit from them but redirect the request for object copy to node s (or source node having the object copy as node d was not interested in that object copy but we still forwarded it the object version number for faster dissemination). We can use the above Object Dissemination Service for doing health checks of various services running on different nodes in a cluster or for different nodes in a cluster. The above novel technique of providing Object Dissemination Service in cloud is the claim for this invention. |
In this invention we have various groups of virtual machines or nodes in the cloud forming different clusters. We will use Gossip-based protocols for diffusing information or object in large-scale distributed group of virtual machines or cluster. Nodes in the cloud might use multiple objects and hence might belong to multiple gossip groups or clusters. General observation is that gossip messages are frequently short, perhaps containing just a few tens of bytes. Hence like other gossip systems we push only object version numbers to optimise message exchanges in the cluster, so if the destination node does not have the latest version of the object, it can request a copy from the exchange node (or source node having the latest version of object copy). An individual object version number can be as short as 12 to 16 bytes in total. The second observation is that there is negligible difference in network overhead between a UDP datagram packet containing 15 bytes or 1500 bytes, as long as the datagram is not fragmented and hence stacking multiple object version numbers in a single datagram packet from node s to node d is possible and imposes practically no additional network overhead. Hence we include in a single datagram packet from node s to node d, object version numbers of all new objects of gossip groups or clusters for which both nodes s and d belong available for dissemination from node s (or invoked by an outside client service by providing object, it’s version and cluster or gossip groups). We can take a step further by including object version numbers for objects that node d is not interested in but present in gossip groups or clusters for which both nodes s and d belong, node d might in turn propagate these object version numbers to nodes that will benefit from them but redirect the request for object copy to node s (or source node having the object copy as node d was not interested in that object copy but we still forwarded it the object version number for faster
dissemination). We can use the above Object Dissemination Service for doing health checks of various services running on different nodes in a cluster or for different nodes in a cluster.