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

Philipp Shergalis updated IGNITE-24400:
---------------------------------------
    Description: 
It seems that being able to put together a cluster without specifying addresses 
is crucial for the onboarding experience. This is possible in Docker Compose or 
K8S but that creates a dependency on these orchestration tools.

Let’s add an alternative node finder that will use a multicast address.

The multicast address should be configurable.

There is no need to combine multicast and static/explicit IPs. There seem to be 
no use case when a user would want to have some nodes connecting through 
multicast and some discovered by IP/DNS.

Using multicast by default creates issues. It should be fine not to make it 
default but provide it as a configuration option.

> Implement multicast finder
> --------------------------
>
>                 Key: IGNITE-24400
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24400
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladimir Pligin
>            Priority: Major
>              Labels: ignite-3
>
> It seems that being able to put together a cluster without specifying 
> addresses is crucial for the onboarding experience. This is possible in 
> Docker Compose or K8S but that creates a dependency on these orchestration 
> tools.
> Let’s add an alternative node finder that will use a multicast address.
> The multicast address should be configurable.
> There is no need to combine multicast and static/explicit IPs. There seem to 
> be no use case when a user would want to have some nodes connecting through 
> multicast and some discovered by IP/DNS.
> Using multicast by default creates issues. It should be fine not to make it 
> default but provide it as a configuration option.



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

Reply via email to