Skip to content

Conversation

@iverase
Copy link
Contributor

@iverase iverase commented Dec 4, 2019

Currently we use the list generated by the AtomicArray in ArraySearchPhaseResults but this List is shared between threads and can get nullify. This change collects results in a local list to prevent concurrent issues.

fixes #49778

@iverase iverase added >bug :Search/Search Search-related issues that do not fall into other categories v8.0.0 v7.6.0 labels Dec 4, 2019
@iverase iverase requested a review from jimczi December 4, 2019 12:28
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search (:Search/Search)

@iverase
Copy link
Contributor Author

iverase commented Dec 4, 2019

@elasticmachine run elasticsearch-ci/1

Copy link
Contributor

@jimczi jimczi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @iverase. I missed the fact that modification could happen before the synchronized call.
We don't want to take concurrent modifications into account since we need to report the shards that are part of the current partial reduce. I opened #49829 to use a different array that is synchronously accessed and modified. This should fix the concurrent issue and the wrong reporting.

@iverase
Copy link
Contributor Author

iverase commented Dec 4, 2019

I see, then I close this PR in favour of #49829

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>bug :Search/Search Search-related issues that do not fall into other categories v7.6.0 v8.0.0-alpha1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CI] Failure in SumIT.testSingleValuedFieldWithFormatter

4 participants