You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/08/06 14:57:00 UTC
[jira] [Commented] (NIFI-7706) When NiFi is restarted, if FlowFile
is queued for a connection that no longer exists, the FlowFile remains but
its data does not
[ https://issues.apache.org/jira/browse/NIFI-7706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172442#comment-17172442 ]
ASF subversion and git services commented on NIFI-7706:
-------------------------------------------------------
Commit eca7f153d0b23d39f14e5c65d1f96c7f663b2bbe in nifi's branch refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=eca7f15 ]
NIFI-7706, NIFI-5702: Allow NiFi to keep FlowFiles if their queue is unknown. This way, if a Flow is inadvertently removed, updated, etc., and NiFi is restarted, the data will not be dropped by default. The old mechanism of dropping data is exposed via a property
This closes #4454.
Signed-off-by: Bryan Bende <bb...@apache.org>
> When NiFi is restarted, if FlowFile is queued for a connection that no longer exists, the FlowFile remains but its data does not
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-7706
> URL: https://issues.apache.org/jira/browse/NIFI-7706
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Blocker
> Fix For: 1.12.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When NiFi is restarted, if there is data in the FlowFile Repository that maps to a given connection, it is placed back into the queue for that connection. If the connection does not exist, it logs a WARNING like the following:
> {quote}
> nifi-app_2020-08-04_12.0.log:2020-08-04 12:18:19,840 WARN [main] o.a.n.c.r.WriteAheadFlowFileRepository Encountered Repository Record (id=137) with Queue identifier ba3261a3-0173-1000-4582-5ee7cffe1e8b but no Queue exists with that ID. Dropping this FlowFile
> {quote}
> The data is not actually dropped - it remains within the NiFi instance and if the flow is restored to have the connection and NiFi is restarted, the FlowFile will be placed back into the queue. However, when the connection does not exist, the Claimant Count is not incremented for the Content Claim. As a result, the data may be reclaimed by the Content Repository. As a result, when the flow is restored and NiFi restarted, the data exists in the queue but its content is gone.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)