Autonomous Application Re-initialization After Server Reboot
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Rebooting of server devices hosting client-facing applications leads to delays in servicing user requests due to the applications not re-initializing until a user request is received, violating service level agreements (SLAs) as they reload, re-initialize, and recompile only after the first request.
Innovation Solution
A configuration file is modified to identify applications that should always run with an automatic start enabled, allowing them to autonomously reload, re-initialize, and recompile upon detecting a device state change such as a reboot, ensuring they are ready to serve requests promptly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If devices are rebooted periodically to avoid faults and hung states, then device reliability is improved, but application service availability deteriorates due to delays in servicing user requests
Solution Approach 1:
The system performs preliminary actions by detecting device state changes (reboots) and automatically re-initializing applications before user requests arrive. The configuration file is modified to include auto-start enabled applications, and a service monitors device state changes to trigger application re-initialization in advance, ensuring applications are ready before the first user request after reboot.
2Loss of energy
If applications wait for user requests to re-initialize after device reboot, then resource usage is optimized, but service response time deteriorates violating SLA requirements
Solution Approach 1:
The system implements feedback by having a service continuously monitor device state changes and automatically trigger application re-initialization when a reboot is detected. The modified configuration file provides feedback information about which applications should auto-start, creating a closed-loop system that responds to device state changes and ensures SLA compliance without wasteful continuous running of all applications.
3Loss of time
If all applications are kept running continuously to avoid startup delays, then service availability is improved, but device resource consumption increases
Solution Approach 1:
Instead of keeping all applications continuously running, the system takes preliminary action only when needed - detecting device state changes and automatically re-initializing applications before user requests. This on-demand approach ensures service availability when reboots occur without the continuous resource consumption of keeping all applications running all the time.
Data Source
AI summary
Arrangements for autonomously re-initializing one or more applications after a detected change in device state are provided. In some examples, a configuration file may be received from one or more computing devices, such as a server, hosting one or more client-facing applications. In some examples, the configuration file may be modified. For instance, one or more properties or attributes may be modified or added to identify applications that have an always running status and identifying a custom class having automatic start enabled. A modified configuration file may be generated and transmitted to the one or more devices. Accordingly, upon detecting a change of device state (e.g., reboot, refresh, or the like) the modified configuration file may reboot and cause the identified applications to automatically or autonomously re-load, re-initialize and recompile prior to receiving a first request for access from a customer or user device.