Apache
/
nifi
mirror of https://github.com/apache/nifi.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

NIFI-7583 Document that Prioritizers do not fully sort a queue when swapping (#9263) 

Signed-off-by: David Handermann <exceptionfactory@apache.org>
This commit is contained in:
Eric Secules 2024-09-14 13:03:25 -07:00 committed by GitHub
parent 00c7a78119
commit 80b3cde95c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
nifi-docs/src/main/asciidoc/administration-guide.adoc
View File

@ -3112,6 +3112,9 @@ available again. These properties govern how that process occurs.
|`nifi.swap.manager.implementation`| The Swap Manager implementation. The default value is `org.apache.nifi.controller.FileSystemSwapManager`.
|`nifi.queue.swap.threshold`|The queue threshold at which NiFi starts to swap FlowFile information to disk. The default value is `20000`.
|====
NOTE: When a queue begins swapping to disk, NiFi does not guarantee that all the FlowFiles in the queue are sorted in the
order specified by the <<user-guide.adoc#_prioritization,prioritizers>> configured on the queue. New FlowFiles arriving at the queue are written to
the swap file without considering prioritizers. They are prioritized when the swap file is read back into memory.
=== Content Repository

4
nifi-docs/src/main/asciidoc/user-guide.adoc
View File

@ -1444,6 +1444,10 @@ processing order is not further specified but an implementation detail that migh
NOTE: With a <<load_balance_strategy>> configured, the connection has a queue per node in addition to the local queue. The prioritizer will sort the data in each queue independently.
NOTE: When a connection has more FlowFiles than the `nifi.queue.swap.threshold`, new FlowFiles arriving at that connection
are not prioritized against the active queue, instead they are sent directly to swap. They will be prioritized when they
get brought back into memory.
==== Changing Configuration and Context Menu Options
After a connection has been drawn between two components, the connection's configuration may be changed, and the connection may be moved to a new destination; however, the processors on either side of the connection must be stopped before a configuration or destination change may be made.