Server Instance Maintenance via Median Frequency Batching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing methods for maintaining server instances in a cloud computing environment are tedious and time-consuming, as they require quarantining and updating each instance individually, disrupting service and reducing throughput.
Innovation Solution
A framework that selects server instances based on usage frequency to maintain them in batches, using a control component and dispatcher to logically quarantine and decouple instances for maintenance, ensuring continuous service and efficient maintenance cycles.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If server instances are maintained individually one-by-one, then maintenance can be completed thoroughly, but service continuity is disrupted and throughput decreases
Solution Approach 1:
The system segments server instances into multiple batches based on their usage frequency relative to the median. Instances are divided into first batches (with usage frequency closer to median) and second batches (with usage frequency further from median), allowing maintenance to proceed in controlled groups rather than individually, thus maintaining service throughput while ensuring maintenance completeness.
Solution Approach 2:
The system performs preliminary classification of server instances by calculating their usage frequencies and determining which instances should be maintained first based on their proximity to the median usage frequency. This preliminary ordering ensures that maintenance proceeds in an optimal sequence that minimizes service disruption while maintaining thoroughness.
2Productivity
If server instances are maintained in batches, then service continuity is maintained and throughput increases, but maintenance complexity increases
Solution Approach 1:
The system implements feedback mechanisms by continuously monitoring usage frequency of server instances and adjusting maintenance scheduling accordingly. The usage frequency calculations and comparisons to median values provide feedback that automatically determines batch composition and maintenance sequencing, reducing the perceived complexity through automated decision-making.
Solution Approach 2:
The maintenance system operates autonomously by automatically calculating usage frequencies, determining median values, classifying instances into batches, and scheduling maintenance without manual intervention. This self-service capability reduces operational complexity while enabling efficient batch maintenance that maintains service throughput.
3Reliability
If high usage frequency instances are maintained first, then service impact is minimized, but maintenance time increases due to prioritizing busier instances
Solution Approach 1:
Instead of maintaining high usage frequency instances first as might be intuitively expected, the system inverts the approach by prioritizing instances with usage frequency closer to the median. This inverted strategy balances service impact and maintenance efficiency, as instances near median frequency represent a compromise point that minimizes overall system disruption while avoiding the time cost of maintaining peak-usage instances.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
A framework for maintaining a plurality of server instances in batches to ensure continuity of service is described herein. In accordance with one aspect, quantities of the server instances are selected in an order based on a usage frequency of the server instances with respect to a median usage frequency of the plurality of server instances. The selected server instances may be logically quarantined for maintenance, one batch at a time. Each batch of server instances may be returned to service when the server instances of the batch are successfully maintained while logically quarantining a next batch of server instances.