> Also, doing message replication is often times an anti-pattern in
messaging because it creates split brain scenarios during many unplanned
outages that require taking the entire cluster down to resend.
Split brain is certainly a potential risk that needs to be mitigated (as
outlined in the docum
Hi Marc-
Yep, that approach sounds on target. The async-replication is a successful
approach to avoid the side-effects with sync-based replication in messaging
systems.
-Matt
> On May 22, 2024, at 5:43 PM, Marc Boorshtein wrote:
>
> Thanks Matt for the explanation. We have two scenarios we
Thanks Matt for the explanation. We have two scenarios we want to be able
to do:
1. In cluster HA - Right now we have one Deployment with a PVC. If the AMQ
dies the client app stops working until the AMQ deployment is back up.
It's not high volume at all. If I hear what you're saying, and have
Hi Marc-
Scenarios when the queue shows up on a broker:
1. A message is delivered
2. A producer, browser or consumer is connected
3. A Virtual Destination subscriber queue is added on one broker and the remote
brokers automatically add them when the proper configuration flags are enabled.
The m
I'm not sure about the exact behavior of ActiveMQ Classic here, but I do
know what ActiveMQ Artemis does, and it doesn't behave according to your
expectations.
I would be a bit surprised if ActiveMQ Classic behaved as you expect
because it wouldn't scale very well. Moving messages around the netwo
>
>
>
>
> When you say "queue" do you mean a JMS queue?
Yes. (right now just from the admin interface).
> Why would you necessarily
> expect a queue created on one node to be created on a different node in the
> network?
This is the mental block i'm having. What my thought is that if a que
> But when I create a queue in amq0, it doesn't appear in amq1.
When you say "queue" do you mean a JMS queue? Why would you necessarily
expect a queue created on one node to be created on a different node in the
network? Also, what exactly are you doing to create the queue on amq0?
> ...when I cr
I've setup 3 brokers in Kubernetes as StatefulSets. Each one has its own
unique broker name. In each broker config I setup a
block similar to:
Each broker connects to the other 2. Once all three are running i can see
in the logs that they're connecting:
amq-orchestra
INFO |
