Warning on ELK version change and volume data index mismatch between Lucene and volume #105
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update readme for elasticsearch volume warning during version change in .env ELK_VERSION
(Thanks for sending a pull request! Please make sure you click the link above to view the contribution guidelines, then fill out the blanks below.)
What does this implement/fix? Explain your changes.
Spent too much time experimenting, I've realised that errors caused by ELK version change. When user runs ELK, volume for elastic becomes already created with 8.8.0. Then when you try to switch <8.6.0, required Lucene version for indexing becomes different.
Does this close any currently open issues?
No
Any relevant logs, error output, etc?
java.lang.IllegalArgumentException: Could not load codec 'Lucene95'. Did you forget to add lucene-backward-codecs.jar?
Any other comments?
It's not confusing, however volume attached to docker is not on local, so it took time for me to realise that. I'm newbie to ELK, so I didn't know Lucene, indexing, elastic stores in docker volume not on local etc.
Where has this been tested?
Ubuntu 20.04, on a typical Amazon EC2 server