You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mike Thomsen (JIRA)" <ji...@apache.org> on 2019/02/22 10:45:02 UTC
[jira] [Commented] (NIFI-6070) Elasticsearch HTTP processors should
use Low-level Java REST client
[ https://issues.apache.org/jira/browse/NIFI-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775001#comment-16775001 ]
Mike Thomsen commented on NIFI-6070:
------------------------------------
There is a new ElasticSearch bundle that does this. It is the "REST API" bundle. It is a work in progress and where we will be using the official client going forward.
> Elasticsearch HTTP processors should use Low-level Java REST client
> -------------------------------------------------------------------
>
> Key: NIFI-6070
> URL: https://issues.apache.org/jira/browse/NIFI-6070
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.9.0
> Reporter: Aaron Leon
> Priority: Major
>
> The Elasticsearch HTTPÂ processors should use Java REST client... Either high-level (which would tie the processor to specific versions of Elasticsearch in the same way the transport client processors are, e.g. PutElasticsearch5) or the low-level, which from my understanding does not depend on a specific version of ES. The reasoning is that the current Elasticsearch HTTP processors simply use OkHTTP to hit the REST API, but this does not include critical features to a production setup such as:
> * load balancing across all available nodes
> * failover in case of node failures and upon specific response codes
> * failed connection penalization (whether a failed node is retried depends on how many consecutive times it failed; the more failed attempts the longer the client will wait before trying that same node again)
> * persistent connections
> * trace logging of requests and responses
> * optional automatic [discovery of cluster nodes|https://www.elastic.co/guide/en/elasticsearch/client/java-rest/current/sniffer.html]
> (source: [https://www.elastic.co/guide/en/elasticsearch/client/java-rest/current/java-rest-low.html)]
> The current PutElasticsearchHTTP processor also sends timed out requests to 'failure' queue as opposed to 'retry' which is not the correct behavior.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)