Persistent Metadata Store for Network File System Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Large-scale network file management systems face inefficiencies during updates, as generating metadata at runtime can be time-intensive and may require querying each content database, leading to slowed or blocked processes, especially when some databases are unavailable.
Innovation Solution
Implementing a persistent metadata store and access control list allows for batch rollouts by storing metadata separately and using a shared access control model, enabling efficient updates without affecting individual content databases and allowing immediate functionality upon registration of connection strings during server farm transitions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If metadata is generated at runtime by querying each content database, then the system can maintain up-to-date metadata, but the update process becomes time-intensive and may be blocked when databases are unavailable
Solution Approach 1:
The patent applies preliminary action by pre-generating and storing metadata in a separate metadata store before runtime operations. During system updates, the metadata is already prepared and available, eliminating the need to query content databases at update time. This allows updates to proceed without waiting for database availability, resolving the contradiction between maintaining accurate metadata and reducing update time.
2Loss of information
If the system queries each content database to generate metadata during updates, then comprehensive metadata can be obtained, but the process is slowed or blocked when some databases are unavailable
Solution Approach 1:
The patent applies segmentation by separating the metadata store from the content databases. Metadata is extracted and stored independently in a dedicated metadata store, which can be updated and queried separately from the content databases. During system updates, only the metadata store needs to be accessed, not the entire content database infrastructure, allowing updates to proceed at full speed without being blocked by unavailable databases while maintaining complete metadata information.
3Reliability
If database operations are performed during rollout updates, then data consistency can be maintained, but downtime increases and system functionality is disrupted
Solution Approach 1:
The patent applies the extraction principle by removing metadata operations from the content database system and placing them in a separate metadata store. During rollout updates, metadata generation and validation operations are extracted from the update process itself, allowing updates to be applied without blocking database operations. This separation enables data consistency to be maintained through the metadata store while avoiding downtime caused by database operations during the update process.
Data Source
AI summary
In one embodiment, a network file management system 120 may use a persistent metadata store 410 and an access control list 420 to facilitate a batch rollout. The network file management system 120 may maintain a content database 312. A network file management system 120 may store a metadata set for the content database 312 in a separate persistent metadata store 410.