# Failover for indexing

**URL:** <https://discuss.elastic.co/t/failover-for-indexing/66624>\
**Category:** Elasticsearch\
**Created:** [November 19, 2016, 2:53pm UTC](https://discuss.elastic.co/t/failover-for-indexing/66624 "2016-11-19T14:53:32Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![limac](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/limac/32/3981_2.png) [@limac](https://discuss.elastic.co/u/limac)\
**Post date:** [November 19, 2016, 2:53pm UTC](https://discuss.elastic.co/t/failover-for-indexing/66624/1 "2016-11-19T14:53:32Z")

</div>

is there amy way to keeping indexing when one node down?

---

<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:** [November 19, 2016, 2:56pm UTC](https://discuss.elastic.co/t/failover-for-indexing/66624/2 "2016-11-19T14:56:54Z")

</div>

How many nodes do you have in the cluster?

---

<div class="post-metadata">

**Author:** ![limac](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/limac/32/3981_2.png) [@limac](https://discuss.elastic.co/u/limac)\
**Post date:** [November 19, 2016, 3:38pm UTC](https://discuss.elastic.co/t/failover-for-indexing/66624/3 "2016-11-19T15:38:47Z")

</div>

9 nodes. The indexing stops when some the node rejoin the cluster.

Wang Yong | Fusionskye

---

<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:** [November 20, 2016, 5:50am UTC](https://discuss.elastic.co/t/failover-for-indexing/66624/4 "2016-11-20T05:50:11Z")

</div>

If you have at least 3 master eligible nodes and have minimum\_master\_nodes correctly set, Elasticsearch should elect a new master in case a node goes down, which should allow indexing to continue.

Which version of Elasticsearch are you on? How much data do you have in the cluster? How many indices/shards do you have? What is the hardware specification of the hosts?

---

<div class="post-metadata">

**Author:** ![limac](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/limac/32/3981_2.png) [@limac](https://discuss.elastic.co/u/limac)\
**Post date:** [November 20, 2016, 11:51am UTC](https://discuss.elastic.co/t/failover-for-indexing/66624/5 "2016-11-20T11:51:39Z")

</div>

Hi, Christian, if one node is down, the search and indexing will survive cause we set number of replica\>0.  
What I mean is when the dead node is restarted and rejoins the cluster, all shards will be reassigned and re synced. And during this period, the cluster will not index any more document.

---

<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:** [November 20, 2016, 4:05pm UTC](https://discuss.elastic.co/t/failover-for-indexing/66624/6 "2016-11-20T16:05:23Z")

</div>

How many replicas do you have configured?

---

<div class="post-metadata">

**Author:** ![limac](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/limac/32/3981_2.png) [@limac](https://discuss.elastic.co/u/limac)\
**Post date:** [November 20, 2016, 10:39pm UTC](https://discuss.elastic.co/t/failover-for-indexing/66624/7 "2016-11-20T22:39:56Z")

</div>

10P+1R, this is a heavy indexing case that average 40k documents/a.

---

<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:** [November 21, 2016, 6:07am UTC](https://discuss.elastic.co/t/failover-for-indexing/66624/8 "2016-11-21T06:07:02Z")

</div>

How long is your cluster in a red state when a node is restarted and joins the cluster? Which version of Elasticsearch are you using? How much data do you have in the cluster? How many indices/shards do you have?

---

<div class="post-metadata">

**Author:** ![limac](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/limac/32/3981_2.png) [@limac](https://discuss.elastic.co/u/limac)\
**Post date:** [November 21, 2016, 2:05pm UTC](https://discuss.elastic.co/t/failover-for-indexing/66624/9 "2016-11-21T14:05:41Z")

</div>

Sometimes the cluster will remain in red for about 30minutes. So we have to wait a long time for the status transited from yellow to green. The index request rate is 0 before it comes to green.

We have pretty big indices, about 20 indices, 500G each.  
The cluster has 9 nodes, 10P+1R, and the version is 1.7.

---

<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:** [December 19, 2016, 2:05pm UTC](https://discuss.elastic.co/t/failover-for-indexing/66624/10 "2016-12-19T14:05:50Z")

</div>

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