Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
Description
In a recent ticket we exposed a property for choosing the maximum capacity of the internal queue used to transfer messages from the threading reading from the channel to the processor.
Currently there is really no way to know if the queue is filling up and the size should be increased. We do an indefinite blocking put() when adding to the queue, but it would be nice if we tried with some amount of timeout and then logged an error so the user was aware that data was being dropped.
Attachments
Issue Links
- is part of
-
NIFI-899 ListenUDP attempts to transfer a FlowFile that is no longer part of the session
- Resolved