# Performance issues on shared Kubernetes cluster

**URL:** https://discuss.elastic.co/t/performance-issues-on-shared-kubernetes-cluster/262846
**Category:** Elasticsearch
**Created:** [February 1, 2021, 2:26pm UTC](https://discuss.elastic.co/t/performance-issues-on-shared-kubernetes-cluster/262846 "2021-02-01T14:26:10Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Konrad\_Moskal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/konrad_moskal/32/70377_2.png) [@Konrad\_Moskal](https://discuss.elastic.co/u/Konrad_Moskal)
#### Post date: [February 1, 2021, 2:26pm UTC](https://discuss.elastic.co/t/performance-issues-on-shared-kubernetes-cluster/262846/1 "2021-02-01T14:26:10Z")

</div>

Hey! I have an issue with performance on a shared K8s cluster. When there is no load on the cluster, performance is great but for reason when activity increases my ES performance declines a lot.

I have 20 indices, ~ 1GB of data, two nodes. 1000m CPU and 2Gi memory. Deployed with Elastic helm chart.

Health:

```auto
        {
        "cluster_name" : "elasticsearch",
        "status" : "green",
        "timed_out" : false,
        "number_of_nodes" : 2,
        "number_of_data_nodes" : 2,
        "active_primary_shards" : 90,
        "active_shards" : 180,
        "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
        }

```

I am not sure how to properly debug why the performance is declining. Could it be networking bottleneck? The K8s cluster when under load is using \< 10% CPU and \< 30% memory, although requested is ~ 90% and 70%.

Tips on debugging performance? Thanks a lot.

---

<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: [February 1, 2021, 11:10pm UTC](https://discuss.elastic.co/t/performance-issues-on-shared-kubernetes-cluster/262846/2 "2021-02-01T23:10:05Z")

</div>

What version are you running? Do you have Monitoring enabled?

---

<div class="post-metadata">

### Author: ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [February 2, 2021, 6:57am UTC](https://discuss.elastic.co/t/performance-issues-on-shared-kubernetes-cluster/262846/3 "2021-02-02T06:57:23Z")

</div>

> [@Konrad\_Moskal](#):
>
> `"number_of_nodes" : 2,`

Be aware that [the smallest highly available cluster size is 3 nodes](https://www.elastic.co/guide/en/elasticsearch/reference/7.10/high-availability-cluster-small-clusters.html).

> [@Konrad\_Moskal](#):
>
> I have 20 indices, ~ 1GB of data, two nodes. 1000m CPU and 2Gi memory. Deployed with Elastic helm chart.

If the pod has 2GB memory assigned, have you set the Elasticsearch heap size to 1GB (50% of total available RAM for Elasticsearch)?

> [@Konrad\_Moskal](#):
>
> The K8s cluster when under load is using \< 10% CPU and \< 30% memory, although requested is ~ 90% and 70%.

This is not the only parameters that affect performance. The performance of your storage is often the limiting factor. What type of storage are you using for these nodes?

---

<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: [March 2, 2021, 6:58am UTC](https://discuss.elastic.co/t/performance-issues-on-shared-kubernetes-cluster/262846/4 "2021-03-02T06:58:17Z")

</div>

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