We are attempting to upgrade our Elasticsearch cluster from V. 1.7.0 to V. 5.3 and when reindexing via the reindex-from-remote procedure are getting the following error:
{
"error": {
"root_cause": [
{
"type": "status_exception",
"reason": "body={"error":"ElasticsearchIllegalArgumentException[Failed to decode scrollId]; nested: IOException[Bad Base64 input character decimal 123 in array position 0]; ","status":400}"
}
],
"type": "status_exception",
"reason": "body={"error":"ElasticsearchIllegalArgumentException[Failed to decode scrollId]; nested: IOException[Bad Base64 input character decimal 123 in array position 0]; ","status":400}",
"caused_by": {
"type": "response_exception",
"reason": "POST http://[source-url]:9200/_search/scroll?scroll=5m: HTTP/1.1 400 Bad Request\n{"error":"ElasticsearchIllegalArgumentException[Failed to decode scrollId]; nested: IOException[Bad Base64 input character decimal 123 in array position 0]; ","status":400}"
}
},
"status": 400
}
The API request that resulted in the above error:
POST _reindex
{
"source": {
"remote": {
"host": "http://[source-url]:9200"
},
"index": "[source-index]"
},
"dest": {
"index": "[destination-index]"
}
}
The same API call made to V. 5.2.2 to the same source server works with no issues. When this is called from 5.3 to a 5.2.2 source previously migrated from the 1.7.0 source it also succeeds. Based on other posts with similar exceptions returned from the source API that reference "scrollId" this appears to possibly be using a feature that was not yet implemented in ES 1.7 but as I mentioned, this Is there a workaround for this or is this a regression that will be fixed in a patch? The production indexes that need to be migrated are quite large and will take quite a bit of time so I really am trying to avoid 1.7.0 -> 5.2.2 -> 5.3.
Sorry about the duplicate. Has that patch been released? I see it has been merged into your master branch.