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 2015/01/27 12:21:34 UTC

[jira] [Created] (IGNITE-138) Ensure that utility cache is really executed in utility pool

Vladimir Ozerov created IGNITE-138:
--------------------------------------

             Summary: Ensure that utility cache is really executed in utility pool
                 Key: IGNITE-138
                 URL: https://issues.apache.org/jira/browse/IGNITE-138
             Project: Ignite
          Issue Type: Bug
          Components: cache
    Affects Versions: sprint-1
            Reporter: Vladimir Ozerov
            Assignee: Vladimir Ozerov
            Priority: Critical
             Fix For: sprint-1


See GridCacheIoManager:
1) sendOrderedMessaage() always use system pool.
2) safeSend() always use system pool.
3) send(ClusterNode, GridCacheMessage) use system pool implicitly.

With such design there is a great risk that system cache either already process some of it's messages in system pool instead of utility pool, or will do it at some point in future.

Possible solutions:
1) Move GridCacheIoManager from shared context to cache context.
2) Force all public methods to specify IO policy explicitly.



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