Cluster File System Synchronization via Bootstrap

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing system configurations are statically dependent on hardware and software components, making it difficult to dynamically adjust to changes in system resources, leading to manual updates and potential downtime when moving configurations across different machines with varying hardware and software setups, and lacking efficient propagation of changes across child configurations.

Innovation Solution

An abstract configuration model that uses parameterized and computed settings to dynamically configure systems, allowing for system-independent configuration templates that adapt to different environments, and a bootstrap for file system synchronization to ensure consistent updates across a cluster.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Stability of the object's composition

If system dependent information is statically and redundantly distributed across the cluster with manual individual configuration of each node, then configuration stability is maintained, but adaptability to hardware and software changes deteriorates

Engineering Contradiction:
Improveconfiguration stabilityVSAvoidadaptability to hardware and software changes
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent merges the configuration management of multiple cluster nodes into a single centralized configuration file that defines the entire cluster topology. This allows dynamic configuration changes to be applied cluster-wide without manual updates to each node, resolving the contradiction by maintaining stability through centralization while enabling adaptability through unified configuration updates.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The invention creates a universal configuration model that can represent different hardware and software environments through abstract node definitions. The configuration system can adapt to various machine setups (different CPUs, memory, operating systems) using the same configuration syntax, allowing the system to be both stable and adaptable simultaneously.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Manufacturing precision

If each node is manually individually configured with static system dependent information, then configuration precision is maintained, but ease of operation deteriorates

Engineering Contradiction:
Improveconfiguration precisionVSAvoidease of configuration updates
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The patent combines all node configurations into a single configuration file with a standardized syntax that defines the entire cluster. This approach maintains configuration precision through structured definitions while dramatically improving ease of operation, as updates can be made in one location and automatically applied to all nodes without manual intervention on each machine.

Inventive Principle:
Principle #5Merging (Combining)

3Device complexity

If Java parameters are stored in one single property with child configurations completely overwriting parent properties, then device complexity is reduced, but loss of information deteriorates

Engineering Contradiction:
Improveconfiguration structure complexityVSAvoidloss of parent configuration changes
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The patent implements a nested configuration structure where child configurations inherit from parent configurations. This allows the configuration system to maintain simple structure while preventing information loss, as children can inherit and extend parent properties rather than completely overwriting them. The nested structure enables progressive configuration building without losing parent-level settings.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The invention introduces a configuration propagation mechanism that provides feedback from parent to child configurations. When parent properties change, the system automatically propagates these changes to child configurations, ensuring that information is not lost and that the configuration hierarchy remains synchronized without requiring complex manual management.

Inventive Principle:
Principle #23Feedback

4Reliability

If VM settings changes require restarting the whole instance, then reliability of configuration application is improved, but loss of time deteriorates

Engineering Contradiction:
Improveconfiguration application reliabilityVSAvoiddowntime during configuration updates
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements a configuration validation and preparation phase that occurs before instance restart. The system validates configuration changes, prepares update packages, and synchronizes configuration across the cluster beforehand. This preliminary action ensures that when restart is necessary, the configuration application is reliable and minimal downtime is required, as the system is already prepared for the transition.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7689600B2System and method for cluster file system synchronization
Publication Date: 2010.03.30 SAP SE
  • US7689600B2 patent drawing
  • US7689600B2 patent drawing
  • US7689600B2 patent drawing

AI summary

A system and method for file system synchronization is described. A method described includes saving content of a cluster file system (CFS) archive to a CFS database, detecting a change made in the CFS database with respect to the CFS archive, comparing an index of the CFS database with an index of the file system, and updating the file system to reflect the change in the CFS database.