Pluggable Database Migration Under Resource Pressure
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database administrators face challenges in dynamically monitoring resources assigned to pluggable databases within a container database management system and determining when a pluggable database needs to be migrated to another container for additional resources.
Innovation Solution
A system is implemented that identifies and groups computing resources dedicated to a pluggable database, monitors these resources in real-time, and determines whether the pluggable database should be migrated based on monitored metrics, such as CPU usage, memory usage, and input/output usage rates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If database administrators manually monitor and manage resources for pluggable databases, then resource allocation can be controlled, but the system complexity and administrative overhead increase significantly
Solution Approach 1:
The system enables automated self-service resource management through the resource monitoring service that continuously monitors resource usage metrics and the resource management service that automatically relocates pluggable databases in response to resource pressure conditions, eliminating the need for manual database administrator intervention while maintaining reliable resource allocation
Solution Approach 2:
The system implements continuous feedback loops where the resource monitoring service collects real-time resource usage metrics, compares them against thresholds, and triggers automated relocation actions through the resource management service when resource pressure conditions are detected, creating a closed-loop control system that maintains resource balance without manual intervention
2Reliability
If resources are over-provisioned to prevent resource pressure, then user response time is maintained, but resource utilization efficiency decreases
Solution Approach 1:
The system dynamically adjusts resource allocation by continuously monitoring resource usage metrics and automatically relocating pluggable databases in response to changing resource pressure conditions, allowing the system to adapt resource distribution in real-time rather than relying on static over-provisioning, thereby maintaining user response time while improving overall resource utilization efficiency
Solution Approach 2:
The system changes operational parameters by monitoring resource usage thresholds and triggering automated relocation actions when parameters exceed defined limits, enabling dynamic resource optimization that prevents both over-provisioning and resource starvation, thus maintaining reliable user response times while maximizing resource utilization
3Reliability
If pluggable databases are frequently migrated to balance resources, then resource pressure is reduced, but system stability and performance during migration decrease
Solution Approach 1:
The system uses feedback-controlled migration triggers that monitor resource pressure conditions and initiate migrations only when thresholds are exceeded, preventing unnecessary frequent migrations while ensuring resource balance is maintained, thus stabilizing the system by migrating only when genuinely needed rather than on fixed schedules or in response to minor fluctuations
Data Source
AI summary
Techniques are provided for implementing a pluggable database monitoring system that groups running processes for the pluggable database into a grouping and monitors resource usage for the grouping to determine whether to migrate the pluggable database to another container. A system identifies a set of running processes associated with a pluggable database. The pluggable database is hosted on a container DBMS, which is hosted on a virtual machine. The system generates a first grouping that contains the set of running processes. The system monitors, in real-time, aggregated resource usage of the first grouping to determine if the aggregated resource usage exceeds a first threshold. In response to the aggregated resource usage of the first grouping exceeding the first threshold, the system migrates the first pluggable database to a second container DBMS.