[jira] [Assigned] (IGNITE-20639) Remove portRange from network configuration

["Mikhail Pochatkin (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-20639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mikhail Pochatkin reassigned IGNITE-20639:
------------------------------------------

    Assignee: Mikhail Pochatkin

> Remove portRange from network configuration
> -------------------------------------------
>
>                 Key: IGNITE-20639
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20639
>             Project: Ignite
>          Issue Type: Task
>          Components: networking
>            Reporter: Aleksandr
>            Assignee: Mikhail Pochatkin
>            Priority: Major
>              Labels: ignite-3
>
> The goal of IGNITE-20512 was to remove {{rest.portRange}} from REST server configuration and force the user to set up the port directly in {{rest.port}} configuration. That makes the configuration robust and easier to understand.
> I've noticed that we also have {{network.portRange}} configuration that looks weird now. It gets even stranger when we configure the node discovery part: {{network.nodeFilter.netClusterNodes: [localhost:3344, localhost:3345]}} . We have to specify peers with the direct address but configure the current address with a range.
> I propose to get rid of {{portRange}} in {{network}} section as well as we did it in {{rest}} and {{clientConnector}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)