u/Rosie871

Hi all,
We're planning ES upgrade from 8.19 -> 9.4, and we have some 7.x indices, that needs to be reindexed before moving them. What options are there for reindex in a way not to block application read and writes? We have big indices, for example, I tested on one index 1000GB, it took 9 hours to reindex, and I don't know if there is a good way to apply all updates and deleted on that index that happened within that 9h interval after the reindex.

Hi all,

We encountered some issues when upgrading Kibana from 8.11-8.19 and then 8.19-9.4, but the issue was resolved itself, now we don't know what was the cause, and I wanted to make sure to learn what is the problem before upgrading production env.
The issue is this:
We have kibana runnind under the host:5601, but we also have server.publicBaseUrl configured in the kibana.yml, which is under nginx service.
Now I'm not sure if the issue is nginx, but after we upgrade the Kibana, the page opens, asks for authentication , and after successfully passing it gets stuck, first time it was just showing loading, this time we got page with this message: Elastic did not load properly

Please reload this page. If the issue persists, check the browser console and server logs.

We tried to reload nginx , and check all logs, no info, and the most bizarre is that it was fixed by itself after a few hours. Now we don't wanna have inaccessible Kibana for a few hours for prod, so I wanted to know if anyone had similar issue, how you fixed it ?

Hi all. I have one question, I wanted to know if you encountered such situation.
We're planning Elastic Upgrade from 8.19 -> 9.4. In upgrade assistent I see this deprecation, that the index .kibana-event-log-7.13.0-000009 is deprecated as created <8 version. I have searched some places, as it's a system index I can't manually reindex it, but the elastic won'r start presumably if I leave it like that and upgarde to 9+ version.
Have you seen this, what have you done?

Hi all.
I have a question from your experience. I'm planning to do ElasticSearch upgrade from 8.11 to 8.19 and then 8.19 to 9.4. The cluster consists of 50 nodes, so I'm planning to do it in multiple days, but I'm concerned whether there can be issues during that time, when the nodes have different versions, as I know it can be an issue during relocation. Have you encountered such issue, or do you have better ideas about the upgrade plan?
I will do the whole cluster to 8.19 first then to 9.4 afterwards.