I lost the plot somewhere along the way I think. What specifically is your use-case? Why are you wanting multiple clusters?
Justin On Wed, Mar 19, 2025 at 8:29 AM William Crowell <wcrow...@perforce.com.invalid> wrote: > Justin, > > So, you would definitely need one cluster with 2 brokers and another > cluster with at least one preferably two brokers as well? > > Regards, > > William Crowell > > From: Justin Bertram <jbert...@apache.org> > Date: Wednesday, March 19, 2025 at 9:25 AM > To: users@activemq.apache.org <users@activemq.apache.org> > Subject: Re: What HA Replication Policy Is For Active-Active Topology > > The HA piece only cares whether a cluster is defined and not necessarily > if it is a health cluster. > > To be clear, HA pairs use clustering mainly for discovery. In the case of > shared storage this discovery allows the primary broker to inform Core > clients (including Core JMS clients) about the cluster topology so they > know where to connect in the case of a failure. > > > Justin > > On Wed, Mar 19, 2025 at 8:03 AM William Crowell > <wcrow...@perforce.com.invalid> wrote: > > > Vilius, > > > > Thank you for your reply. Can we do 2 broker clusters of 1 node each > with > > HA on top? The HA piece only cares whether a cluster is defined and not > > necessarily if it is a health cluster. > > > > Regards, > > > > William Crowell > > > > From: Vilius Šumskas <vilius.sums...@rivile.lt.INVALID> > > Date: Tuesday, March 18, 2025 at 8:23 AM > > To: users@activemq.apache.org <users@activemq.apache.org> > > Subject: RE: What HA Replication Policy Is For Active-Active Topology > > [You don't often get email from vilius.sums...@rivile.lt.invalid. Learn > > why this is important at https://aka.ms/LearnAboutSenderIdentification ] > > > > 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Factivemq.apache.org%2Fcomponents%2Fartemis%2Fdocumentation%2Flatest%2Fclusters.html%23performance-considerations&data=05%7C02%7CWCrowell%40perforce.com%7C16cc14e4c5b14f5a948d08dd66e989b8%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638779875436778391%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=N%2F4t2VbUzfFRF%2F7ka0gz8kAOzwDze4nKR9EGMtXn6kk%3D&reserved=0 > < > https://activemq.apache.org/components/artemis/documentation/latest/clusters.html#performance-considerations > > > > < > > > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Factivemq.apache.org%2Fcomponents%2Fartemis%2Fdocumentation%2Flatest%2Fclusters.html%23performance-considerations&data=05%7C02%7CWCrowell%40perforce.com%7C16cc14e4c5b14f5a948d08dd66e989b8%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638779875436808353%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=0bPs1K1BLwLCpF6Simhm3Ol9qEVVPXs0BXhtoPcN5eY%3D&reserved=0 > < > 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Factivemq.apache.org%2Fcomponents%2Fartemis%2Fdocumentation%2Flatest%2Fha&data=05%7C02%7CWCrowell%40perforce.com%7C16cc14e4c5b14f5a948d08dd66e989b8%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638779875436824312%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=H7NJm%2BxlyLrDW3u9OCnPowWfK5r5fvUNl8u5SgvwDmU%3D&reserved=0 > <https://activemq.apache.org/components/artemis/documentation/latest/ha> > > < > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Factivemq.apache.org%2Fcomponents%2Fartemis%2Fdocumentation%2Flatest%2Fha&data=05%7C02%7CWCrowell%40perforce.com%7C16cc14e4c5b14f5a948d08dd66e989b8%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638779875436837713%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=4ZKWpmbaqwGNE3GQhL1FHDLZSWUhlDmiBe23m%2BHixk0%3D&reserved=0 > <https://activemq.apache.org/components/artemis/documentation/latest/ha>> > > > .html#replication< > > > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Factivemq.apache.org%2Fcomponents%2Fartemis%2Fdocum&data=05%7C02%7CWCrowell%40perforce.com%7C16cc14e4c5b14f5a948d08dd66e989b8%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638779875436851310%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=s4B405nb9QN9IAragT%2BRjakicTUmi4UtkArKNv96KgQ%3D&reserved=0 > <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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Factivemq.apache.org%2Fcontact&data=05%7C02%7CWCrowell%40perforce.com%7C16cc14e4c5b14f5a948d08dd66e989b8%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638779875436866850%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=px9kD5I2AWdBh0L5SGUbJ1YMK27%2BPyYSfqto1CUrkVk%3D&reserved=0 > <https://activemq.apache.org/contact> > > < > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Factivemq.apache.org%2Fcontact&data=05%7C02%7CWCrowell%40perforce.com%7C16cc14e4c5b14f5a948d08dd66e989b8%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638779875436882229%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=kG%2BGXqDIxfXKi49J7TenqTa0lGLRrEMZMqJERkenEGg%3D&reserved=0 > <https://activemq.apache.org/contact>> > > > > > > > > > > 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. > > > > > > > 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. > >
