[
https://issues.apache.org/jira/browse/METRON-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15340781#comment-15340781
]
David M. Lyle commented on METRON-236:
--------------------------------------
Turns out this is supported using optionalSettings in ElasticsearchWriter.
> Expose client.transport.sniff in ElasticsearchWriter
> ----------------------------------------------------
>
> Key: METRON-236
> URL: https://issues.apache.org/jira/browse/METRON-236
> Project: Metron
> Issue Type: Improvement
> Reporter: David M. Lyle
>
> Per
> https://www.elastic.co/guide/en/elasticsearch/client/java-api/current/transport-client.html:
> "The Transport client comes with a cluster sniffing feature which allows it
> to dynamically add new hosts and remove old ones. When sniffing is enabled
> the transport client will connect to the nodes in its internal node list,
> which is built via calls to addTransportAddress. After this, the client will
> call the internal cluster state API on those nodes to discover available data
> nodes. The internal node list of the client will be replaced with those data
> nodes only. This list is refreshed every five seconds by default. Note that
> the IP addresses the sniffer connects to are the ones declared as the publish
> address in those node’s elasticsearch config."
> Exposing this option will allow better support of production environments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
