[jboss-jira] [JBoss JIRA] (JGRP-2253) FD_SOCK is not working in AWS environment

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596056#comment-13596056 ] 

Bela Ban commented on JGRP-2253:
--------------------------------

I can't really see something other than the SUSPECT/UNSUSPECT cycles in your logs, which are suspicious and point to FD_SOCK not being able to connect to the destination it is supposed to monitor:

{noformat}
21:52:16.021 TRACE 1108 — [jgroups-13,cluster,ip-143-60500] FD_SOCK : - - ip-143-60500: received SUSPECT message from ip-48-43121: suspects=[ip-143-60500]
21:52:16.022 TRACE 1108 — [jgroups-13,cluster,ip-143-60500] FD_SOCK : - - ip-143-60500: received SUSPECT message from ip-48-43121: suspects=[ip-163-65450]
21:52:16.024 TRACE 1108 — [jgroups-3,cluster,ip-143-60500] FD_SOCK : - - ip-143-60500: received UNSUSPECT message from ip-48-43121: mbrs=[ip-143-60500]
21:52:16.025 TRACE 1108 — [jgroups-4,cluster,ip-143-60500] FD_SOCK : - - ip-143-60500: received UNSUSPECT message from ip-48-43121: mbrs=[ip-163-65450]
{noformat}

My bet is that this is caused by incorrect ports, which causes FD_SOCK to malfunction.

I'm also not sure that termination on EC2/AWS closes the sockets of a process, or whether termination is more like a power-down / pull-the power-plug like behavior. I seem to recall that this was the case. If so, FD_SOCK would not kick in, but FD would instead...

> 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
>             Fix For: 4.0.13
>
>
> 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)