![]() ![]() Might our data be structured in a certain way as to make it only compatible in 6.x?Īre there newer libraries that the devs should be using to help this? To first test an upgrade I created an identical version 6.8 ES cluster, loaded it with the sample data that AWS handily provides in Kibana, then I upgraded it to 7.4 and I could still access the data (in Kibana).Īre there any special things I can do to further test after an upgrade to see what the issue might be? Special curl commands? ![]() I roll the cluster back to 6.8, restore the data from a snapshot (because when I roll back the data is then gone), and all works fine again. I initially tried upgrading to 7.10 and that did the same. ![]() If I upgrade it to 7.4 it looks like there is still data there according to the AWS ElasticSearch dashboard, but after the upgrade the search does not work and behind the scenes the developer is getting the errors I will put at the end of this post. So we have a site that uses ElasticSearch (in AWS) to look up names for our site. (Please bear in mind that I am new to ElasticSearch and I am not a web programmer) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |