Quorum Policy for Data Grid Service Availability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern computing systems face challenges in managing large-scale data access and transaction demands, particularly in ensuring continuous availability and resource management in data grid clusters, where millions of users simultaneously access applications, leading to increased resource requirements and potential failures.

Innovation Solution

Implementing a quorum policy in a data grid cluster that specifies a minimum number of service members required for performing service actions, allowing the cluster to manage resource availability and behavior through quorum features, such as root cluster, partitioned cache, and proxy services, with customizable policies to ensure optimal performance and reliability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a distributed data management and cache service is run in the application tier to meet high user demand, then the system can handle millions of simultaneous users, but the complexity of configuring and managing the application server cluster increases

Engineering Contradiction:
Improveuser access capacityVSAvoidcluster configuration and management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system implements automatic quorum determination and service availability management, where the cluster nodes autonomously determine quorum status based on present state conditions without requiring manual configuration or intervention. The quorum policy automatically adjusts service availability based on the number of available nodes, eliminating the need for complex manual cluster management.

Inventive Principle:
Principle #25Self-service

2Productivity

If the number of cluster nodes is increased to handle increased transaction demands, then the system can accommodate more users and transactions, but the difficulty of managing and coordinating the cluster nodes increases

Engineering Contradiction:
Improvetransaction handling capacityVSAvoidcluster node management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The quorum policy dynamically adapts to changing cluster conditions by automatically determining service availability based on the present state of cluster nodes. As nodes are added or removed, the system dynamically recalculates quorum requirements and adjusts service permissions accordingly, eliminating the need for static manual reconfiguration.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system segments the cluster management function into individual node self-assessment operations, where each node independently evaluates its own state and contributes to the overall quorum determination. This segmentation simplifies management by distributing the coordination logic across individual nodes rather than requiring centralized complex management.

Inventive Principle:
Principle #1Segmentation

3Reliability

If manual intervention is used to manage service availability in the cluster, then service actions can be controlled, but the system cannot maintain continuous availability during resource failures or network outages

Engineering Contradiction:
Improveservice availabilityVSAvoidmanual intervention requirement
Core Design Contradiction:
ReliabilityVSExtent of automation

Solution Approach 1:

The system implements continuous feedback loops where cluster nodes automatically monitor and report their present state to the quorum policy mechanism. This feedback enables automatic determination of service availability based on real-time cluster conditions, allowing the system to maintain continuous availability during failures without manual intervention by constantly adjusting service permissions based on current node status.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The quorum policy is pre-configured with rules for determining service availability under various cluster conditions. Before failures occur, the system has predetermined logic in place that automatically triggers appropriate service permissions based on the number of available nodes, eliminating the need for reactive manual intervention during crises.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If a quorum policy is implemented to ensure service reliability, then the system can maintain optimal performance during failures, but the device complexity increases due to additional policy configuration

Engineering Contradiction:
Improveservice reliability during failuresVSAvoidquorum policy configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The quorum policy uses simple parameter-based thresholds (number of available nodes) to determine service availability, rather than complex rule sets. By changing the approach from complex policy logic to simple numerical thresholds that automatically scale with cluster size, the system achieves high reliability during failures while minimizing configuration complexity.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10122595B2System and method for supporting service level quorum in a data grid cluster
Publication Date: 2018.11.06 ORACLE INT CORP
  • US10122595B2 patent drawing
  • US10122595B2 patent drawing
  • US10122595B2 patent drawing

AI summary

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.