Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to upgrade Elasticsearch Deployment Template. #78

Open
nickkostov opened this issue Mar 7, 2022 · 2 comments
Open

How to upgrade Elasticsearch Deployment Template. #78

nickkostov opened this issue Mar 7, 2022 · 2 comments

Comments

@nickkostov
Copy link

nickkostov commented Mar 7, 2022

Hello,

I have been trying to upgrade the Elasticsearch version of my search configurations.
Current version is: 6.3.1.
I run this in an EKS cluster.

What I am asking is any tips regarding the upgrade.
When I firstly attempted to upgrade it failed.
I am trying to jump to >= 7.2
Is there a document showing how to update it, because I have started receiving feedback from our back-end developers stating that the application has been down for a whole day.
When I checked the logs find around 12/14 attempts of Fusion to connect to Elasticsearch.
Looking into the Elasticsearch logs shows that
[2022-03-03T05:04:55,070][WARN ][o.e.x.s.a.s.m.NativeRoleMappingStore] [PcFr0Jo] Failed to clear cache for realms [[]]

During the whole day Fusionauth was attempting to restart and connect and Elasticsearch was still trying start I guess.

@nickkostov
Copy link
Author

If possible, can we update the default template inside the examples for search ?

@drpebcak
Copy link
Contributor

drpebcak commented Mar 7, 2022

I would advise following the upgrade procedures outlined by elastic. I believe you need to be on ~6.8 to upgrade to >=7.2. Here is a link to some documentation about it - https://www.elastic.co/guide/en/elasticsearch/reference/7.17/setup-upgrade.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants