GHES upgrading from 3.7.19 to 3.8.17, it took long time on the Elasticsearch indices upgrade

[wanglanfei]

Select Topic Area

Bug

Body

during the upgrade process , elasticsearch-upgrade.service is in activating (start) and Elasticsearch indices upgrade is still not completed after 1h 1min

● elasticsearch-upgrade.service - ElasticSearch indices upgrade
Loaded: loaded (/lib/systemd/system/elasticsearch-upgrade.service; static; ve
Active: activating (start) since Fri 2025-02-21 02:05:22 UTC; 1h 1min ago
Main PID: 24292 (ghe-es-upgrade)
Tasks: 23 (limit: 4915)
Memory: 27.4M
CGroup: /system.slice/elasticsearch-upgrade.service
├─24292 /bin/bash /usr/local/share/enterprise/ghe-es-upgrade
├─24294 /bin/bash /usr/local/bin/github-env bin/rake --trace es:enter
└─24363 docker exec -i github-env-64bdc494-bf29-db78-e473-fe961338ca7

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[wanglanfei]

when i restarted the vm .
elasticsearch-upgrade.service is inactive.
systemctl status elasticsearch-upgrade.service
● elasticsearch-upgrade.service - ElasticSearch indices upgrade
Loaded: loaded (/lib/systemd/system/elasticsearch-upgrade.service; static; ve
Active: inactive (dead)

and checking the upgrade status :

elasticsearch-upgrade.service is not active, but Elasticsearch indices upgrade is not completed yet.
You could run 'systemctl --no-block start elasticsearch-upgrade.service' on MySQL primary node to restart the service.
For further assistance, please contact GitHub Enterprise Support team.
Elasticsearch indices:
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open discussions-6 hVL4xjocddSdPjhe7LNY2Q 1 0 0 0 162b 162b
green open registry-packages-4 7j8RhLfVfeGSPH48Hk0uyA 1 0 0 0 192b 192b

Is that means the upgrading is in process?

[wanglanfei]

the upgrading is completed , but it is took more than four hours.
Elasticsearch indices upgrade is completed
All background upgrade jobs are completed

[wanglanfei]

i will close this discussion . thanks.

[wanglanfei]

the upgrading is completed , but it is took more than four hours.
Elasticsearch indices upgrade is completed
All background upgrade jobs are completed