# Intermittent response from master in Kubernetes

**URL:** <https://discuss.elastic.co/t/intermittent-response-from-master-in-kubernetes/165492>\
**Category:** Elasticsearch\
**Created:** [January 23, 2019, 10:22pm UTC](https://discuss.elastic.co/t/intermittent-response-from-master-in-kubernetes/165492 "2019-01-23T22:22:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bladerunner512](https://avatars.discourse-cdn.com/v4/letter/b/b77776/32.png) [@bladerunner512](https://discuss.elastic.co/u/bladerunner512)\
**Post date:** [January 23, 2019, 10:22pm UTC](https://discuss.elastic.co/t/intermittent-response-from-master-in-kubernetes/165492/1 "2019-01-23T22:22:03Z")

</div>

Elasticsearch v6.2.1 on Ubuntu 16.04  
Getting "connection refused" intermittently - no problems can be seen in log files. Reduced to running a single master, but got the same issue:  
NAME READY STATUS RESTARTS AGE  
es-data-9768f6585-82j64 1/1 Running 0 2h  
es-data-9768f6585-p4x9k 1/1 Running 0 2h  
es-data-9768f6585-sh24n 1/1 Running 0 2h  
es-ingest-64799798fd-msm2g 1/1 Running 0 2h  
es-master-75bff957-djrj4 1/1 Running 0 2h  
es-master-75bff957-pm2q5 1/1 Running 0 2h  
es-master-75bff957-qv2qp 1/1 Running 0 2h

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE  
elasticsearch ClusterIP 10.244.159.27 9200/TCP 7d  
elasticsearch-discovery ClusterIP 10.244.85.54 9300/TCP 7d

elasticsearch@es-master-75bff957-djrj4:/root$ curl [http://10.244.159.27:9200/\_cluster/health?pretty](http://10.244.159.27:9200/_cluster/health?pretty)  
curl: (7) Failed to connect to 10.244.159.27 port 9200: Connection refused

elasticsearch@es-master-75bff957-djrj4:/root$ curl [http://10.244.159.27:9200/\_cluster/health?pretty](http://10.244.159.27:9200/_cluster/health?pretty)  
{  
"cluster\_name" : "es-cluster",  
"status" : "green",  
"timed\_out" : false,  
"number\_of\_nodes" : 7,  
"number\_of\_data\_nodes" : 3,  
"active\_primary\_shards" : 0,  
"active\_shards" : 0,  
"relocating\_shards" : 0,  
"initializing\_shards" : 0,  
"unassigned\_shards" : 0,  
"delayed\_unassigned\_shards" : 0,  
"number\_of\_pending\_tasks" : 0,  
"number\_of\_in\_flight\_fetch" : 0,  
"task\_max\_waiting\_in\_queue\_millis" : 0,  
"active\_shards\_percent\_as\_number" : 100.0  
}

elasticsearch@es-master-75bff957-djrj4:/root$ curl [http://10.244.159.27:9200/\_cluster/health?pretty](http://10.244.159.27:9200/_cluster/health?pretty)  
curl: (7) Failed to connect to 10.244.159.27 port 9200: Connection refused

---

<div class="post-metadata">

**Author:** ![bladerunner512](https://avatars.discourse-cdn.com/v4/letter/b/b77776/32.png) [@bladerunner512](https://discuss.elastic.co/u/bladerunner512)\
**Post date:** [January 24, 2019, 10:03pm UTC](https://discuss.elastic.co/t/intermittent-response-from-master-in-kubernetes/165492/2 "2019-01-24T22:03:59Z")

</div>

Resolved by setting DATA nodes as HTTP\_ENABLED - only INGEST node had flag set but service pointed to DATA nodes too.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 21, 2019, 10:04pm UTC](https://discuss.elastic.co/t/intermittent-response-from-master-in-kubernetes/165492/3 "2019-02-21T22:04:05Z")

</div>

Closed on February 21, 2019, 10:04pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.