# Elasticsearch in RKE in running status but not active

**URL:** https://discuss.elastic.co/t/elasticsearch-in-rke-in-running-status-but-not-active/335655
**Category:** Elasticsearch
**Created:** [June 9, 2023, 7:58pm UTC](https://discuss.elastic.co/t/elasticsearch-in-rke-in-running-status-but-not-active/335655 "2023-06-09T19:58:09Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)
#### Post date: [June 9, 2023, 11:24pm UTC](https://discuss.elastic.co/t/elasticsearch-in-rke-in-running-status-but-not-active/335655/9 "2023-06-09T23:24:48Z")

</div>

> [@Mhvrke](#):
>
> In order to give more space do I need to stop logstash and Kibana?

You should stop both Logstash and Kibana, and start them after the cluster is up again.

> [@Mhvrke](#):
>
> Also while I give more space do I need to escalate to 0 my elasticsearch pods I mean restart elasticsearch?

Not sure, I do not use Elasticsearch on k8s, so I do not know what will happen if you scale it to 0. You just need to stop the pods, increase the space and start them again.

> [@Mhvrke](#):
>
> What I read about Elasticsearch running in rke with 3 workers nodes and one persistent volume is the following

No idea if this is correct, as I only use Elastic on traditional VMs and I do not know how this shared persistent volume works, but you need to make sure that you won't hit the watermarks, since the underlying storage is shared, all your cluster will probably hit the watermark as the same time, and this can be problematic.

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-in-rke-in-running-status-but-not-active/335655)._