[
https://issues.apache.org/jira/browse/IGNITE-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193085#comment-15193085
]
Ryan Zhao commented on IGNITE-2404:
-----------------------------------
Hi, in the implementation of the change presented above, I have found that many
component in Ignite have a portRange parameter, such as
IgniteConfiguration#getTimeServerPortRange and
ConnectorConfiguration#getPortRange. And in these scenarios portRange equals 0
is considered to be a mistake.
So, I think we should keep this consistency, and make the docs more clear.
Any thoughts?
> TcpDiscoverySpi.setLocalPortRange set 0 doesn't work
> -----------------------------------------------------
>
> Key: IGNITE-2404
> URL: https://issues.apache.org/jira/browse/IGNITE-2404
> Project: Ignite
> Issue Type: Bug
> Reporter: Denis Magda
> Assignee: Ryan Zhao
> Labels: community, newbie
>
> Local port range set to 0 presently doesn't work at least for
> TcpCommunicationSpi and TcpDiscoverySpi. However SPIs support it.
> In my understanding the condition has to changed to the following one (from <
> to <=).
> x = port; x <= port + range
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
