Stateful Application Migration Using Snapshot-Based State Transfer

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Stateful applications in distributed computing environments face challenges when moving between nodes due to the lack of access to state data, leading to inconsistencies and communication failures during transitions, particularly for applications that store state data only in local memory.

Innovation Solution

Utilizing an ingest valve to pause communications, generate a snapshot of state data, and store it in persistent storage, then relocate and restart the application on a new node with the stored state data, ensuring seamless communication resumption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a stateful application is moved between nodes in a distributed computing environment, then application availability and load balancing are improved, but state data consistency and communication reliability deteriorate due to loss of access to local memory state

Engineering Contradiction:

Improveapplication mobilityVSAvoidstate data consistency

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary actions by pausing the application before node migration, capturing the state data from local memory while the application is still accessible, and transferring it to the target node before the application resumes. This ensures state data consistency is maintained during the migration process.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary mechanism that captures state data from the source node's local memory and transfers it to the target node. This intermediary process ensures that the state data is properly preserved and transferred, maintaining reliability during the migration.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Manufacturing precision

If communications are paused during node migration, then state data integrity is maintained, but communication productivity and service availability deteriorate

Engineering Contradiction:

Improvestate data integrityVSAvoidcommunication throughput

Core Design Contradiction:

Manufacturing precisionVSProductivity

Solution Approach 1:

The system performs the state data capture and transfer as a preliminary action before pausing communications. By preparing the target node with the necessary state data in advance, the actual communication pause duration is minimized, reducing the impact on productivity.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements a rapid state transfer mechanism that quickly copies state data from local memory to persistent storage or transfers it to the target node. This minimizes the time communications are paused, rushing through the migration process to reduce productivity loss.

Inventive Principle:

Principle #21Skipping (Rushing through)

3Speed

If state data is stored in local memory for fast access, then application performance is improved, but data persistence and recoverability worsen when nodes fail or applications are restarted

Engineering Contradiction:

Improvestate access speedVSAvoiddata persistence

Core Design Contradiction:

SpeedVSReliability

Solution Approach 1:

The patent segments state data management into two parts: fast local memory storage for active application access, and persistent storage for data preservation. This segmentation allows the system to enjoy both fast access speeds and data persistence reliability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system creates copies of state data - one copy remains in local memory for fast access during application execution, while another copy is maintained in persistent storage for reliability and recoverability. This copying approach resolves the contradiction between speed and persistence.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS20260030045A1Moving a stateful application between nodes of a distributed computing environment

Publication Date: 2026.01.29 RED HAT INC

AI summary

In one example, a system can operate an event ingest valve to pause event streaming to an event processing application executing on a first node of a distributed computing environment. The system can then access state data, of the event processing application, stored in a local memory of the first node. The system can generate a snapshot of the state data of the event processing application. After generating the snapshot, the system can shut down the event processing application on the first node. The system can then provide the snapshot to a second node of the distributed computing environment, the second node being configured to start the event processing application using the state data. After the event processing application is started on the second node, the system can operate the event ingest valve to resume the event streaming to the event processing application executing on the second node.