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
CI: BulkIT.testBulkUpdate_largerVolume fails one of its GetRequests #13379
Comments
I think this is a bug in |
whoa!!! good catch we need a get and commit stress test... that reproduces this problem in isolation |
When we commit the translog, documents that were in it before cannot be retrieved from it anymore via get and have to be retrieved from the index instead. But they will only be visible if between index and get a refresh is called. Therfore we have to call first refresh and then translog.commit() because otherwise there is a small gap in which we cannot read from the translog anymore but also not from the index. closes elastic#13379
When we commit the translog, documents that were in it before cannot be retrieved from it anymore via get and have to be retrieved from the index instead. But they will only be visible if between index and get a refresh is called. Therfore we have to call first refresh and then translog.commit() because otherwise there is a small gap in which we cannot read from the translog anymore but also not from the index. closes #13379
When we commit the translog, documents that were in it before cannot be retrieved from it anymore via get and have to be retrieved from the index instead. But they will only be visible if between index and get a refresh is called. Therfore we have to call first refresh and then translog.commit() because otherwise there is a small gap in which we cannot read from the translog anymore but also not from the index. closes #13379
http://build-us-00.elastic.co/job/es_core_2x_strong/28/
The issue is reproducible most of the time running this seed (on osx), further parameters having no influence already removed:
When not running in
local
mode, this does not occur, also addingwaitForRelocations
makes it vanish, but I am not sure, if this is the underlying issue here.The text was updated successfully, but these errors were encountered: