Skip to content

testForceMergeWithSoftDeletesRetentionAndRecoverySource fails #48735

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

Closed
DaveCTurner opened this issue Oct 31, 2019 · 2 comments · Fixed by #48766
Closed

testForceMergeWithSoftDeletesRetentionAndRecoverySource fails #48735

DaveCTurner opened this issue Oct 31, 2019 · 2 comments · Fixed by #48766
Assignees
Labels
:Distributed Indexing/Engine Anything around managing Lucene and the Translog in an open shard. >test-failure Triaged test failures from CI

Comments

@DaveCTurner
Copy link
Contributor

On master (3e4791a) I get the following failure:

  2> REPRODUCE WITH: ./gradlew ':server:test' --tests "org.elasticsearch.index.engine.InternalEngineTests.testForceMergeWithSoftDeletesRetentionAndRecoverySource" -Dtests.seed=15017DBA718DE0ED -Dtests.security.manager=true -Dtests.jvms=4 -Dtests.locale=de-DE -Dtests.timezone=America/Cambridge_Bay -Dcompiler.java=12 -Druntime.java=12
  2> java.lang.AssertionError:
    Expected: a collection with size <0>
         but: collection size was <2>
        at __randomizedtesting.SeedInfo.seed([15017DBA718DE0ED:930E7D8A8C86530A]:0)
        at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
        at org.junit.Assert.assertThat(Assert.java:956)
        at org.junit.Assert.assertThat(Assert.java:923)
        at org.elasticsearch.index.engine.InternalEngineTests.testForceMergeWithSoftDeletesRetentionAndRecoverySource(InternalEngineTests.java:1732)
  2> NOTE: leaving temporary files on disk at: /home/davidturner/elasticsearch/server/build/testrun/test/temp/org.elasticsearch.index.engine.InternalEngineTests_15017DBA718DE0ED-002
  2> NOTE: test params are: codec=Asserting(Lucene80), sim=Asserting(org.apache.lucene.search.similarities.AssertingSimilarity@6a559181), locale=de-DE, timezone=America/Cambridge_Bay
  2> NOTE: Linux 4.15.0-47-generic amd64/Oracle Corporation 12 (64-bit)/cpus=8,threads=1,free=360496288,total=536870912
  2> NOTE: All tests run in this JVM: [InternalEngineTests]

The REPRODUCE WITH line does seem to reliably reproduce this.

@DaveCTurner DaveCTurner added >test-failure Triaged test failures from CI :Distributed Indexing/Engine Anything around managing Lucene and the Translog in an open shard. labels Oct 31, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (:Distributed/Engine)

@dnhatn
Copy link
Member

dnhatn commented Oct 31, 2019

Relates to #48533.
Relates to #41628.

@dnhatn dnhatn self-assigned this Oct 31, 2019
dnhatn added a commit that referenced this issue Nov 1, 2019
This test failure manifests the limitation of the recovery source merge 
policy explained in #41628. If we already merge down to a single segment
then subsequent force merges will be noop although they can prune
recovery source. We need to adjust this test until we have a fix for the
merge policy.

Relates #41628
Closes #48735
dnhatn added a commit that referenced this issue Nov 3, 2019
This test failure manifests the limitation of the recovery source merge
policy explained in #41628. If we already merge down to a single segment
then subsequent force merges will be noop although they can prune
recovery source. We need to adjust this test until we have a fix for the
merge policy.

Relates #41628
Closes #48735
dnhatn added a commit that referenced this issue Nov 3, 2019
This test failure manifests the limitation of the recovery source merge
policy explained in #41628. If we already merge down to a single segment
then subsequent force merges will be noop although they can prune
recovery source. We need to adjust this test until we have a fix for the
merge policy.

Relates #41628
Closes #48735
dnhatn added a commit that referenced this issue Nov 9, 2019
This test failure manifests the limitation of the recovery source merge
policy explained in #41628. If we already merge down to a single segment
then subsequent force merges will be noop although they can prune
recovery source. We need to adjust this test until we have a fix for the
merge policy.

Relates #41628
Closes #48735
dnhatn added a commit that referenced this issue Nov 9, 2019
This test failure manifests the limitation of the recovery source merge
policy explained in #41628. If we already merge down to a single segment
then subsequent force merges will be noop although they can prune
recovery source. We need to adjust this test until we have a fix for the
merge policy.

Relates #41628
Closes #48735
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Indexing/Engine Anything around managing Lucene and the Translog in an open shard. >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants