[
https://issues.apache.org/jira/browse/NIFI-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-799:
----------------------------
Description: GetTwitter uses the hosebird client, which takes a
BlockingQueue that it can use to put all tweets on. The BlockingQueue currently
has a max capacity of 100,000, but on small heaps that can be problematic by
causing OutOfMemoryError. We need to reduce that considerably, to about 10,000
or maybe even 1,000. (was: GetTwitter uses the hosebird client, which takes a
BlockingQueue that it can use to put all tweets on. The BlockingQueue currently
has a max capacity of 100,000, but on 4 GB of heap that can be problematic by
causing OutOfMemoryError. We need to reduce that considerably, to about 10,000
or maybe even 1,000.)
> GetTwitter allows buffering of too much data
> --------------------------------------------
>
> Key: NIFI-799
> URL: https://issues.apache.org/jira/browse/NIFI-799
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 0.3.0
>
> Attachments:
> 0001-NIFI-831-NIFI-799-Fixed-a-NullPointerException-use-a.patch
>
>
> GetTwitter uses the hosebird client, which takes a BlockingQueue that it can
> use to put all tweets on. The BlockingQueue currently has a max capacity of
> 100,000, but on small heaps that can be problematic by causing
> OutOfMemoryError. We need to reduce that considerably, to about 10,000 or
> maybe even 1,000.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
