[ https://issues.apache.org/jira/browse/IGNITE-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16569937#comment-16569937 ]
Anton Kalashnikov commented on IGNITE-5103: ------------------------------------------- Changes looks good for me. But various tests in SPI suit started to fail often than usual. Perhaps we will need to change tests or maybe clientFailureDetectionTimeout is incorrect. https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Spi&branch_IgniteTests24Java8=pull%2F4446%2Fhead&tab=buildTypeStatusDiv > TcpDiscoverySpi ignores maxMissedClientHeartbeats property > ---------------------------------------------------------- > > Key: IGNITE-5103 > URL: https://issues.apache.org/jira/browse/IGNITE-5103 > Project: Ignite > Issue Type: Bug > Components: general > Affects Versions: 1.9 > Reporter: Valentin Kulichenko > Assignee: Evgenii Zhuravlev > Priority: Blocker > Fix For: 2.7 > > Attachments: TcpDiscoveryClientSuspensionSelfTest.java > > > 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005)