You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/03/27 06:01:00 UTC
[jira] [Commented] (KYLIN-3913) Remove getAllOutputs api in
ExecutableManager to avoid OOM for large metadata
[ https://issues.apache.org/jira/browse/KYLIN-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802478#comment-16802478 ]
ASF GitHub Bot commented on KYLIN-3913:
---------------------------------------
lshmouse commented on pull request #557: KYLIN-3913: Remove getAllOutputs api in ExecutableManager to avoid OOM for large metadata
URL: https://github.com/apache/kylin/pull/557
See: https://issues.apache.org/jira/browse/KYLIN-3913
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> Remove getAllOutputs api in ExecutableManager to avoid OOM for large metadata
> -----------------------------------------------------------------------------
>
> Key: KYLIN-3913
> URL: https://issues.apache.org/jira/browse/KYLIN-3913
> Project: Kylin
> Issue Type: Improvement
> Reporter: Liu Shaohui
> Priority: Major
>
> In a big cluster, there will be many job info left in the metadata. The kylin server will be OOM when search the jobs with a long time range. The reason is that ExecutableManager will load all job output info into memory when search a job.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)