[infinispan-issues] [JBoss JIRA] (ISPN-11851) FD_SOCK should use the same bind address as TCP
Dan Berindei (Jira)
issues at jboss.org
Tue Jun 2 07:40:00 EDT 2020
[ https://issues.redhat.com/browse/ISPN-11851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130254#comment-14130254 ]
Dan Berindei commented on ISPN-11851:
-------------------------------------
Bela clarified that the JGroups default is actually fine: the transport passes its bind address up to all the other protocols.
I have updated the pull request to remove all the unnecessary {{bind_addr}} attributes from {{FD_SOCK}}, and also {{MPING}}.
> FD_SOCK should use the same bind address as TCP
> -----------------------------------------------
>
> Key: ISPN-11851
> URL: https://issues.redhat.com/browse/ISPN-11851
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration, Core
> Affects Versions: 11.0.0.Dev05, 10.1.8.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> In the JGroups configuration files we ship, we use a different default for {{TCP.bind_addr}} and {{UDP.bind_addr}} than JGroups does.
> {code:xml}
> <TCP bind_addr="${jgroups.bind.address,jgroups.tcp.address:SITE_LOCAL}"/>
> <UDP bind_addr="${jgroups.bind.address,jgroups.udp.address:SITE_LOCAL}"/>
> {code}
> However, we didn't change the default for {{FD_SOCK}}, so it uses the JGroups default:
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
More information about the infinispan-issues
mailing list