# Content type errors when reindexing

**URL:** <https://discuss.elastic.co/t/content-type-errors-when-reindexing/187835>\
**Category:** Elasticsearch\
**Created:** [June 27, 2019, 1:11pm UTC](https://discuss.elastic.co/t/content-type-errors-when-reindexing/187835 "2019-06-27T13:11:24Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamesp220291](https://avatars.discourse-cdn.com/v4/letter/j/91b2a8/32.png) [@jamesp220291](https://discuss.elastic.co/u/jamesp220291)\
**Post date:** [June 27, 2019, 1:11pm UTC](https://discuss.elastic.co/t/content-type-errors-when-reindexing/187835/1 "2019-06-27T13:11:25Z")

</div>

Hi

I am trying to reindex from a remote host

I am running this command -

curl -X POST "[http://localhost:9200/\_reindex](http://localhost:9200/_reindex)" -H 'Content-Type: application/json' -d'  
{  
"source": {  
"remote": {  
"host": "[http://remoteip:9200](http://remoteip:9200)"  
},  
"index": "mylogs-2019.06.17" \<---- Remote cluster index  
},  
"dest": {  
"index": "mylogs-2019.06.17" \<---- Local Index  
}  
}'  
{"error":{"root\_cause":[{"type":"x\_content\_parse\_exception","reason":"[7:18] [reindex] failed to parse field [source]"}],"type":"x\_content\_parse\_exception","reason":"[7:18] [reindex] failed to parse field [source]","caused\_by":{"type":"json\_parse\_exception","reason":"Unexpected character ('\<' (code 60)): was expecting comma to separate Object entries\n at [Source: org.elasticsearch.transport.netty4.ByteBufStreamInput@58cd6dfa; line: 7, column: 49]"}},"status":400}

Can anyone advise how to fix this? Ive tried content type text/plain but apparently this is not supported.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [June 27, 2019, 2:01pm UTC](https://discuss.elastic.co/t/content-type-errors-when-reindexing/187835/2 "2019-06-27T14:01:24Z")

</div>

Remove `<---- Remote cluster index` and the other one.

---

<div class="post-metadata">

**Author:** ![jamesp220291](https://avatars.discourse-cdn.com/v4/letter/j/91b2a8/32.png) [@jamesp220291](https://discuss.elastic.co/u/jamesp220291)\
**Post date:** [June 27, 2019, 2:32pm UTC](https://discuss.elastic.co/t/content-type-errors-when-reindexing/187835/3 "2019-06-27T14:32:36Z")

</div>

well, thats embarrassing.

Thank you for noticing that.

---

<div class="post-metadata">

**Author:** ![jamesp220291](https://avatars.discourse-cdn.com/v4/letter/j/91b2a8/32.png) [@jamesp220291](https://discuss.elastic.co/u/jamesp220291)\
**Post date:** [June 27, 2019, 4:14pm UTC](https://discuss.elastic.co/t/content-type-errors-when-reindexing/187835/4 "2019-06-27T16:14:36Z")

</div>

I have another question re reindexing.

If I am reindexing from a single node ELK stack to a Multi-node Elastic search cluster.

Which node on the elastic search cluster do I do this from?, One of the dedicated master nodes, or one of the dedicated data nodes?

Obviously I want the data I am reindexing to be spread out across the cluster, and not just dumped onto one of the nodes, is this a concern, or will elasticsearch just do this naturally?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [June 27, 2019, 5:08pm UTC](https://discuss.elastic.co/t/content-type-errors-when-reindexing/187835/5 "2019-06-27T17:08:06Z")

</div>

It will do it naturally unless you have only one shard.

---

<div class="post-metadata">

**Author:** ![jamesp220291](https://avatars.discourse-cdn.com/v4/letter/j/91b2a8/32.png) [@jamesp220291](https://discuss.elastic.co/u/jamesp220291)\
**Post date:** [June 27, 2019, 5:32pm UTC](https://discuss.elastic.co/t/content-type-errors-when-reindexing/187835/6 "2019-06-27T17:32:32Z")

</div>

OK Thanks.

So it doesnt matter which node I run the command on? Would it be best to do this on a dedicated master, or dedicated data?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [June 27, 2019, 9:57pm UTC](https://discuss.elastic.co/t/content-type-errors-when-reindexing/187835/7 "2019-06-27T21:57:20Z")

</div>

It's better to run it on a node which is not overloaded.

---

<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 25, 2019, 9:57pm UTC](https://discuss.elastic.co/t/content-type-errors-when-reindexing/187835/8 "2019-07-25T21:57:33Z")

</div>

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