Storage Controller Recycling Soft-Deleted Container Objects

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern storage systems face performance degradation and resource inefficiencies due to frequent garbage collection operations, especially in container-based environments, where reclaimable capacity is not effectively utilized, leading to out-of-space conditions despite available space.

Innovation Solution

A method and system for recycling container storage objects by soft-deleting objects and reusing their metadata, where labels are associated with new containers to match and recycle data from soft-deleted objects, reducing the need for write operations and optimizing resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If garbage collection operations are performed to reclaim space, then reclaimable capacity is recovered, but system performance degrades and resource consumption increases

Engineering Contradiction:
Improvereclaimable capacityVSAvoidsystem performance
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The system performs preliminary actions by soft-deleting container objects and maintaining them in a recycling pool before actual deletion occurs. This allows the storage controller to proactively prepare reusable objects with preserved metadata and data, so when new containers are created, ready-to-use objects can be immediately allocated without triggering garbage collection operations, thus avoiding performance degradation while ensuring capacity is available.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system discards the traditional approach of immediately deleting container objects when no longer needed. Instead, it recovers and reuses soft-deleted objects by maintaining them in a recycling pool, where their metadata and data are preserved. This allows the system to recover and reuse storage resources without performing expensive garbage collection operations, resolving the contradiction between capacity reclamation and performance maintenance.

Inventive Principle:
Principle #34Discarding and recovering

2Quantity of substance

If container objects are immediately deleted after use, then storage capacity is freed, but garbage collection overhead increases and resource efficiency decreases

Engineering Contradiction:
Improvestorage capacityVSAvoidgarbage collection overhead
Core Design Contradiction:
Quantity of substanceVSLoss of energy

Solution Approach 1:

The storage controller implements self-service by automatically managing the recycling pool and matching soft-deleted objects with new container creation requests. The system autonomously performs label matching, object resurrection, and data recycling without requiring external garbage collection interventions. This self-managed approach eliminates the need for separate garbage collection processes, reducing overhead while maintaining efficient storage capacity utilization.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Instead of completely discarding deleted container objects, the system recovers them by soft-deleting and storing in a recycling pool. The metadata and data of these objects are preserved and can be recovered for reuse when new containers with matching labels are created. This recovery mechanism eliminates the need for traditional garbage collection to reclaim space, significantly reducing the associated overhead and improving resource efficiency.

Inventive Principle:
Principle #34Discarding and recovering

3Productivity

If soft-deleted objects are maintained for recycling, then data reuse is enabled, but storage space is occupied by unreclaimed objects

Engineering Contradiction:
Improvedata recycling efficiencyVSAvoidstorage space occupancy
Core Design Contradiction:
ProductivityVSArea of stationary object

Solution Approach 1:

The storage controller implements a universal recycling pool that serves multiple functions: it stores soft-deleted container objects, maintains their metadata for matching, and provides ready-to-use objects for new container creations. This multi-functional approach allows the same storage space to serve both as active container storage and as a recycling repository, eliminating the need for separate garbage collection spaces and optimizing overall storage utilization while enabling efficient data reuse.

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

4Adaptability or versatility

If labels are checked and matched for container recycling, then object reuse is optimized, but additional processing time is required

Engineering Contradiction:
Improveobject matching accuracyVSAvoidlabel checking duration
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary labeling when container objects are soft-deleted, preserving their labels in the recycling pool before any matching is needed. This preliminary action ensures that when new containers are created, the label matching process can quickly compare against pre-labeled soft-deleted objects without requiring additional time for label extraction or processing, thus optimizing matching accuracy while minimizing time loss.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12175291B2Recycling container storage objects at a storage controller
Publication Date: 2024.12.24 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US12175291B2 patent drawing
  • US12175291B2 patent drawing
  • US12175291B2 patent drawing

AI summary

Method and system are provided for recycling container storage objects at a storage controller. The method includes receiving a create operation of a new container by an orchestrator, including information indicating a purpose of the container, and associating a label with the new container, with the label indicating the orchestrator-defined information. The method includes checking labels of soft-deleted container objects for a suitable match with the label of the new container, where soft-deleted container objects are logical objects for deleted containers that are maintained for recycling. The method includes recycling metadata of a matched soft-deleted container object for the new container. The method includes checking received input/output operations for the new container against already stored data of the matched soft-deleted container to recycle data and skip writes where they match.