[jira] [Updated] (IGNITE-4037) High memory consumption when executing TeraSort Hadoop example

["Vladimir Ozerov (JIRA)" <ji...@apache.org>]

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

Vladimir Ozerov updated IGNITE-4037:
------------------------------------
    Fix Version/s:     (was: 1.9)
                   2.0

> High memory consumption when executing TeraSort Hadoop example
> --------------------------------------------------------------
>
>                 Key: IGNITE-4037
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4037
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 1.6
>            Reporter: Ivan Veselovsky
>            Assignee: Ivan Veselovsky
>             Fix For: 2.0
>
>
> When executing TeraSort Hadoop example, we observe high memory consumption that frequently leads to cluster malfunction.
> The problem can be reproduced in unit test, even with 1 node, and with not huge input data set as 100Mb. 
> Dump analysis shows that  memory is taken in various queues: 
> org.apache.ignite.internal.processors.hadoop.taskexecutor.HadoopExecutorService#queue 
> and 
> task queue of org.apache.ignite.internal.processors.hadoop.jobtracker.HadoopJobTracker#evtProcSvc  .
> Since objects stored in these queues hold byte arrays of significant size, memory if consumed very fast.
> It looks like real cause of the problem is that some tasks are blocked.



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