# Kibana Instance Connections

**URL:** <https://discuss.elastic.co/t/kibana-instance-connections/134306>\
**Category:** Kibana\
**Created:** [June 3, 2018, 9:16am UTC](https://discuss.elastic.co/t/kibana-instance-connections/134306 "2018-06-03T09:16:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidv](https://avatars.discourse-cdn.com/v4/letter/d/4af34b/32.png) [@davidv](https://discuss.elastic.co/u/davidv)\
**Post date:** [June 3, 2018, 9:16am UTC](https://discuss.elastic.co/t/kibana-instance-connections/134306/1 "2018-06-03T09:16:37Z")

</div>

Hi there,

~This might be related to Elasticsearch discussion forum also.  
I'm encountering some performance issues with my EK.  
I have ES and Kibana 6.2.3 installed both on the same physical machine (250RAM, 88 Cores). This is not production and basically, I'm the only one who uses it. I did ingest data.  
Of course, jvm is configured as recommended. The EK does bearly utilize the machine's resources.

I noticed few things that might be related:

1. Kibana single instance has more than 100K connections. please confirm this is normal (On Kibana restart - the connections reset back to 0 and then constantly growing).  

2. I have 571 unassigned\_shards - all because of UNASSIGNED CLUSTER\_RECOVERED.

3. Elasticsearch cluster status is yellow - Allocate missing replica shards (Could this effect the performance?).

Should I separate ES and Kibana to run on different VMs? Is it the unassigned\_shards?

Thanks for the assistant,  
David

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 3, 2018, 9:44am UTC](https://discuss.elastic.co/t/kibana-instance-connections/134306/2 "2018-06-03T09:44:45Z")

</div>

> [@davidv](#):
>
> Elasticsearch cluster status is yellow - Allocate missing replica shards (Could this affect the performance?).

Nope. You only have 1 node so you cannot allocate the replicas. You _could_ setup multiple nodes on a box that size, use docker for eg.

---

<div class="post-metadata">

**Author:** ![davidv](https://avatars.discourse-cdn.com/v4/letter/d/4af34b/32.png) [@davidv](https://discuss.elastic.co/u/davidv)\
**Post date:** [June 3, 2018, 10:47am UTC](https://discuss.elastic.co/t/kibana-instance-connections/134306/3 "2018-06-03T10:47:14Z")

</div>

> [@warkolm](#):
>
> Nope. You only have 1 node so you cannot allocate the replicas. You _could_ setup multiple nodes on a box that size, use docker for eg.

Hi Mark,

Thanks for the quick reply. Do you have more information regarding the other points I mentioned? (bullets 1/2)

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 4, 2018, 2:19am UTC](https://discuss.elastic.co/t/kibana-instance-connections/134306/4 "2018-06-04T02:19:04Z")

</div>

2 is probably related to 3. I don't know about 1 sorry.

---

<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:** [July 2, 2018, 2:19am UTC](https://discuss.elastic.co/t/kibana-instance-connections/134306/5 "2018-07-02T02:19:10Z")

</div>

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