# How to avoid yellow server status when updating without any indexing and querying

**URL:** <https://discuss.elastic.co/t/how-to-avoid-yellow-server-status-when-updating-without-any-indexing-and-querying/9590>\
**Category:** Elasticsearch\
**Created:** [November 7, 2012, 1:26am UTC](https://discuss.elastic.co/t/how-to-avoid-yellow-server-status-when-updating-without-any-indexing-and-querying/9590 "2012-11-07T01:26:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jae](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jae/32/791_2.png) [@Jae](https://discuss.elastic.co/u/Jae)\
**Post date:** [November 7, 2012, 1:26am UTC](https://discuss.elastic.co/t/how-to-avoid-yellow-server-status-when-updating-without-any-indexing-and-querying/9590/1 "2012-11-07T01:26:07Z")

</div>

I've been running elasticsearch cluster for more than 2 months. It was a  
long journey and I finally came to the kafka river, which can make  
elasticseach cluster more resilient because data pulling model is much more  
stable than pushing model. Good thing is, I can totally stop elasticsearch  
indexing without any data loss.

Question is, even though I stopped all indexing by stopping all river  
instances, when I restarted one elasticsearch instance, the server status  
became yellow. So, how can I update elasticsearch cluster without making  
the server status yellow even there's no indexing and querying?

Thank you  
Best, Jae

--

---

<div class="post-metadata">

**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\
**Post date:** [November 7, 2012, 11:43am UTC](https://discuss.elastic.co/t/how-to-avoid-yellow-server-status-when-updating-without-any-indexing-and-querying/9590/2 "2012-11-07T11:43:44Z")

</div>

The yellow state means that at least one of the replicas is not yet  
available. Let's say you have one replica per shard. When you shut down a  
node, you remove all shards on this node from service. It means that  
cluster losses at least some of the replicas and it needs some time to  
rebalance and allocate these lost replicas somewhere else. The process  
takes time and while cluster is doing it, it's state turns yellow. This is  
normal and not something that you should worry about.

On Tuesday, November 6, 2012 8:26:07 PM UTC-5, Jae wrote:

> I've been running elasticsearch cluster for more than 2 months. It was a  
> long journey and I finally came to the kafka river, which can make  
> elasticseach cluster more resilient because data pulling model is much more  
> stable than pushing model. Good thing is, I can totally stop elasticsearch  
> indexing without any data loss.
> 
> Question is, even though I stopped all indexing by stopping all river  
> instances, when I restarted one elasticsearch instance, the server status  
> became yellow. So, how can I update elasticsearch cluster without making  
> the server status yellow even there's no indexing and querying?
> 
> Thank you  
> Best, Jae

--

---

<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 6, 2017, 3:05am UTC](https://discuss.elastic.co/t/how-to-avoid-yellow-server-status-when-updating-without-any-indexing-and-querying/9590/3 "2017-07-06T03:05:45Z")

</div>