[
https://issues.apache.org/jira/browse/FLUME-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749077#comment-13749077
]
Hari Shreedharan commented on FLUME-2177:
-----------------------------------------
We can add a configuration to make sure that users are not suddenly shocked by
the sudden surge in memory usage. Also, replay does not cause the cache to be
rebuilt (this will take replay to take too long). Only new events will be
cached, this allows takes to be faster. I am not sure if this will help in any
real way (since we need to go to disk anyway)
> File Channel caching
> --------------------
>
> Key: FLUME-2177
> URL: https://issues.apache.org/jira/browse/FLUME-2177
> Project: Flume
> Issue Type: Bug
> Reporter: Hari Shreedharan
>
> We could cache the events in memory even though it is pushed. We can add some
> additional metadata into the FEQ to decide where in memory we are holding the
> events.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
