Cluster Controller File Replication via Service Agents
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In high-availability controller clusters, maintaining data coherency across multiple controllers is challenging, especially during master switchover, file replication, and deletion, leading to potential delays and bandwidth inefficiencies due to chaotic data copying and unclear replication sources.
Innovation Solution
A cluster file replication system where each controller has a filesystem with a system database and service agents that coordinate replication of changes from a master controller to follower controllers, disabling initiation of replication on followers while supporting change reception, ensuring transparent data replication and persistence.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If frequent data copying is implemented across controllers, then data coherency is improved, but system bandwidth and processor resources are consumed excessively
Solution Approach 1:
The patent implements preliminary action by pre-establishing replication objects and configuring replication policies before data coherency issues arise. Service agents proactively monitor controller roles and initiate replication only when necessary (e.g., during master controller changes), rather than continuously copying data. This approach ensures data coherency is maintained while avoiding unnecessary bandwidth consumption during stable operational states.
2Reliability
If data replication is coordinated across controllers, then data coherency is improved, but device complexity increases
Solution Approach 1:
The patent introduces service agents as intermediary components that mediate between controllers and the replication mechanism. These agents abstract the complexity of replication coordination by automatically detecting controller role changes (master/follower status) and triggering appropriate replication actions. This intermediary layer simplifies the overall system architecture by centralizing replication logic and reducing direct coordination overhead between controllers.
3Reliability
If replication objects are enabled on all controllers, then data reception capability is improved, but chaotic data initiation occurs
Solution Approach 1:
The patent applies local quality by differentiating the functionality of replication objects based on controller role. Replication objects on the master controller are configured to initiate replication (source mode), while replication objects on follower controllers are configured only to receive replication (destination mode). This role-based differentiation ensures that data flow is unidirectional and controlled, preventing chaotic data initiation while maintaining robust reception capability across all controllers.
Data Source
AI summary
A cluster data replication system includes a plurality of network elements and controllers. The controllers form a cluster that is able to elect one of the controllers as a master controller with the others being follower controllers. The elected controller updates, responsive to being elected the master controller, state information in a system database of the elected controller to indicate that the elected one of the controllers is the master controller. The master controller includes one or more objects that are enabled in reaction to the state information, and which coordinate replication of changes to the data, system database, and state information from the master to the follower controllers. Each follower controller includes one or more objects able to, in reaction to the state information, disable initiation of the replication of changes to the data, system database and state information by the one or more objects in each follower controller.