# Restart replication on elasticsearch 2.3.3 without restart

**URL:** <https://discuss.elastic.co/t/restart-replication-on-elasticsearch-2-3-3-without-restart/96455>\
**Category:** Elasticsearch\
**Created:** [August 9, 2017, 2:34pm UTC](https://discuss.elastic.co/t/restart-replication-on-elasticsearch-2-3-3-without-restart/96455 "2017-08-09T14:34:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![zozo6015](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zozo6015/32/12117_2.png) [@zozo6015](https://discuss.elastic.co/u/zozo6015)\
**Post date:** [August 9, 2017, 2:34pm UTC](https://discuss.elastic.co/t/restart-replication-on-elasticsearch-2-3-3-without-restart/96455/1 "2017-08-09T14:34:18Z")

</div>

Hello I have an elasticsearch cluster 2.3.3 and the cluster stopped replicating because one of the nodes had the disk amost full. After I have solved the full disk issue the replication does not restart by itself. Is there a way to restart the replication without restarting the cluster? This is very important since it's handling production data.

Regards,  
peter

---

<div class="post-metadata">

**Author:** ![zozo6015](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zozo6015/32/12117_2.png) [@zozo6015](https://discuss.elastic.co/u/zozo6015)\
**Post date:** [August 9, 2017, 4:25pm UTC](https://discuss.elastic.co/t/restart-replication-on-elasticsearch-2-3-3-without-restart/96455/2 "2017-08-09T16:25:02Z")

</div>

I have removed the nodes which had disk issues and added some new nodes, but the cluster is not replicating to the new nodes.

```
curl localhost:19266/_cat/shards
kibana.rets.ci 3 p STARTED 0 160b 10.0.0.6 api.rets.ci-client-cluster-2 
kibana.rets.ci 3 r UNASSIGNED                                                        
kibana.rets.ci 4 p STARTED 2 803.3kb 10.0.0.6 api.rets.ci-client-cluster-2 
kibana.rets.ci 4 r UNASSIGNED                                                        
kibana.rets.ci 2 p STARTED 0 160b 10.0.0.6 api.rets.ci-client-cluster-2 
kibana.rets.ci 2 r UNASSIGNED                                                        
kibana.rets.ci 1 p STARTED 1 16.3kb 10.0.0.6 api.rets.ci-client-cluster-2 
kibana.rets.ci 1 r UNASSIGNED                                                        
kibana.rets.ci 0 p STARTED 0 160b 10.0.0.6 api.rets.ci-client-cluster-2 
kibana.rets.ci 0 r UNASSIGNED                  

```

as you can see the cluster has three nodes:

```
curl localhost:19266/_cat/nodes
10.0.0.11 10.0.0.11 2 76 0.33 d m api.rets.ci-client-cluster-4 
10.0.0.8 10.0.0.8 7 96 0.21 d m api.rets.ci-client-cluster-5 
10.0.0.6 10.0.0.6 46 93 0.28 d * api.rets.ci-client-cluster-2            

```

Any way I can force the cluster to replicate on the 2 new nodes?

---

<div class="post-metadata">

**Author:** ![zozo6015](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zozo6015/32/12117_2.png) [@zozo6015](https://discuss.elastic.co/u/zozo6015)\
**Post date:** [August 9, 2017, 4:55pm UTC](https://discuss.elastic.co/t/restart-replication-on-elasticsearch-2-3-3-without-restart/96455/3 "2017-08-09T16:55:27Z")

</div>

I found out that the reason for which the new nodes were not replicating was the different version of elasticsearch

---

<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:** [September 6, 2017, 4:55pm UTC](https://discuss.elastic.co/t/restart-replication-on-elasticsearch-2-3-3-without-restart/96455/4 "2017-09-06T16:55:34Z")

</div>

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