Distributed File Handle Identifier Embedding Protocol Server Location

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The allocation of files across multiple nodes in distributed file systems is time and resource-consuming, particularly when handling client-initiated operations and maintaining persistent file handles across node failures or load balancing.

Innovation Solution

A method and system that generate a unique handle identifier for file handles, embedding a protocol server identifier within the handle, allowing clients to efficiently locate the protocol server and execute operations, thereby optimizing file system operations in distributed server systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If files are allocated across multiple nodes in distributed file systems, then storage capacity and redundancy are improved, but file handle location and operation execution become time-consuming and resource-intensive

Engineering Contradiction:
Improvestorage capacityVSAvoidfile handle location time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The handle identifier is structured as a nested container where the protocol server identifier is embedded within the broader handle identifier. This nested structure allows the handle to encode location information about the protocol server, enabling direct navigation to the correct node without traversing the entire distributed file system.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The protocol server identifier acts as an intermediary element that bridges the client and the distributed file system nodes. By embedding this identifier in the handle, the system creates a direct reference mechanism that mediates between the client's operation requests and the appropriate protocol server, eliminating the need for time-consuming search operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If persistent file handles are maintained across node failures or load balancing, then service continuity is improved, but system complexity and resource consumption increase

Engineering Contradiction:
Improveservice continuityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The protocol server identifier is assigned and embedded in the handle identifier at the time of handle creation, before any node failures or load balancing events occur. This preliminary encoding of location information ensures that when a client needs to reconnect after a failure, the handle already contains the necessary information to locate the appropriate protocol server, simplifying the recovery process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The handle identifier structure enables the system to automatically locate and redirect clients to appropriate protocol servers without requiring complex centralized coordination or manual intervention. The embedded protocol server identifier allows the distributed system to self-manage failover and load balancing by using the information already present in the handle.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If unique handle identifiers are generated for each client connection, then client connection management is improved, but handle identifier generation and processing complexity increase

Engineering Contradiction:
Improveclient connection managementVSAvoidhandle generation complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The handle identifier structure serves multiple functions simultaneously: it uniquely identifies the handle, encodes the protocol server location information, and enables client connection management. By making the handle identifier universal and multi-functional, the system avoids the need for separate mechanisms for each function, thereby reducing overall complexity despite the enhanced capabilities.

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

Data Source

PatentUS10038752B2Method and system for execution of client-initiated operations on file handles in a distributed server system
Publication Date: 2018.07.31 DELL PROD LP
  • US10038752B2 patent drawing
  • US10038752B2 patent drawing
  • US10038752B2 patent drawing

AI summary

A method and a system for execution of client-initiated operations on file handles in a distributed server system. The method may include: generating a file handle, responsive to a connect request sent by a client to a distributed file system, wherein the handle has a handle identifier that is unique throughout the distributed file system; embedding a protocol server identifier within the handle identifier, wherein the protocol server identifier relates to a protocol server to which the handle is assigned, wherein the protocol server is a data structure containing a list of all valid handles that belong to a specific file; sending an operation request from said client to the distributed file system, wherein the file system operation request includes the handle identifier; and locating the protocol server based on the protocol server identifier embedded within the handle identifier upon receiving the operation request at the distributed file system.