You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Gura (JIRA)" <ji...@apache.org> on 2015/04/30 20:22:06 UTC
[jira] [Updated] (IGNITE-848) Excessive memory and CPU consumption
by TTL manager
[ https://issues.apache.org/jira/browse/IGNITE-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrey Gura updated IGNITE-848:
-------------------------------
Description:
There is an excessive memory and CPU consuming on data nodes in case of expiration policy configured for cache and continuous data streaming performs.
Some observation:
1. Heap fills up very quickly and eventually leads to OOM.
2. Inconsistent query results on the {{QueryWords}} example (with out expiration policy there are consistent).
3. There is suspicious CPU activity when streaming node stopped.
> Excessive memory and CPU consumption by TTL manager
> ---------------------------------------------------
>
> Key: IGNITE-848
> URL: https://issues.apache.org/jira/browse/IGNITE-848
> Project: Ignite
> Issue Type: Bug
> Affects Versions: sprint-4
> Reporter: Andrey Gura
> Assignee: Andrey Gura
> Priority: Blocker
> Fix For: sprint-4
>
>
> There is an excessive memory and CPU consuming on data nodes in case of expiration policy configured for cache and continuous data streaming performs.
> Some observation:
> 1. Heap fills up very quickly and eventually leads to OOM.
> 2. Inconsistent query results on the {{QueryWords}} example (with out expiration policy there are consistent).
> 3. There is suspicious CPU activity when streaming node stopped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)