[
https://issues.apache.org/jira/browse/NIFI-12322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-12322:
------------------------------------
Fix Version/s: 2.0.0
1.24.0
(was: 1.latest)
(was: 2.latest)
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Add resource usage documentation for ElasticSearchClientServiceImpl
> -------------------------------------------------------------------
>
> Key: NIFI-12322
> URL: https://issues.apache.org/jira/browse/NIFI-12322
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
> Fix For: 2.0.0, 1.24.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We observed a significant resource usage when using many ES controller
> service instances. After investigation, it appears that the ES client relies
> on a RestClient where the Apache Http Async Client starts by default one
> dispatcher thread, and a number of worker threads used by the connection
> manager, as many as the number of locally detected processors (depending on
> what Runtime.getRuntime().availableProcessors() returns).
> I think it'd be worth adding this in the documentation and the proper
> annotation where relevant.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
