Object Storage Crash Recovery via Segmented Transaction Metadata

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Resource-constrained systems face challenges in providing efficient object storage services due to limited computing resources, leading to high costs and slow recovery times after service interruptions, as they struggle to scan and iterate through multiple objects for various actions.

Innovation Solution

Implementing a resource-constrained set of interconnected computing systems that can scan and perform multiple actions on objects efficiently by treating each file, directory, and object as separate entities, allowing for immediate service resumption after interruptions and reduced I/O operations through background transaction recovery and lifecycle management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If resource-constrained systems scan and iterate through multiple objects to perform various actions, then object storage services can be provided, but computing resource costs increase and service recovery time increases after interruptions

Engineering Contradiction:
Improveservice recovery timeVSAvoidcomputing resource allocation cost
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by recording transaction states and metadata before interruptions occur. Transaction recovery information including state identifiers, object identifiers, and action types are pre-documented, enabling immediate resumption without re-scanning objects. This preliminary documentation allows the system to recover from interruptions by continuing from the recorded state rather than reprocessing all objects.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent segments the object storage service into distinct transaction units with individual state tracking. Each transaction is treated as a separate entity with its own state metadata, allowing selective recovery of only affected transactions after interruptions. This segmentation eliminates the need to reprocess entire object sets and reduces computing resource consumption during recovery.

Inventive Principle:
Principle #1Segmentation

2Productivity

If resource-constrained systems perform multiple scans of objects to execute different actions, then comprehensive object management is achieved, but I/O operations increase and system efficiency decreases

Engineering Contradiction:
Improvesystem efficiencyVSAvoidI/O operations time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system implements multi-functionality by combining multiple object management actions into a single scan operation. The agent server process performs transaction recovery, lifecycle policy implementation, and integrity verification simultaneously during one object access. This universal approach eliminates the need for separate scans for each action type, reducing I/O operations and improving system efficiency.

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

Solution Approach 2:

The patent ensures continuity of useful action by maintaining persistent transaction state information that allows uninterrupted processing. When interruptions occur, the system continues from the recorded state without re-scanning objects or repeating previous actions. This continuous processing approach minimizes I/O operations and maintains high system efficiency throughout the object storage service lifecycle.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS11726954B1Multi-action background process for a resource-constrained system
Publication Date: 2023.08.15 AMAZON TECH INC
  • US11726954B1 patent drawing
  • US11726954B1 patent drawing
  • US11726954B1 patent drawing

AI summary

Aspects related to a resource-constrained system are described herein that can provide object storage services after a service interruption is resolved, even if all of the transactions that were pending and incomplete prior to the service interruption have not yet been recovered and/or executed. For example, file systems implemented by computing systems of the resource-constrained system may treat each file or directory as a separate object. Thus, a transaction directed to one file may not affect the file's directory or other files in the directory. As a result, the resource-constrained system can achieve read-after-write consistency without first recovering and executing the pending, incomplete transactions. Instead, read-after-write consistency for an object can be achieved simply by completing any pending, incomplete transaction directed to that object. Accordingly, the resource-constrained system can provide object storage services to user devices immediately after the service interruption is resolved, thereby resulting in fast crash recovery times.