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
Ignore 3x segment upgrade if unneeded #11383
Conversation
@s1monw pushed another commit making this encapsulated into the InternalEngine |
@@ -118,7 +119,24 @@ public InternalEngine(EngineConfig engineConfig) throws EngineException { | |||
boolean success = false; | |||
try { | |||
try { | |||
upgrade3xSegments(store); | |||
String version = engineConfig.getIndexSettings().get("index.version.created"); | |||
boolean autoUpgrade = true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you use Version#indexCreated(Settings)
here instead?
left one comment otherwise LGTM |
If the index was created with 0.90.x or later, skip the check for 3x segments, since Lucene 4.x was used for those versions. This helps in particular with sharedfs recoveries, where the check for upgrading segments can cause FS race conditions.
e154495
to
1ed7bfb
Compare
@s1monw Are we saying that v1.6 will not be compatible with indices created before v0.19? |
@s1monw I see. Thanks! It looks like this is going to be a problem only in master, which cannot open these files anyway. It might be a good idea to improve the error message though. I will take a look. |
If the index was created with 0.90.x or later, skip the check for 3x
segments, since Lucene 4.x was used for those versions.
This helps in particular with sharedfs recoveries, where the check for
upgrading segments can cause FS race conditions.
(Note, this is for 1.x only)
Slightly related to #11361