We experimented with the idea of a custom "Global Prioritizer". One of the problems with this approach is that it ran the risk of breaking the multi-tenancy philosophy. If there were a truly global priority, it would affect all flows, each may have different priority rules. However, if this could be applied only at the process group level, it might have legs.
You can follow the initial approach to such a mechanism in the JIRA ticket. https://issues.apache.org/jira/browse/NIFI-6831 On Tue, Apr 12, 2022 at 12:06 PM Ryan Hendrickson < [email protected]> wrote: > I just went to the config button in my process group, hoping to set all > relationships in there to priority first.... Lots of right clicking & > dragging instead. > > +1 for an approach like that. > > On Tue, Apr 12, 2022 at 11:44 AM Joe Witt <[email protected]> wrote: > > > Hello > > > > Certainly the spirit of this is a good idea. Would likely need to > approach > > it at a more flow/process group centric level. > > > > Thanks > > > > On Tue, Apr 12, 2022 at 8:34 AM Ryan Hendrickson < > > [email protected]> wrote: > > > > > This would be very helpful. > > > > > > Ryan > > > > > > On Fri, Feb 19, 2021 at 4:51 PM Salvatore Foss < > [email protected]> > > > wrote: > > > > > > > Hi, > > > > > > > > Do you see much value in being able to specify an instance-wide (or > > > > cluster-wide) default prioritizer for all connections that do not > have > > > one > > > > manually set? > > > > > > > > Along with the the following properties in nifi.properties: > > > > nifi.queue.backpressure.count=10000 > > > > nifi.queue.backpressure.size=1 GB > > > > > > > > I'd like to see see something like > > > > nifi.queue.prioritizer.default=org.apache.nifi.prioritize. > > > > PriorityAttributePrioritizer > > > > > > > > Thoughts? My only concern would be if connection prioritizers have a > > > > noticeable impact on system resources. > > > > > > > > > >
