I’m not sure what’s the issue to be honest.
You should try the latest version of Artemis and you still hit an issue you
would have to communicate us a way to reproduce the issue.
On Mon, Feb 11, 2019 at 3:32 PM jraju wrote:
> Hi,
>
> Any update to this issue please?
>
> I am also trying a Symm
Hi,
Any update to this issue please?
I am also trying a Symmetric cluster with Multi server environment where
JGroups is used for discovery. The JGroup ping file is pointed to shared
file location.
Thanks.
Raju J
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Any follow-up on that because I'm also struggling with version 2.5.0?
Marcin
-Original Message-
From: Archibald [mailto:arch...@gmx.net]
Sent: 26 April 2018 20:37
To: users@activemq.apache.org
Subject: Re: [ARTEMIS] Clustered broker with multiple live servers and shared
JDBC-
@jbertram: 2.5.0
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
What version of Artemis are you using?
Justin
On Thu, Apr 26, 2018 at 5:00 AM, Archibald wrote:
> The more I search for answers by reading other threads the more I get the
> impression, that the whole replication strategy only works on your test
> cases (or single host) but not in a real clust
The more I search for answers by reading other threads the more I get the
impression, that the whole replication strategy only works on your test
cases (or single host) but not in a real clustered (multi host)
environment...
See
http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-envi
Hi Justin,
After spending hours of reading through documentation and examples I finally
decided to
continue with the replication/colocate approach.
So I've started two brokers which should pair with each other using static
connectors.
true
1
-1
> what I understood from the documentation is that with the scale-down
option it should very well be possible to offload the current work to
another live server (in case of normal shutdown, of course). Or am I wrong?
Your understanding is correct. However, scale-down and HA are not the same
thing
Hi Justin,
what I understood from the documentation is that with the scale-down option
it should very well be possible to offload the current work to another live
server (in case of normal shutdown, of course). Or am I wrong?
And how's scaled down interally handled? A client currently connected t
You've stolen the words from my mouth Justin :)
@archibald Can just say: as he has said :)
Il giorno mar 24 apr 2018 alle ore 15:04 Justin Bertram
ha scritto:
> > If have 3 live servers running in one cluster which do load balancing,
> HA, etc. Do I really need backup servers? If one is down, I
Good old politics , fair enough.
Re docker I think there is such a thing now as statefulservice think it was
called petservice for a while before. But essentially gives you stateful disk.
But totally get your reasons, half our decisions in life is due to internal
politics :)
Sent from my i
@MichelAndrePearce
That's a valid question. And the answer is more or less politically driven.
If you break down a monolith application which does everything in one
transaction people are getting nervious about their data. Keeping messages
within a database (which itself is also clustered and ther
> If have 3 live servers running in one cluster which do load balancing,
HA, etc. Do I really need backup servers? If one is down, I suspect the two
others to take over message processing...
The issue here is that HA isn't provided between live servers. HA only
works between live and backup server
Hi Franz,
I just checked the artemis-configuration.xsd and you're right! There's a
node-manager-store-table-name specified. I was missing that in the latest
documentation about the jdbc-store. So I can have multiple tables for each
broker and a shared set of tables for bindings and messages?
If
Is there a reason you don’t look at replicates journal setup?
Journal is the primary and most performant way to run, especially in a scalable
way which is what multi master is about.
JDBC really is just for retro users, you won’t get benefit from multi master as
you will have the shared single
Hi Archibald!
If you want to have 3 servers running over the same shared store I think
you have to choose 1 to be the live and the remaining 2 to be backups.
If you want to have 3 live servers, each one with shared store HA you need
to specify for each [live, backups] group a different node manag
16 matches
Mail list logo
