Distributed File System Snapshot via Secondary Namespace

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed data processing systems like Hadoop face challenges in creating robust point-in-time images (PPIs) due to the complexity and latency involved in tracking changes across multiple data blocks and their replicas, which is essential for system backups and restoration but is currently inefficient.

Innovation Solution

The technology creates a secondary namespace within a local file system to manage metadata, utilizing the PPI features of the local file system to create a point-in-time image of the distributed file system, thereby reducing complexity and latency by separating metadata management and data storage, and using periodic checkpoints to ensure data integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If the system traverses through each directory in HDFS to examine each file to identify changes for PPI creation, then the PPI can be created with complete accuracy, but the process creates huge latency and is very slow

Engineering Contradiction:
ImprovePPI creation accuracyVSAvoidPPI creation time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent extracts the metadata management function from the data storage function by introducing a separate namespace system. The NameNode maintains a namespace that mirrors the file system hierarchy and stores metadata about files and directories, separating this from the actual data blocks stored in DataNodes. This extraction allows PPI creation to operate on the lightweight namespace structure rather than traversing all data blocks, significantly reducing creation time while maintaining accuracy.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the file system into two independent components: the namespace (metadata structure) and data blocks (actual file content). The namespace is further segmented into directory structures that can be independently managed. This segmentation enables the PPI mechanism to work solely on the namespace layer, creating snapshots of the file system structure without needing to process or verify actual data block contents, thus resolving the contradiction between accuracy and speed.

Inventive Principle:
Principle #1Segmentation

2Reliability

If the system tracks the state of multiple data blocks and their replicas associated with HDFS changes, then the PPI reflects complete file system state, but the complexity and latency increase significantly

Engineering Contradiction:
ImprovePPI completenessVSAvoidPPI creation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the tracking function from data blocks to the namespace structure. Instead of tracking individual data block states and their replicas, the system tracks the namespace structure which inherently represents the complete file system state. The namespace contains directory entries, file metadata, and hierarchical relationships that collectively describe the entire file system, eliminating the need for complex block-level tracking while maintaining completeness.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The namespace structure serves multiple functions simultaneously: it stores file metadata, maintains directory hierarchy, tracks file system state, and enables PPI creation. This multi-functional namespace replaces the need for separate tracking mechanisms for data blocks and replicas, reducing system complexity while maintaining the ability to reflect the complete file system state in PPIs.

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

3Ease of repair

If the system creates a copy of the storage directory and hard links existing block files for local PPI, then the PPI can be restored by removing hard links, but the process is complex and does not allow roll forward

Engineering Contradiction:
ImproveRollback capabilityVSAvoidPPI management complexity
Core Design Contradiction:
Ease of repairVSDevice complexity

Solution Approach 1:

The patent creates a logical copy of the namespace structure at the time of PPI creation. This namespace snapshot captures the complete file system state including all directory entries, file metadata, and hierarchical relationships. The copy is lightweight and can be stored efficiently, enabling both rollback and rollforward operations by simply switching between different namespace snapshots without complex hard link management.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

Instead of creating physical copies of data blocks with hard links (as in the prior art), the patent inverts the approach by creating logical copies of the namespace structure. The namespace snapshot references the same data blocks but maintains an independent view of the file system state. This inversion simplifies PPI management because namespace snapshots can be created, stored, and switched without affecting the actual data blocks or requiring complex link management.

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentUS9946716B2Distributed file system snapshot
Publication Date: 2018.04.17 NETAPP INC
  • US9946716B2 patent drawing
  • US9946716B2 patent drawing
  • US9946716B2 patent drawing

AI summary

Technology is disclosed for managing data in a distributed file system (“the technology”). The technology can gather metadata information associated with the data stored within the distributed file system, create a secondary namespace within a local file system of a local host using the gathered metadata information and store the gathered metadata information as files within the secondary namespace. Further, when a request to create a PPI of the distributed file system is received, the technology can create a PPI of the secondary namespace using a PPI creation feature of the local file system.