Graph Database Replica Expansion via Copy-Only Mode
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
As graph data continues to grow in scale and complexity, existing distributed graph databases face challenges in managing storage capacity and performance, leading to the need for replica expansion to accommodate increasing data volumes and maintain data integrity and security.
Innovation Solution
The proposed replica expansion method involves setting a data storage node to a data copy-only mode during graph data shard migration, followed by a data storage service mode where data synchronization is performed with a primary replica based on a data snapshot, ensuring data integrity and security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If graph data storage capacity is increased by adding more data storage nodes, then storage capacity is improved, but system complexity increases
Solution Approach 1:
The patent segments the graph data into multiple shards and distributes them across different data storage nodes. When expansion is needed, only specific shards are migrated to new nodes rather than moving all data, thereby increasing storage capacity while managing system complexity through selective segmentation.
Solution Approach 2:
The patent creates a data snapshot before migration and establishes a copy-only mode in advance. This preliminary preparation ensures that data can be safely copied without disrupting ongoing services, allowing capacity expansion while maintaining system stability and reducing operational complexity.
2Quantity of substance
If data migration is performed during normal service, then storage expansion is achieved, but data integrity and security may be compromised
Solution Approach 1:
The patent creates a data snapshot before migration begins and records the data point at the time of starting migration. This preliminary action establishes a baseline that can be used to verify data integrity during and after the migration process, ensuring that data has not been corrupted or lost.
Solution Approach 2:
The patent uses a copy-only mode during migration, where data is copied to the new storage node without allowing read/write services on the original node. This copying mechanism ensures that the original data remains intact and unchanged, while the copied data can be verified against the snapshot to maintain data integrity and security.
3Productivity
If read/write service is provided during data migration, then service continuity is maintained, but data synchronization accuracy decreases
Solution Approach 1:
The patent establishes a copy-only mode before migration begins, which prepares the system to receive data without allowing concurrent read/write operations. This preliminary setup ensures that data is copied accurately without interference from ongoing services, and service continuity is maintained by redirecting operations to the new node after migration.
Solution Approach 2:
The patent uses a copy-only mode that allows data to be copied to the new storage node without permitting read/write services during the migration process. This copying mechanism ensures accurate data synchronization by preventing any modifications or reads during the critical migration window, while service continuity is maintained through proper service routing.
4Reliability
If data snapshot is created during migration, then data integrity is ensured, but migration time increases
Solution Approach 1:
The patent creates the data snapshot as a preliminary action before migration begins, capturing the data point at the moment migration starts. This preliminary snapshot creation ensures data integrity is established before any migration occurs, and since it's done upfront rather than during the migration process, it minimizes the time added to the migration operation.
Data Source
AI summary
A computer-implemented method for distributed graph database replica expansion and performed by a second data storage data node to be expanded includes, in response to reception of graph data migration information, entering a data copy-only mode and initiating graph data migration from a first data storage node to obtain a data snapshot of a first graph data shard. Following graph data migration, entering a data storage service mode and sending a graph data shard deletion notification to the first data storage node to delete the first graph data shard. In the data storage service mode, performing data synchronization with a corresponding first graph data shard of a primary replica based on a data point in the data snapshot. The first data storage node deletes a migrated graph data shard in response to the graph data shard deletion notification.