Distributed Filesystem Cloud Controller Data Distribution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network-based storage systems face challenges in maintaining data consistency and scalability, particularly in cloud-based storage solutions, where access latency and network failures can lead to data consistency issues and increased management overhead.

Innovation Solution

A distributed filesystem system that uses cloud controllers to cache and manage data across multiple cloud storage systems, employing incremental snapshots and metadata to ensure data consistency, and migrates data between storage systems based on cost, access frequency, and network bandwidth to optimize performance and cost.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data is stored in cloud-based storage systems, then storage capacity and scalability are improved, but access latency increases

Engineering Contradiction:
Improvestorage capacityVSAvoidaccess latency
Core Design Contradiction:
Quantity of substanceVSSpeed

Solution Approach 1:

The system segments data into two distinct components: metadata (describing data location and properties) and data itself. Metadata is stored locally in the filesystem, while data is stored remotely in cloud storage systems. This segmentation allows clients to access metadata quickly without incurring network latency for data retrieval, thus improving access speed while maintaining cloud storage capacity benefits.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The local filesystem acts as an intermediary between clients and cloud storage systems. It caches metadata and provides local access to frequently used data, mediating between the need for fast local access and the need for scalable cloud storage. This intermediary layer reduces the impact of network latency by serving common requests locally.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If data is stored remotely in cloud-based storage systems, then storage management overhead is reduced, but data consistency problems occur

Engineering Contradiction:
Improvestorage management overheadVSAvoiddata consistency
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs preliminary actions by pre-computing and caching metadata locally before data access is needed. It also pre-establishes consistent data placement decisions by determining which cloud storage system should store data based on client location and access patterns before actual data transfer occurs. This prevents consistency issues from arising in the first place.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where cloud controllers continuously monitor data access patterns, storage costs, and network conditions. Based on this feedback, they dynamically adjust data placement decisions, migration timing, and replication strategies to maintain data consistency while optimizing for cost and performance.

Inventive Principle:
Principle #23Feedback

3Reliability

If data is replicated across multiple cloud storage systems, then reliability is improved, but storage cost increases

Engineering Contradiction:
Improvedata availabilityVSAvoidstorage cost
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system applies local quality by storing different types of data in different locations based on their specific characteristics and access patterns. Frequently accessed data is replicated across multiple cloud systems for high availability, while rarely accessed data is stored in lower-cost systems. Metadata is always stored locally for immediate access. This differentiated storage strategy maintains reliability for critical data while reducing overall storage costs.

Inventive Principle:
Principle #3Local quality

4Quantity of substance

If data is migrated between cloud storage systems, then cost optimization is improved, but network bandwidth consumption increases

Engineering Contradiction:
Improvestorage costVSAvoidnetwork bandwidth
Core Design Contradiction:
Quantity of substanceVSUse of energy by moving object

Solution Approach 1:

The system performs preliminary actions by pre-positioning data in optimal cloud storage locations based on predicted access patterns and cost conditions. It proactively migrates data during low-cost periods or low-traffic times before actual access occurs, rather than reacting to cost changes after they happen. This timing strategy reduces unnecessary migrations and bandwidth consumption.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses periodic action by scheduling data migrations during specific time periods when network bandwidth is less critical or costs are lower. Instead of continuously monitoring and migrating data in real-time, it performs migrations periodically at optimal moments, reducing overall network bandwidth consumption while still achieving cost optimization.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS8799413B2Distributing data for a distributed filesystem across multiple cloud storage systems
Publication Date: 2014.08.05 PANZURA LLC
  • US8799413B2 patent drawing
  • US8799413B2 patent drawing
  • US8799413B2 patent drawing

AI summary

The disclosed embodiments provide a system that distributes data for a distributed filesystem across multiple cloud storage systems. Two or more cloud controllers collectively manage distributed filesystem data that is stored in one or more cloud storage systems; the cloud controllers cache and ensure data consistency for the stored data. Whenever each cloud controller receives new data from a client, it outputs an incremental metadata snapshot for the new data that is propagated to the other cloud controllers and an incremental data snapshot containing the new data that is sent to a cloud storage system. During operation, data stored in the distributed filesystem can be distributed across two or more cloud storage systems to optimize performance and/or cost for the distributed filesystem.