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

Posted to dev@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/12/22 10:28:58 UTC

[jira] [Created] (IGNITE-4476) GridIoManger must always process messages asynchronously

Vladimir Ozerov created IGNITE-4476:
---------------------------------------

             Summary: GridIoManger must always process messages asynchronously
                 Key: IGNITE-4476
                 URL: https://issues.apache.org/jira/browse/IGNITE-4476
             Project: Ignite
          Issue Type: Task
          Components: general
    Affects Versions: 1.8
            Reporter: Vladimir Ozerov
             Fix For: 2.0


*Problem*
If message is to be sent to remote node, we just send it (surprise :-)). But if message is to be sent to local node, we have a strange "optimization" - we process it synchronously in the same thread. 
This is wrong as it easily leads to all kind of weird starvations and deadlocks.

*Solution*
Never ever process messages synchronously. For local node we should put message runnable into appropriate thread pool and exit.




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