You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgenii Zhuravlev (JIRA)" <ji...@apache.org> on 2017/07/05 10:46:00 UTC
[jira] [Updated] (IGNITE-5700) Port range defined in addresses
should override TcpDiscoverySpi.localPortRange
[ https://issues.apache.org/jira/browse/IGNITE-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Evgenii Zhuravlev updated IGNITE-5700:
--------------------------------------
Summary: Port range defined in addresses should override TcpDiscoverySpi.localPortRange (was: Port range defines in addresses should override TcpDiscoverySpi.localPortRange)
> Port range defined in addresses should override TcpDiscoverySpi.localPortRange
> -------------------------------------------------------------------------------
>
> Key: IGNITE-5700
> URL: https://issues.apache.org/jira/browse/IGNITE-5700
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Evgenii Zhuravlev
> Priority: Minor
>
> If addresses were configured with
> {code:java}
> <property name="addresses">
> <list>
> <!-- In distributed environment, replace with actual host IP address. -->
> <value>127.0.0.1:47500..47502</value>
> </list>
> </property>
> {code}
> with default localPortRange(100) it's possible for node to bind on 47503 port.
> If localPortRange was set to 0, node can't join to 47501 port.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)