Cluster Update Locking System for Staged Device Coordination
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing distributed systems, such as computer clusters, is challenging during updates, as existing technologies often result in conflicts and downtime due to simultaneous updates across devices.
Innovation Solution
A locking system that places persistent objects on each device in a computer cluster to indicate an ongoing update, preventing other systems from updating until the process is complete, using identifiers and executable code to manage and coordinate updates across the system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If updates are performed simultaneously across all devices in a cluster, then update speed is improved, but system stability deteriorates due to conflicts and downtime
Solution Approach 1:
The patent segments the cluster update process by introducing version-based locking objects (e.g., version 1.0, 1.1, 2.0) that divide the update timeline into distinct phases. Each locking object represents a specific update version and coordinates devices to proceed through updates in an organized sequence, preventing simultaneous conflicting updates while maintaining overall system productivity.
Solution Approach 2:
The patent implements preliminary action by placing locking objects on devices before updates begin and removing them after updates complete. This preliminary locking mechanism prepares the system in advance by establishing update coordination rules, ensuring that devices are ready to proceed with updates in a controlled manner without causing conflicts or downtime.
2Reliability
If locking objects are placed on all devices to prevent conflicts, then system stability is improved, but update coordination complexity increases
Solution Approach 1:
The patent uses copying by creating identical locking object structures across all devices in the cluster. Each device receives a standardized locking object with the same format, fields, and behavior rules, simplifying the implementation complexity. Instead of designing unique locking mechanisms for each device, the system copies a proven locking object template throughout the cluster, reducing overall system complexity while maintaining reliability.
3Reliability
If staged updates are performed device by device, then system availability is maintained, but total update time increases
Solution Approach 1:
The patent implements periodic action by organizing updates into regular cycles or waves across different device groups. Instead of updating all devices sequentially one at a time, the system divides devices into cohorts and updates each cohort in succession using versioned locking objects. This periodic approach maintains system availability while reducing total update time compared to purely sequential updates.
Solution Approach 2:
The patent applies dynamics by making the locking object version numbers dynamic and adaptive. As updates progress, the locking object versions evolve (e.g., from 1.0 to 1.1 to 2.0), allowing the system to adjust update coordination in real-time based on progress and system state. This dynamic versioning enables flexible staged updates that maintain availability while optimizing total update time.
Data Source
AI summary
A locking system may place a persistent object on each of the devices in a computer cluster. The objects may indicate that an update is being performed on the devices so that other systems may not also update the devices. When an update has completed, the objects may be removed. The objects may include an identifier for the system owning the objects, as well as other information regarding the update. In some cases, the objects may include executable code and perform some of the update functions on the various devices.