[
https://issues.apache.org/jira/browse/IGNITE-10555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722031#comment-16722031
]
Ignite TC Bot commented on IGNITE-10555:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}[Inspections] Core{color} [[tests 0 BuildFailureOnMetric
|https://ci.ignite.apache.org/viewLog.html?buildId=2548656]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2548661&buildTypeId=IgniteTests24Java8_RunAll]
> 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
> Priority: Major
> 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)
