[
https://issues.apache.org/jira/browse/NIFI-10823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Hendrickson updated NIFI-10823:
------------------------------------
Description:
I assigned this to Mark so he'd take notice since we were chatting about this
on the Apache NiFi Slack Channel:
[https://apachenifi.slack.com/archives/C0L9VCD47/p1668546036757219]
We have been setting the following two nifi.properties for quite some time...
* nifi.queue.backpressure.count=20000
* nifi.queue.swap.threshold=20000
Today we updated the dataflow on with a NiFi that can have a huge amount of
FlowFiles queue up if backpressure isn't set correctly. We realized that the
new relationships drawn on the canvas did not inherit the
nifi.queue.backpressure.count set in nifi.properties. (Discussion on Slack)
Hunting back, it looks like NIFI-8195 in NiFi 1.14.0 attempted to Migrate
backpressure settings from nifi.properties to the Process Groups in the UI.
# It looks like in the Pull Request, it was intended to read the
nifi.properties file value and set that to the root process group value.
## [https://github.com/apache/nifi/pull/5192,]
## "verified the default values of the added elements are “0 sec” for FlowFile
Expiration, and obtained from nifi.properties for back pressure settings" and
## "The backpressure defaults from nifi.properties should only be used when at
the root level"
## Still in the code:
[https://github.com/apache/nifi/blob/main/nifi-commons/nifi-properties/src/main/java/org/apache/nifi/util/NiFiProperties.java#L90]
# The Migration Guidance from 1.14.0 doesn't say anything about the
nifi.properties `nifi.queue.backpressure.count` no longer being used.
[https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance]
# The core properties still have it listed:
[https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#core-properties]
Version: Apache NiFi 1.16.3 Stanealone and Cluster
*We observed that when the nifi.properties value is set, the UI sets the value
to 0 (unlimited), and every process group underneath there.*
was:
I assigned this to Mark so he'd take notice since we were chatting about this
on the Apache NiFi Slack Channel:
[https://apachenifi.slack.com/archives/C0L9VCD47/p1668546036757219]
We have been setting the following two nifi.properties for quite some time...
* nifi.queue.backpressure.count=20000
* nifi.queue.swap.threshold=20000
Today we updated the dataflow on with a NiFi that can have a huge amount of
FlowFiles queue up if backpressure isn't set correctly. We realized that the
new relationships drawn on the canvas did not inherit the
nifi.queue.backpressure.count set in nifi.properties. (Discussion on Slack)
Hunting back, it looks like NIFI-8195 in NiFi 1.14.0 attempted to Migrate
backpressure settings from nifi.properties to the Process Groups in the UI.
# It looks like in the Pull Request, it was intended to read the
nifi.properties file value and set that to the root process group value.
## [https://github.com/apache/nifi/pull/5192,]
## "verified the default values of the added elements are “0 sec” for FlowFile
Expiration, and obtained from nifi.properties for back pressure settings" and
## "The backpressure defaults from nifi.properties should only be used when at
the root level"
## Still in the code:
https://github.com/apache/nifi/blob/main/nifi-commons/nifi-properties/src/main/java/org/apache/nifi/util/NiFiProperties.java#L90
# The Migration Guidance from 1.14.0 doesn't say anything about the
nifi.properties `nifi.queue.backpressure.count` no longer being used.
[https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance]
# The core properties still have it listed:
[https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#core-properties]
Version: Apache NiFi 1.16.3 Stanealone and Cluster
> Backpressure Queue - Properties file vs. Canvas update, Properties file not
> respected.
> --------------------------------------------------------------------------------------
>
> Key: NIFI-10823
> URL: https://issues.apache.org/jira/browse/NIFI-10823
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.14.0, 1.15.0, 1.16.0, 1.16.3
> Reporter: Ryan Hendrickson
> Assignee: Mark Payne
> Priority: Major
>
> I assigned this to Mark so he'd take notice since we were chatting about this
> on the Apache NiFi Slack Channel:
> [https://apachenifi.slack.com/archives/C0L9VCD47/p1668546036757219]
> We have been setting the following two nifi.properties for quite some time...
> * nifi.queue.backpressure.count=20000
> * nifi.queue.swap.threshold=20000
> Today we updated the dataflow on with a NiFi that can have a huge amount of
> FlowFiles queue up if backpressure isn't set correctly. We realized that the
> new relationships drawn on the canvas did not inherit the
> nifi.queue.backpressure.count set in nifi.properties. (Discussion on Slack)
> Hunting back, it looks like NIFI-8195 in NiFi 1.14.0 attempted to Migrate
> backpressure settings from nifi.properties to the Process Groups in the UI.
>
> # It looks like in the Pull Request, it was intended to read the
> nifi.properties file value and set that to the root process group value.
> ## [https://github.com/apache/nifi/pull/5192,]
> ## "verified the default values of the added elements are “0 sec” for
> FlowFile Expiration, and obtained from nifi.properties for back pressure
> settings" and
> ## "The backpressure defaults from nifi.properties should only be used when
> at the root level"
> ## Still in the code:
> [https://github.com/apache/nifi/blob/main/nifi-commons/nifi-properties/src/main/java/org/apache/nifi/util/NiFiProperties.java#L90]
> # The Migration Guidance from 1.14.0 doesn't say anything about the
> nifi.properties `nifi.queue.backpressure.count` no longer being used.
> [https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance]
> # The core properties still have it listed:
> [https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#core-properties]
>
>
> Version: Apache NiFi 1.16.3 Stanealone and Cluster
> *We observed that when the nifi.properties value is set, the UI sets the
> value to 0 (unlimited), and every process group underneath there.*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
