Skip to content

Prevent possible assertion failure in IndicesQueryCache.close #38714

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

Conversation

droberts195
Copy link
Contributor

The assertion that the stats2 map is empty in
IndicesQueryCache.close has been observed to
fail very occasionally in internal cluster tests.

The likely cause is a cross-thread visibility
problem for a count variable. This change
makes that count volatile.

Relates #37117

The assertion that the stats2 map is empty in
IndicesQueryCache.close has been observed to
fail very occasionally in internal cluster tests.

The likely cause is a cross-thread visibility
problem for a count variable.  This change
makes that count volatile.

Relates elastic#37117
@droberts195 droberts195 added :Search/Search Search-related issues that do not fall into other categories >test-failure Triaged test failures from CI v7.0.0 v6.7.0 v8.0.0 v7.2.0 labels Feb 11, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search

@romseygeek
Copy link
Contributor

LGTM, thanks @droberts195

@droberts195 droberts195 merged commit 6871f14 into elastic:master Feb 11, 2019
@droberts195 droberts195 deleted the fix_indices_query_cache_assert_fail_on_close branch February 11, 2019 14:59
droberts195 added a commit to droberts195/elasticsearch that referenced this pull request Feb 11, 2019
)

The assertion that the stats2 map is empty in
IndicesQueryCache.close has been observed to
fail very occasionally in internal cluster tests.

The likely cause is a cross-thread visibility
problem for a count variable.  This change
makes that count volatile.

Relates elastic#37117
droberts195 added a commit to droberts195/elasticsearch that referenced this pull request Feb 11, 2019
)

The assertion that the stats2 map is empty in
IndicesQueryCache.close has been observed to
fail very occasionally in internal cluster tests.

The likely cause is a cross-thread visibility
problem for a count variable.  This change
makes that count volatile.

Relates elastic#37117
droberts195 added a commit that referenced this pull request Feb 11, 2019
The assertion that the stats2 map is empty in
IndicesQueryCache.close has been observed to
fail very occasionally in internal cluster tests.

The likely cause is a cross-thread visibility
problem for a count variable.  This change
makes that count volatile.

Relates #37117
Backport of #38714
droberts195 added a commit that referenced this pull request Feb 11, 2019
The assertion that the stats2 map is empty in
IndicesQueryCache.close has been observed to
fail very occasionally in internal cluster tests.

The likely cause is a cross-thread visibility
problem for a count variable.  This change
makes that count volatile.

Relates #37117
Backport of #38714
droberts195 added a commit that referenced this pull request Feb 11, 2019
The assertion that the stats2 map is empty in
IndicesQueryCache.close has been observed to
fail very occasionally in internal cluster tests.

The likely cause is a cross-thread visibility
problem for a count variable.  This change
makes that count volatile.

Relates #37117
Backport of #38714
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Search/Search Search-related issues that do not fall into other categories >test-failure Triaged test failures from CI v6.7.0 v7.0.0-beta1 v7.2.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants