Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NIFI-12322 - add resource usage note in ES Client CS documentation details #7986

Closed
wants to merge 1 commit into from
Closed

NIFI-12322 - add resource usage note in ES Client CS documentation details #7986

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 10 additions & 0 deletions .../docs/org.apache.nifi.elasticsearch.ElasticSearchClientServiceImpl/additionalDetails.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,5 +50,15 @@ <h2>Sniffing</h2>
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>