[JBoss JIRA] (WFLY-9375) META-INF/services are always accessible from dependencies
by Jan Stourac (JIRA)
[ https://issues.jboss.org/browse/WFLY-9375?page=com.atlassian.jira.plugin.... ]
Jan Stourac updated WFLY-9375:
------------------------------
Affects: Release Notes
> META-INF/services are always accessible from dependencies
> ---------------------------------------------------------
>
> Key: WFLY-9375
> URL: https://issues.jboss.org/browse/WFLY-9375
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.Final, 10.1.0.Final, 11.0.0.CR1
> Reporter: Alexander Kudrevatykh
> Assignee: Stuart Douglas
> Fix For: 12.0.0.Beta1
>
>
> I found regression in Wildfly 10.1 (10.0 and 11 CR1 also affected) - META-INF/services entries are accesible from war dependencies, even if not marked as "import"
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
- 1
- 0
[JBoss JIRA] (WFLY-9880) ServletContainerInitializer@onStartup is not invoked for deployment
by Jan Stourac (JIRA)
[ https://issues.jboss.org/browse/WFLY-9880?page=com.atlassian.jira.plugin.... ]
Jan Stourac commented on WFLY-9880:
-----------------------------------
Thank you, Stuart, you are right. After adding the {{services="import"}} attribute in jboss-deployment-structure.xml as you said, it starts to work.
I was able to find that this change in behaviour is becaus of this fix WFLY-9375. I think we should make some note in release notes about this change as some customers might have similarly broken deployments too. I'll put a comment in that original jira.
> ServletContainerInitializer@onStartup is not invoked for deployment
> -------------------------------------------------------------------
>
> Key: WFLY-9880
> URL: https://issues.jboss.org/browse/WFLY-9880
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 12.0.0.Beta1
> Reporter: Jan Stourac
> Assignee: Stuart Douglas
> Attachments: deployment-with-dep.war, module.xml, servlet-container-init.jar
>
>
> The {{ServletContainerInitializer@onStartup}} is not invoked for deployment. See {{Steps to Reproduce}}.
> Problematic part seems to be on [this line|https://github.com/undertow-io/undertow/blob/1706a5f41adb8f1a719617c...] in Undertow
> {code}
> //then run the SCI's
> ---> for (final ServletContainerInitializerInfo sci : deploymentInfo.getServletContainerInitializers()) {
> final InstanceHandle<? extends ServletContainerInitializer> instance = sci.getInstanceFactory().createInstance();
> try {
> instance.getInstance().onStartup(sci.getHandlesTypes(), servletContext);
> } finally {
> instance.release();
> }
> }
> {code}
> It looks like calling {{deploymentInfo.getServletContainerInitializers()}} does not include our deployment and simply ignores it.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
- 1
- 0
[JBoss JIRA] (WFCORE-3641) Upgrade JBoss MSC to 1.3.1.Final
by Richard Opalka (JIRA)
Richard Opalka created WFCORE-3641:
--------------------------------------
Summary: Upgrade JBoss MSC to 1.3.1.Final
Key: WFCORE-3641
URL: https://issues.jboss.org/browse/WFCORE-3641
Project: WildFly Core
Issue Type: Component Upgrade
Reporter: Richard Opalka
Assignee: Richard Opalka
Fix For: 4.0.0.Beta2
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
- 1
- 0
[JBoss JIRA] (JGRP-2253) FD_SOCK is not working in AWS environment
by Sibin Karnavar (JIRA)
[ https://issues.jboss.org/browse/JGRP-2253?page=com.atlassian.jira.plugin.... ]
Sibin Karnavar edited comment on JGRP-2253 at 2/22/18 12:16 PM:
----------------------------------------------------------------
All timestamps are in UTC
Members in the cluster: ip-10-93-136-91, ip-10-93-133-149 and ip-10-93-135-215
+Node 0: (Master Node / Leader)+
ip-10-93-136-91
This node was the leader node and I have killed it at 2018-02-22 16:19:58.186 UTC time. If you see the FD_SOCK Trace timestamp, its not detecting the TCP socket connection break immediately.
2018-02-22 16:21:19.430 TRACE 23603 --- [jgroups-13,ABC_test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (559 secs old)
)
+_Node 1:_+
ip-10-93-133-149
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|17] (2) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458]
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - I am not the master!
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - ip-10-93-135-215-41546 is the master for service ABC
2018-02-22 16:21:19.408 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|18] (3) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320]
2018-02-22 16:21:19.409 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - I am not the master!
2018-02-22 16:21:19.430 TRACE 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (559 secs old)
)
2018-02-22 16:21:19.434 TRACE 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.434 DEBUG 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: suspecting [ip-10-93-135-215-41546]
2018-02-22 16:21:19.435 DEBUG 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: broadcasting unsuspect(ip-10-93-135-215-41546)
2018-02-22 16:21:19.435 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.436 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:19.437 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.429 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:49.429 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: who-has-sock ip-10-93-133-149-13458
2018-02-22 16:21:49.429 DEBUG 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: suspecting [ip-10-93-135-215-41546]
2018-02-22 16:21:49.430 DEBUG 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: broadcasting unsuspect(ip-10-93-135-215-41546)
2018-02-22 16:21:49.430 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:49.431 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.432 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.437 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-136-91-22320:
mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.527 INFO 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: MergeView::[ip-10-93-135-215-41546|20] (3)
[ip-10-93-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320], 2 subgroups: [ip-10-93-136-91-22320|19] (1) [ip-10-93-136-91-22320], [ip-10-93-135-215-41546|18] (3) [ip-10-93-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-
91-22320]
+Node-2+
ip-10-93-135-215
2018-02-22 16:21:19.403 INFO 19074 --- [jgroups-24,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|18] (3) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320]
2018-02-22 16:21:19.426 TRACE 19074 --- [jgroups-27,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (1599 secs old)
)
2018-02-22 16:21:19.430 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.430 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: suspecting []
2018-02-22 16:21:19.432 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.432 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:19.432 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: suspecting [ip-10-93-133-149-13458]
2018-02-22 16:21:19.433 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: broadcasting unsuspect(ip-10-93-133-149-13458)
2018-02-22 16:21:19.433 TRACE 19074 --- [jgroups-27,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
was (Author: sibin.karnavar):
All timestamps are in UTC
Members in the cluster: ip-10-93-136-91, ip-10-93-133-149 and ip-10-93-135-215
+Node 0: (Master Node / Leader)+
ip-10-93-136-91
This node was the leader node and I have killed it at 2018-02-22 16:19:58.186 UTC time. If you see the FD_SOCK Trace timestamp, its not detecting the TCP socket connection break immediately.
2018-02-22 16:21:19.430 TRACE 23603 --- [jgroups-13,ABC_test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (559 secs old)
)
+_Node 1:_+
ip-10-93-133-149
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|17] (2) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458]
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - I am not the master!
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - ip-10-93-135-215-41546 is the master for service ABC
2018-02-22 16:21:19.408 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|18] (3) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320]
2018-02-22 16:21:19.409 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - I am not the master!
2018-02-22 16:21:19.430 TRACE 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (559 secs old)
)
2018-02-22 16:21:19.434 TRACE 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.434 DEBUG 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: suspecting [ip-10-93-135-215-41546]
2018-02-22 16:21:19.435 DEBUG 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: broadcasting unsuspect(ip-10-93-135-215-41546)
2018-02-22 16:21:19.435 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.436 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:19.437 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.429 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:49.429 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: who-has-sock ip-10-93-133-149-13458
2018-02-22 16:21:49.429 DEBUG 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: suspecting [ip-10-93-135-215-41546]
2018-02-22 16:21:49.430 DEBUG 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: broadcasting unsuspect(ip-10-93-135-215-41546)
2018-02-22 16:21:49.430 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:49.431 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.432 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.437 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-136-91-22320:
mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.527 INFO 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: MergeView::[ip-10-93-135-215-41546|20] (3)
[ip-10-93-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320], 2 subgroups: [ip-10-93-136-91-22320|19] (1) [ip-10-93-136-91-22320], [ip-10-93-135-215-41546|18] (3) [ip-10-93-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-
91-22320]
+
Node-2+
ip-10-93-135-215
2018-02-22 16:21:19.403 INFO 19074 --- [jgroups-24,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|18] (3) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320]
2018-02-22 16:21:19.426 TRACE 19074 --- [jgroups-27,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (1599 secs old)
)
2018-02-22 16:21:19.430 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.430 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: suspecting []
2018-02-22 16:21:19.432 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.432 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:19.432 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: suspecting [ip-10-93-133-149-13458]
2018-02-22 16:21:19.433 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: broadcasting unsuspect(ip-10-93-133-149-13458)
2018-02-22 16:21:19.433 TRACE 19074 --- [jgroups-27,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
> FD_SOCK is not working in AWS environment
> -----------------------------------------
>
> Key: JGRP-2253
> URL: https://issues.jboss.org/browse/JGRP-2253
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.10
> Environment: AWS - EC2
> Reporter: Sibin Karnavar
> Assignee: Bela Ban
>
> We have our failure detection defined like below.
> <FD_SOCK external_port="7804" />
> <FD timeout="3000" max_tries="3" />
> <VERIFY_SUSPECT timeout="3000" />
> Please note that we have used FD instead of FD_ALL in AWS. We will be changing it to FD_ALL later after detailed testing.
> In my local, this is working perfect. As soon as I kill my node, I was able to see that view change was happening immediately with FD_SOCK.
> We were not mentioning the external_port in the FD_SOCK but later I thought it may be an issue with the port and defined it as 7804 and added the same port to the security group that allows to access this port among all the nodes. So no issue with the port.
> Can you please let us know if we need any additional configurations to make FD_SOCK works well in AWS.
> Thanks,
> Sibin
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
- 1
- 0
[JBoss JIRA] (JGRP-2253) FD_SOCK is not working in AWS environment
by Sibin Karnavar (JIRA)
[ https://issues.jboss.org/browse/JGRP-2253?page=com.atlassian.jira.plugin.... ]
Sibin Karnavar edited comment on JGRP-2253 at 2/22/18 12:15 PM:
----------------------------------------------------------------
All timestamps are in UTC
Members in the cluster: ip-10-93-136-91, ip-10-93-133-149 and ip-10-93-135-215
+Node 0: (Master Node / Leader)+
ip-10-93-136-91
This node was the leader node and I have killed it at 2018-02-22 16:19:58.186 UTC time. If you see the FD_SOCK Trace timestamp, its not detecting the TCP socket connection break immediately.
2018-02-22 16:21:19.430 TRACE 23603 --- [jgroups-13,ABC_test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (559 secs old)
)
_Node 1:_
ip-10-93-133-149
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|17] (2) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458]
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - I am not the master!
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - ip-10-93-135-215-41546 is the master for service ABC
2018-02-22 16:21:19.408 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|18] (3) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320]
2018-02-22 16:21:19.409 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - I am not the master!
2018-02-22 16:21:19.430 TRACE 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (559 secs old)
)
2018-02-22 16:21:19.434 TRACE 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.434 DEBUG 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: suspecting [ip-10-93-135-215-41546]
2018-02-22 16:21:19.435 DEBUG 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: broadcasting unsuspect(ip-10-93-135-215-41546)
2018-02-22 16:21:19.435 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.436 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:19.437 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.429 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:49.429 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: who-has-sock ip-10-93-133-149-13458
2018-02-22 16:21:49.429 DEBUG 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: suspecting [ip-10-93-135-215-41546]
2018-02-22 16:21:49.430 DEBUG 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: broadcasting unsuspect(ip-10-93-135-215-41546)
2018-02-22 16:21:49.430 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:49.431 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.432 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.437 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-136-91-22320:
mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.527 INFO 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: MergeView::[ip-10-93-135-215-41546|20] (3)
[ip-10-93-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320], 2 subgroups: [ip-10-93-136-91-22320|19] (1) [ip-10-93-136-91-22320], [ip-10-93-135-215-41546|18] (3) [ip-10-93-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-
91-22320]
+
Node-2+
ip-10-93-135-215
2018-02-22 16:21:19.403 INFO 19074 --- [jgroups-24,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|18] (3) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320]
2018-02-22 16:21:19.426 TRACE 19074 --- [jgroups-27,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (1599 secs old)
)
2018-02-22 16:21:19.430 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.430 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: suspecting []
2018-02-22 16:21:19.432 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.432 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:19.432 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: suspecting [ip-10-93-133-149-13458]
2018-02-22 16:21:19.433 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: broadcasting unsuspect(ip-10-93-133-149-13458)
2018-02-22 16:21:19.433 TRACE 19074 --- [jgroups-27,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
was (Author: sibin.karnavar):
All timestamps are in UTC
Members in the cluster: ip-10-93-136-91, ip-10-93-133-149 and ip-10-93-135-215
Node 0: (Master Node / Leader)
ip-10-93-136-91
This node was the leader node and I have killed it at 2018-02-22 16:19:58.186 UTC time. If you see the FD_SOCK Trace timestamp, its not detecting the TCP socket connection break immediately.
2018-02-22 16:21:19.430 TRACE 23603 --- [jgroups-13,ABC_test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (559 secs old)
)
Node 1:
ip-10-93-133-149
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|17] (2) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458]
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - I am not the master!
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - ip-10-93-135-215-41546 is the master for service ABC
2018-02-22 16:21:19.408 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|18] (3) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320]
2018-02-22 16:21:19.409 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - I am not the master!
2018-02-22 16:21:19.430 TRACE 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (559 secs old)
)
2018-02-22 16:21:19.434 TRACE 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.434 DEBUG 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: suspecting [ip-10-93-135-215-41546]
2018-02-22 16:21:19.435 DEBUG 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: broadcasting unsuspect(ip-10-93-135-215-41546)
2018-02-22 16:21:19.435 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.436 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:19.437 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.429 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:49.429 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: who-has-sock ip-10-93-133-149-13458
2018-02-22 16:21:49.429 DEBUG 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: suspecting [ip-10-93-135-215-41546]
2018-02-22 16:21:49.430 DEBUG 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: broadcasting unsuspect(ip-10-93-135-215-41546)
2018-02-22 16:21:49.430 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:49.431 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.432 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.437 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-136-91-22320:
mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.527 INFO 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: MergeView::[ip-10-93-135-215-41546|20] (3)
[ip-10-93-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320], 2 subgroups: [ip-10-93-136-91-22320|19] (1) [ip-10-93-136-91-22320], [ip-10-93-135-215-41546|18] (3) [ip-10-93-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-
91-22320]
Node-2
ip-10-93-135-215
2018-02-22 16:21:19.403 INFO 19074 --- [jgroups-24,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|18] (3) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320]
2018-02-22 16:21:19.426 TRACE 19074 --- [jgroups-27,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (1599 secs old)
)
2018-02-22 16:21:19.430 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.430 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: suspecting []
2018-02-22 16:21:19.432 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.432 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:19.432 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: suspecting [ip-10-93-133-149-13458]
2018-02-22 16:21:19.433 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: broadcasting unsuspect(ip-10-93-133-149-13458)
2018-02-22 16:21:19.433 TRACE 19074 --- [jgroups-27,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
> FD_SOCK is not working in AWS environment
> -----------------------------------------
>
> Key: JGRP-2253
> URL: https://issues.jboss.org/browse/JGRP-2253
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.10
> Environment: AWS - EC2
> Reporter: Sibin Karnavar
> Assignee: Bela Ban
>
> We have our failure detection defined like below.
> <FD_SOCK external_port="7804" />
> <FD timeout="3000" max_tries="3" />
> <VERIFY_SUSPECT timeout="3000" />
> Please note that we have used FD instead of FD_ALL in AWS. We will be changing it to FD_ALL later after detailed testing.
> In my local, this is working perfect. As soon as I kill my node, I was able to see that view change was happening immediately with FD_SOCK.
> We were not mentioning the external_port in the FD_SOCK but later I thought it may be an issue with the port and defined it as 7804 and added the same port to the security group that allows to access this port among all the nodes. So no issue with the port.
> Can you please let us know if we need any additional configurations to make FD_SOCK works well in AWS.
> Thanks,
> Sibin
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
- 1
- 0
[JBoss JIRA] (JGRP-2253) FD_SOCK is not working in AWS environment
by Sibin Karnavar (JIRA)
[ https://issues.jboss.org/browse/JGRP-2253?page=com.atlassian.jira.plugin.... ]
Sibin Karnavar edited comment on JGRP-2253 at 2/22/18 12:15 PM:
----------------------------------------------------------------
All timestamps are in UTC
Members in the cluster: ip-10-93-136-91, ip-10-93-133-149 and ip-10-93-135-215
+Node 0: (Master Node / Leader)+
ip-10-93-136-91
This node was the leader node and I have killed it at 2018-02-22 16:19:58.186 UTC time. If you see the FD_SOCK Trace timestamp, its not detecting the TCP socket connection break immediately.
2018-02-22 16:21:19.430 TRACE 23603 --- [jgroups-13,ABC_test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (559 secs old)
)
+_Node 1:_+
ip-10-93-133-149
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|17] (2) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458]
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - I am not the master!
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - ip-10-93-135-215-41546 is the master for service ABC
2018-02-22 16:21:19.408 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|18] (3) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320]
2018-02-22 16:21:19.409 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - I am not the master!
2018-02-22 16:21:19.430 TRACE 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (559 secs old)
)
2018-02-22 16:21:19.434 TRACE 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.434 DEBUG 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: suspecting [ip-10-93-135-215-41546]
2018-02-22 16:21:19.435 DEBUG 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: broadcasting unsuspect(ip-10-93-135-215-41546)
2018-02-22 16:21:19.435 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.436 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:19.437 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.429 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:49.429 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: who-has-sock ip-10-93-133-149-13458
2018-02-22 16:21:49.429 DEBUG 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: suspecting [ip-10-93-135-215-41546]
2018-02-22 16:21:49.430 DEBUG 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: broadcasting unsuspect(ip-10-93-135-215-41546)
2018-02-22 16:21:49.430 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:49.431 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.432 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.437 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-136-91-22320:
mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.527 INFO 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: MergeView::[ip-10-93-135-215-41546|20] (3)
[ip-10-93-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320], 2 subgroups: [ip-10-93-136-91-22320|19] (1) [ip-10-93-136-91-22320], [ip-10-93-135-215-41546|18] (3) [ip-10-93-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-
91-22320]
+
Node-2+
ip-10-93-135-215
2018-02-22 16:21:19.403 INFO 19074 --- [jgroups-24,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|18] (3) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320]
2018-02-22 16:21:19.426 TRACE 19074 --- [jgroups-27,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (1599 secs old)
)
2018-02-22 16:21:19.430 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.430 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: suspecting []
2018-02-22 16:21:19.432 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.432 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:19.432 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: suspecting [ip-10-93-133-149-13458]
2018-02-22 16:21:19.433 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: broadcasting unsuspect(ip-10-93-133-149-13458)
2018-02-22 16:21:19.433 TRACE 19074 --- [jgroups-27,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
was (Author: sibin.karnavar):
All timestamps are in UTC
Members in the cluster: ip-10-93-136-91, ip-10-93-133-149 and ip-10-93-135-215
+Node 0: (Master Node / Leader)+
ip-10-93-136-91
This node was the leader node and I have killed it at 2018-02-22 16:19:58.186 UTC time. If you see the FD_SOCK Trace timestamp, its not detecting the TCP socket connection break immediately.
2018-02-22 16:21:19.430 TRACE 23603 --- [jgroups-13,ABC_test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (559 secs old)
)
_Node 1:_
ip-10-93-133-149
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|17] (2) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458]
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - I am not the master!
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - ip-10-93-135-215-41546 is the master for service ABC
2018-02-22 16:21:19.408 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|18] (3) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320]
2018-02-22 16:21:19.409 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - I am not the master!
2018-02-22 16:21:19.430 TRACE 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (559 secs old)
)
2018-02-22 16:21:19.434 TRACE 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.434 DEBUG 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: suspecting [ip-10-93-135-215-41546]
2018-02-22 16:21:19.435 DEBUG 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: broadcasting unsuspect(ip-10-93-135-215-41546)
2018-02-22 16:21:19.435 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.436 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:19.437 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.429 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:49.429 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: who-has-sock ip-10-93-133-149-13458
2018-02-22 16:21:49.429 DEBUG 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: suspecting [ip-10-93-135-215-41546]
2018-02-22 16:21:49.430 DEBUG 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: broadcasting unsuspect(ip-10-93-135-215-41546)
2018-02-22 16:21:49.430 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:49.431 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.432 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.437 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-136-91-22320:
mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.527 INFO 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: MergeView::[ip-10-93-135-215-41546|20] (3)
[ip-10-93-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320], 2 subgroups: [ip-10-93-136-91-22320|19] (1) [ip-10-93-136-91-22320], [ip-10-93-135-215-41546|18] (3) [ip-10-93-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-
91-22320]
+
Node-2+
ip-10-93-135-215
2018-02-22 16:21:19.403 INFO 19074 --- [jgroups-24,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|18] (3) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320]
2018-02-22 16:21:19.426 TRACE 19074 --- [jgroups-27,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (1599 secs old)
)
2018-02-22 16:21:19.430 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.430 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: suspecting []
2018-02-22 16:21:19.432 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.432 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:19.432 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: suspecting [ip-10-93-133-149-13458]
2018-02-22 16:21:19.433 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: broadcasting unsuspect(ip-10-93-133-149-13458)
2018-02-22 16:21:19.433 TRACE 19074 --- [jgroups-27,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
> FD_SOCK is not working in AWS environment
> -----------------------------------------
>
> Key: JGRP-2253
> URL: https://issues.jboss.org/browse/JGRP-2253
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.10
> Environment: AWS - EC2
> Reporter: Sibin Karnavar
> Assignee: Bela Ban
>
> We have our failure detection defined like below.
> <FD_SOCK external_port="7804" />
> <FD timeout="3000" max_tries="3" />
> <VERIFY_SUSPECT timeout="3000" />
> Please note that we have used FD instead of FD_ALL in AWS. We will be changing it to FD_ALL later after detailed testing.
> In my local, this is working perfect. As soon as I kill my node, I was able to see that view change was happening immediately with FD_SOCK.
> We were not mentioning the external_port in the FD_SOCK but later I thought it may be an issue with the port and defined it as 7804 and added the same port to the security group that allows to access this port among all the nodes. So no issue with the port.
> Can you please let us know if we need any additional configurations to make FD_SOCK works well in AWS.
> Thanks,
> Sibin
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
- 1
- 0
[JBoss JIRA] (JGRP-2253) FD_SOCK is not working in AWS environment
by Sibin Karnavar (JIRA)
[ https://issues.jboss.org/browse/JGRP-2253?page=com.atlassian.jira.plugin.... ]
Sibin Karnavar edited comment on JGRP-2253 at 2/22/18 12:14 PM:
----------------------------------------------------------------
All timestamps are in UTC
Members in the cluster: ip-10-93-136-91, ip-10-93-133-149 and ip-10-93-135-215
Node 0: (Master Node / Leader)
ip-10-93-136-91
This node was the leader node and I have killed it at 2018-02-22 16:19:58.186 UTC time. If you see the FD_SOCK Trace timestamp, its not detecting the TCP socket connection break immediately.
2018-02-22 16:21:19.430 TRACE 23603 --- [jgroups-13,ABC_test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (559 secs old)
)
Node 1:
ip-10-93-133-149
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|17] (2) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458]
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - I am not the master!
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - ip-10-93-135-215-41546 is the master for service ABC
2018-02-22 16:21:19.408 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|18] (3) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320]
2018-02-22 16:21:19.409 INFO 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - I am not the master!
2018-02-22 16:21:19.430 TRACE 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (559 secs old)
)
2018-02-22 16:21:19.434 TRACE 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.434 DEBUG 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: suspecting [ip-10-93-135-215-41546]
2018-02-22 16:21:19.435 DEBUG 23603 --- [jgroups-13,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: broadcasting unsuspect(ip-10-93-135-215-41546)
2018-02-22 16:21:19.435 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.436 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:19.437 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.429 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:49.429 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: who-has-sock ip-10-93-133-149-13458
2018-02-22 16:21:49.429 DEBUG 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: suspecting [ip-10-93-135-215-41546]
2018-02-22 16:21:49.430 DEBUG 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: broadcasting unsuspect(ip-10-93-135-215-41546)
2018-02-22 16:21:49.430 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:49.431 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.432 TRACE 23603 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.437 TRACE 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-136-91-22320:
mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.527 INFO 23603 --- [jgroups-16,ABC-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: MergeView::[ip-10-93-135-215-41546|20] (3)
[ip-10-93-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320], 2 subgroups: [ip-10-93-136-91-22320|19] (1) [ip-10-93-136-91-22320], [ip-10-93-135-215-41546|18] (3) [ip-10-93-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-
91-22320]
Node-2
ip-10-93-135-215
2018-02-22 16:21:19.403 INFO 19074 --- [jgroups-24,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|18] (3) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320]
2018-02-22 16:21:19.426 TRACE 19074 --- [jgroups-27,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (1599 secs old)
)
2018-02-22 16:21:19.430 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.430 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: suspecting []
2018-02-22 16:21:19.432 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.432 TRACE 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:19.432 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: suspecting [ip-10-93-133-149-13458]
2018-02-22 16:21:19.433 DEBUG 19074 --- [jgroups-22,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: broadcasting unsuspect(ip-10-93-133-149-13458)
2018-02-22 16:21:19.433 TRACE 19074 --- [jgroups-27,ABC-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
was (Author: sibin.karnavar):
All timestamps are in UTC
Members in the cluster: ip-10-93-136-91, ip-10-93-133-149 and ip-10-93-135-215
Node 0: (Master Node / Leader)
ip-10-93-136-91
This node was the leader node and I have killed it at 2018-02-22 16:19:58.186 UTC time. If you see the FD_SOCK Trace timestamp, its not detecting the TCP socket connection break immediately.
2018-02-22 16:21:19.430 TRACE 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (559 secs old)
)
Node 1:
ip-10-93-133-149
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|17] (2) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458]
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - I am not the master!
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - ip-10-93-135-215-41546 is the master for service SOM-SKS
2018-02-22 16:21:19.408 INFO 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|18] (3) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320]
2018-02-22 16:21:19.409 INFO 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - I am not the master!
2018-02-22 16:21:19.430 TRACE 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (559 secs old)
)
2018-02-22 16:21:19.434 TRACE 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.434 DEBUG 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: suspecting [ip-10-93-135-215-41546]
2018-02-22 16:21:19.435 DEBUG 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: broadcasting unsuspect(ip-10-93-135-215-41546)
2018-02-22 16:21:19.435 TRACE 23603 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.436 TRACE 23603 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:19.437 TRACE 23603 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.429 TRACE 23603 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:49.429 TRACE 23603 --- [jgroups-16,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: who-has-sock ip-10-93-133-149-13458
2018-02-22 16:21:49.429 DEBUG 23603 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: suspecting [ip-10-93-135-215-41546]
2018-02-22 16:21:49.430 DEBUG 23603 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: broadcasting unsuspect(ip-10-93-135-215-41546)
2018-02-22 16:21:49.430 TRACE 23603 --- [jgroups-16,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:49.431 TRACE 23603 --- [jgroups-16,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.432 TRACE 23603 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.437 TRACE 23603 --- [jgroups-16,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-136-91-22320:
mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.527 INFO 23603 --- [jgroups-16,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: MergeView::[ip-10-93-135-215-41546|20] (3)
[ip-10-93-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320], 2 subgroups: [ip-10-93-136-91-22320|19] (1) [ip-10-93-136-91-22320], [ip-10-93-135-215-41546|18] (3) [ip-10-93-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-
91-22320]
Node-2
ip-10-93-135-215
2018-02-22 16:21:19.403 INFO 19074 --- [jgroups-24,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|18] (3) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320]
2018-02-22 16:21:19.426 TRACE 19074 --- [jgroups-27,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (1599 secs old)
)
2018-02-22 16:21:19.430 TRACE 19074 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.430 DEBUG 19074 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: suspecting []
2018-02-22 16:21:19.432 TRACE 19074 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.432 TRACE 19074 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:19.432 DEBUG 19074 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: suspecting [ip-10-93-133-149-13458]
2018-02-22 16:21:19.433 DEBUG 19074 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: broadcasting unsuspect(ip-10-93-133-149-13458)
2018-02-22 16:21:19.433 TRACE 19074 --- [jgroups-27,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
> FD_SOCK is not working in AWS environment
> -----------------------------------------
>
> Key: JGRP-2253
> URL: https://issues.jboss.org/browse/JGRP-2253
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.10
> Environment: AWS - EC2
> Reporter: Sibin Karnavar
> Assignee: Bela Ban
>
> We have our failure detection defined like below.
> <FD_SOCK external_port="7804" />
> <FD timeout="3000" max_tries="3" />
> <VERIFY_SUSPECT timeout="3000" />
> Please note that we have used FD instead of FD_ALL in AWS. We will be changing it to FD_ALL later after detailed testing.
> In my local, this is working perfect. As soon as I kill my node, I was able to see that view change was happening immediately with FD_SOCK.
> We were not mentioning the external_port in the FD_SOCK but later I thought it may be an issue with the port and defined it as 7804 and added the same port to the security group that allows to access this port among all the nodes. So no issue with the port.
> Can you please let us know if we need any additional configurations to make FD_SOCK works well in AWS.
> Thanks,
> Sibin
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
- 1
- 0
[JBoss JIRA] (JGRP-2253) FD_SOCK is not working in AWS environment
by Sibin Karnavar (JIRA)
[ https://issues.jboss.org/browse/JGRP-2253?page=com.atlassian.jira.plugin.... ]
Sibin Karnavar commented on JGRP-2253:
--------------------------------------
All timestamps are in UTC
Members in the cluster: ip-10-93-136-91, ip-10-93-133-149 and ip-10-93-135-215
Node 0: (Master Node / Leader)
ip-10-93-136-91
This node was the leader node and I have killed it at 2018-02-22 16:19:58.186 UTC time. If you see the FD_SOCK Trace timestamp, its not detecting the TCP socket connection break immediately.
2018-02-22 16:21:19.430 TRACE 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (559 secs old)
)
Node 1:
ip-10-93-133-149
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|17] (2) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458]
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - I am not the master!
2018-02-22 16:20:26.917 INFO 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - ip-10-93-135-215-41546 is the master for service SOM-SKS
2018-02-22 16:21:19.408 INFO 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|18] (3) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320]
2018-02-22 16:21:19.409 INFO 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - I am not the master!
2018-02-22 16:21:19.430 TRACE 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (559 secs old)
)
2018-02-22 16:21:19.434 TRACE 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.434 DEBUG 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: suspecting [ip-10-93-135-215-41546]
2018-02-22 16:21:19.435 DEBUG 23603 --- [jgroups-13,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: broadcasting unsuspect(ip-10-93-135-215-41546)
2018-02-22 16:21:19.435 TRACE 23603 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.436 TRACE 23603 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:19.437 TRACE 23603 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.429 TRACE 23603 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:49.429 TRACE 23603 --- [jgroups-16,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: who-has-sock ip-10-93-133-149-13458
2018-02-22 16:21:49.429 DEBUG 23603 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: suspecting [ip-10-93-135-215-41546]
2018-02-22 16:21:49.430 DEBUG 23603 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: broadcasting unsuspect(ip-10-93-135-215-41546)
2018-02-22 16:21:49.430 TRACE 23603 --- [jgroups-16,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:49.431 TRACE 23603 --- [jgroups-16,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.432 TRACE 23603 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.437 TRACE 23603 --- [jgroups-16,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] org.jgroups.protocols.FD_SOCK : - - ip-10-93-133-149-13458: received UNSUSPECT message from ip-10-93-136-91-22320:
mbrs=[ip-10-93-133-149-13458]
2018-02-22 16:21:49.527 INFO 23603 --- [jgroups-16,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-133-149-13458] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: MergeView::[ip-10-93-135-215-41546|20] (3)
[ip-10-93-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320], 2 subgroups: [ip-10-93-136-91-22320|19] (1) [ip-10-93-136-91-22320], [ip-10-93-135-215-41546|18] (3) [ip-10-93-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-
91-22320]
Node-2
ip-10-93-135-215
2018-02-22 16:21:19.403 INFO 19074 --- [jgroups-24,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] c.w.s.c.ServiceClusterCoordinator : - - Detected change in view membership: [ip-10-93-135-215-41546|18] (3) [ip-10-93
-135-215-41546, ip-10-93-133-149-13458, ip-10-93-136-91-22320]
2018-02-22 16:21:19.426 TRACE 19074 --- [jgroups-27,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: i-have-sock: ip-10-93-136-91-22320 -->
10.93.136.91:7804 (cache is ip-10-93-133-149-13458: 10.93.133.149:7804 (559 secs old)
ip-10-93-136-91-22320: 10.93.136.91:7804 (0 ms old)
ip-10-93-135-215-41546: 10.93.135.215:7804 (1599 secs old)
)
2018-02-22 16:21:19.430 TRACE 19074 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.430 DEBUG 19074 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: suspecting []
2018-02-22 16:21:19.432 TRACE 19074 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received UNSUSPECT message from ip-10-93-133-149-
13458: mbrs=[ip-10-93-135-215-41546]
2018-02-22 16:21:19.432 TRACE 19074 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received SUSPECT message from ip-10-93-136-91-22320:
suspects=[ip-10-93-133-149-13458]
2018-02-22 16:21:19.432 DEBUG 19074 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: suspecting [ip-10-93-133-149-13458]
2018-02-22 16:21:19.433 DEBUG 19074 --- [jgroups-22,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: broadcasting unsuspect(ip-10-93-133-149-13458)
2018-02-22 16:21:19.433 TRACE 19074 --- [jgroups-27,SOM-SKS-test_SJX_080220180246_XSJ,ip-10-93-135-215-41546] org.jgroups.protocols.FD_SOCK : - - ip-10-93-135-215-41546: received UNSUSPECT message from ip-10-93-135-215-
41546: mbrs=[ip-10-93-133-149-13458]
> FD_SOCK is not working in AWS environment
> -----------------------------------------
>
> Key: JGRP-2253
> URL: https://issues.jboss.org/browse/JGRP-2253
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.10
> Environment: AWS - EC2
> Reporter: Sibin Karnavar
> Assignee: Bela Ban
>
> We have our failure detection defined like below.
> <FD_SOCK external_port="7804" />
> <FD timeout="3000" max_tries="3" />
> <VERIFY_SUSPECT timeout="3000" />
> Please note that we have used FD instead of FD_ALL in AWS. We will be changing it to FD_ALL later after detailed testing.
> In my local, this is working perfect. As soon as I kill my node, I was able to see that view change was happening immediately with FD_SOCK.
> We were not mentioning the external_port in the FD_SOCK but later I thought it may be an issue with the port and defined it as 7804 and added the same port to the security group that allows to access this port among all the nodes. So no issue with the port.
> Can you please let us know if we need any additional configurations to make FD_SOCK works well in AWS.
> Thanks,
> Sibin
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
- 1
- 0
[JBoss JIRA] (JGRP-2253) FD_SOCK is not working in AWS environment
by Sibin Karnavar (JIRA)
[ https://issues.jboss.org/browse/JGRP-2253?page=com.atlassian.jira.plugin.... ]
Sibin Karnavar commented on JGRP-2253:
--------------------------------------
I have done below changes. I am attaching the logs below.
1) <TCP
external_addr="${ext-addr}"
bind_addr="match-interface:eth0"
.........../>
2) <FD_SOCK external_port="7804" external_addr="${ext-addr}" bind_addr="match-interface:eth0"/>
3) Added -Dext-addr as the IP address of the EC2 node
4)Enabled the Trace log for FD_SOCK.
You wil see that, socket connections break is not immediately detected after I kill one of the node.
> FD_SOCK is not working in AWS environment
> -----------------------------------------
>
> Key: JGRP-2253
> URL: https://issues.jboss.org/browse/JGRP-2253
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.10
> Environment: AWS - EC2
> Reporter: Sibin Karnavar
> Assignee: Bela Ban
>
> We have our failure detection defined like below.
> <FD_SOCK external_port="7804" />
> <FD timeout="3000" max_tries="3" />
> <VERIFY_SUSPECT timeout="3000" />
> Please note that we have used FD instead of FD_ALL in AWS. We will be changing it to FD_ALL later after detailed testing.
> In my local, this is working perfect. As soon as I kill my node, I was able to see that view change was happening immediately with FD_SOCK.
> We were not mentioning the external_port in the FD_SOCK but later I thought it may be an issue with the port and defined it as 7804 and added the same port to the security group that allows to access this port among all the nodes. So no issue with the port.
> Can you please let us know if we need any additional configurations to make FD_SOCK works well in AWS.
> Thanks,
> Sibin
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
- 1
- 0
[JBoss JIRA] (WFLY-9878) EclipseLink Entity Scanning broken in Wildfly 11
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-9878?page=com.atlassian.jira.plugin.... ]
Scott Marlow updated WFLY-9878:
-------------------------------
Fix Version/s: (was: 12.0.0.Final)
> EclipseLink Entity Scanning broken in Wildfly 11
> ------------------------------------------------
>
> Key: WFLY-9878
> URL: https://issues.jboss.org/browse/WFLY-9878
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 11.0.0.Final
> Environment: Enterprise Maven Project
> Wildfly 11
> Eclipse Link 2.7.1 (2.6.3 and 2.64 were also tested)
> Reporter: Alessandro Moscatelli
> Assignee: Scott Marlow
>
> Following :
> https://docs.jboss.org/author/display/WFLY/JPA+Reference+Guide#JPAReferen...
> When you try to persist ANY entity (located in ejb, or jar or anywhere you want) if such entity is not listed in persistence.xml you'll get a :
> Caused by: javax.ejb.EJBException: java.lang.IllegalArgumentException: Object: org.visiontech.optoplus.entity.Provider[ id=null ] is not a known Entity type
> If I list such entity in persistence.xml the error is gone and the entity is persisted.
> Inside standalone.xml I used :
> <system-properties>
> ...
> <property name="eclipselink.archive.factory" value="org.jipijapa.eclipselink.JBossArchiveFactoryImpl"/>
> </system-properties>
> Is this a problem related to the last version (11 Final) of jipijapa.eclipselink ?
> I found several topic stating that what I done worked with Wildfly 10 and older version of jipijapa.
> I tried several combination of older jipijapa and eclipselink versions without success.
> I have about 130 entities in my probject, I'd REALLY love not to enlist them all.
> My persistence.xml :
> <persistence-unit name="optoplus">
> <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
> <jta-data-source>java:/jdbc/db_optoplus</jta-data-source>
> <exclude-unlisted-classes>false</exclude-unlisted-classes>
> </persistence-unit>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
- 1
- 0