Virtual Server Dormancy for Seamless Software Upgrades
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing virtual server deployment systems face challenges in synchronizing multiple components to ensure data integrity, leading to difficulties in minimizing downtime during upgrades and restarts.
Innovation Solution
The implementation of a dormant state for server components, where they cannot accept new connections and become read-only for existing connections, allowing for safe and seamless upgrades and load balancing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual shutdown of each component is performed to ensure data integrity, then data integrity is improved, but system downtime increases
Solution Approach 1:
The system is divided into multiple independent virtual server components that can be managed separately. Each component can be transitioned to dormant state individually, allowing other components to remain active and handle requests, thus maintaining system availability while ensuring data integrity during updates
Solution Approach 2:
The dormant state mechanism performs preliminary actions by transitioning components to a controlled dormant state before actual updates or maintenance activities. This preliminary state ensures that no new connections are accepted and existing connections are completed, guaranteeing data integrity before the component is fully shut down for maintenance
2Reliability
If multiple server components are synchronized to ensure data integrity, then data integrity is improved, but system complexity increases
Solution Approach 1:
The dormant state acts as an intermediary mechanism between active server components and maintenance operations. By introducing this intermediate state, the system simplifies coordination between multiple components, as each component independently transitions through the dormant state without requiring complex inter-component synchronization protocols
3Reliability
If servers are taken offline for upgrades, then software reliability is improved, but system availability decreases
Solution Approach 1:
The server system is segmented into multiple independent virtual server components that can be upgraded sequentially. While one component is taken offline for upgrades, other components remain active and continue to handle client requests, maintaining overall system availability while ensuring software reliability through systematic updates
Solution Approach 2:
The system maintains continuity of useful action by ensuring that while one virtual server component is upgraded, other components continue to provide services. The load balancing mechanism redistributes requests to active components, ensuring uninterrupted service delivery and maintaining system availability throughout the upgrade process
Data Source
AI summary
A method for providing a dormant state for content management servers is provided. Client devices are allowed to conduct transactions with servers when the servers are active. However, in a dormant state, the servers are not allowed to accept new transactions. Thus, by utilizing the dormant state, software upgrades can be made to one server at a time. Alternatively, all servers can be taken down for major upgrades, with the servers still operated in a read-only mode based on a file image from a point in time just prior to the shutdown. When the upgrade is completed, the servers can be returned to the active state.