Edge Node Conflict Resolution in Distributed Namespace Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for resolving conflicts in distributed object sharing, such as overwriting or moving conflicting files to a special directory, either lose previous updates or complicate management by allowing many objects under the special directory, leading to usability and flexibility issues.
Innovation Solution
Implementing a conflict resolution policy that prioritizes the center namespace over the application target namespace, with edge nodes determining conflict cases and executing processes according to predefined policies, which may involve creating a directory for evacuation and applying updates from the center namespace to the local namespace.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If the overwriting method is adopted to resolve conflicts, then the conflict resolution process is simple, but the content of the previously updated object is lost
Solution Approach 1:
The system performs preliminary actions by creating backup copies of conflicting objects before applying updates. When a conflict is detected between the center namespace and local namespace, the system preserves the existing object content and applies updates selectively, preventing information loss while maintaining a relatively simple resolution process.
2Loss of information
If the method of moving the conflict file to the special directory for evacuation is adopted, then the previously updated object content is preserved, but the management becomes complicated due to many objects existing under the special directory
Solution Approach 1:
The system extracts only the necessary conflicting objects from the namespace and moves them to a special directory for evacuation, rather than moving all objects. This selective extraction approach preserves the content of previously updated objects while avoiding the management complexity that would arise from moving numerous non-conflicting objects.
Solution Approach 2:
The system applies different management approaches to different types of objects based on their conflict status. Conflicting objects are moved to the special directory for evacuation with detailed management, while non-conflicting objects remain in their original locations with standard management, thereby reducing overall management complexity.
3Ease of manufacture
If a fixed conflict resolution method is always applied, then the process is consistent and simple to implement, but the flexibility and usability are reduced
Solution Approach 1:
The system implements dynamic conflict resolution by allowing the resolution method to change based on the specific conflict situation. Different conflict cases (such as file vs. directory conflicts, different update types) can trigger different resolution strategies, providing flexibility and adaptability while maintaining implementation consistency through a unified framework.
Data Source
AI summary
(A) and (B), described hereinafter, are carried out for objects which differ between an reflection source namespace and a reflection destination namespace, with respect to either: a center node in a migration, which applies an update of a first local namespace which a first edge node (any edge node) provides to a center namespace; or a second edge node (any edge node other than the first edge node) in a synchronization, which applies an update of the center namespace to a second local namespace which the second edge node provides. Specifically, either the center node or the second edge node: (A) determines whether the situation with respect to the differing objects corresponds to a conflict case among defined conflict cases; and (B) if the result of the determination in (A) is affirmative, executes a process according to a confliction resolution policy which is associated with the corresponding conflict case.