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

Posted to dev@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2016/02/16 21:26:18 UTC

[jira] [Created] (IGNITE-2666) Node is not stopped when RingMessageWorker is interrupted

Denis Magda created IGNITE-2666:
-----------------------------------

             Summary: Node is not stopped when RingMessageWorker is interrupted
                 Key: IGNITE-2666
                 URL: https://issues.apache.org/jira/browse/IGNITE-2666
             Project: Ignite
          Issue Type: Bug
    Affects Versions: 1.5.0.final
            Reporter: Denis Magda
            Assignee: Denis Magda
             Fix For: 1.6


Presently if RingMessageWorker is stopped due to some exception we stop the node forcibly to avoid OOM on that node and cluster instability.

However, the node wasn't stopped when RingMessageWorker stopped its execution gracefully when {{isInterrupted()}} called returned {{true}}.
At this situation the node has to be stopped as well.

In addition we have to print the stack trace of a Thread that interrupted the message worker for debug purposes.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)