[
https://issues.apache.org/jira/browse/NIFI-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003812#comment-16003812
]
Olav Jordens commented on NIFI-1603:
------------------------------------
This is an important issue for flows that have large numbers of very small and
large numbers of very large files. If the small files remain enqueued for a
while, they may prevent large claims being garbage collected. This has caused
storage disks to fill up to 100% with content that is no longer required. Back
pressure is one way to handle it, but not always satisfactory for complex
flows. If it is decided that these two nifi.content properties are to be
removed, it would be useful to have a way to force one flowfile per claim.
> Remove deprecated content repo properties
> -----------------------------------------
>
> Key: NIFI-1603
> URL: https://issues.apache.org/jira/browse/NIFI-1603
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Configuration, Core Framework
> Affects Versions: 0.5.1
> Reporter: Aldrin Piri
> Priority: Trivial
>
> Both nifi.content.claim.max.appendable.size &
> nifi.content.claim.max.flow.files no longer appear to be used with defaults
> specified for the associated properties in FileSystemRepository's
> maxAppendClaimLength and the configured writableClaimQueue length.
> These should either be removed from both the codebase and documentation or
> configured to use the associated properties and have their documentation
> updated to reflect current configuration defaults.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
