You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2016/05/26 09:17:12 UTC
[jira] [Updated] (IGNITE-3038) Optimize internally used
ContinuousQueries
[ https://issues.apache.org/jira/browse/IGNITE-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Semen Boikov updated IGNITE-3038:
---------------------------------
Fix Version/s: 1.7
> Optimize internally used ContinuousQueries
> ------------------------------------------
>
> Key: IGNITE-3038
> URL: https://issues.apache.org/jira/browse/IGNITE-3038
> Project: Ignite
> Issue Type: Bug
> Reporter: Semen Boikov
> Assignee: Semen Boikov
> Priority: Critical
> Fix For: 1.7
>
>
> There are several issues:
> - even if for server nodes queries are local they still send custom discovery messages (probably this should be fixed not only for internal queries)
> - ideally client nodes also should not send discovery messages since queries are always started, so they can be statically configured
> - GridServiceProcessor starts two queries, looks like only one can be used
> - marshaller cache query is started before GridCachePartitionExchangeManager.onKernalStart, this can slowdown exchange process (not an issue is previous items are fixed)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)