Skip to content

UpdateSettingsIT#testEngineGCDeletesSetting failure #38874

@talevy

Description

@talevy

test failing:

org.elasticsearch.indices.settings.UpdateSettingsIT testEngineGCDeletesSetting

#38254 introduced a new VersionConflictEngineException assertion that seems
to be dependent on cache invalidation timed by Thread.sleep.

exception:

java.lang.AssertionError: expected a class org.elasticsearch.index.engine.VersionConflictEngineException exception to be thrown

	at __randomizedtesting.SeedInfo.seed([103812063D7BAB96:96D53E0C3D9BE721]:0)
	at org.elasticsearch.test.hamcrest.ElasticsearchAssertions.assertThrows(ElasticsearchAssertions.java:596)
	at org.elasticsearch.test.hamcrest.ElasticsearchAssertions.assertThrows(ElasticsearchAssertions.java:543)
	at org.elasticsearch.test.hamcrest.ElasticsearchAssertions.assertThrows(ElasticsearchAssertions.java:520)
	at org.elasticsearch.indices.settings.UpdateSettingsIT.testEngineGCDeletesSetting(UpdateSettingsIT.java:452)

was tough to get a stacktrace, but looks to fail in InternalEngine#planIndexingAsPrimary

with the exception:

[type][1]: version conflict, required seqNo [3], primary term [1]. but no document was found

ci link: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.0+internalClusterTest/472/console

reproduce:

./gradlew :server:integTest \
  -Dtests.seed=EAF25E026AF61CCF \
  -Dtests.class=org.elasticsearch.indices.settings.UpdateSettingsIT \
  -Dtests.method="testEngineGCDeletesSetting" \
  -Dtests.security.manager=true \
  -Dtests.locale=is-IS \
  -Dtests.timezone=Australia/Canberra \
  -Dcompiler.java=11 \
  -Druntime.java=8

This is easy to reproduce if one removes the Thread.sleep(300). Which means that
cache hadn't changed in the CI run in time for the assertion.

Metadata

Metadata

Assignees

Labels

:Distributed Indexing/CRUDA catch all label for issues around indexing, updating and getting a doc by id. Not search.>test-failureTriaged test failures from CIv7.0.0-rc2

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions