as the document states, you should take the first option and update to 2.4.x in the first place and reindex the existing indices. After this you can do the switch to 5.5.
If you insist on using the single jump update with the reindex-from-remote, you have to install the elasticsearch 5.5.0 release with custom port/cluster/data.path settings on the same machine and run them side by side. But be prepared for issues, as this will require lots of memory.
Thanks Comradin, I tried upgrading to 2.4 (then will move to 5.5 ).
And I am using Elasticsearch Migration Plugin for re-indexing.
Issue I am facing with existing indices:
curl -XGET 'localhost:9200/_cat/indices?v&pretty'
health status index pri rep docs.count docs.deleted store.size pri.store.size
yellow open .kibana 5 1 9 0 41.3kb 41.3kb
yellow open logstash-2017.07.20 5 1 2148 0 634.5kb 634.5kb
yellow open .reindex-status 1 1 0 0 159b 159b
It is show health for all indices as yellow and plugin will not work until it moves to green.
What it the reason for yellow status of indices.
Can you please help in this how can I re-index my existing indexes.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.