[
https://issues.apache.org/jira/browse/IGNITE-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16103485#comment-16103485
]
Denis Mekhanikov edited comment on IGNITE-5700 at 7/27/17 4:52 PM:
-------------------------------------------------------------------
_localPort_ and _IpFinder_ serve different purpose. Port for listening is
chosen based on _localPort_ and _localPortRange_. On the other hand, _IpFinder_
defines the set of addresses that should be used during nodes discovery. So,
port range, specified in _IpFinder_, should not necessary contain the port that
the new node starts listening to.
was (Author: dmekhanikov):
_localPort_ and _IpFinder_ serve different purpose. Port for listening is
chosen based on _localPort_ and _localPortRange_. On the other hand, IpFinder
defines the set of addresses that should be used during nodes discovery. So,
port range, specified in IpFinder, should not necessary contain the port that
the new node starts listening to.
> 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
> Assignee: Denis Mekhanikov
> 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)
