You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "Sergey Chugunov (JIRA)" <ji...@apache.org> on 2019/05/22 13:05:00 UTC

[jira] [Created] (IGNITE-11865) FailureProcessor treats tcp-comm-worker as blocked when it works on reestablishing connect to failed client node

Sergey Chugunov created IGNITE-11865:
----------------------------------------

             Summary: 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
             Fix For: 2.8


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)