-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
Delete operation on primary don't do version handling correctly, on 5.3 & 5.x #23069
Comments
areek
added a commit
to areek/elasticsearch
that referenced
this issue
Feb 9, 2017
As @bleskes pointed out in elastic#23069 there were inconsistencies in version handling on 5.x and 5.3 from master due to backport of elastic#21964. This change ensures versions are handled uniformly and fixes minor issues in shard bulk action to be similar to master fixes elastic#23069
@areek I think this is closed by your PR? unless we want to keep it open until we have unit tests? |
Fixed by #23083 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I believe this has happened during the back port of #21964 and only relates to the yet to be released 5.3.0
Here's the logic of the delete operation (it's the same both on master and 5.x):
Notice how it doesn't do any version conversion for replicas.
On master, this is done in
TransportShardBulkAction#executeBulkItemRequest
:5.x doesn't have that logic in the same method, but rather relies on handling in the execute*OnPrimary method. Here is the relevant code from the index variant:
We need to go through the backport again and make 5.x do what master does.
PS. This is yet another proof unit tests are badly needed for this. @dakrone has already started working on it.
PPS. Areek is working on making this entire thing less messy.
The text was updated successfully, but these errors were encountered: