Inode Management and ACL Parity in Synchronous Replication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Synchronous replication techniques face challenges in maintaining data consistency and efficiency, particularly during transition operations and quick reconciliations, due to issues with timestamp inconsistency, hole reservation flags, and the sequential replication of operations, which can lead to latency and data integrity problems.
Innovation Solution
Implementing a system that intercepts operations to split and replicate them in parallel, ensuring timestamp consistency, replicating hole reservation flags, and selectively replicating operations based on on-disk modifications to maintain parity between nodes, while using a dirty region log and metadata log for transition operations to synchronize data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If operations are replicated sequentially from first node to second node, then data consistency is maintained, but replication latency increases
Solution Approach 1:
The patent segments the replication process into independent parallel operations. Instead of sequentially replicating operations from first node to second node, the system divides operations into multiple independent replication tasks that can execute simultaneously across different nodes, reducing overall replication latency while maintaining data consistency through coordinated completion markers.
Solution Approach 2:
The patent implements preliminary actions by pre-establishing replication relationships and pre-allocating resources before actual data replication begins. Transition operations prepare the replication environment in advance, including setting up metadata logs and dirty region logs, so that subsequent data replication can proceed in parallel without setup delays.
2Reliability
If timestamp consistency is enforced across replicated operations, then data integrity is improved, but operation execution complexity increases
Solution Approach 1:
The patent introduces an intermediary mechanism (transition operation) that mediates between replicated operations and timestamp management. This intermediary layer handles timestamp consistency enforcement centrally, coordinating timestamp assignment across parallel operations without requiring each operation to independently manage complexity, thus maintaining data integrity while reducing overall system complexity.
3Reliability
If all operations are replicated to maintain parity between nodes, then data consistency is ensured, but network bandwidth and processing overhead increase
Solution Approach 1:
The patent applies partial replication by selectively replicating only necessary operations and data portions. Instead of replicating all operations unconditionally, the system uses dirty region logs to identify and replicate only modified regions, and employs metadata logs to track which operations require replication. This partial action approach maintains data consistency while significantly reducing network bandwidth consumption and processing overhead.
Data Source
AI summary
Techniques are provided for inofile management and access control list file handle parity. For example, operations targeting a first storage object of a first node are replicated to a second storage object of a second node. A size of an inofile maintained by the second node is increased if an inode number to be allocated by the replication operation is greater than a current size of the inofile. Access control list file handle parity is achieved by maintaining parity between inode number and generation number pairings of the first node and the second node.