[JBoss JIRA] (ISPN-11851) FD_SOCK should use the same bind address as TCP
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-11851?page=com.atlassian.jira.plugi... ]
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)
2 years, 12 months
[JBoss JIRA] (ISPN-11945) JGroups Kubernetes stack should set `port_range="0"`
by Ryan Emerson (Jira)
Ryan Emerson created ISPN-11945:
-----------------------------------
Summary: JGroups Kubernetes stack should set `port_range="0"`
Key: ISPN-11945
URL: https://issues.redhat.com/browse/ISPN-11945
Project: Infinispan
Issue Type: Enhancement
Components: Cloud, Configuration
Affects Versions: 11.0.0.CR1
Reporter: Ryan Emerson
Assignee: Ryan Emerson
Fix For: 11.0.0.Final
Currently the provided jgroups kubernetes stack does not set {{port_range="0"}}. This doesn't make sense in Kubernetes deployments as ports are tightly controlled, so we want the sockets to always just use the configured {{bind_port}}.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
2 years, 12 months
[JBoss JIRA] (ISPN-11943) Single MediaType ignored in JSON config
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-11943?page=com.atlassian.jira.plugi... ]
Work on ISPN-11943 started by Gustavo Fernandes.
------------------------------------------------
> Single MediaType ignored in JSON config
> ---------------------------------------
>
> Key: ISPN-11943
> URL: https://issues.redhat.com/browse/ISPN-11943
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 11.0.0.CR1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> The recently introduced single MediaType config for both keys and values is being ignored when creating a cache from JSON:
> {code:json}
> {
> "distributed-cache":{
> "encoding":{
> "media-type":"application/x-protostream"
> }
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
2 years, 12 months