[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=13595640#comment-13595640 ] 

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

<<One thing you should do is to separate TCP.bind_port (7803), TCP.diagnostics_port (7806) and FD_SOCK.start_port (7804)>>

Currently we have defined my bind port as 7803 and port_range as 0. So There is no chance that a member can use 7804 as my TCP bind port. We did this because we want to make sure only one port is dedicated for TCP bind port. In addition to that, we have only one member running in one EC2 instance. Do you think it is still an issue?  if So What is the other best way to separate it out.

<<Note that I've run JGroups on AWS before, and I didn't define any start_port or client_bind_port in FD_SOCK, so these ports are picked by the OS.>>

We have defined a security group inbound ports in AWS so only certain port is allows to access an EC2 instance. If JGroup uses a random client_bind_port, then it won't work. That's why we have mentioned a specific port. I was able to make FD_SOCK work after defining that port. Thats why kill -9 always work. But for some reason terminating EC2 instance from console doesn't work well. 

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