Hi Stan,
any news on this?
Sincerely
пт, 20 июл. 2018 г., 4:12 Dmitriy Setrakyan :
> Why not use a combination of Multicast and VM finders? This way we do not
> have to make any sacrifices.
>
> D.
>
> On Wed, Jul 18, 2018 at 9:38 PM, Vladimir Ozerov
> wrote:
>
> > TcpDiscoveryVmIpFinder can be
Why not use a combination of Multicast and VM finders? This way we do not
have to make any sacrifices.
D.
On Wed, Jul 18, 2018 at 9:38 PM, Vladimir Ozerov
wrote:
> TcpDiscoveryVmIpFinder can be configured with 127.0.0.1. Example with
> remote nodes will work fine on a single machine. Users rare
TcpDiscoveryVmIpFinder can be configured with 127.0.0.1. Example with
remote nodes will work fine on a single machine. Users rarely run examples
on multiple machines.
чт, 19 июля 2018 г. в 5:30, Dmitriy Setrakyan :
> I am confused, the TcpDiscoveryVmIpFinder will only discover nodes with
> specif
I am confused, the TcpDiscoveryVmIpFinder will only discover nodes with
specified list of IPs. Don't we have examples that require remote nodes to
join?
D.
On Wed, Jul 18, 2018 at 7:52 AM, Stanislav Lukyanov
wrote:
> > It can seem not important, but saves a minute for everyone.
> No, it actuall
> It can seem not important, but saves a minute for everyone.
No, it actually does seem important when you think about it :) Thanks for the
suggestion.
Let me correct this then.
The issue is
IGNITE-6826: Change default DiscoverySpi ipFinder type for examples
https://issues.apache.org/jira/browse
