[
https://issues.apache.org/jira/browse/NIFI-13796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884101#comment-17884101
]
ASF subversion and git services commented on NIFI-13796:
--------------------------------------------------------
Commit 457d83ef84e683a59a8502dd33daed34be1485e4 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=457d83ef84 ]
NIFI-13796: When writing to a content claim and its size + offset exceeds the
max appendable size, do not write to that content claim again
This closes #9306.
Signed-off-by: Joseph Witt <[email protected]>
> Improve efficiency of FlowFile content slab allocation
> ------------------------------------------------------
>
> Key: NIFI-13796
> URL: https://issues.apache.org/jira/browse/NIFI-13796
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 2.0.0-M5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When we write to the content repository, we write until the we hit the
> configurable max appendable claim size. Then we move on to another resource
> claim in the content repository. However, this only happens inter-session, as
> the session holds open an OutputStream to a Content Claim for efficiency
> purposes.
> This, however, has the downside of being less efficient in terms of splitting
> FlowFile across content claims. As a result, we can write significantly far
> beyond the 50 KB max when writing many FlowFiles in a session (think
> UnpackContent, Split*, etc.)
> We can improve this by checking the size of the content claim + offset when
> we finish writing to a content claim and only adding back to our active claim
> queue if that size is less than the max appendable size. This should improve
> NiFi's ability to cleanup content more aggressively.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
