[jboss-jira] [JBoss JIRA] (JGRP-2253) FD_SOCK is not working in AWS environment
[
https://issues.jboss.org/browse/JGRP-2253?page=com.atlassian.jira.plugin....
]
Sibin Karnavar commented on JGRP-2253:
--------------------------------------
Thank you, Thanks for your hints :) Your documents was really helpful.
Do you think, you may need to log as WARN, when failed to establish a socket connection
due to any reason?
Even I found TCP has a default diagnostics_port. I just defined my own port and added that
as well to security group.
Thanks,
Sibin
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)