Hi, active/active deployment you are talking about in Artemis world is just "group of brokers". It doesn't provide you HA by default, but two groups can be configured for HA. It's a little bit wasteful because you will have to add 3-4 broker to satisfy your requirements, but generally it works.
I recommend reading RedHat's AMQ (which is based on Artemis) clustering documentation at https://docs.redhat.com/en/documentation/red_hat_amq/7.4/html/configuring_amq_broker/setting-up-broker-cluster-configuring#setting-up-broker-cluster-configuring . They have a little bit more information and some nice pictures to understand how Artemis clustering can be configured. -- Vilius -----Original Message----- From: William Crowell <wcrow...@perforce.com.INVALID> Sent: Tuesday, March 18, 2025 1:53 PM To: users@activemq.apache.org Subject: Re: What HA Replication Policy Is For Active-Active Topology Domenico, Hi. I require 2 brokers to be primary/active at the same time. The way the documentation is written it does not come out and say you can run with that configuration; however, this statement leads you to believe that configuration is possible: https://activemq.apache.org/components/artemis/documentation/latest/clusters.html#performance-considerations 1. “Start simple. Benchmark your use-case with a single broker first. A single broker can handle millions of messages per second in certain use-cases. If you can’t meet your performance goal with a single broker only then move to a clustered configuration. Only add complexity when there is a clear benefit.” Regards, William Crowell From: Domenico Francesco Bruscino <bruscin...@gmail.com> Date: Tuesday, March 18, 2025 at 6:15 AM To: users@activemq.apache.org <users@activemq.apache.org> Subject: Re: What HA Replication Policy Is For Active-Active Topology Hi William, the HA policies allow the system to continue functioning after failure of one or more of the servers. They require at least 2 brokers to work. The first broker is active and the second broker waits for the first broker failure to replace it reloading durable/persisted messages. In this way, the client connections can migrate from one server to another in event of server failure so client applications can continue to operate. Can you clarify your expectations from an active/active deployment? Regards, Domenico On Mon, 17 Mar 2025 at 16:22, William Crowell <wcrow...@perforce.com.invalid> wrote: > Good morning, > > It appears all HA policies are for active/passive setup. Are there > any for active/active? Does this exist? > > I was reading through: > https://activemq.apache.org/components/artemis/documentation/latest/ha > .html#replication<https://activemq.apache.org/components/artemis/docum > entation/latest/ha.html#replication> > > For example, you have 2 Artemis brokers and you want them both to be > active at the same time, and the data directories are separate. > > Would you just specify the following in broker.xml on both servers? > > <ha-policy> > <replication> > <primary/> > </replication> > </ha-policy> > > I looked through the examples here and could not find it (unless I > missed > it): > > > https://github.com/apache/activemq-artemis-examples/tree/main/examples > /features/ha > > Regards, > > William Crowell > > > This e-mail may contain information that is privileged or > confidential. If you are not the intended recipient, please delete the > e-mail and any attachments and notify us immediately. > > CAUTION: This email originated from outside of the organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe. This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org For additional commands, e-mail: users-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
