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

Posted to dev@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2015/09/03 12:44:45 UTC

[jira] [Created] (IGNITE-1366) Start CacheProcessor before QueryProcessor

Semen Boikov created IGNITE-1366:
------------------------------------

             Summary: Start CacheProcessor before QueryProcessor
                 Key: IGNITE-1366
                 URL: https://issues.apache.org/jira/browse/IGNITE-1366
             Project: Ignite
          Issue Type: Bug
          Components: cache
            Reporter: Semen Boikov
            Assignee: Semen Boikov
            Priority: Critical
             Fix For: ignite-1.5


Now QueryProcessor is started before CacheProcessor. With this order cache processor can be stopped at the moment when query request is processed, and this causes sporadic errors like NPE (I see this from time to time in IgniteCacheQueryNodeRestartSelfTest).

Looks like cache processor does not need QueryProcessor when it's 'start' method is called so I think start order should be changed. 



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