[
https://issues.apache.org/jira/browse/NIFI-12322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783315#comment-17783315
]
ASF subversion and git services commented on NIFI-12322:
--------------------------------------------------------
Commit 50fd8c432eaf8cdcd0a6d908ff7800c1bb043261 in nifi's branch
refs/heads/support/nifi-1.x from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=50fd8c432e ]
NIFI-12322 Added resource usage note in ES Client CS documentation
This closes #7986
Signed-off-by: David Handermann <[email protected]>
(cherry picked from commit b24249c8508949c9945de03c52dea84f3f1da2f4)
> 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: 1.latest, 2.latest
>
> 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)
