Elasticsearch version: 1.7.6 and 5.4
Plugins installed: None
JVM version: 1.8.0_111, 1.8.0_131
OS version: Ubuntu 16.04
Description of the problem including expected versus actual behavior:
We are migrating from a 1.7.6 cluster to 5.4 using the reindex from remote in 5.4. I'm getting a weird ElasticsearchParseException error on the response after executing the request to reindex.
Here is my _reindex command I ran on my 5.4 cluster:
POST - http://search02:9200/_reindex
{
"source": {
"remote": {
"host": "http://search01:9200"
},
"index": "labor"
},
"dest": {
"index": "labor"
}
}
Here is the response I got:
{
"error": {
"root_cause": [
{
"type": "status_exception",
"reason": "body={\"error\":\"ElasticsearchParseException[Failed to parse [300000000000nanos]]; nested: NumberFormatException[For input string: \\\"300000000000nano\\\"]; \",\"status\":400}"
}
],
"type": "status_exception",
"reason": "body={\"error\":\"ElasticsearchParseException[Failed to parse [300000000000nanos]]; nested: NumberFormatException[For input string: \\\"300000000000nano\\\"]; \",\"status\":400}",
"caused_by": {
"type": "response_exception",
"reason": "POST http://search01:9200/_search/scroll?scroll=300000000000nanos: HTTP/1.1 400 Bad Request\n{\"error\":\"ElasticsearchParseException[Failed to parse [300000000000nanos]]; nested: NumberFormatException[For input string: \\\"300000000000nano\\\"]; \",\"status\":400}"
}
},
"status": 400
}
I can execute a request with a "size" parameter in place and it works, but only the first 200 records.
{
"size": 200,
"source": {
"remote": {
"host": "http://search01:9200"
},
"index": "labor",
"size": 2000,
"sort": { "_id": "desc" }
},
"dest": {
"index": "labor"
}
}
If that size parameter goes up to 300 I get the same error as before but with a different scroll number:
{
"error": {
"root_cause": [
{
"type": "status_exception",
"reason": "body={\"error\":\"ElasticsearchParseException[Failed to parse [2620000083934nanos]]; nested: NumberFormatException[For input string: \\\"2620000083934nano\\\"]; \",\"status\":400}"
}
],
"type": "status_exception",
"reason": "body={\"error\":\"ElasticsearchParseException[Failed to parse [2620000083934nanos]]; nested: NumberFormatException[For input string: \\\"2620000083934nano\\\"]; \",\"status\":400}",
"caused_by": {
"type": "response_exception",
"reason": "POST http://search01:9200/_search/scroll?scroll=2620000083934nanos: HTTP/1.1 400 Bad Request\n{\"error\":\"ElasticsearchParseException[Failed to parse [2620000083934nanos]]; nested: NumberFormatException[For input string: \\\"2620000083934nano\\\"]; \",\"status\":400}"
}
},
"status": 400
}
I've played around with ?requests_per_second but that didn't seem to make any difference. I am seriously stumped... any ideas what I'm doing wrong?
Thanks
Elasticsearch version: 1.7.6 and 5.4
Plugins installed: None
JVM version: 1.8.0_111, 1.8.0_131
OS version: Ubuntu 16.04
Description of the problem including expected versus actual behavior:
We are migrating from a 1.7.6 cluster to 5.4 using the reindex from remote in 5.4. I'm getting a weird ElasticsearchParseException error on the response after executing the request to reindex.
Here is my _reindex command I ran on my 5.4 cluster:
Here is the response I got:
I can execute a request with a "size" parameter in place and it works, but only the first 200 records.
If that size parameter goes up to 300 I get the same error as before but with a different scroll number:
I've played around with ?requests_per_second but that didn't seem to make any difference. I am seriously stumped... any ideas what I'm doing wrong?
Thanks