System and method for supporting service level quorum in a data grid cluster

• US 10,122,595 B2
• Filed: 12/30/2015
• Issued: 11/06/2018
• Est. Priority Date: 01/28/2011
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: ORCALE INTERNATIONAL CORPORATION
• Inventors: Lee, Robert H., Falco, Mark, Glezyer, Gene, Purdy, Cameron
• Primary Examiner(s): Tokuta, Shean
• Application Number:
  US14/984,648
• Publication Number:
  US 20160119197A1
• Time in Patent Office: 1,042 Days
• CPC Class Codes: G06F 11/1425 by reconfiguration of node membership
• CPC Class Codes: G06F 2209/505 Clust
• CPC Class Codes: G06F 9/5061 Partitioning or combining of resources
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• 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/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

A system and method is described for use with a data grid cluster, for supporting service level quorum in the data grid cluster. The data grid cluster includes a plurality of cluster nodes that support performing at least one service action. A quorum policy, defined in a cache configuration file associated with the data grid cluster, can specify a minimum number of service members that are required in the data grid cluster for performing the service action. The data grid cluster uses the quorum policy to determine whether the service action is allowed to be performed, based on a present state of the plurality of cluster nodes in the data grid cluster.

Claims

1. A system for supporting service level quorum in a data grid cluster, comprising:

a plurality of computer servers, the data grid cluster executing thereon, wherein the data grid cluster comprises a plurality of interoperating cluster nodes in the data grid cluster, wherein the data grid cluster supports performing a plurality of services including a root cluster service performed by all of the plurality of interoperating cluster nodes, and at least one other cluster service performed by at least one of the plurality of interoperating cluster nodes specified as a service member of the at least one other cluster service, and wherein the at least one other cluster service provides a different type of service than the root cluster service;

a root cluster service quorum policy, wherein the root cluster service quorum policy specifies a minimum number of qualified root cluster service members that are required for performing root cluster service actions of said root cluster service;

a cache configuration file associated with the data grid cluster, the cache configuration file accessible to all of the plurality of interoperating cluster nodes and including;

a service name element for a first cluster service of the at least one other cluster service that uniquely identifies a name of the first cluster service; and

a quorum policy scheme element that contains a reference to a custom action policy for the first cluster service of the at least one other cluster service, the custom action policy specified in a user application;

wherein the data grid cluster uses the root cluster service quorum policy to determine whether root service actions are allowed to be performed based on how many qualified root cluster service members are operational in said plurality of interoperating cluster nodes in the data grid cluster; and

wherein the custom action policy specified in the user application provides resource-driven control of the first cluster service, wherein the resource-driven control is provided by the custom action policy to the first cluster service via a pluggable interface provided by the data grid cluster and implemented by the user application, and wherein the resource-driven control is based on an external state managed by the user application.

2. The system according to claim 1, wherein the pluggable interface is a com.tangosol.net.ActionPolicy pluggable interface, and wherein the data grid cluster is an ORACLE COHERENCE data grid cluster.

3. The system according to claim 1, wherein the external state is a deployment topology of the user application within the data grid cluster.

4. The system of claim 1, wherein the first cluster service of the at least one other cluster service is a partitioned cache service.

5. The system of claim 1, wherein a class-name element is present within the quorum policy scheme element, and wherein the class name element contains a fully qualified name of a class that implements the custom action policy.

6. The system of claim 5, wherein the class that implements the custom action policy is a factory class.

7. The system of claim 6, wherein a method name element is present within the quorum policy scheme element, and wherein the method name element specifies the name of a static factory method on the factory class that performs instantiation of an object of the class.

8. A method for supporting service level quorum in a data grid cluster comprising a plurality of computer servers, the data grid cluster executing thereon, wherein the data grid cluster comprises a plurality of interoperating cluster nodes in the data grid cluster, wherein the data grid cluster supports performing a plurality of services including a root cluster service performed by all of the plurality of interoperating cluster nodes and at least one other cluster service performed by at least one of the plurality of interoperating cluster nodes specified as a service member of the at least one other cluster service, and wherein the at least one other cluster service provides a different type of service than the root cluster service, the method comprising:

providing a root cluster service quorum policy, wherein the root cluster service quorum policy specifies a minimum number of qualified root cluster service members that are required for performing root cluster service actions of said root cluster service;

providing a cache configuration file;

associating the cache configuration file with the data grid cluster such that the cache configuration file is accessible to all of the plurality of interoperating cluster nodes;

defining, in the cache configuration file, a service name element for a first cluster service of the at least one other service, the service name element uniquely identifying a name of the first cluster service;

defining, in the cache configuration file, a quorum policy scheme element that contains a reference to a custom action policy for the first cluster service of the at least one other cluster service, the custom action policy specified in a user application;

using the root cluster service quorum policy to determine whether root cluster service actions are allowed to be performed based on how many qualified root cluster service members are operational in said plurality of interoperating cluster nodes in the data grid cluster; and

using the custom action policy specified in the user application to provide resource-driven control of the first cluster service

providing, by the data grid cluster, a pluggable interface;

implementing, by the user application, the pluggable interface;

providing the resource-driven control via the pluggable interface implemented by the user application; and

basing the resource-driven control on an external state managed by the user application.

9. The method of claim 8, wherein the pluggable interface is a com.tangosol.net.ActionPolicy pluggable interface, and wherein the data grid cluster is an ORACLE COHERENCE data grid cluster.

10. The method of claim 8, wherein the external state is a deployment topology of the user application within the data grid cluster.

11. The method of claim 8, wherein the first cluster service of the at least one other cluster service is a partitioned cache service.

12. The method of claim 8, further comprising:

providing a class-name element within the quorum policy scheme element, wherein the class name element contains a fully qualified name of a class that implements the custom action policy.

13. The method of claim 12, wherein the class that implements the custom action policy is a factory class.

14. The method of claim 13, further comprising:

providing a method name element within the quorum policy scheme element, wherein the method name element specifies the name of a static factory method on the factory class that performs instantiation of an object of the class.

15. A non-transitory machine readable medium having instructions stored thereon for supporting service level quorum in a data grid cluster comprising a plurality of computer servers, the data grid cluster executing thereon, wherein the data grid cluster comprises a plurality of interoperating cluster nodes in the data grid cluster, wherein the data grid cluster supports performing a plurality of services including a root cluster service performed by all of the plurality of interoperating cluster nodes and at least one other service performed by at least one of the plurality of interoperating cluster nodes specified as a service member of the at least one other cluster service, and wherein the at least one other cluster service provides a different type of service than the root cluster service, which instructions, when executed cause the data grid cluster to perform steps comprising:

providing a root cluster service quorum policy, wherein the root cluster service quorum policy specifies a minimum number of qualified root cluster service members that are required for performing root cluster service actions of said root cluster service;

providing a cache configuration file;

associating the cache configuration file with the data grid cluster such that the cache configuration file is accessible to all of the plurality of interoperating cluster nodes;

defining, in the cache configuration file, a service name element for a first cluster service of the at least one other cluster service, the service name element uniquely identifying a name of the first cluster service;

defining, in the cache configuration file, a quorum policy scheme element that contains a reference to a custom action policy for the first cluster service of the at least one other cluster service, the custom action policy specified in a user application;

using the root cluster service quorum policy to determine whether root cluster service actions are allowed to be performed based on how many qualified root cluster service members are operational in said plurality of interoperating cluster nodes in the data grid cluster; and

using the custom action policy specified in the user application to provide resource-driven control of the first cluster service

providing, by the data grid cluster, a pluggable interface;

implementing, by the user application, the pluggable interface;

providing the resource-driven control via the pluggable interface implemented by the user application; and

basing the resource-driven control on an external state managed by the user application.

16. The non-transitory machine readable medium of claim 15, wherein the external state is a deployment topology of the user application within the data grid cluster.

17. The non-transitory machine readable medium of claim 15, wherein the first cluster service of the at least one other cluster service is a partitioned cache service.

18. The non-transitory machine readable medium of claim 15, further comprising:

providing a class-name element within the quorum policy scheme element, wherein the class name element contains a fully qualified name of a class that implements the custom action policy.

19. The non-transitory machine readable medium of claim 18, wherein the class that implements the custom action policy is a factory class.

20. The non-transitory machine readable medium of claim 19, further comprising:

providing a method name element within the quorum policy scheme element, wherein the method name element specifies the name of a static factory method on the factory class that performs instantiation of an object of the class.