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

[Sibin Karnavar (JIRA)]

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

Sibin Karnavar commented on JGRP-2253:
--------------------------------------

And I thought the suspect messages in my logs are due to FD fails 3 times and I have defined VERIFY_SUSPECT.  So What I was mentioning was some how FD_SOCK is not detecting TCP connection breakage while terminating an EC2 instance but FD is catching it before FD_SOCK. But FD_SOCK is able to detect it when I do a kill -9.

> 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)