Global Prevent Table for Cluster Data Loss Prevention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current computer storage systems lack a mechanism to proactively prevent data unavailability and data loss across multiple computing clusters, particularly when upgrades or configuration changes lead to issues, resulting in potential data unavailability and loss for users on other clusters with the same software configuration.
Innovation Solution
A system that maintains information about prohibited operations, accessible to multiple computing clusters, which fetches and updates a global prevent table to identify risky configurations and operations, preventing them from being performed across clusters to avoid data unavailability and loss.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a computing cluster performs an upgrade or configuration change, then the system can benefit from new features or improvements, but data unavailability and data loss may occur across multiple clusters with the same software configuration
Solution Approach 1:
The system performs preliminary actions by maintaining a global prevent table that identifies risky software configurations and operations before they are executed. The service checks this table prior to allowing upgrades or configuration changes, preventing problematic actions from occurring in the first place rather than reacting after data loss occurs
Solution Approach 2:
The global prevent table acts as an intermediary between the software configuration system and the computing clusters. It mediates by providing a centralized repository of prohibited operations that all clusters must consult before executing configuration changes, ensuring coordinated prevention across the distributed system
2Reliability
If a global prevent table is maintained separately from computing clusters, then data loss can be prevented across clusters, but system complexity increases
Solution Approach 1:
The global prevent table serves multiple functions: it stores prohibited operations, provides a reference for the service to check against cluster operations, and acts as a centralized configuration repository. This multi-functionality reduces the need for separate specialized components, managing complexity while achieving reliable data loss prevention
3Reliability
If the service checks the global prevent table before each operation, then risky operations can be blocked, but operation speed decreases
Solution Approach 1:
The service performs a partial check by consulting the global prevent table only for specific operations that could potentially cause data loss, rather than blocking or checking all operations. This selective approach maintains operation safety for critical actions while minimizing the impact on overall system performance
Data Source
AI summary
A system can maintain information indicative of prohibited computer operations, wherein the information is accessible to respective computing clusters of a group of computing clusters, and wherein the information is stored separately from the group of computing clusters. The system can obtain, by a service of a first computing cluster of the group of computing clusters, the information. The system can, in response to receiving, at the first computing cluster, a request to perform an operation on a first computer of the first computing cluster, in response to determining, based on the information, that the operation is prohibited, prevent the operation from occurring; and, in response to determining, based on the information, that the operation is not prohibited, permit the operation to occur.