# ES seems to be stuck in resyncing mappings

**URL:** <https://discuss.elastic.co/t/es-seems-to-be-stuck-in-resyncing-mappings/4951>\
**Category:** Elasticsearch\
**Created:** [July 26, 2011, 1:41am UTC](https://discuss.elastic.co/t/es-seems-to-be-stuck-in-resyncing-mappings/4951 "2011-07-26T01:41:55Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anurag\_Phadke](https://avatars.discourse-cdn.com/v4/letter/a/5f9b8f/32.png) [@Anurag\_Phadke](https://discuss.elastic.co/u/Anurag_Phadke)\
**Post date:** [July 26, 2011, 1:41am UTC](https://discuss.elastic.co/t/es-seems-to-be-stuck-in-resyncing-mappings/4951/1 "2011-07-26T01:41:55Z")

</div>

We added 3 more nodes to our cluster and increased the replication  
from 0 to 1. The following WARN msgs are coming in the log files:  
11/07/25 18:40:16 WARN cluster.metadata: [Carrion] [socorro\_110703]  
re-syncing mappings with cluster state for types [[crash\_reports]]  
11/07/25 18:40:16 WARN cluster.metadata: [Carrion] [socorro\_110609]  
re-syncing mappings with cluster state for types [[crash\_reports]]  
11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110520]  
re-syncing mappings with cluster state for types [[crash\_reports]]  
11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110704]  
re-syncing mappings with cluster state for types [[crash\_reports]]  
11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110609]  
re-syncing mappings with cluster state for types [[crash\_reports]]  
11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110608]  
re-syncing mappings with cluster state for types [[crash\_reports]]

This has been going for almost an hour now:  
curl -XGET [http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health)  
{"cluster\_name":"socorro","status":"red","timed\_out":false,"number\_of\_nodes":7,"number\_of\_data\_nodes":7,"active\_primary\_shards":457,"active\_shards":457,"relocating\_shards":1,"initializing\_shards":0,"unassigned\_shards":8}

returns red.

curl -XGET '[http://localhost:9200/\_cluster/state?pretty=true&filter\_nodes=true&filter\_indices=true](http://localhost:9200/_cluster/state?pretty=true&filter_nodes=true&filter_indices=true)'  
returns everything in:  
"state" : "STARTED",

any idea what might be going wrong here?

-anurag

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [July 26, 2011, 4:58am UTC](https://discuss.elastic.co/t/es-seems-to-be-stuck-in-resyncing-mappings/4951/2 "2011-07-26T04:58:30Z")

</div>

Are you using the same version across the cluster?

On Tue, Jul 26, 2011 at 4:41 AM, Anurag [anurag.phadke@gmail.com](mailto:anurag.phadke@gmail.com) wrote:

> We added 3 more nodes to our cluster and increased the replication  
> from 0 to 1. The following WARN msgs are coming in the log files:  
> 11/07/25 18:40:16 WARN cluster.metadata: [Carrion] [socorro\_110703]  
> re-syncing mappings with cluster state for types [[crash\_reports]]  
> 11/07/25 18:40:16 WARN cluster.metadata: [Carrion] [socorro\_110609]  
> re-syncing mappings with cluster state for types [[crash\_reports]]  
> 11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110520]  
> re-syncing mappings with cluster state for types [[crash\_reports]]  
> 11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110704]  
> re-syncing mappings with cluster state for types [[crash\_reports]]  
> 11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110609]  
> re-syncing mappings with cluster state for types [[crash\_reports]]  
> 11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110608]  
> re-syncing mappings with cluster state for types [[crash\_reports]]
> 
> This has been going for almost an hour now:  
> curl -XGET [http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health)
> 
> {"cluster\_name":"socorro","status":"red","timed\_out":false,"number\_of\_nodes":7,"number\_of\_data\_nodes":7,"active\_primary\_shards":457,"active\_shards":457,"relocating\_shards":1,"initializing\_shards":0,"unassigned\_shards":8}
> 
> returns red.
> 
> curl -XGET '  
> [http://localhost:9200/\_cluster/state?pretty=true&filter\_nodes=true&filter\_indices=true](http://localhost:9200/_cluster/state?pretty=true&filter_nodes=true&filter_indices=true)  
> '  
> returns everything in:  
> "state" : "STARTED",
> 
> any idea what might be going wrong here?
> 
> -anurag

---

<div class="post-metadata">

**Author:** ![Anurag\_Phadke](https://avatars.discourse-cdn.com/v4/letter/a/5f9b8f/32.png) [@Anurag\_Phadke](https://discuss.elastic.co/u/Anurag_Phadke)\
**Post date:** [July 26, 2011, 1:46pm UTC](https://discuss.elastic.co/t/es-seems-to-be-stuck-in-resyncing-mappings/4951/3 "2011-07-26T13:46:55Z")

</div>

yes - 0.17.1

On Mon, Jul 25, 2011 at 9:58 PM, Shay Banon  
[shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com) wrote:

> Are you using the same version across the cluster?
> 
> On Tue, Jul 26, 2011 at 4:41 AM, Anurag [anurag.phadke@gmail.com](mailto:anurag.phadke@gmail.com) wrote:
> 
> > We added 3 more nodes to our cluster and increased the replication  
> > from 0 to 1. The following WARN msgs are coming in the log files:  
> > 11/07/25 18:40:16 WARN cluster.metadata: [Carrion] [socorro\_110703]  
> > re-syncing mappings with cluster state for types [[crash\_reports]]  
> > 11/07/25 18:40:16 WARN cluster.metadata: [Carrion] [socorro\_110609]  
> > re-syncing mappings with cluster state for types [[crash\_reports]]  
> > 11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110520]  
> > re-syncing mappings with cluster state for types [[crash\_reports]]  
> > 11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110704]  
> > re-syncing mappings with cluster state for types [[crash\_reports]]  
> > 11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110609]  
> > re-syncing mappings with cluster state for types [[crash\_reports]]  
> > 11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110608]  
> > re-syncing mappings with cluster state for types [[crash\_reports]]
> > 
> > This has been going for almost an hour now:  
> > curl -XGET [http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health)
> > 
> > {"cluster\_name":"socorro","status":"red","timed\_out":false,"number\_of\_nodes":7,"number\_of\_data\_nodes":7,"active\_primary\_shards":457,"active\_shards":457,"relocating\_shards":1,"initializing\_shards":0,"unassigned\_shards":8}
> > 
> > returns red.
> > 
> > curl -XGET  
> > '[http://localhost:9200/\_cluster/state?pretty=true&filter\_nodes=true&filter\_indices=true](http://localhost:9200/_cluster/state?pretty=true&filter_nodes=true&filter_indices=true)'  
> > returns everything in:  
> > "state" : "STARTED",
> > 
> > any idea what might be going wrong here?
> > 
> > -anurag

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [July 26, 2011, 2:04pm UTC](https://discuss.elastic.co/t/es-seems-to-be-stuck-in-resyncing-mappings/4951/4 "2011-07-26T14:04:12Z")

</div>

Can you do a GET Mapping on the mentioned index and type and gist it?  
Basically, its a process that goes and tries to resync mappings across  
nodes, and it seems to always think that it needs to resync it...

On Tue, Jul 26, 2011 at 4:46 PM, Anurag [anurag.phadke@gmail.com](mailto:anurag.phadke@gmail.com) wrote:

> yes - 0.17.1
> 
> On Mon, Jul 25, 2011 at 9:58 PM, Shay Banon  
> [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com) wrote:
> 
> > Are you using the same version across the cluster?
> > 
> > On Tue, Jul 26, 2011 at 4:41 AM, Anurag [anurag.phadke@gmail.com](mailto:anurag.phadke@gmail.com) wrote:
> > 
> > > We added 3 more nodes to our cluster and increased the replication  
> > > from 0 to 1. The following WARN msgs are coming in the log files:  
> > > 11/07/25 18:40:16 WARN cluster.metadata: [Carrion] [socorro\_110703]  
> > > re-syncing mappings with cluster state for types [[crash\_reports]]  
> > > 11/07/25 18:40:16 WARN cluster.metadata: [Carrion] [socorro\_110609]  
> > > re-syncing mappings with cluster state for types [[crash\_reports]]  
> > > 11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110520]  
> > > re-syncing mappings with cluster state for types [[crash\_reports]]  
> > > 11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110704]  
> > > re-syncing mappings with cluster state for types [[crash\_reports]]  
> > > 11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110609]  
> > > re-syncing mappings with cluster state for types [[crash\_reports]]  
> > > 11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110608]  
> > > re-syncing mappings with cluster state for types [[crash\_reports]]
> > > 
> > > This has been going for almost an hour now:  
> > > curl -XGET [http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health)
> 
> {"cluster\_name":"socorro","status":"red","timed\_out":false,"number\_of\_nodes":7,"number\_of\_data\_nodes":7,"active\_primary\_shards":457,"active\_shards":457,"relocating\_shards":1,"initializing\_shards":0,"unassigned\_shards":8}
> 
> > > returns red.
> > > 
> > > curl -XGET  
> > > '  
> > > [http://localhost:9200/\_cluster/state?pretty=true&filter\_nodes=true&filter\_indices=true](http://localhost:9200/_cluster/state?pretty=true&filter_nodes=true&filter_indices=true)  
> > > '  
> > > returns everything in:  
> > > "state" : "STARTED",
> > > 
> > > any idea what might be going wrong here?
> > > 
> > > -anurag

---

<div class="post-metadata">

**Author:** ![Anurag\_Phadke](https://avatars.discourse-cdn.com/v4/letter/a/5f9b8f/32.png) [@Anurag\_Phadke](https://discuss.elastic.co/u/Anurag_Phadke)\
**Post date:** [July 26, 2011, 2:21pm UTC](https://discuss.elastic.co/t/es-seems-to-be-stuck-in-resyncing-mappings/4951/5 "2011-07-26T14:21:09Z")

</div>

here u go: [gist:e36e0e0a1140d0adcaa8 · GitHub](https://gist.github.com/e36e0e0a1140d0adcaa8)  
seems to be some issue wrt date field.  
default mapping file (socorro\_mapping.json):  
[gist:8f145b1c60d1f6a47aa3 · GitHub](https://gist.github.com/8f145b1c60d1f6a47aa3)

On Tue, Jul 26, 2011 at 7:04 AM, Shay Banon  
[shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com) wrote:

> Can you do a GET Mapping on the mentioned index and type and gist it?  
> Basically, its a process that goes and tries to resync mappings across  
> nodes, and it seems to always think that it needs to resync it...
> 
> On Tue, Jul 26, 2011 at 4:46 PM, Anurag [anurag.phadke@gmail.com](mailto:anurag.phadke@gmail.com) wrote:
> 
> > yes - 0.17.1
> > 
> > On Mon, Jul 25, 2011 at 9:58 PM, Shay Banon  
> > [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com) wrote:
> > 
> > > Are you using the same version across the cluster?
> > > 
> > > On Tue, Jul 26, 2011 at 4:41 AM, Anurag [anurag.phadke@gmail.com](mailto:anurag.phadke@gmail.com) wrote:
> > > 
> > > > We added 3 more nodes to our cluster and increased the replication  
> > > > from 0 to 1. The following WARN msgs are coming in the log files:  
> > > > 11/07/25 18:40:16 WARN cluster.metadata: [Carrion] [socorro\_110703]  
> > > > re-syncing mappings with cluster state for types [[crash\_reports]]  
> > > > 11/07/25 18:40:16 WARN cluster.metadata: [Carrion] [socorro\_110609]  
> > > > re-syncing mappings with cluster state for types [[crash\_reports]]  
> > > > 11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110520]  
> > > > re-syncing mappings with cluster state for types [[crash\_reports]]  
> > > > 11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110704]  
> > > > re-syncing mappings with cluster state for types [[crash\_reports]]  
> > > > 11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110609]  
> > > > re-syncing mappings with cluster state for types [[crash\_reports]]  
> > > > 11/07/25 18:40:17 WARN cluster.metadata: [Carrion] [socorro\_110608]  
> > > > re-syncing mappings with cluster state for types [[crash\_reports]]
> > > > 
> > > > This has been going for almost an hour now:  
> > > > curl -XGET [http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health)
> > > > 
> > > > {"cluster\_name":"socorro","status":"red","timed\_out":false,"number\_of\_nodes":7,"number\_of\_data\_nodes":7,"active\_primary\_shards":457,"active\_shards":457,"relocating\_shards":1,"initializing\_shards":0,"unassigned\_shards":8}
> > > > 
> > > > returns red.
> > > > 
> > > > curl -XGET
> > > > 
> > > > '[http://localhost:9200/\_cluster/state?pretty=true&filter\_nodes=true&filter\_indices=true](http://localhost:9200/_cluster/state?pretty=true&filter_nodes=true&filter_indices=true)'  
> > > > returns everything in:  
> > > > "state" : "STARTED",
> > > > 
> > > > any idea what might be going wrong here?
> > > > 
> > > > -anurag

---

<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:59am UTC](https://discuss.elastic.co/t/es-seems-to-be-stuck-in-resyncing-mappings/4951/6 "2017-07-06T03:59:19Z")

</div>


