[ 
https://issues.apache.org/jira/browse/IGNITE-17415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571287#comment-17571287
 ] 

Ignite TC Bot commented on IGNITE-17415:
----------------------------------------

{panel:title=Branch: [pull/10170/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10170/head] Base: [master] : New Tests 
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}SPI (Discovery){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=6697355]]
* {color:#013220}IgniteSpiDiscoverySelfTestSuite: 
TcpDiscoveryDeadNodeAddressResolvingTest.test - PASSED{color}

{color:#00008b}Basic 1{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=6697261]]
* {color:#013220}IgniteBasicTestSuite: 
IgniteUtilsSelfTest.testResolveLocalAddressesWithHostNameDefinedAndLocalHostNameNotIgnored
 - PASSED{color}
* {color:#013220}IgniteBasicTestSuite: 
IgniteUtilsSelfTest.testResolveLocalAddressesWithHostNameDefined - PASSED{color}

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6697370&buildTypeId=IgniteTests24Java8_RunAll]

> A node receives and resolves obsolete addresses from the previously restarted 
> and killed nodes
> ----------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-17415
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17415
>             Project: Ignite
>          Issue Type: Bug
>          Components: networking
>    Affects Versions: 2.13
>            Reporter: Semyon Danilov
>            Assignee: Semyon Danilov
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Observation: Ignite tries to resolve *all* known IP and DNS names exposed by 
> the nodes since the cluster startup. This might cause a delay in response if 
> DNS resolution takes some time and critical for Kubernetes envroments.
> The issue is due to the ignite keeping track of the topology history.



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

Reply via email to