You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by "Dan Smith (JIRA)" <ji...@apache.org> on 2017/03/13 21:42:41 UTC
[jira] [Commented] (GEODE-2651) Function service should provide
built-in mechanism for streaming back large function results
[ https://issues.apache.org/jira/browse/GEODE-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922998#comment-15922998 ]
Dan Smith commented on GEODE-2651:
----------------------------------
Geode does support streaming results using ResultSender.addResult within the function and using a custom result collector when executing a function.
However, geode does provide any sort of back pressure for this stream, so it's possible that streaming back a large amount of data could still result in running out of memory.
> Function service should provide built-in mechanism for streaming back large function results
> --------------------------------------------------------------------------------------------
>
> Key: GEODE-2651
> URL: https://issues.apache.org/jira/browse/GEODE-2651
> Project: Geode
> Issue Type: Improvement
> Components: functions
> Reporter: Jared Stewart
>
> It would be convenient to have a built-in mechanism for streaming back large function results that does not require keeping all results in memory on either end of the function execution. Example use cases:
> - Executing a function to gather all logs on server (this may produce a very large zip file)
> - Executing netstat -lsof currently runs out of memory in CI
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)