From f89c8ddf20812f831ebff096dc6c7cb895abb069 Mon Sep 17 00:00:00 2001 From: Priyanka Date: Thu, 17 May 2018 06:18:09 +0000 Subject: Dmaap and Clamp nsPrefix Changes Issue-ID: OOM-1029 Change-Id: I13d44d09bce42250b434d459612c0be6b46239c0 Signed-off-by: Priyanka --- kubernetes/clamp/charts/clamp-dash-es/resources/config/elasticsearch.yml | 1 - 1 file changed, 1 deletion(-) (limited to 'kubernetes/clamp/charts') diff --git a/kubernetes/clamp/charts/clamp-dash-es/resources/config/elasticsearch.yml b/kubernetes/clamp/charts/clamp-dash-es/resources/config/elasticsearch.yml index d631f44f34..ab3ec43eba 100644 --- a/kubernetes/clamp/charts/clamp-dash-es/resources/config/elasticsearch.yml +++ b/kubernetes/clamp/charts/clamp-dash-es/resources/config/elasticsearch.yml @@ -86,7 +86,6 @@ network.host: 0.0.0.0 # By default, Elasticsearch will bind to the available loopback addresses and will scan ports 9300 to 9305 to try # to connect to other nodes running on the same server. # -#discovery.zen.ping.unicast.hosts: ["elasticsearch.{{.Values.nsPrefix}}" #$discovery.zen.ping.unicast.hosts # # This setting tells Elasticsearch to not elect a master unless there are enough master-eligible nodes -- cgit 1.2.3-korg