Bus Exception Handling in Multi-Controller Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In dual-control and quadruple-control architecture configurations, communication exceptions between controllers often lead to 'split-brain' scenarios and data inconsistency, particularly when all controllers are poorly connected, causing multiple master controllers to be elected and resulting in inconsistent data handling.
Innovation Solution
A bus exception handling method that monitors data from multiple target buses, including a master bus and candidate buses, to determine if a bus exception condition is met, such as data content or marker exceptions, and selects a healthy candidate bus as a new master bus to ensure consistent data communication, thereby preventing 'split-brain' and data inconsistency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple controllers are used in dual-control or quadruple-control architecture, then service performance and disaster tolerance are improved, but communication exceptions between controllers may cause split-brain scenarios and data inconsistency
Solution Approach 1:
The system performs preliminary actions by continuously monitoring bus communication status and detecting exceptions before they cause split-brain scenarios. The master controller proactively identifies communication failures between controllers and takes corrective action by reelecting a new master controller, preventing the harmful effect of data inconsistency from occurring.
Solution Approach 2:
The system implements feedback mechanisms through continuous monitoring of bus communication status between controllers. When communication exceptions are detected, the system provides feedback by triggering a reelection process, ensuring that the master controller status reflects the actual communication state and preventing split-brain scenarios.
2Reliability
If all controllers are poorly connected on the bus, then communication failure occurs, but multiple master controllers may be elected causing data inconsistency
Solution Approach 1:
The system uses feedback from bus monitoring to detect when all controllers are poorly connected. The master controller continuously monitors communication status and, upon detecting universal communication failure, triggers a reelection process to ensure only one master controller is active, preventing data inconsistency even when communication is compromised.
Solution Approach 2:
The system performs self-service by automatically detecting communication exceptions and initiating the reelection process without external intervention. The master controller monitors its own communication status and takes corrective action, ensuring data consistency is maintained through autonomous exception handling.
3Reliability
If bus communication is monitored continuously to detect exceptions, then split-brain can be prevented, but system complexity increases
Solution Approach 1:
The system extracts the exception detection and handling functionality into a dedicated master controller that performs monitoring and reelection operations. This separation of concerns allows other controllers to focus on their primary functions while the master controller handles the complexity of communication monitoring and exception management, reducing overall system complexity.
Data Source
AI summary
Provided are a bus exception handling method and apparatus, an electronic device and a computer-readable storage medium. The method includes: respectively obtaining, from multiple target buses, multiple pieces of target data corresponding to the multiple target buses, where the multiple target buses include a master bus and one or more candidate buses, and the target data corresponding to the master bus is referred to as first data; determining whether the first data satisfies a bus exception condition, where the bus exception condition is a data bus marker exception condition or a data content exception condition; and in response to determining that the first data satisfies the bus exception condition, selecting a target candidate bus in a healthy state as a new master bus, and updating local bus data.