I've used a PET project I created just to generate a commit report for
Artemis, and compiled it between 2.4.0 and 2.6.1, to give you an idea
of what we did between 2.4.0 and 2.6.1:
https://clebertsuconic.github.io/report-2.4.0-til-2.6.1.html
I had gone through that list before and I didn't see
When we started, we started with 2.4.0, and are so far trying to understand how
we can use it effectively for our purpose. That said, the later versions of
Artemis are definitely in our radar.
Thanks,
Anindya Haldar
Oracle Marketing Cloud
> On Jun 14, 2018, at 4:48 PM, Clebert Suconic
>
I think you should use 2.6.1. There is nothing that it is not equivalent.
And where we are actively fixing issues now.
On Thu, Jun 14, 2018 at 6:40 PM Anindya Haldar
wrote:
> Thanks, again, for your quick response.
>
> Anindya Haldar
> Oracle Marketing Cloud
>
>
> > On Jun 14, 2018, at 3:34
Thanks, again, for your quick response.
Anindya Haldar
Oracle Marketing Cloud
> On Jun 14, 2018, at 3:34 PM, Justin Bertram wrote:
>
>> 1) It is possible to define multiple groups within a cluster, and a
> subset of the brokers in the cluster can be members of a specific group. Is
> that
> 1) It is possible to define multiple groups within a cluster, and a
subset of the brokers in the cluster can be members of a specific group. Is
that correct?
Yes.
> 2) The live-backup relationship is guided by group membership, when there
is explicit group membership defined. Is that correct?
I have a few quick follow up questions. From the discussion here, and from what
I understand reading the Artemis manual, here is my understanding about the
idea of a cluster vs. the idea of a group within a cluster:
1) It is possible to define multiple groups within a cluster, and a subset of
Many thanks, Justin. This makes things much clearer for us when it comes to
designing the HA cluster.
As for the Artemis evaluation scope, we want to use it as one of the supported
messaging backbones in our application suite. The application suite requires
strong transactional guarantees,
> Q1: At this point, will the transaction logs replicate from A to C?
No. A will be replicating to B since B is the designated backup. Also, by
"transaction logs" I assume you mean what the Artemis documentation refers
to as the journal (i.e. all persistent message data).
> Q2: At this point
BTW, these are questions related to Artemis 2.4.0, which is what we are
evaluating right now for our solution.
> On Jun 13, 2018, at 5:52 PM, Anindya Haldar wrote:
>
> I have some questions related to the HA cluster, failover and split-brain
> cases.
>
> Suppose I have set up a 3 node
I have some questions related to the HA cluster, failover and split-brain cases.
Suppose I have set up a 3 node cluster with:
A = master
B = slave 1
C = slave 2
Also suppose they are all part of same group, and are set up to offer
replication based HA.
Scenario 1
Say,
B starts up
10 matches
Mail list logo
