[
https://issues.apache.org/jira/browse/NIFI-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15484018#comment-15484018
]
ASF GitHub Bot commented on NIFI-2754:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/1000
@patricker @mcgilman looking at the PR, I do think that this will resolve
the specific use case that you're running into, Peter. I think, though, that it
is addressing a very specific corner case and could actually be solved a little
more generally, though. Instead of changing the number of swap files based on
the specific condition of `activeQueue.size() == 0 && numSwapFiles > 0 &&
swapQueue.size() % SWAP_RECORD_POLL_SIZE == 0` what do you think of just
calling `migrateSwapToActive()` at the beginning of the
`writeSwapFilesIfNecessary()`? This should also ensure that we keep with the
same ordering guarantees that we have provided throughout the rest of the class.
> FlowFiles Queue into Swap Only
> ------------------------------
>
> Key: NIFI-2754
> URL: https://issues.apache.org/jira/browse/NIFI-2754
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Peter Wicks
>
> If the Active queue is empty and the number of FlowFiles added to the queue
> is perfectly splitable by the current Swap size (100000 Flow Files / 20000
> files per swap file = 5 with no remainder), then no FlowFiles will move to
> Active and all will remain in Swap.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
