Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
We've had cases where a user would like to have backpressure on a relationship, and if that threshold is reached then divert new incoming FlowFiles down an alternate (perhaps less computationally intensive) path. In thinking about how to do this, DistributeLoad seems like a possibility. We could potentially allow the addition of a (probably single) relationship with a weight of "0", that is never used unless the strategy is "next available", and all other relationships are unavailable. This would be the "overflow" relationship, providing the desired behavior. This is somewhat related to the "Interactive Queue Management"[1] that is progressing, but comes from a slightly different direction. If anyone has any additional thoughts, pros / cons, etc... please feel free to chime in.
[1] https://cwiki.apache.org/confluence/display/NIFI/Interactive+Queue+Management
Attachments
Issue Links
- duplicates
-
NIFI-7400 Processor to route Flowfile when relationship is unavailable
-
- Resolved
-