I'm still playing with different topologies of ActiveMQ Artemis in
Kubernetes. An almost satisfactory one (also playing with colocated but
anti-affinity is difficult there) is to have master and slaves paired in
two stateful sets:
+---+
|
The setup:
- We are setting up a cluster of 6 brokers using Artemis 2.4.0.
- The cluster has 3 groups.
- Each group has one master, and one slave broker pair.
- The HA uses replication.
- Each master broker configuration has the flag ‘check-for-live-server’ set to
true.
- Each slave broker
> Do you have any alternatives/proposal to retrieve this information?
I believe I provided possible alternatives in my previous email on your
other thread. I recommend you follow-up there if you have additional
questions.
If there are additional metrics which aren't currently provided please
Thanks for the response Justin.
> How can we run or test out the example against our broker set up to
> see
the result of Queue Message counter related APIs as we need these for our
development work further.
I'm not exactly sure what you're asking here. If you want to run the example
against
> The response just indicates the counters as -1, -1, -1,
...and it is very hard to interpret this output, given that it
does not reflect what each counter signifies. Can someone point towards the
description or syntax of this output JSON?
You'll notice that there are 24 entries in
> Trying to understand the resetMessageCounter() API. Does this reset all
the queue counters to 0? Also, does it set a reset time, which we can
leverage further? If yes, which field would signify that?
Calling resetMessageCounter() will reset count, countDelta,
messageCountDelta,
