Hello, I am running two controllers with RAIDB-1 scheme. But, the problem is when network is partitioned because of a switch failure. In this scenario, two controllers will receive user's requests from each. So, it will make two backends inconsistent. >From the Bianca's papers I reallized that this network partition very often can happen.
When I look at this mailing-list, Emmanuel suggested to unify database communication path and user request path in network topology. But, in our case, databases are already communicating via gigabit network, seperated from outside communication channel. And, I read the "C-JDBC Horizontal Scalability: A controller replication user guide", and understood I need to make a JMX client which listens from JMX notification of Sequoia controllers. I think that this process will need to stop one controller, when two controllers are partitioned, or switch a backend database to the read-only mode. At this point, I have a quick question. I wonder if there is another better solution dealing with this sort of network partition in Sequoia. Thank you for your reading. Best,
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
