Hi can you please remove me from the mailing list Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: Justin Bertram <jbert...@apache.org> Sent: Friday, December 22, 2023 12:38:07 AM To: users@activemq.apache.org <users@activemq.apache.org> Subject: Re: Looking for HA/replication boilerplate broker.xml and advice
The first thing to note is that you're reading quite old documentation. Notice that the URL references "1.0." I assume you're not actually using ActiveMQ Artemis 1.0, but if so you should upgrade. I recommend you read the latest documentation found here [1]. The second thing, and more to your point, is that the broker ships with a number of examples that demonstrate HA in various configurations for a handful of different use-cases. You can find these in the examples/features/ha directory in the broker distribution (although in the future these will be available separately [2]). I recommend you check out the "replicated-transaction-failover" example. After you run it you'll have 2 fully functional brokers configured for replication in the target/server0 and target/server1 directories. Another option would be to use the --replicated switch when creating the broker instances. You can combine this with --slave for configuring the backup. Justin [1] https://activemq.apache.org/components/artemis/documentation/latest [2] https://github.com/apache/activemq-artemis-examples On Thu, Dec 21, 2023 at 4:27 PM John Lilley <john.lil...@redpointglobal.com.invalid> wrote: Greetings, We want to configure Artemis for HA using “replication” strategy. I’ve been reading https://activemq.apache.org/components/artemis/documentation/1.0.0/ha.html https://activemq.apache.org/components/artemis/documentation/1.1.0/clusters.html https://activemq.apache.org/components/artemis/documentation/1.0.0/client-reconnection.html and well, there’s just a lot to understand and configure. Is there a simple boilerplate broker.xml available for a master and slave which basically works? And by “works” I mean, I can kill the master in a running system, watch the slave take over, and all of this is done w/o losing any messages? This will ultimately be deployed in Kubernetes, I believe using anti-affinity to ensure that master and slave are on different nodes. Any advice for K8S would also be much appreciated. Thanks john [rg] <https://www.redpointglobal.com/> John Lilley Data Management Chief Architect, Redpoint Global Inc. 34 Washington Street, Suite 205 Wellesley Hills, MA 02481 M: +1 7209385761<tel:+1%207209385761> | john.lil...@redpointglobal.com<mailto:john.lil...@redpointglobal.com> PLEASE NOTE: This e-mail from Redpoint Global Inc. (“Redpoint”) is confidential and is intended solely for the use of the individual(s) to whom it is addressed. If you believe you received this e-mail in error, please notify the sender immediately, delete the e-mail from your computer and do not copy, print or disclose it to anyone else. If you properly received this e-mail as a customer, partner or vendor of Redpoint, you should maintain its contents in confidence subject to the terms and conditions of your agreement(s) with Redpoint.
