Partitioning Distributed Filesystem Namespace via Domain Framework

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing complex namespace policies in large distributed filesystems, such as OneFS, is challenging due to the need for different policies across various parts of the namespace, leading to complex data service management.

Innovation Solution

Implementing a domain framework that allows grouping files into domains within the filesystem namespace, enabling efficient management by associating domain membership information with file metadata, which can be rapidly retrieved and filtered for data services, reducing the need for each service to maintain its own grouping information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If different policies are applied to different parts of the namespace, then policy management flexibility is improved, but data service management complexity increases

Engineering Contradiction:
Improvepolicy management flexibilityVSAvoiddata service management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The namespace is segmented into multiple domains, where each domain represents a partitioned portion of the filesystem namespace. Data services can be selectively applied to specific domains rather than the entire namespace, reducing management complexity while maintaining policy flexibility. The domain manager divides the large namespace into manageable units that can be independently configured.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A domain manager is introduced as an intermediary component that handles domain creation, maintenance, and membership management. This intermediary abstracts the complexity of policy management from individual data services, providing a centralized mechanism for managing domain assignments and policy applications across the distributed filesystem.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If each data service maintains its own grouping information, then service independence is improved, but resource usage increases

Engineering Contradiction:
Improveservice independenceVSAvoidresource usage
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

Multiple data services share a common domain grouping mechanism managed by the domain manager. Instead of each service maintaining separate grouping information, services can reference the same domain structures and membership data. This merging reduces redundant storage and processing resources while services retain their independence in how they utilize the shared domain information.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The domain manager provides universal domain management capabilities that serve multiple data services simultaneously. A single domain structure can be utilized by different data services for their respective policies, making the domain management system multi-functional and reducing overall system resource requirements compared to duplicate service-specific implementations.

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

3Productivity

If domain membership information is rapidly retrieved, then operational speed is improved, but information storage requirements increase

Engineering Contradiction:
Improveoperational speedVSAvoidinformation storage requirements
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

Domain membership information is pre-computed and maintained in advance by the domain manager. When data services need to determine file membership or apply policies, the information is already prepared and available for rapid retrieval. This preliminary preparation of domain membership data enables fast operations without requiring intensive real-time computation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Domain membership information is stored in a centralized data structure that can be efficiently copied or referenced by multiple data services. Rather than each service storing complete duplicate information, services can access copies or references to the domain membership data, reducing total storage requirements while enabling rapid retrieval when needed.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10983953B2Partitioning a distributed filesystem namespace
Publication Date: 2021.04.20 EMC IP HLDG CO LLC
  • US10983953B2 patent drawing
  • US10983953B2 patent drawing
  • US10983953B2 patent drawing

AI summary

The described technology is generally directed towards domains that data services can use to collect files of a global filesystem namespace into groups. A data service (a domain patron) creates a domain, e.g., for a particular directory, and a domain manager associates files under that directory with domain membership information. Thereafter, the data service can use the domain membership information associated with a file to determine whether to include that file in a data service operation. In one implementation the membership information is maintained in file metadata, facilitating fast and efficient retrieval of the information in near constant time. Exclusion from a domain, hard links, renames and alternate data streams are among the various aspects supported by the domain technology.