Apache
/
nifi
mirror of https://github.com/apache/nifi.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

NIFI-12322 Added resource usage note in ES Client CS documentation 

This closes #7986

Signed-off-by: David Handermann <exceptionfactory@apache.org>
This commit is contained in:
Pierre Villard 2023-11-06 18:22:50 +01:00 committed by exceptionfactory
parent f650c2078a
commit b24249c850
No known key found for this signature in database
GPG Key ID: 29B6A52D2AAE8DBA
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-client-service/src/main/resources/docs/org.apache.nifi.elasticsearch.ElasticSearchClientServiceImpl/additionalDetails.html
View File

@ -50,5 +50,15 @@
Elasticsearch sniffing best practices: What, when, why, how</a> for more details of the best practices.
</p>
<h2>Resources Usage Consideration</h2>
<p>
This Elasticsearch client relies on a <code>RestClient</code> using the Apache HTTP Async Client. By default, it will start one
dispatcher thread, and a number of worker threads used by the connection manager. There will be as many worker thread as the number
of locally detected processors/cores on the NiFi host. Consequently, it is highly recommended to have only one instance of this
controller service per remote Elasticsearch destination and have this controller service shared across all of the Elasticsearch
processors of the NiFi flows. Having a very high number of instances could lead to resource starvation and result in OOM errors.
</p>
</body>
</html>