[
https://issues.apache.org/jira/browse/NIFI-15913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18078764#comment-18078764
]
ASF subversion and git services commented on NIFI-15913:
--------------------------------------------------------
Commit 1cabec6b5e55ef4ba782ecb66a3d51e55dcdb753 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1cabec6b5e5 ]
NIFI-15913 Fixed Repository Record creation for S2S and Load-Balanced
Connections (#11215)
- Add system test reproducing premature content claim truncation after node
offload
- Fixed bug in which we create RepositoryRecords with the incorrect 'type' when
receiving data via site-to-site or load-balanced connections; also addressed
the same issue in cases where we have a Stateless Process Group with an
OutputPort that clones to multiple destinations.
Signed-off-by: David Handermann <[email protected]>
> If a node is offloaded or load balanced, receiving node may prematurely
> truncate the data
> -----------------------------------------------------------------------------------------
>
> Key: NIFI-15913
> URL: https://issues.apache.org/jira/browse/NIFI-15913
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> If data is offloaded or load balanced, and nifi is configured to truncate
> content claims and truncation is active (archive is disabled or content repo
> is nearly full and all archive files have been removed), the receiving node
> may truncate the data prematurely.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
