Metadata Server Request Queue Segmentation for Parallel Computing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In parallel computing environments, log-in nodes experience slow interactive response times due to pending requests from batch jobs that fill the request queue of the metadata server, leading to long latency for interactive users.

Innovation Solution

A metadata server node with a virtual machine monitor, interactive client proxy, and batch client proxy is implemented to separate and prioritize metadata requests from interactive and batch clients, using request queues to ensure timely processing of interactive requests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If batch jobs fill the request queue of the metadata server, then the system can handle large numbers of concurrent requests, but interactive users experience long latency

Engineering Contradiction:
Improveconcurrent request handling capacityVSAvoidinteractive response latency
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments the single request queue into separate queues for interactive clients and batch clients. The metadata server maintains distinct queue structures to isolate request types, allowing interactive requests to be processed independently of batch job requests. This segmentation prevents batch jobs from blocking interactive users while maintaining high concurrent request handling capacity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by providing different service characteristics to different client types. Interactive clients receive prioritized processing with lower latency guarantees, while batch clients receive standard processing. The metadata server implements selective resource allocation where interactive requests receive preferential treatment in terms of processing priority and queue access, ensuring quality of service differentiation.

Inventive Principle:
Principle #3Local quality

2Device complexity

If a single request queue is used for all clients, then the system structure is simple, but interactive requests are delayed by batch jobs

Engineering Contradiction:
Improverequest queue structureVSAvoidinteractive request processing
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

The patent divides the monolithic request queue into multiple specialized queues - one for interactive clients and another for batch clients. This segmentation increases structural complexity but enables differentiated processing behaviors. The metadata server manages separate queue data structures that can be independently controlled, allowing interactive requests to bypass batch job delays.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic queue management where the metadata server can selectively access different queues based on client type. The system dynamically switches between processing interactive requests from the interactive queue and batch requests from the batch queue, enabling flexible resource allocation that adapts to different operational requirements without requiring complete system redesign.

Inventive Principle:
Principle #15Dynamics

3Loss of time

If metadata requests are prioritized by client type, then interactive response times improve, but request processing complexity increases

Engineering Contradiction:
Improveinteractive request latencyVSAvoidrequest processing logic
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

Rather than implementing complex prioritization logic within a single queue, the patent segments requests into separate queues at the point of entry. The metadata server then simply selects the appropriate queue based on client type, which is a simpler operation than implementing dynamic prioritization algorithms. This approach moves complexity from the processing logic to the queue structure itself.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces client type identification as an intermediary mechanism that determines queue selection. Before requests enter the processing stage, the system identifies whether the client is interactive or batch and routes accordingly. This intermediary classification layer simplifies the overall processing logic by making client type awareness explicit and separate from the core request handling logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9110695B1Request queues for interactive clients in a shared file system of a parallel computing system
Publication Date: 2015.08.18 EMC IP HLDG CO LLC
  • US9110695B1 patent drawing
  • US9110695B1 patent drawing
  • US9110695B1 patent drawing

AI summary

Interactive requests are processed from users of log-in nodes. A metadata server node is provided for use in a file system shared by one or more interactive nodes and one or more batch nodes. The interactive nodes comprise interactive clients to execute interactive tasks and the batch nodes execute batch jobs for one or more batch clients. The metadata server node comprises a virtual machine monitor; an interactive client proxy to store metadata requests from the interactive clients in an interactive client queue; a batch client proxy to store metadata requests from the batch clients in a batch client queue; and a metadata server to store the metadata requests from the interactive client queue and the batch client queue in a metadata queue based on an allocation of resources by the virtual machine monitor. The metadata requests can be prioritized, for example, based on one or more of a predefined policy and predefined rules.