US Patent 8,983,876 — System and method for using cluster level quorum to prevent split brain scenario in a data grid cluster

Life of the patent

14 dated events

⤢ drag to zoom

ProsecutionTerm & feeshover for detail · click to open

Abstract

A system and method is described for use with a data grid cluster, which uses cluster quorum to prevent split brain scenario. The data grid cluster includes a plurality of cluster nodes, each of which runs a cluster service. Each cluster service collects and maintains statistics regarding communication flow between its cluster node and the other cluster nodes in the data grid cluster. The statistics are used to determine a status associated with other cluster nodes in the data grid cluster whenever a disconnect event happens. The data grid cluster is associated with a quorum policy, which is defined in a cache configuration file, and which specifies a time period that a cluster node will wait before making a decision on whether or not to evict one or more cluster nodes from the data grid cluster.

Claims

20 · 3 independent · depth 5

20 granted claims

›1.independentA system for using cluster quorum to prevent split brain scenario in a distributed data grid cluster, comprising:na data grid cluster comprising a plu…+9

A system for using cluster quorum to prevent split brain scenario in a distributed data grid cluster, comprising:na data grid cluster comprising a plurality of cluster nodes wherein each cluster node comprises a microprocessor;a plurality of cluster services, wherein each cluster service runs on a particular cluster node of said plurality of cluster nodes in the data grid cluster and collects and maintains statistics regarding communication flow between the particular cluster node and other cluster nodes in the data grid cluster, and wherein the statistics are used by the data grid cluster to determine a status associated with each other cluster node in the data grid cluster when a disconnection event happens in the data grid cluster;a cluster quorum policy defined in a cache configuration file associated with the data grid cluster, wherein the cluster quorum policy specifies a minimum number of cluster nodes required to permit a decision whether to evict one or more cluster nodes from the data grid cluster, and a time period that the data grid cluster defers to make a decision on whether or not to evict one or more cluster nodes from the data grid cluster; andwherein, when one or more cluster nodes are detected to have been disconnected (disconnected nodes) from the data grid cluster as a results of a disconnection event,nthe data grid cluster defers to make a decision on whether or not to evict the disconnected nodes from the data grid cluster for the time period specified in the cluster quorum policy,if a connection is reestablished to the disconnected nodes prior to expiration of the time period specified in the cluster quorum policy, the data grid cluster does not evict the disconnected nodes; andif the connection is not reestablished to the disconnected nodes prior to expiration of the time period specified in the cluster quorum policy and a number of cluster nodes remaining in the cluster after excluding the disconnected nodes is equal to at least the minimum number of cluster nodes required to permit a decision whether to evict one or more cluster nodes from the data grid cluster, the data grid cluster does evict the disconnected nodes.

›2.↳ 1The system according to claim 1, wherein:neach cluster service is a root cluster service, and wherein there is exactly one root cluster service runnin…d2

›3.↳ 1The system according to claim 1, wherein:nthe status associated with each other cluster node in the data grid cluster is one ofna node that is definit…d2

›4.↳ 1The system according to claim 1, wherein:nthe data grid cluster automatically recovers from the disconnection event to provide services to users.d2

›5.↳ 1The system according to claim 1, wherein:nif the connection is not reestablished to the disconnected nodes prior to expiration of the time period spec…d2

›6.↳ 1The system according to claim 1, further comprising:nthe data grid cluster supports a pluggable interface that allows users to implement custom polici…d2+3

›10.↳ 1The system according to claim 1, wherein:na cluster node in the data grid cluster is considered becoming a suspected cluster member when it has not re…d2

›11.independentA method for using cluster level quorum in a data grid cluster comprising a plurality of cluster nodes, the method comprising:nrunning a cluster servi…+7

A method for using cluster level quorum in a data grid cluster comprising a plurality of cluster nodes, the method comprising:nrunning a cluster service on each cluster node of the plurality of clusters nodes in the data grid cluster;collecting and maintaining, via the cluster service running on each particular cluster node, statistics regarding communication flow between the particular cluster node and other cluster nodes in the data grid cluster;determining a status associated with each cluster node in the data grid cluster when a disconnection event happens;providing a cluster quorum policy defined in a cache configuration file associated with the data grid cluster, wherein the cluster quorum policy specifies a minimum number of cluster nodes required to permit a decision whether to evict one or more cluster nodes from the data grid cluster, and a time period that the data grid cluster defers to make a decision on whether or not to evict one or more cluster nodes from the data grid cluster; andin response to detecting one or more cluster nodes to have been disconnected (disconnected nodes) from the data grid cluster as a results of a disconnection event,ndeferring to make a decision for the time period specified in the cluster quorum policy on whether or not to evict the disconnected nodes from the data grid cluster based on the cluster quorum policy,if a connection is reestablished to the disconnected nodes prior to expiration of the time period specified in the cluster quorum policy, determining not to evict the disconnected nodes; andif the connection is not reestablished to the disconnected nodes prior to expiration of the time period specified in the cluster quorum policy and a number of cluster nodes remaining in the cluster after excluding the disconnected nodes is equal to at least the minimum number of cluster nodes required to permit a decision whether to evict one or more cluster nodes from the data grid cluster, the data grid cluster does evict the disconnected nodes.

›12.↳ 11The method of claim 11, further comprising:nrunning each cluster service as a root cluster service, wherein there is exactly one root cluster service …d2

›13.↳ 11The method of claim 11, wherein the status associated with each other cluster node in the data grid cluster is one of:na node that is definitely dead;…d2

›14.↳ 11The method of claim 11, further comprising:nrequiring user input to evict the disconnected nodes if the connection is not reestablished to the disconn…d2

›15.↳ 11The method of claim 11, further comprising:nproviding a pluggable interface that allows users to implement custom policies to configure the data grid …d2

›16.↳ 11The method of claim 11, further comprising:nproviding a pluggable interface that allows users to implement a custom policy to configure the data grid …d2

›17.↳ 11The method of claim 11, further comprising:nproviding a pluggable interface that allows users to implement a custom policy to configure the data grid …d2

›18.↳ 11The method of claim 11, further comprising:nproviding a pluggable interface that allows users to implement a custom policy to configure the data grid …d2

›19.independentA non-transitory machine readable medium having instructions stored thereon for using cluster quorum to prevent split brain scenario in a distributed …+1

A non-transitory machine readable medium having instructions stored thereon for using cluster quorum to prevent split brain scenario in a distributed data grid cluster comprising a plurality of cluster nodes, which instructions, when executed by a system, cause the system to perform steps comprising:nrunning a cluster service on each cluster node of the plurality of clusters nodes in the data grid cluster;collecting and maintaining, via the cluster service running on each particular cluster node, statistics regarding communication flow between the particular cluster node and other cluster nodes in the data grid cluster;determining a status associated with each cluster node in the data grid cluster when a disconnection event happens;providing a cluster quorum policy defined in a cache configuration file associated with the data grid cluster, wherein the cluster quorum policy specifies a minimum number of cluster nodes required to permit a decision whether to evict one or more cluster nodes from the data grid cluster, and a time period that the data grid cluster defers to make a decision on whether or not to evict one or more cluster nodes from the data grid cluster; andin response to detecting one or more cluster nodes to have been disconnected (disconnected nodes) from the data grid cluster as a results of a disconnection event,ndeferring to make a decision for the time period specified in the cluster quorum policy on whether or not to evict the disconnected nodes from the data grid cluster based on the cluster quorum policy,if a connection is reestablished to the disconnected nodes prior to expiration of the time period specified in the cluster quorum policy, determining not to evict the disconnected nodes; andif the connection is not reestablished to the disconnected nodes prior to expiration of the time period specified in the cluster quorum policy and a number of cluster nodes remaining in the cluster after excluding the disconnected nodes is equal to at least the minimum number of cluster nodes required to permit a decision whether to evict one or more cluster nodes from the data grid cluster, the data grid cluster does evict the disconnected nodes.

Classifications

3 codes

IPC · International Patent Classification

Section G — Physics

G06F11/14
G06F9/50

USPC · US Patent Classification

706/10

Claim changes

Soon

Coming soonHow the claims changed between publication and grant

See which claims were amended, added or cancelled during examination, with every added and removed word marked.

AmendedAddedCancelledUnchanged

The published claims of this patent are not paired with the granted ones in what we hold.

File wrapper

⤢ drag to zoom

USPTOApplicanthover for detail · click to open

Pendency

3.2 y

1,155 days filing → grant

Office actions

2

non-final + final

Responses

2

2 RCE

Examiner

Ilya Traktovenko

art unit —

Law firm

Law firm · Log in to unlock

Citations: 54 back · 0 forward

See the full prosecution history — every USPTO and applicant action on this file, in order.

Log in to unlock

Term & fees

See the term timeline — pendency span, in-force span, the maintenance fees paid and both computed expiry dates.

Log in to unlock

Priority chain

2 priority documents

Priority

28 Jan 2011

earliest claimed

›Priority documents — 2

Type	Document	Date
provisional	US 61437546	28 Jan 2011
related publication	US 20120197822 A1	2 Aug 2012

Validity challenges

See the validity challenges on record — reexaminations, IPRs and PGRs, with their institution decisions and outcomes.

Log in to unlock

Citations

See every patent this one cites and every patent that cites it back — publication, assignee, and how each one was found.

Log in to unlock