-
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] [Segment Replication] Segment replication is broken for plugins using custom codecs #7781
Comments
This error is also manifested when using an older lucene codec implementation during index creation. One such example (verified on OS 2.7.0)
|
Created backports to |
After this fix backported, verified this bug is not present during OS upgrades from 2.7.1 -> 2.8.0 for kNN plugin |
Closing this issue as the bug is fixed and backports PRs have been merged to 2.7 branch and will be released in 2.7.1 Verified with fix on 2.7 branch
Documentation change will be tracked in opensearch-project/documentation-website#4194 To prevent such future occurrence, taken up below action items.
|
What is the bug?
Segment replicaion event fails for plugins using custom codecs (e.g. kNN). The bug prevents replica shard from allocation resulting in forever unassigned replica.
Background
During peer recovery, for segment replication enabled indices a force segment sync is performed to keep the shard upto date from primary. Recently, we added a fix where to prevent segment replication events b/w primary and replica when they are using a different codec implementations. The fix had a bug where replica shard's default codec was used rather than the one on the engine config.
How can one reproduce the bug?
Steps to reproduce the behavior:
Replica shards remain unassigned and will remain forever because all shard replica allocation tries goes through same code flow.
This bug is also manifested when an older lucene codec is used during index creation
What is the expected behavior?
Replica shards should be assigned for all type of plugins
What is your host/environment?
The text was updated successfully, but these errors were encountered: