zookeeper fail-over causes broker downtime

Solution In Progress - Updated -

Issue

We have a setup with 3 machines, all having 1 root-container and 1 child container.
The child container runs a replicated leveldb broker, the root-containers are all part of the ensemble.

Scenario:
1) all containers are running
2) shutdown child number 3, broker still works as expected, fail-over if needed.
3) shutdown root container 3, the master broker (child container 1) now gets the message "Demoted to slave", while the second broker gets the message "Not enough cluster members connected to elect a master."

This causes downtime of the service while this wasn't expected when shutting down a slave broker. Majority should still remain at this point for both the zookeeper ensemble and the brokers.

Environment

  • JBoss Fuse/A-MQ 6.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.