Ok, that makes sense. I'll play around with things some more and see what I
come up with. Thanks for the help!
On Wed, Jan 11, 2017 at 7:43 PM, Clebert Suconic
wrote:
> You are still bound to connect retries and TTLs. So I would say that a good
> reaction time would be 30s. You can decrease tha
You are still bound to connect retries and TTLs. So I would say that a good
reaction time would be 30s. You can decrease that but I am not sure I
recommend it.
It's up to you thought. If I was implementing my own system I would prefer
the cloud infra since you are AWS. I believe that's what m
Thanks for the response. The paired LiveA/BackupB + LiveB/BackupA is what I
was wondering out with the JMS clustered topic. I'd like to not rely on
infrastructure to restart because of the latency that involves - I'd like
to keep any hiccups to < 1 sec if possible.
On Wed, Jan 11, 2017 at 1:46 PM,
You are using AWS. Do you have the storage disk? or is it transient?
What I have been suggesting to cloud user is to just monitor their
system, and have the system restarting itself in case of a failure.
That is the best scenario you can get since the infra-structure would
give you the needed HA.
Your reply is much appreciated. So crossing master/slave is only possible
in a colocated environment? If so I think that's doable in my situation.
"what you are looking is having a copy of the topic subscription on every
node, making it a single cluster among different nodes,"
Is there an example
when you have a topic subscription in cluster.. the message will be
copied to every subscription on the cluster connection (or network of
brokers)...
When you have the same subscription among different nodes.. (that
is... the same core-queue name on more than one node), then
load-balancing will h
Bump. Any help appreciated :)
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-question-on-JMS-clustered-topic-and-high-availability-tp4720803p4720983.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I've been investigating switching from a single activemq server to a
cluster of artemis servers on aws and I have a question on clustered jms
topics and high availability.
Firstly, I like the idea that the producers/consumers can connect to any
node in the cluster and fail over (client side) to a
