activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Catalin Alexandru Zamfir (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (ARTEMIS-1285) Standby slave would not announce replication to master when the slave is down
Date Tue, 17 Apr 2018 19:01:00 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16441335#comment-16441335
] 

Catalin Alexandru Zamfir edited comment on ARTEMIS-1285 at 4/17/18 7:00 PM:
----------------------------------------------------------------------------

Hello,

Seems to affect 2.5.0 also. We're using the vanilla 2.5.0 distribution of Artemis. Seems to
affecting other spin-offs:
 - [https://issues.jboss.org/browse/ENTMQBR-1021]

 - [https://issues.jboss.org/browse/ENTMQBR-882]

We're on the same Jgroups + TCPPING configuration as ENTMQBR-882. The inital_hosts is set
to the live servers with send_cache_on_join and return_entire_cache set to true.

I've managed to have live + backup (let's call it r1 for live and r2 for backup). But when
we added "r3" it seem to stop for a while then it started spamming the logs with 'Server is
stopped'. Hawtio confirmed the server was stopped (same exception when viewing the attributes).
It seems to enter a loop.
{code:java}
2018-04-17 18:36:59.132 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: Apache ActiveMQ Artemis
2.5.0
2018-04-17 18:36:59.133 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:36:51,737
INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis
Server

... standardlogs saying it's starting, the defaults ...

2018-04-17 18:36:59.138 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:36:55,882
INFO [org.apache.activemq.artemis] AMQ241004: Artemis Console available at http://10.117.28.55:8161/console
2018-04-17 18:36:59.138 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:36:55,882
INFO [org.apache.activemq.artemis] AMQ241001: HTTP Server started at http://10.117.28.55:8161
2018-04-17 18:36:59.138 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:36:55,876
INFO [org.eclipse.jetty.server.AbstractConnector] Started ServerConnector@3ad2e17{HTTP/1.1,[http/1.1]}{10.117.28.55:8161}
2018-04-17 18:37:24.140 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:37:18,305
INFO [io.hawt.web.keycloak.KeycloakServlet] Keycloak integration is disabled
2018-04-17 18:37:49.142 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:37:42,544
WARN [org.apache.activemq.artemis.core.server] AMQ222040: Server is stopped
2018-04-17 18:37:49.142 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:37:42,637
WARN [org.apache.activemq.artemis.core.server] AMQ222040: Server is stopped
2018-04-17 18:37:49.142 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:37:42,653
WARN [org.apache.activemq.artemis.core.server] AMQ222040: Server is stopped
2018-04-17 18:37:49.142 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:37:42,727
WARN [org.apache.activemq.artemis.core.server] AMQ222040: Server is stopped
2018-04-17 18:37:49.142 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:37:42,781
WARN [org.apache.activemq.artemis.core.server] AMQ222040: Server is stopped

... and it goes on forever ...{code}
I would set this as "blocker" or "critical". Most deployments will prefer an 3x data replication
(1 live + 2x backup). Any hints on how we can help? What to look at?


was (Author: antauri):
Hello,

Seems to affect 2.5.0 also. We're using the vanilla 2.5.0 distribution of Artemis. Seems to
affecting other spin-offs:

- [https://issues.jboss.org/browse/ENTMQBR-1021]

- [https://issues.jboss.org/browse/ENTMQBR-882]

I've managed to have live + backup (let's call it r1 for live and r2 for backup). But when
we added "r3" it seem to stop for a while then it started spamming the logs with 'Server is
stopped'. Hawtio confirmed the server was stopped (same exception when viewing the attributes).
It seems to enter a loop.
{code:java}
2018-04-17 18:36:59.132 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: Apache ActiveMQ Artemis
2.5.0
2018-04-17 18:36:59.133 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:36:51,737
INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis
Server

... standardlogs saying it's starting, the defaults ...

2018-04-17 18:36:59.138 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:36:55,882
INFO [org.apache.activemq.artemis] AMQ241004: Artemis Console available at http://10.117.28.55:8161/console
2018-04-17 18:36:59.138 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:36:55,882
INFO [org.apache.activemq.artemis] AMQ241001: HTTP Server started at http://10.117.28.55:8161
2018-04-17 18:36:59.138 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:36:55,876
INFO [org.eclipse.jetty.server.AbstractConnector] Started ServerConnector@3ad2e17{HTTP/1.1,[http/1.1]}{10.117.28.55:8161}
2018-04-17 18:37:24.140 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:37:18,305
INFO [io.hawt.web.keycloak.KeycloakServlet] Keycloak integration is disabled
2018-04-17 18:37:49.142 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:37:42,544
WARN [org.apache.activemq.artemis.core.server] AMQ222040: Server is stopped
2018-04-17 18:37:49.142 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:37:42,637
WARN [org.apache.activemq.artemis.core.server] AMQ222040: Server is stopped
2018-04-17 18:37:49.142 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:37:42,653
WARN [org.apache.activemq.artemis.core.server] AMQ222040: Server is stopped
2018-04-17 18:37:49.142 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:37:42,727
WARN [org.apache.activemq.artemis.core.server] AMQ222040: Server is stopped
2018-04-17 18:37:49.142 dlk-p-mqs003 dockerc: i3-shared-artemis-r3-p: 2018-04-17 18:37:42,781
WARN [org.apache.activemq.artemis.core.server] AMQ222040: Server is stopped

... and it goes on forever ...{code}
I would set this as "blocker" or "critical". Most deployments will prefer an 3x data replication
(1 live + 2x backup). Any hints on how we can help? What to look at?

> Standby slave would not announce replication to master when the slave is down
> -----------------------------------------------------------------------------
>
>                 Key: ARTEMIS-1285
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1285
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.1.0
>            Reporter: yangwei
>            Priority: Major
>
> We have a cluster of 3 instances: A is master, B is slave and C is standby slave. When
slave is down, we expect C announces replication to A but A is in standalone mode all the
time. We see C waits at "nodeLocator.locateNode()" through jstack command.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message