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

Bela Ban (JIRA) issues at jboss.org
Fri Apr 27 06:04:01 EDT 2018


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

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

Sorry for the delay!

Well, first of all, external_addr for FD_SOCK seems not necessary since you're only using internal IP addresses.

Secondly, terminating an EC2 instance apparently doesn't (always) close the sockets of the killed process, so it is not the same as {{kill -3/-9}}. In that case, FD_ALL (or FD) acts as second line of defense.
IIRC, AWS allows you to add a hook (script) to the termination process, in that hook, you could kill the process. But I haven't used AWS for months, so maybe this has changed...

The best way would be to shut down the cluster node *gracefully*, ie. via {{JChannel.close()}}; this would install a new view in the remaining members quickly.


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


More information about the jboss-jira mailing list