[
https://issues.apache.org/jira/browse/IGNITE-14499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317008#comment-17317008
]
Ignite TC Bot commented on IGNITE-14499:
----------------------------------------
{panel:title=Branch: [pull/8981/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8981/head] Base: [master] : New Tests
(14)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}SPI{color} [[tests
14|https://ci.ignite.apache.org/viewLog.html?buildId=5955898]]
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryVmIpFinderDnsResolveTest.testFqdnResolveAfterDnsHostChange -
PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryVmIpFinderDnsResolveTest.testMultiFqdnResolve - PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryVmIpFinderDnsResolveTest.testFqdnResolveWhenDnsCantResolveHostName
- PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryVmIpFinderDnsResolveTest.testMultiFqdnResolveWithPortRange -
PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryVmIpFinderDnsResolveTest.testFqdnWithPortRangeResolveWithTwoIpRoundRobinDns
- PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryVmIpFinderDnsResolveTest.testFqdnWithPortRangeResolveAfterDnsHostChange
- PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryVmIpFinderDnsResolveTest.testMultiFqdnWithPortRangeResolveWithRegisteredAddrs
- PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryVmIpFinderDnsResolveTest.testMultiFqdnResolveWithRegisteredAddrs -
PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryVmIpFinderDnsResolveTest.testFqdnResolveWithRegisteredAddrs -
PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryVmIpFinderDnsResolveTest.testMultiFqdnWithPortResolve -
PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryVmIpFinderDnsResolveTest.testFqdnWithPortResolveWithRegisteredAddrs
- PASSED{color}
... and 3 new tests
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5955970&buildTypeId=IgniteTests24Java8_RunAll]
> TcpDiscoveryVM IP Finder: thick client does not try to resolve the FQDN again
> during reconnection
> -------------------------------------------------------------------------------------------------
>
> Key: IGNITE-14499
> URL: https://issues.apache.org/jira/browse/IGNITE-14499
> Project: Ignite
> Issue Type: Bug
> Components: messaging
> Affects Versions: 2.10
> Reporter: Andrey Aleksandrov
> Assignee: Andrey Aleksandrov
> Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Client reconnect logic has for the following scenarios:
> 1)You have 3 servers. FQDN name can be resolved to one of them (but only to
> reachable server node).
> 2)You have 3 servers. FQDN name will be resolved to the list of the reachable
> server IPs.
> Results:
> Thick clients do not try to resolve FQDN once again upon connection failure.
> Reconnect doesn't work.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
