-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
5.6.10 to 6.3.0 rolling upgrade broken with 'commit doesn't contain history uuid' when a synced flush is performed #31482
Comments
Pinging @elastic/es-distributed |
This bug can happen in the following scenario.
|
@praseodym Thanks for reporting this bug. We are working on the fix. |
…6.3 (#31506) Today we make sure that a 5.x index commit should have all required commit tags in RecoveryTarget#cleanFiles method. The reason we do this in RecoveryTarget#cleanFiles method because this is only needed in a file-based recovery and we assume that #cleanFiles should be called in a file-based recovery. However, this assumption is not valid if the index is sealed (.i.e synced-flush). This incorrect assumption would prevent users from rolling upgrade from 5.x to 6.3 if their index were sealed. Closes #31482
…6.3 (#31506) Today we make sure that a 5.x index commit should have all required commit tags in RecoveryTarget#cleanFiles method. The reason we do this in RecoveryTarget#cleanFiles method because this is only needed in a file-based recovery and we assume that #cleanFiles should be called in a file-based recovery. However, this assumption is not valid if the index is sealed (.i.e synced-flush). This incorrect assumption would prevent users from rolling upgrade from 5.x to 6.3 if their index were sealed. Closes #31482
This is fixed by #31506. This fix be will included in 6.3.1. |
Thank you! Considering that this is a blocker for upgrades, when will 6.3.1 be released? |
That's still unknown at this point. Obviously this is a serious issue. Working on it. |
Is removing the replica shard an option after upgrading? Or would that not work and upgrade to 6.3.1 is the only option? |
@gmoskovicz a direct rolling upgrade to 6.3 from 5.x just won't work. You can do a rolling upgrade to a 6.x version before 6.3 and then to 6.3. You can also push to 6.3 using a full cluster restart and then reduce the number of replicas and bring it back up (forcing the data to be cleaned). PLEASE try this first - I think it should work but it should be clear by now this is tricky - many moving parts. |
A cleaner workaround would be force flush the offending index, then retry the cluster allocation.
|
Rolling upgrades of an Elasticsearch 5.6.10 cluster to version 6.3.0 fail with a
java.lang.IllegalStateException: commit doesn't contain history uuid
when a synced flush (_flush/synced
) is performed, as described in the rolling upgrade documentation.Steps to reproduce:
I cannot reproduce the problem without performing the synced flush. I think this problem could have been introduced in #28245.
Reproduction script, takes about a minute to reproduce the issue
Log including stack traces from the upgraded node
The text was updated successfully, but these errors were encountered: