Adaptive HCI Node Event Notification Interval Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Hyper-converged infrastructure (HCI) managers are often overwhelmed, leading to undesirably delayed event notifications due to using static, worst-case scenario-based intervals, which impacts the timeliness of notifications.
Innovation Solution
Implementing a node-side event notification monitoring service that adjusts notification intervals based on parameters such as urgency and success/failure of previous notifications, using formulas to dynamically adjust the frequency of notifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a static, worst-case scenario-based notification interval is used, then the HCI manager is not overwhelmed, but the timeliness of event notifications deteriorates
Solution Approach 1:
The notification interval is transformed from a static, fixed value to a dynamic parameter that automatically adjusts based on the HCI manager's current workload and processing capacity. The system continuously monitors the manager's state and modifies the interval accordingly, allowing shorter intervals when the manager is underutilized and longer intervals when overloaded, thus resolving the contradiction between reliability and timeliness
Solution Approach 2:
The system implements a feedback mechanism where the HCI manager's processing status and notification queue state are continuously monitored and fed back to the node. Based on this feedback, the notification interval is automatically adjusted - if the manager is processing notifications quickly, the interval is reduced; if the manager is overwhelmed, the interval is increased. This closed-loop control resolves the contradiction by adapting to real-time conditions
2Productivity
If a constant notification frequency is used, then the HCI manager can be managed predictably, but the urgency of critical events is not adequately prioritized
Solution Approach 1:
The notification system applies different quality levels to different notifications based on their urgency. Critical notifications receive preferential treatment with shorter intervals and higher priority, while non-critical notifications use longer intervals. This local differentiation of notification quality resolves the contradiction by ensuring critical events are responded to reliably while maintaining overall system productivity
Solution Approach 2:
The system changes the notification interval parameter dynamically based on the urgency level of pending notifications. When critical notifications are detected in the queue, the interval parameter is reduced to ensure timely delivery. When only non-critical notifications are present, the interval is extended to maintain productivity. This parameter adaptation resolves the contradiction between throughput and critical event responsiveness
Data Source
AI summary
A disclosed event notification management method and service for use with a multi-node, hyper-converged infrastructure (HCl) cluster employs a service running on a corresponding node to monitor one or more parameters associated with event notifications sent to a cluster. The service may adjust a node's notification interval based on the monitored parameters. The parameters may include a last event notification successful (LENS) parameter indicating whether a recent notification was successful and a severity parameter determined based on an urgency type of a plurality of pending notifications within an event queue. The service may employ a first formula to decrease the notification interval following a successful previous notification and a second formula to increase the notification interval following an unsuccessful notification. The magnitude by which the notification interval is adjusted may be influenced by the severity parameter, e.g., to aggressively reduce the notification interval following successful notifications when urgency is high.