Cluster Event Management Module for Ordered Queueing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing distributed network systems lack an efficient and reliable mechanism for notifying applications of cluster events such as membership changes, service availability, and node additions/deletions, which are critical for maintaining accurate configurations and ensuring system reliability.
Innovation Solution
A cluster event management module (CEM) is deployed within a container orchestration service, which receives and queues events related to membership changes and resource availability, and notifies subscribed members in a reliable and ordered manner, ensuring that events are processed hierarchically across all subscribers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a distributed file system is used to provide networked computers working together, then system scalability is improved, but event notification reliability and ordering become more difficult to maintain
Solution Approach 1:
The patent introduces an event notification service as an intermediary component that sits between event sources and event consumers. This mediator collects events from various sources, maintains a centralized event queue, and distributes events to subscribers in a reliable manner, solving the scalability-reliability contradiction in distributed systems.
Solution Approach 2:
The event notification service provides universal functionality by serving multiple purposes: collecting events from diverse sources, maintaining ordering, ensuring delivery to multiple subscribers, and handling priority Queues. This multi-functional approach enables reliable event notification across scalable distributed systems.
2Reliability
If multiple applications track cluster events to maintain accurate configurations, then system reliability is improved, but event processing complexity increases
Solution Approach 1:
The event notification service acts as an intermediary that simplifies event processing by centralizing event collection, ordering, and distribution. Applications only need to subscribe to events through a simple interface, while the mediator handles the complex tasks of maintaining order, ensuring delivery, and managing priorities.
Solution Approach 2:
The system segments event processing into distinct phases: event collection from sources, event ordering in a priority queue, and event distribution to subscribers. This segmentation allows each component to focus on a specific function, reducing overall processing complexity while maintaining reliability.
3Speed
If events are delivered to all subscribers immediately, then response time is improved, but event ordering and priority handling become difficult to maintain
Solution Approach 1:
The system performs preliminary action by pre-establishing priority levels for different event types and subscribers before events occur. The priority queue is pre-configured with ordering rules, allowing events to be automatically sorted and delivered in the correct sequence without complex real-time decision-making.
Solution Approach 2:
The event notification service as an intermediary manages the complexity of ordering and priority handling centrally. It receives events from multiple sources, sorts them according to predefined priorities, and delivers them to subscribers in the correct order, maintaining both speed and ordering simplicity.
Data Source
AI summary
A cluster event management module that is deployed in a container orchestration service of a distributed (clustered) network that has multiple running services. The CEM receives and queues events that affect membership changes and system resource (services, nodes, pods) availability, and notifies current subscribed members in so that appropriate action can be taken with respect to their own services and resources. The CEM provides notifications such that events are delivered in the order of generation, all subscribers see the same sequence of events, each event is processed in a hierarchical order across all subscribers in a way that ensures that no event is missed and reliability of event notification is maintained.