Cloud Storage Data Clearing via Deletion Log and Slicing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data deletion methods in cloud storage systems are inefficient, leading to potential deletion failures, excessive resource consumption, and prolonged processing times due to direct deletion of meta and data, resulting in wasted storage space and poor user experience.
Innovation Solution
The method involves slicing user data into independent data slices, deleting meta information upon file deletion, and distributing data for processing across multiple nodes, allowing for efficient data clearing and resource management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If direct deletion of meta and data is performed, then deletion operation is simple, but deletion failure rate increases and storage space is wasted
Solution Approach 1:
The patent applies preliminary action by creating a deletion log before actual deletion occurs. When a user deletes a file, the system records the deletion request in a log rather than immediately deleting the data. This allows the deletion to be processed asynchronously and recoverably, preventing data loss from failed deletion operations while keeping the user interface simple.
Solution Approach 2:
The patent introduces a deletion log as an intermediary between the deletion request and actual data removal. The log serves as a buffer that decouples the deletion command from the deletion execution, allowing the system to track and manage deletions reliably without complicating the user's deletion operation.
2Reliability
If direct deletion of all meta and data is performed, then deletion is thorough, but processing time increases
Solution Approach 1:
The system performs preliminary recording of deletion requests in a log without immediately executing the deletion. This separates the deletion acknowledgment (instant) from the actual data removal (asynchronous), reducing perceived processing time while ensuring thorough deletion through the log-driven cleanup process.
Solution Approach 2:
The patent implements periodic action by processing deletions asynchronously rather than synchronously. The deletion log is processed periodically or in batches, allowing the system to maintain deletion completeness while significantly reducing the time users wait for deletion confirmation.
3Productivity
If multiple direct deletion operations are performed, then data is cleared, but server resource consumption increases
Solution Approach 1:
The patent merges multiple deletion operations into a single log entry per file, regardless of how many times the file is referenced or how complex the deletion logic is. This consolidation reduces the number of actual deletion operations the system must perform, lowering server resource consumption while maintaining full data clearing capability.
Solution Approach 2:
By recording deletions in advance in a log, the system can batch-process and optimize the actual deletion operations. This preliminary recording allows the system to consolidate resource-intensive deletion tasks, reducing overall server resource consumption compared to immediate individual deletions.
4Adaptability or versatility
If deletion logics are diverse and complicated, then various deletion scenarios are handled, but deletion failure rate increases
Solution Approach 1:
The deletion log acts as an intermediary that simplifies complex deletion logic into a uniform recording mechanism. Regardless of the complexity of deletion scenarios (different file types, permissions, storage locations), all deletions are recorded in the same log format, reducing failure rates by eliminating complex conditional logic from the critical deletion path.
Solution Approach 2:
The system performs preliminary analysis and categorization of deletion requests in the log before execution. This allows complex deletion scenarios to be prepared and validated in advance, with the actual deletion being a simpler, more reliable operation that follows pre-determined logic based on the logged information.
Data Source
AI summary
An object of the present invention is to provide a method and apparatus for clearing data in a cloud storage system. The method according to the present invention comprises the following steps: deleting meta information of a data slice corresponding to the file upon detecting that a user is deleting a file; wherein the method comprises the following steps: exporting all data slices to be processed when data needs to be cleared; by traversing each file in the meta information, determining each data slice that may be accessed through the meta information and thereby obtaining corresponding access data information; based on the access data information, determining the data to be cleared in said all data slices to perform data clearing operation for the data to be cleared. The present invention has the following advantages: avoiding likely deletion failure in the conventional manner of directly deleting the data information of the file, thereby reducing the storage space occupied by trash data and improving a resource utilization rate and a load level of the system.