Transactional Index Schema Amendment via Parallel Build
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In-memory database systems face significant downtime when rebuilding transactional indexes due to schema modifications, as the entire system must be taken offline to prevent data inconsistencies.
Innovation Solution
A system that allows for the background building of a new transactional index while the old one is still in use, maintaining both indices in parallel and switching to the new one when complete, minimizing downtime by incorporating metadata amendments and using a processor to manage the transition.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the transactional index is completely rebuilt to incorporate schema modifications, then the index remains current and accurate, but the system must be taken offline causing significant downtime
Solution Approach 1:
The system performs preliminary actions by creating a new transactional index in advance while the old index is still in use. The new index is built incrementally in the background, allowing the system to switch to it once complete, thereby avoiding downtime. This is achieved through maintaining multiple transactional indices and progressively building the new one before it is needed.
Solution Approach 2:
The system introduces an intermediary mechanism by maintaining multiple transactional indices simultaneously. The old index continues to serve queries while the new index is being built in the background. Once the new index is complete, the system transitions to using it, ensuring continuous operation without requiring the system to go offline during the rebuild process.
2Reliability
If the system is taken offline to rebuild the transactional index, then data inconsistencies are prevented, but continuous operation is interrupted
Solution Approach 1:
The system ensures continuity of useful action by allowing the old transactional index to continue serving queries while the new index is being built in the background. This parallel operation maintains system availability and productivity throughout the index rebuild process, eliminating the need to interrupt service for maintenance.
Solution Approach 2:
The new transactional index is built in advance as a preliminary action while the system remains operational. This allows the rebuild process to complete before the old index becomes obsolete, ensuring data consistency is maintained without interrupting system availability or productivity.
3Power
If the transactional index is rebuilt offline, then system resources are freed for the rebuild process, but the system cannot serve queries during the rebuild
Solution Approach 1:
The system segments the transactional index functionality by maintaining multiple indices simultaneously. The old index continues to handle queries while the new index is being built with dedicated processing capacity. This segmentation allows the system to allocate resources for the rebuild process without compromising query service continuity, as both operations can proceed in parallel.
Data Source
AI summary
A system for indexing includes an interface and a processor. The interface is configured to receive a metadata amendment. The metadata amendment defines a change to a transactional index schema to a first transactional index. The first transactional index comprises a querying system data. The processor is configured to maintain a first state of the first transactional index. The first transactional index does not incorporate the metadata amendment. The processor is configured to build a second transactional index incorporating the metadata amendment, determine whether an indication to switch from the first transactional index to the second transactional index has been received, and indicate to switch from using the first transactional index to the second transactional index for queries regarding a system data.