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

Roman Puchkovskiy updated IGNITE-22369:
---------------------------------------
    Description: 
Currently, we can only bind to one address. It should be possible to bind to 
many addresses.

Another potential improvement is that we can include port in each listen 
address, so that different addresses use different ports (this probably needs 
discussion).

Implementation of this issue will probably require to solve the following:
 # How to get all local IP addresses (already partially solved)
 # Currently, <consistentId, address> pair is used to identify a node. If there 
will be many addresses (with no obvious way to choose the primary address), 
we'll need to identify a node differently. We could take a look at how it's 
done in Apache Ignite 2

  was:
Currently, we can only bind to one address. It should be possible to bind to 
many addresses.

Another potential improvement is that we can include port in each listen 
address, so that different addresses use different ports (this probably needs 
discussion).


> Support binding to multiple addresses
> -------------------------------------
>
>                 Key: IGNITE-22369
>                 URL: https://issues.apache.org/jira/browse/IGNITE-22369
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>
> Currently, we can only bind to one address. It should be possible to bind to 
> many addresses.
> Another potential improvement is that we can include port in each listen 
> address, so that different addresses use different ports (this probably needs 
> discussion).
> Implementation of this issue will probably require to solve the following:
>  # How to get all local IP addresses (already partially solved)
>  # Currently, <consistentId, address> pair is used to identify a node. If 
> there will be many addresses (with no obvious way to choose the primary 
> address), we'll need to identify a node differently. We could take a look at 
> how it's done in Apache Ignite 2



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

Reply via email to