So does that mean that -- after shutting down master and then slave -- it's
not enough to start the slave again and that the master server must be then
started as well? Because, obviously, starting the master first isn't an
option as it might have older data than its slave, right?
--
Sent from:
I already committed a fix [1]. :)
Justin
[1]
https://github.com/apache/activemq-artemis/commit/c8a6d0da95c21acb9c395ec7e98c9206bf47dc9a
On Mon, Jun 24, 2019 at 8:34 PM wildpeanut wrote:
> Thanks a lot, I should post a typo issue or try to fix it. Could you tell
> me
> where to start?
>
>
>
>
Thanks a lot, I should post a typo issue or try to fix it. Could you tell me
where to start?
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Ohhh.. you're talking about rsync... perhaps if we disabled reclaim..
it would always be a new file... as right now we reuse a file
if we disabled reclaim for your case.. it wouldn't need to reuse
files... and it wouldn't have a case of corruption.
On Mon, Jun 24, 2019 at 2:40 PM Clebert Suconic
I don't understand what you're talking about with small corruptions of
the journal?
We write on the backup.. and wait for confirmation.. so clients are
blocked until the backup has a copy of the data.
On Sun, Jun 23, 2019 at 8:24 PM warm-sun wrote:
>
> >>> Technically speaking, replication is as
> So when the network is down between master and slave (eg slaves network
card fails)... the master will keep ACK-ing messages it receieves in this
case?
In general, yes. Like I said before, the master can be configured to
initiate a quorum vote and will shut itself down if it's isolated.
> If so
If you're really hitting a dead-lock then that's worth a JIRA [1].
It's worth noting that there are legitimate exceptions which can be thrown
by the client during failover. See the "Handling Blocking Calls During
Failover" [2] section of the "High Availability and Failover" chapter in
the document
Ah, my bad then. I’m sorry, I must have been out of my mind when writing the
post.
The reason why I still have to deal with this is that I’ve experienced
deadlocks when committing during failover. Nothing but rebooting the client
helped. I might open a different topic in case it happens again.
Ja
Hi again:
I checked further stuffs on this issue, and I think I am not able to fetch
JMS Messages > 400, because of optimizedDispatch="true" in the policyEntry
configuration of the broker. I had it as below:
``
This was a recommended setting for scaling broker service.
Could it be because of th
I think there's a handful of different ways to address this...
In general, it seems like your consumption isn't keeping up with your
production otherwise you wouldn't have such a large build-up of messages on
one of the brokers. It's a good idea to balance message production with
adequate consump
>From what I can tell everything is working as designed. As the
documentation [1] states:
In the replication case, the backup just keeps waiting for a live
server to pair with. Note that in replication the backup server does not
know whether any data it might have is up to date, so it really c
[@@ THALES ALENIA SPACE INTERNAL @@]
-Message d'origine-
De : Justin Bertram [mailto:jbert...@apache.org]
Envoyé : lundi 24 juin 2019 15:52
À : users@activemq.apache.org
Objet : Re: how does HA config(backup-port-offset) work?
> Why backup server need to do offset?
The offset is neces
> Why backup server need to do offset?
The offset is necessary to avoid port conflicts when starting the colocated
backup. If both brokers try to use the same ports then one of the brokers
won't work.
> Does that mean backup server 1 will create new listen port 5545 to live
server, and backup ser
Hi, below my test:
1) start master and slave;
2) send two messages, stored on master;
3) stop master;
4) slave is live and it has 2 messages;
5) stop slave;
6) restart slave but i haven't previous messages;
Thanks in advance for the help!
Kind regards,
Gianfranco Aloi
--
Sent from: http://act
I read HA-related document and still can't figure out the config element
'backup-port-offset' meaning.
>From the sentence in document, if the HA policy is colocated then connectors
and acceptors will be inherited from the live server creating it and offset
depending on the setting of backup-port-o
I don't really understand what you mean by, "If the only node to start is
the slave, i lose all information in the queue." Can you elaborate on this?
How are you losing information?
Justin
On Mon, Jun 24, 2019 at 8:37 AM galoi wrote:
> I'm using artemis ActiveMQ Artemis 2.9.0, and i configured
I'm using artemis ActiveMQ Artemis 2.9.0, and i configured two nodes master
and slave in replication HA. View Below:
true
true
As I know, Artemis use Netty mqtt connector, which means Netty should support
mqtt 5 first.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
I can't speak for anybody else, but I don't have any plans right now to
implement MQTT 5. I skimmed over the MQTT 5 specification awhile back, but
haven't had time to invest in an implementation.
Have you given any thought to contributing an implementation? Artemis uses
the MQTT codec support in N
I'm not quite sure I understand your question. The test doesn't call
commit() because it calls rollback() instead. The point of the test is to
make the broker send the message to the dead-letter address and it can't do
that unless the delivery fails. The failed delivery is triggered by
invoking rol
Isn't the test missing the "consumer.commit(...)" part? If not, why?
It seems that without it the committing does not happen. One would say that
it's obvious, right? :-) Yet the test works without it. Is it because the
consumer is closed right after consuming the message?
--
Sent from: http://
Hi! DId you have checked against the latest version of Artemis on master?
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
I too have experienced this issue with a large amount of "large messages".
I'm talking several GiBs of data. Suddenly, the amount of opened FDs went so
high the broker stopped working.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi:
I am using ActiveMQ 5.15.4 on Windows.
I am trying to optimize my broker for scaling issues. I read the book
"ActiveMQ in action" and also went through this article
(https://javabeat.net/deploying-activemq-for-large-numbers-of-concurrent-applications/).
Currently, I am trying to use the same
Are there any plans to support MQTT 5 in ActiveMQ Artemis in the near future?
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
25 matches
Mail list logo
