ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Semen Boikov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-1366) Start CacheProcessor before QueryProcessor
Date Fri, 04 Sep 2015 07:36:45 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Semen Boikov updated IGNITE-1366:
---------------------------------
    Fix Version/s:     (was: ignite-1.5)
                   ignite-1.4

> 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.4
>
>
> 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)

Mime
View raw message