[
https://issues.apache.org/jira/browse/IGNITE-14324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322448#comment-17322448
]
Ignite TC Bot commented on IGNITE-14324:
----------------------------------------
{panel:title=Branch: [pull/8980/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8980/head] Base: [master] : New Tests
(14)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}SPI{color} [[tests
10|https://ci.ignite.apache.org/viewLog.html?buildId=5967721]]
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryIpFinderFailureTest.testServerNodeStartupWithEmptySharedIpFinder -
PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryIpFinderFailureTest.testServerNodeDynamicIpFinderWithEmptyAddresses
- PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryIpFinderFailureTest.testServerNodeDynamicIpFinderFailureInTheMiddle
- PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryIpFinderFailureTest.testClientNodeSharedIpFinderFailure -
PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryIpFinderFailureTest.testClientNodeStaticIpFinderFailure -
PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryIpFinderFailureTest.testServerNodeBrokenStaticIpFinderZeroJoinTimeout
- PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryIpFinderFailureTest.testServerNodeBrokenDynamicIpFinderFromTheStartNoJoinTimeout
- PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryIpFinderFailureTest.testClientNodeIpFinderFailureWithZeroReconnectDelay
- PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryIpFinderFailureTest.testServerNodeStaticIpFinderFailureInTheMiddle
- PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryIpFinderFailureTest.testServerNodeBrokenStaticIpFinderWithJoinTimeout
- PASSED{color}
{color:#00008b}Kubernetes{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5967709]]
* {color:#013220}IgniteKubernetesTestSuite:
TestClusterClientConnection.testClientConnectsToCluster - PASSED{color}
* {color:#013220}IgniteKubernetesTestSuite:
TestKubernetesIpFinderDisconnection.testClientNodeDisconnectsWithMaxRetries -
PASSED{color}
* {color:#013220}IgniteKubernetesTestSuite:
TestKubernetesIpFinderDisconnection.testClientNodeIsNotDisconnectedWithBigNetworkTimeout
- PASSED{color}
* {color:#013220}IgniteKubernetesTestSuite:
TestKubernetesIpFinderDisconnection.testClientNodeDisconnectsWithDefaultSettings
- PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5967793&buildTypeId=IgniteTests24Java8_RunAll]
> EVT_CLIENT_NODE_DISCONNECTED is not triggered in k8s
> ----------------------------------------------------
>
> Key: IGNITE-14324
> URL: https://issues.apache.org/jira/browse/IGNITE-14324
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 2.9.1
> Reporter: Alexandr Shapkin
> Assignee: Alexandr Shapkin
> Priority: Major
> Labels: discovery
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Scenario:
> Kubernetes world, a server node, a k8s service, and a thick client. The
> client is subscribed to EVT_CLIENT_NODE_DISCONNECTED event and is connected
> to the server node.
> When a service goes down alongside the server, no
> EVT_CLIENT_NODE_DISCONNECTED is caught and the client reports only about a
> socket exception and inability to resolve IP addresses from the services,
> cause k8s resource is not available. The DEBUG logs (attached) show that
> discovery is constantly trying to use KubernetesIpFinder and restore the
> connection.
> Expected:
> Discovery realizes that a client is disconnected, no more reconnection
> attempts happen and EVT_CLIENT_NODE_DISCONNECTED is thrown.
> Solution:
> Count resolution attempts and if it’s more than the threshold (2 if
> failuredetectiontimeout is not configured, otherwise #reconnCount) give up
> and invoke disconnection logic
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
