Database Quiesce via Request Scheduling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database quiesce operations cause applications attempting to access the database to fail, resulting in business losses due to periods of database outage and inefficient resource usage.
Innovation Solution
A method that modifies control parameters to schedule incoming access requests instead of abnormally terminating them, allowing in-flight transactions to complete before performing maintenance or log operations, and then writing data to permanent storage for continued access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the database is forced to a quiesce point by abnormally terminating all access requests, then the database can be safely quiesced for maintenance operations, but applications attempting to access the database during the quiesce operation fail and business is lost
Solution Approach 1:
The system performs preliminary actions by setting a quiesce indicator and scheduling pending access requests before actually quiescing the database. This allows the database to be prepared for quiesce operations while maintaining application access continuity, resolving the contradiction between safe quiesce and continuous productivity
Solution Approach 2:
The patent introduces a command processor as an intermediary layer between applications and the database. The command processor manages the quiesce operation by scheduling access requests and coordinating with the database manager, allowing quiesce operations to proceed without forcing applications to fail
2Reliability
If the database is quiesced using traditional methods, then maintenance operations can be performed, but the time and processor burden required for quiesce operations increases
Solution Approach 1:
The system maintains continuity of useful action by allowing access requests to be scheduled and processed during the quiesce operation rather than terminating them. This reduces the total time required for quiesce operations while maintaining the ability to perform maintenance, as the database can be quiesced without forcing applications to fail and without requiring lengthy deallocation and reallocation cycles
Data Source
AI summary
A technique to quiesce a database without causing after-arriving access requests to abnormally terminate interrogates database management system control structures associated with the database. Specified modifications to these control structures can be made so that subsequent access requests to the database (i.e., during quiesce operations) are not abnormally terminated. Once quiesced, regular or special purpose maintenance or testing operations, the starting or stopping of log keeping operations or similar operations may be made to the database. Once these are complete, the database control structures may be updated again to permit pending/scheduled access requests to proceed.