Methods, devices and systems for initiating, forming and joining memberships in distributed computing systems

• US 9,900,381 B2
• Filed: 03/16/2016
• Issued: 02/20/2018
• Est. Priority Date: 12/28/2012
• Status: Active Grant

• Current Assignee: Cirata Incorporated
• Original Assignee: WANdisco, Inc.
• Inventors: Aahlad, Yeturu, Parkin, Michael, Akhtar, Naeem
• Primary Examiner(s): NANO, SARGON N
• Application Number:
  US15/071,447
• Publication Number:
  US 20170026465A1
• Time in Patent Office: 706 Days
• CPC Class Codes: H04L 12/185 with management of multicast group membership
• 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/1044 Group management mechanisms management of multicast group membership H04L12/185; reconfiguring of node membership in a computing system to eliminate errors G06F11/1425
• CPC Class Codes: H04L 67/1046 Joining mechanisms
• CPC Class Codes: H04L 67/1048 Departure or maintenance mechanisms

Abstract

A computer-implemented method of deploying a membership of nodes in a distributed computing system may comprise selecting nodes to be part of a membership of nodes; creating a membership task identifying a membership creator node as the node that is creating the membership and comprising a membership target identifying at least one node of the distributed computing system that is to become a member of the membership; and creating a beacon configured to send a create membership message to each identified node, the create membership message comprising at least an identity of the membership task and an identification of the membership. Upon receiving a response from a node in the membership target, the node from which the response was received may be removed from the beacon. The membership may be deployed when a response has been received from each of the nodes identified in the membership target.

Claims

1. A computer-implemented method of deploying a membership of distributed compute nodes in a distributed computing system, comprising;

selecting distributed compute nodes to be part of membership of distributed compute nodes to be deployed;

creating a membership task identifying a membership creator distributed compute node as the distributed compute node that is creating the membership to be deployed, the membership task further comprising a membership target identifying at least one distributed compute node of the distributed computing system that is to become a member of the membership, the membership target not including the membership creator distributed compute node;

repeatedly sending, over a computer network, a create membership message to each distributed compute node identified in the membership target, the create membership message comprising at least an identity of the membership task and an identification of the membership to be deployed;

upon receiving a response from a distributed compute node in the membership target, deploying the membership when a response has been received from each of the distributed compute nodes identified in the membership target, and

after a response has been received from each of the distributed compute nodes identified in the membership target and the membership has been deployed, storing the deployed membership task in a persistent memory;

restarting, by the membership creator distributed compute node, the membership task and repeatedly resending duplicate create membership messages to at least one of the distributed compute nodes identified in the membership target if the membership creator distributed compute node fails before it has received responses from each of the distributed compute nodes identified in the membership target.

2. The computer-implemented method of claim 1, further comprising assigning at least one role to the distributed compute nodes selected to be part of the membership to be deployed.

3. The computer-implemented method of claim 2, wherein the at least one role comprises a role of a membership creator and a role of a membership target.

4. The computer-implemented method of claim 1, wherein the create membership message further comprises an identification of the membership creator distributed compute node and sufficient information to enable communication therewith.

5. The computer-implemented method of claim 4, wherein the information sufficient to communicate with the membership creator distributed compute node comprises at least one of an identification, a location, a hostname and port of the membership creator distributed compute node.

6. The computer-implemented method of claim 1, wherein the membership task is identified by a unique task identifier.

7. The computer-implemented method of claim 1, wherein deployment of the membership is idempotent.

8. The computer-implemented method of claim 1, wherein the response comprises the identification of the membership to be deployed and a distributed compute node and location identity of the distributed compute node in the membership target sending the response.

9. The computer-implemented method of claim 1, further comprising:

extracting the identification of the membership to be deployed from the response;

removing the responding distributed compute node from the distributed compute nodes identified in the membership target to which the create membership message is repeatedly sent; and

checking whether a response has been received from each of the distributed compute nodes identified in the membership target.

10. A computing device, comprising:

a memory;

a processor, and

a plurality of processes spawned by the processor, the processes being configured to cause the computing device to deploy a membership of distributed compute nodes in a distributed computing system, the plurality of processes comprising processing logic to;

select distributed compute nodes to be part of membership of distributed compute nodes to be deployed;

create a membership task identifying a membership creator distributed compute node as the distributed compute node that is creating the membership to be deployed, the membership task further comprising a membership target identifying at least one distributed compute node of the distributed computing system that is to become a member of the membership, the membership target not including the membership creator distributed compute node;

repeatedly send, over a computer network, a create membership message to each distributed compute node identified in the membership target, the create membership message comprising at least an identity of the membership task and an identification of the membership to be deployed;

upon receiving a response from a distributed compute node in the membership target, deploy the membership when a response has been received from each of the distributed compute nodes identified in the membership target, and

after a response has been received from each of the distributed compute nodes identified in the membership target and the membership has been deployed, store the deployed membership task in a persistent memory;

restart, by the membership creator distributed compute node, the membership task and repeatedly resend duplicate create membership messages to at least one of the distributed compute nodes identified in the membership target if the membership creator distributed compute node fails before it has received responses from each of the distributed compute nodes identified in the membership target.

11. The computing device of claim 10, further comprising processing logic to assign at least one role to the distributed compute nodes selected to be part of the membership to be deployed.

12. The computing device of claim 11, wherein the at least one role comprises a role of a membership creator and a role of a membership target.

13. The computing device of claim 10, wherein the create membership message further comprises an identification of the membership creator distributed compute node and sufficient information to enable communication therewith.

14. The computing device of claim 13, wherein the information sufficient to communicate with the membership creator distributed compute node comprises at least one of an identification, a location, a hostname and port of the membership creator distributed compute node.

15. The computing device of claim 10, wherein the membership task is identified by a unique task identifier.

16. The computing device of claim 10, wherein deployment of the membership is idempotent.

17. The computing device of claim 10, wherein the response comprises the identification of the membership to be deployed and a distributed compute node and location identity of the distributed compute node in the membership target sending the response.

18. The computing device of claim 10, further comprising processing logic to:

extract the identification of the membership to be deployed from the response;

remove the responding distributed compute node from the distributed compute nodes identified in the membership target to which the create membership message is repeatedly sent; and

check whether a response has been received from each of the distributed compute nodes identified in the membership target.

19. A non-transitory machine-readable medium having data stored thereon representing sequences of instructions which, when executed by a computing device, cause the computing device to deploy a membership of distributed compute nodes in a distributed computing system by:

selecting distributed compute nodes to be part of membership of nodes to be deployed;

creating a membership task identifying a membership creator distributed compute node as the distributed compute node that is creating the membership to be deployed, the membership task further comprising a membership target identifying at least one distributed compute node of the distributed computing system that is to become a member of the membership, the membership target not including the membership creator distributed compute node;

repeatedly sending, over a computer network, a create membership message to each distributed compute node identified in the membership target, the create membership message comprising at least an identity of the membership task and an identification of the membership to be deployed;

upon receiving a response from a distributed compute node in the membership target, deploying the membership when a response has been received from each of the distributed compute nodes identified in the membership target, and after a response has been received from each of the distributed compute nodes identified in the membership target and the membership has been deployed, storing the deployed membership task in a persistent memory;

restarting, by the membership creator distributed compute node, the membership task and repeatedly resending duplicate create membership messages to at least one of the distributed compute nodes identified in the membership target if the membership creator distributed compute node fails before it has received responses from each of the distributed compute nodes identified in the membership target.