[
https://issues.apache.org/jira/browse/IGNITE-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847311#comment-16847311
]
Ignite TC Bot commented on IGNITE-11865:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Scala (Visor Console){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3922845]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3913074&buildTypeId=IgniteTests24Java8_RunAll]
> FailureProcessor treats tcp-comm-worker as blocked when it works on
> reestablishing connect to failed client node
> ----------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-11865
> URL: https://issues.apache.org/jira/browse/IGNITE-11865
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.7
> Reporter: Sergey Chugunov
> Assignee: Sergey Chugunov
> Priority: Minor
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When client node fails tcp-comm-worker thread on server keeps trying to
> reestablish connection to the client until failed node is removed from
> topology (on expiration of clientFailureDetectionTimeout).
> As tcp-comm-worker thread doesn't update its heartbeats from internal loops
> FailureProcessor considers it as blocked and prints out misleading message to
> logs along with full thread dump.
> To avoid polluting logs with unnecessary messages we need to teach
> tcp-comm-worker how to update its heartbeat timestamp in FailureProcessor.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
