JDBC slave cannot acquire lock when the master loose database connection.
Issue
We use ActiveMQ Message broker with a Master/Slave, Network of Broker topology with Database as persistence.
Many a times we have seen that when DB connectivity is lost. Our Master goes down but the Database lock is not released for the slave to become master. In addition, when the old Master is brought back up, it could not get the lock either and we are left with two slaves.
Environment
- Fuse Message Broker 5.5.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.