You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Gilman (JIRA)" <ji...@apache.org> on 2017/07/06 18:35:00 UTC

[jira] [Updated] (NIFI-4143) Make configurable maximum number of concurrent requests

     [ https://issues.apache.org/jira/browse/NIFI-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Gilman updated NIFI-4143:
------------------------------
    Labels: documentation  (was: )

> Make configurable maximum number of concurrent requests
> -------------------------------------------------------
>
>                 Key: NIFI-4143
>                 URL: https://issues.apache.org/jira/browse/NIFI-4143
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Pierre Villard
>            Assignee: Pierre Villard
>              Labels: documentation
>
> At the moment, the maximum number of concurrent requests is hard coded in {{ThreadPoolRequestReplicator}}
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-cluster/src/main/java/org/apache/nifi/cluster/coordination/http/replication/ThreadPoolRequestReplicator.java
> The value is equal to 100.
> In some situations where multiple factors are combined (large cluster, S2S to load balance data in the cluster, multiple users accessing the UI), the limit can be reached and the UI may become intermittently unavailable with the message: "There are too many outstanding HTTP requests with a total 100 outstanding requests".
> This value should be configurable in nifi.properties allowing users to increase the value.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)