Justin, That is what I expected too. And it is one of the scenarios that I tried. Indeed, the status turns green while stating "HA Policy: Live Only". But at the same time, that server is no longer connecting to the other cluster members, even though exactly the same cluster-connections and connectors are used. And then the server is no longer part of the cluster as intended...
Erwin -----Oorspronkelijk bericht----- Van: Justin Bertram <jbert...@apache.org> Verzonden: donderdag 18 februari 2021 19:19 Aan: users@activemq.apache.org Onderwerp: Re: non-standard cluster topology EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe. EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre. I believe the "red cross" is showing up because you've defined an ha-policy in your broker.xml and designated the broker explicitly as a master. It therefore expects a backup to be available, and since there is no backup it displays the red cross. If you just take the ha-policy out of broker.xml then the status screen should show all green check marks. I just tested this and it works as expected. Justin On Thu, Feb 18, 2021 at 12:00 PM Dondorp, Erwin <erwin.dond...@cgi.com> wrote: > Hello, > > > > In the cluster topology, one can define a server as “master” or “slave”. > > For a specific application, only non-persistent messages are present. > > (and non-persistent messages are not sent to the slave servers) > > This makes the master/slave situation a bit useless; and so, I want to > use only “master” servers. > > However, when no slave servers are available, a big red cross is shown > on the “Status” screen of the master servers. > > Is there a way to use a master-only cluster without showing this warning? > > i.e. tell it that it is fine that there is no slave-server. > > > > thx, > > Erwin > > > >
