You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "David M. Lyle (JIRA)" <ji...@apache.org> on 2016/06/17 11:24:05 UTC

[jira] [Created] (METRON-236) Expose client.transport.sniff in ElasticsearchWriter

David M. Lyle created METRON-236:
------------------------------------

             Summary: 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)