[
https://issues.apache.org/jira/browse/NIFI-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eylon Ronen updated NIFI-9034:
------------------------------
Description:
When indexing to elasticsearch you rarely want to send all your data to one
node. One might use a coordinator node but when ingesting a lot of data that
too is not enough. All ES SDKs support the use of multiple nodes and load
balancing between them, but since this processor uses GoHttp client it does
not, which forces users with scale to use a load balancer such as nginx.
The solution would be to allow the user to insert a list of urls (much like in
the kafka processors) and then load balancing between them
Priority: Minor (was: Major)
Remaining Estimate: 1h
Original Estimate: 1h
> Allow multiple urls in PutElasticsearchHttp and round robin between them
> ------------------------------------------------------------------------
>
> Key: NIFI-9034
> URL: https://issues.apache.org/jira/browse/NIFI-9034
> Project: Apache NiFi
> Issue Type: Task
> Reporter: Eylon Ronen
> Priority: Minor
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When indexing to elasticsearch you rarely want to send all your data to one
> node. One might use a coordinator node but when ingesting a lot of data that
> too is not enough. All ES SDKs support the use of multiple nodes and load
> balancing between them, but since this processor uses GoHttp client it does
> not, which forces users with scale to use a load balancer such as nginx.
> The solution would be to allow the user to insert a list of urls (much like
> in the kafka processors) and then load balancing between them
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
