[
https://issues.apache.org/jira/browse/IGNITE-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-4476.
-------------------------------------
Resolution: Won't Fix
Too risky from performance perspective.
> 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)
