Remote File Cloning Delegation and Cleanup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In distributed file systems, remote cloning of files can lead to resource allocation issues due to failures during the cloning process, resulting in resources being assigned to clones that are not used, and existing solutions do not effectively manage these failures to ensure data consistency and resource release.
Innovation Solution
A method is introduced where a first node requests a full exclusive delegation of an original file from a second node, marks the file to lock it at a specific point in time, creates a clone file, and manages the delegation to ensure the original and clone files match until the clone is committed, with mechanisms for resource cleanup in case of failures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If remote cloning is performed in distributed file systems, then file replication capability is improved, but resource allocation reliability deteriorates due to failures during cloning process
Solution Approach 1:
The patent applies preliminary action by performing delegations and locking the original file at a specific point in time before the cloning operation begins. This ensures that the original file state is preserved and resources are properly allocated before any cloning failure can occur, resolving the reliability issue while maintaining replication capability
Solution Approach 2:
The patent implements feedback mechanisms through delegation tracking and commitment status monitoring. The system continuously monitors the cloning process and provides feedback about resource allocation status, enabling proper cleanup when failures occur and ensuring resource allocation reliability is maintained throughout the replication process
2Productivity
If cloning process continues without failure management, then cloning speed is improved, but data consistency deteriorates due to unhandled failures
Solution Approach 1:
The patent applies beforehand cushioning by establishing delegation relationships and locking mechanisms prior to the cloning operation. This creates a protective framework that cushions against potential failures, ensuring data consistency is maintained even if cloning operations encounter issues during execution
3Adaptability or versatility
If resources are allocated during cloning, then cloning functionality is improved, but resource waste increases when cloning fails
Solution Approach 1:
The patent implements discarding and recovering by automatically releasing delegations and cleaning up resources when cloning operations fail or are aborted. The system tracks resource allocation throughout the cloning process and ensures proper recovery, preventing resource waste while maintaining full cloning functionality
Solution Approach 2:
The patent applies self-service through automatic resource management and cleanup mechanisms. The system autonomously handles delegation release and resource recovery without external intervention, ensuring that resources are properly managed and wasted resources are minimized while preserving cloning capabilities
Data Source
AI summary
Approaches and mechanisms for cloning a file are described. A first node requests a clone of a file at a time when it also requests an exclusive delegation of the original file from a second node where the original file is stored. The second node marks the original file as delegated to the first node and the second node records an intent to create the clone file and a delegation record for the clone file. The second node creates the clone file. The delegation of and the identity of the clone file are returned to the first node. The first node marks in the delegation record that the clone file was committed in response to modification. If the clone file was committed the delegation is cleared and the clone file is kept, and if the clone file was not committed, the delegation is cleared, and the clone file is deleted.