You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Ian Cox (Jira)" <ji...@apache.org> on 2023/02/10 15:30:00 UTC
[jira] [Updated] (ARTEMIS-4166) 3x2 live backup pairs, stop and start a live node taking traffic does not restore
[ https://issues.apache.org/jira/browse/ARTEMIS-4166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Cox updated ARTEMIS-4166:
-----------------------------
Description:
Have a 6 node cluster running on a 4 node docker swarm (compose file attached). When running a test app that publishes to 1 queue which is replicated to 3 other queues which are consumed, stopping any live node taking traffic will trigger the bakup for that node starting and taking traffic. Restarting the node terminates the connections to the backup node but the live node is never fully activated and cannot be accessed via app or console.
Restarting the application and the stack allows the 'trapped' items to appear on queues and they get consumed. Presumably because they are stored on the NFS volume associated with the broker.
Link to initial discussions
[spring boot - ActiveMQ Artemis - Queue published to but not consumed - Stack Overflow|https://stackoverflow.com/questions/75337989/activemq-artemis-queue-published-to-but-not-consumed]
was:
Have a 6 node cluster running on a 4 node docker swarm (compose file attached). When running a test app that publishes to 1 queue which is replicated to 3 other queues which are consumed, stopping any live node taking traffic will trigger the bakup for that node starting and taking traffic. Restarting the node terminates the connections to the backup node but the live node is never fully activated and cannot be accessed via app or console.
Link to initial discussions
[spring boot - ActiveMQ Artemis - Queue published to but not consumed - Stack Overflow|https://stackoverflow.com/questions/75337989/activemq-artemis-queue-published-to-but-not-consumed]
> 3x2 live backup pairs, stop and start a live node taking traffic does not restore
> ---------------------------------------------------------------------------------
>
> Key: ARTEMIS-4166
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4166
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.27.1
> Environment: 4 node RPI 4 docker with NFS V4 volumes
> 6 node 2.27.1 artemis allocated across the 4 nodes
> Attached log from stopped live node, compose file and broker.xml from each node.
> Reporter: Ian Cox
> Priority: Minor
> Attachments: artemis.zip
>
>
> Have a 6 node cluster running on a 4 node docker swarm (compose file attached). When running a test app that publishes to 1 queue which is replicated to 3 other queues which are consumed, stopping any live node taking traffic will trigger the bakup for that node starting and taking traffic. Restarting the node terminates the connections to the backup node but the live node is never fully activated and cannot be accessed via app or console.
> Restarting the application and the stack allows the 'trapped' items to appear on queues and they get consumed. Presumably because they are stored on the NFS volume associated with the broker.
> Link to initial discussions
> [spring boot - ActiveMQ Artemis - Queue published to but not consumed - Stack Overflow|https://stackoverflow.com/questions/75337989/activemq-artemis-queue-published-to-but-not-consumed]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)