Hello, I have some issues with scaledown of colocated servers. I have a symmetric statically defined cluster of two colocated nodes configured with scale down. The situation occurs thus:
1. Start both brokers. They form a connection and replicate. 2. Close server1 -> Server shuts down, server0 detects the shutdown and scales down from replicated backup. 3. Start server1 --> Server0 logs: 2018-03-09 10:57:57,434 WARN [org.apache.activemq.artemis.core.server] AMQ222138: Local Member is not set at on ClusterConnection ClusterConnectionImpl@914942811[nodeUUID=1ed6bd4b-2377-11e8-a9e2-0a0027000011, connector=TransportConfiguration(name=netty-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=localhost&activemq-passwordcodec=****, address=, server=ActiveMQServerImpl::serverUUID=1ed6bd4b-2377-11e8-a9e2-0a0027000011] Server1 logs in an infinite loop: 2018-03-09 11:00:57,162 INFO [org.apache.activemq.artemis.core.server] AMQ221066: Initiating quorum vote: RequestBackupQuorumVote 2018-03-09 11:01:02,156 INFO [org.apache.activemq.artemis.core.server] AMQ221066: Initiating quorum vote: RequestBackupQuorumVote 2018-03-09 11:01:07,154 INFO [org.apache.activemq.artemis.core.server] AMQ221066: Initiating quorum vote: RequestBackupQuorumVote 2018-03-09 11:01:12,153 INFO [org.apache.activemq.artemis.core.server] AMQ221066: Initiating quorum vote: RequestBackupQuorumVote 2018-03-09 11:01:17,152 INFO [org.apache.activemq.artemis.core.server] AMQ221066: Initiating quorum vote: RequestBackupQuorumVote 2018-03-09 11:01:22,153 INFO [org.apache.activemq.artemis.core.server] AMQ221066: Initiating quorum vote: RequestBackupQuorumVote 2018-03-09 11:01:27,152 INFO [org.apache.activemq.artemis.core.server] AMQ221066: Initiating quorum vote: RequestBackupQuorumVote 2018-03-09 11:01:32,149 INFO [org.apache.activemq.artemis.core.server] AMQ221066: Initiating quorum vote: RequestBackupQuorumVote ... The situation only normalizes when server1 is shut down and restarted. Broker configurations for replicating: https://github.com/ilkkavi/activemq-artemis/tree/scaledown-issue/issues/IssueExample/src/main/resources/activemq I also have a separate issue that I've so far been unable to replicate locally. When the brokers deployed on two different physical servers, after one node shuts down, the other stops accepting connections. Clients attempting connections log : org.apache.activemq.artemis.api.core.ActiveMQConnectionTimedOutException: AMQ119013: Timed out waiting to receive cluster topology. Group:null I don't really understand why this is happening or why it doesn't happen locally. The cluster topology should be known already for everyone involved. I understand that it's difficult to comment on this as there's no means of replicating this but maybe it's a situation someone has come across before? Best regards, - Ilkka