-
Notifications
You must be signed in to change notification settings - Fork 1.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
[BUG] all shards failed after node upgrade to 2.11 #11491
Comments
@cwperks @scrawfor99 @peternied folks, this seems to be related to
|
@reta There is a fix for this that was merged, but it didn't make it into 2.11.1. opensearch-project/security#3769 |
Thanks @cwperks , @peternied could we move it to |
@reta this can be closed as a duplicate of: opensearch-project/security#3771 |
Guys, we got the same issue when upgrading from 2.12.0 to 2.17.0 :) |
Thanks @spliakos, please comment on opensearch-project/security#3771, this is not an OpenSearch core issue. |
@spliakos This is known to affect rolling upgrades between 2.12,2.13,2.14 to >2.14. A fix is targeted for 2.18: opensearch-project/security#4741 |
Describe the bug
Starting with the upgrade to 2.11 and 2.11.1 our clusters have issues recovering shards.
There were two cases. One case were the cluster it self did not get green and some shards failed on one node. Even clearing the Data of the Node did not help. Only a full cluster reboot.
In the second case the cluster it self gets green but the other cluster making search request via remote search on the upgraded cluster spams errors with failing shards.
Only doing a full cluster reboot of the upgraded cluster helps to solve this issue.
Following is a trace of the main cluster running OpenSearch 2.10 that does the remote search on the upgraded cluster. The cause is always the same
-84 is not a valid id
. In both cases for all affected indices.To Reproduce
Had no time yet to test it with clean OpenSearch. Will add it later.
In my current setup it always starts once I upgrade a cluster doing node by node reboots.
Expected behavior
I expect node upgrade to work one by one without failing shards.
Plugins
Host/Environment (please complete the following information):
OpenSearch runs within docker using the base OpenSearch image with removed opensearch-performance-analyzer and added s3 plugin.
Additional context
The text was updated successfully, but these errors were encountered: