ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vyacheslav Daradur (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-10555) Set 'TcpDiscoveryVmIpFinder' as default IP finder for tests instead of 'TcpDiscoveryMulticastIpFinder'
Date Wed, 05 Dec 2018 15:25:00 GMT
Vyacheslav Daradur created IGNITE-10555:
-------------------------------------------

             Summary: Set 'TcpDiscoveryVmIpFinder' as default IP finder for tests instead
of 'TcpDiscoveryMulticastIpFinder'
                 Key: IGNITE-10555
                 URL: https://issues.apache.org/jira/browse/IGNITE-10555
             Project: Ignite
          Issue Type: Improvement
            Reporter: Vyacheslav Daradur
            Assignee: Vyacheslav Daradur
             Fix For: 2.8


Most of our tests starting Ignite nodes in the same JVM, that allows
us using shared 'TcpDiscoveryVmIpFinder'.

There are following main advantages of using 'TcpDiscoveryVmIpFinder':
* reducing possible conflicts in the development environment, when
nodes from different clusters may find each other;
* speedup of nodes initial discovery, especially on Windows;
* avoiding of overwriting 'getConfiguration' and copypasta only to set
up static IP finder in tests;

We should change the default IP finder in tests to
'TcpDiscoveryVmIpFinder' as the first step and remove related
boilerplate as the second step.

Once the first step of the change will be finished then we should fill a separate task for
removing related boilerplate.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message