Network Data Resynchronization via Journal-Based GUID Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Network devices face inefficiencies in resynchronizing large volumes of mutually shared data due to resource-intensive processes and potential data loss during communication interruptions, particularly when using traditional methods like two-phase commit or full database copying.
Innovation Solution
Implementing an 'agreed-ordering' protocol for network devices to exchange change instructions and globally unique identifiers, allowing for efficient resynchronization by copying only the necessary data between devices using a journal-based approach, which records change instructions and identifiers in a specific order, enabling faster and more targeted data updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full database copying is used for resynchronization, then data consistency is ensured, but transmission time and network bandwidth consumption increase significantly
Solution Approach 1:
The patent extracts only the changed data portions from the full database for transmission during resynchronization. Instead of copying the entire database, the system identifies and transmits only the specific data changes that occurred during the network interruption, significantly reducing transmission time while maintaining data consistency.
Solution Approach 2:
The patent segments the database into individual change records that can be independently identified and transmitted. By breaking down the database into discrete change units (insertions, deletions, modifications), the system can selectively transmit only the necessary segments rather than the entire database.
2Reliability
If two-phase commit approach is used, then data consistency is maintained, but system flexibility and ability to make changes during network issues deteriorate
Solution Approach 1:
The patent performs preliminary actions by recording all data changes in a journal during network interruptions before attempting resynchronization. This allows the system to accumulate changes locally and then replay them in the correct sequence after network restoration, maintaining consistency without requiring real-time coordination with other nodes.
Solution Approach 2:
The patent introduces a journal as an intermediary mechanism that stores change records locally during network interruptions. This journal acts as a buffer that decouples the local system from remote systems, allowing changes to be made independently and then synchronized later through resynchronization protocols.
3Productivity
If network devices process messages independently without ordering protocol, then processing speed increases, but message order and data consistency across devices deteriorate
Solution Approach 1:
The patent assigns sequence numbers to change records in advance before transmission. This preliminary ordering allows receiving devices to process messages independently at high speed while ensuring correct ordering by simply comparing sequence numbers, without requiring complex coordination protocols during processing.
Data Source
AI summary
Techniques are described for resynchronizing mutually shared data stored on network devices of a computer network. Upon receiving change instruction and globally unique identifier (GUID) messages, each of the network devices records the change instructions and GUIDs in a journal of the network device. When communication is lost for a period of time between a first network device and a second network device, the mutually shared data of the first network device may need to be resynchronized with the mutually shared data of the second network device. The techniques described herein allow resynchronization of the mutually shared data of the first network device based on a common GUID recorded in the journals of both first and second network devices, the journal of the first network device, and the journal of the second network device.