Justin, Thanks that helps! From a high level does that look like I have configured a shared store correctly? Anything I left out?
Regards, William Crowell From: Justin Bertram <jbert...@apache.org> Date: Monday, April 28, 2025 at 11:30 PM To: users@activemq.apache.org <users@activemq.apache.org> Subject: Re: Apache Artemis: Is a cluster with 2 brokers that have a shared store considered a symmetric cluster? I think this bit from the example's documentation is relevant: With a symmetric cluster, the cluster is homogeneous, i.e. each node is configured the same as every other node, and every node is connected to every other node in the cluster. Given that an HA pair of brokers are explicitly not configured the same way (i.e. one is a primary and the other is a backup) I would say the cluster they form is not symmetric. In any case, "symmetric" is just a description of the configuration. It's not an especially important term as it's not used directly in any configuration files. Hope that helps! Justin On Mon, Apr 28, 2025 at 8:29 PM William Crowell <wcrow...@perforce.com.invalid> wrote: > Good evening, > > Stupid question for you and need some clarification. > > In Apache Artemis, is a cluster with 2 brokers that have a shared store > setup in a primary/backup configuration considered a symmetrical cluster? > The documentation is a little vague: > > > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Factivemq.apache.org%2Fcomponents%2Fartemis%2Fdocumentation%2Flatest%2Fclusters.html%23symmetric-cluster&data=05%7C02%7CWCrowell%40perforce.com%7C8337f77e742f428d01b508dd86ce230d%7C95b666d19a7549ab95a38969fbcdc08c%7C0%7C0%7C638814942088388103%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=3TDsqPfl%2BTcLLa4K%2FNaMEQlIo%2FuE02dMEXNsA7HtmTo%3D&reserved=0<https://activemq.apache.org/components/artemis/documentation/latest/clusters.html#symmetric-cluster> > > “With a symmetric cluster every node in the cluster is connected to every > other node in the cluster. In other words every node in the cluster is no > more than one hop away from every other node.” > > Then this example: > https://github.com/apache/activemq-artemis-examples/tree/main/examples/features/clustered/symmetric-cluster > > says this: “To set up ActiveMQ Artemis to form a symmetric cluster we > simply need to mark each broker as clustered and we need to define a > cluster-connection in broker.xml”. > > For example, on my first broker the only changes I made to broker.xml just > below <core> and <persistence-enabled> was: > > … > <core…> > <name>node-0</name> > > <connectors> > <connector name="node-0">tcp://artemis-broker-1:61616</connector> > <connector name="node-1">tcp://artemis-broker-2:61616</connector> > </connectors> > > <cluster-connections> > <cluster-connection name="my-cluster"> > <connector-ref>node-0</connector-ref> > <static-connectors> > <connector-ref>node-1</connector-ref> > </static-connectors> > </cluster-connection> > </cluster-connections> > > <ha-policy> > <shared-store> > <primary> > <failover-on-shutdown>true</failover-on-shutdown> > </primary> > </shared-store> > </ha-policy> > > <persistence-enabled>true</persistence-enabled> > … > > On my second broker I had: > > … > <core …> > > <name>node-1</name> > > <connectors> > <connector name="node-0">tcp://artemis-broker-1:61616</connector> > <connector name="node-1">tcp://artemis-broker-2:61616</connector> > </connectors> > > <cluster-connections> > <cluster-connection name="my-cluster"> > <connector-ref>node-1</connector-ref> > <static-connectors> > <connector-ref>node-0</connector-ref> > </static-connectors> > </cluster-connection> > </cluster-connections> > > <ha-policy> > <shared-store> > <backup> > <failover-on-shutdown>true</failover-on-shutdown> > <allow-failback>true</allow-failback> > </backup> > </shared-store> > </ha-policy> > > <persistence-enabled>true</persistence-enabled> > … > > Would this be considered a symmetrical cluster? > > 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.
