Skip to content
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

IndexFollowingIT#testFollowIndex can fail with assertion error. #41037

Closed
jtibshirani opened this issue Apr 9, 2019 · 1 comment · Fixed by #41987
Closed

IndexFollowingIT#testFollowIndex can fail with assertion error. #41037

jtibshirani opened this issue Apr 9, 2019 · 1 comment · Fixed by #41987
Assignees
Labels
:Distributed/CCR Issues around the Cross Cluster State Replication features >test-failure Triaged test failures from CI

Comments

@jtibshirani
Copy link
Contributor

I wasn't able to reproduce the error locally. It looks like this failure has popped up 2-3 times in CI over the past month. It may be related to #38949, feel free to close this in favor of that one if you'd prefer to track work there.


Link to the build: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+intake/3039/console

Command to reproduce:

./gradlew :x-pack:plugin:ccr:internalClusterTest --tests "org.elasticsearch.xpack.ccr.IndexFollowingIT.testFollowIndex" \
  -Dtests.seed=899F6DBC812AC342 \
  -Dtests.security.manager=true \
  -Dtests.locale=mer-KE \
  -Dtests.timezone=America/Fortaleza \
  -Dcompiler.java=12 \
  -Druntime.java=11

Relevant excerpt from the logs:

org.elasticsearch.xpack.ccr.IndexFollowingIT > testFollowIndex FAILED
    java.lang.AssertionError: 
    Expected: <0>
         but: was <1>
        at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
        at org.junit.Assert.assertThat(Assert.java:956)
        at org.junit.Assert.assertThat(Assert.java:923)
        at org.elasticsearch.xpack.CcrIntegTestCase.lambda$ensureNoCcrTasks$3(CcrIntegTestCase.java:418)
        at org.elasticsearch.test.ESTestCase.assertBusy(ESTestCase.java:862)
        at org.elasticsearch.xpack.CcrIntegTestCase.ensureNoCcrTasks(CcrIntegTestCase.java:399)
        at org.elasticsearch.xpack.CcrIntegTestCase.pauseFollow(CcrIntegTestCase.java:395)
        at org.elasticsearch.xpack.ccr.IndexFollowingIT.testFollowIndex(IndexFollowingIT.java:191)

    java.lang.AssertionError: not all translog generations have been released

    com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught exception in thread: Thread[id=277, name=elasticsearch[follower1][generic][T#4], state=RUNNABLE, group=TGRP-IndexFollowingIT]

        Caused by:
        java.lang.AssertionError: invalid global checkpoint[5596] source_meta_data [{local_checkpoint=5596, max_unsafe_auto_id_timestamp=-1, min_retained_seq_no=0, translog_uuid=oPl81yVBToWbh_M-LBrEqA, history_uuid=rudbNf_KSZuvLto5xdE5nQ, translog_generation=1, max_seq_no=5889}]

@jtibshirani jtibshirani added >test-failure Triaged test failures from CI :Distributed/CCR Issues around the Cross Cluster State Replication features labels Apr 9, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

dnhatn added a commit that referenced this issue May 10, 2019
If remote recovery copies an index commit which has gaps in sequence
numbers to a follower; then these assertions (introduced in #40823)
don't hold for follower replicas.

Closes #41037
dnhatn added a commit that referenced this issue May 10, 2019
If remote recovery copies an index commit which has gaps in sequence
numbers to a follower; then these assertions (introduced in #40823)
don't hold for follower replicas.

Closes #41037
Megamiun pushed a commit to Megamiun/elasticsearch that referenced this issue May 18, 2019
If remote recovery copies an index commit which has gaps in sequence
numbers to a follower; then these assertions (introduced in elastic#40823)
don't hold for follower replicas.

Closes elastic#41037
gurkankaymak pushed a commit to gurkankaymak/elasticsearch that referenced this issue May 27, 2019
gurkankaymak pushed a commit to gurkankaymak/elasticsearch that referenced this issue May 27, 2019
If remote recovery copies an index commit which has gaps in sequence
numbers to a follower; then these assertions (introduced in elastic#40823)
don't hold for follower replicas.

Closes elastic#41037
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed/CCR Issues around the Cross Cluster State Replication features >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants