[IGNITE-5103] TcpDiscoverySpi ignores maxMissedClientHeartbeats property

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.9
• Fix Version/s: 2.7
• Component/s: general
• Assignee: Evgenii Zhuravlev
• Reporter: Valentin Kulichenko
• Created: 27/Apr/17 14:27
• Updated: 10/Aug/18 11:28
• Resolved: 10/Aug/18 11:24

Description

Test scenario is the following:

• Start one or more servers.
• Start a client node.
• Suspend client process using -SIGSTOP signal.
• Wait for maxMissedClientHeartbeats*heartbeatFrequency.
• Client node is expected to be removed from topology, but server nodes don't do that.

Attached is the unit test reproducing the same by stopping the heartbeat sender thread on the client.

Issue Links

• duplicates: IGNITE-5015 In TcpCommunicationSpi use IgniteConfiguration.clientFailureDetectionTimeout
• links to: CR-710
• links to: GitHub Pull Request #4446