[
https://issues.apache.org/jira/browse/IGNITE-9738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648005#comment-16648005
]
Ignite TC Bot commented on IGNITE-9738:
---------------------------------------
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2066812]]
* WalRolloverRecordLoggingFsyncTest.testAvoidInfinityWaitingOnRolloverOfSegment
(last started)
{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2066796]]
* GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxSixNodesTwoBackups
(last started)
{color:#d04437}Cache (Deadlock Detection){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2066841]]
* TxDeadlockDetectionNoHangsTest.testNoHangsPessimistic (last started)
{color:#d04437}_Javadoc_{color} [[tests 0 Exit Code , BuildFailureOnMessage
|https://ci.ignite.apache.org/viewLog.html?buildId=2066820]]
{color:#d04437}_Licenses Headers_{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2066821]]
{color:#d04437}Cache 2{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2066832]]
* IgniteCacheTestSuite2:
CacheTxLoadingConcurrentGridStartSelfTestAllowOverwrite.testLoadCacheWithDataStreamerSequentialClientWithConfig
- 1,0% fails in last 100 master runs.
{color:#d04437}Cache 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2066833]]
* IgniteBinaryObjectsCacheTestSuite3:
IgniteCacheGroupsTest.testNoKeyIntersectTx - 1,0% fails in last 100 master runs.
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=2066854&buildTypeId=IgniteTests24Java8_RunAll]
> Client node can suddenly fail on start
> --------------------------------------
>
> Key: IGNITE-9738
> URL: https://issues.apache.org/jira/browse/IGNITE-9738
> Project: Ignite
> Issue Type: Bug
> Reporter: Vladislav Pyatkov
> Assignee: Vladislav Pyatkov
> Priority: Major
>
> If client joining to large topology it can to spend some time on waiting
> {{TcpDiscoveryNodeAddFinishedMessage}}, but in that time it can not to send
> {{TcpDiscoveryClientMetricsUpdateMessage.}} By that reason server can to
> reset client from topology.
> {noformat}
> Client node considered as unreachable and will be dropped from cluster,
> because no metrics update messages received in interval:
> TcpDiscoverySpi.clientFailureDetectionTimeout() ms. It may be caused by
> network problems or long GC pause on client node, try to increase this
> parameter. [nodeId=a3493895-7c13-403c-bf0d-94eab0000011,
> clientFailureDetectionTimeout=30000];
> {noformat}
> We should to sent {{TcpDiscoveryClientMetricsUpdateMessage as soon as
> possible}} without, waiting finish of join procedure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
