[
https://issues.apache.org/jira/browse/NIFI-2731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531636#comment-15531636
]
ASF GitHub Bot commented on NIFI-2731:
--------------------------------------
Github user mosermw commented on the issue:
https://github.com/apache/nifi/pull/1071
Yes @joewitt you've alleviated my concerns about the default for Max Bins.
I forgot that default values get serialized to the flow.xml when a new
processor is dropped on the graph. Thanks.
I was on board with setting a default for Max Entries and not leaving that
unbounded. It certainly can cause trouble otherwise, and new users won't know
why.
> MergeContent default max number of flow files and max number of bins should
> be smaller
> --------------------------------------------------------------------------------------
>
> Key: NIFI-2731
> URL: https://issues.apache.org/jira/browse/NIFI-2731
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Joseph Witt
> Assignee: Pierre Villard
> Fix For: 1.1.0
>
>
> Presently there is no default on max entries. It should probably be set to
> 1000 by default. These are flow files and their objects are read into memory
> and can add up quickly. Further, if we have 100 default max bins we could
> end up with 100s of thousands of flow file objects held in memory during
> common dataflow scenarios. Recommend moving to max 5 different bins by
> default and max 1000 flow files by default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
