Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/1962
@pvillard31 Just started reviewing this PR. I'm wondering if the property
should be associated with the cluster section instead of the web properties.
This property is only relevant when clustered and am concerned it may be
confusing being colocated with the jetty thread configuration. Since that
thread pool drives the size of the thread pool that Jetty uses it could be
confused with the maximum number of concurrent requests. It might make sense to
associate this property with other request replication properties.
For instance the replication thread pool size:
```
nifi.cluster.node.protocol.threads=${nifi.cluster.node.protocol.threads}
nifi.cluster.node.protocol.max.threads=${nifi.cluster.node.protocol.max.threads}
```
Or the replication timeouts:
```
nifi.cluster.node.connection.timeout=${nifi.cluster.node.connection.timeout}
nifi.cluster.node.read.timeout=${nifi.cluster.node.read.timeout}
```
Thoughts?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
