Skip to content

ReplicaShardAllocatorSyncIdIT.testFullClusterRestartPerformNoopRecovery failed on master #51750

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.

Sign up for GitHub

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

Jump to bottom
Closed
mayya-sharipova opened this issue Jan 31, 2020 · 3 comments · Fixed by #51831
Closed

ReplicaShardAllocatorSyncIdIT.testFullClusterRestartPerformNoopRecovery failed on master #51750

mayya-sharipova opened this issue Jan 31, 2020 · 3 comments · Fixed by #51831
Assignees
@dnhatn
Labels
:Distributed Indexing/Recovery Anything around constructing a new shard, either from a local or a remote source. >test-failure Triaged test failures from CI

Comments

@mayya-sharipova
Copy link
Contributor

Log: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob+fast+part1/3424/console
Build Scans: https://gradle-enterprise.elastic.co/s/c5muqklxtniog

REPRODUCE WITH: ./gradlew ':server:integTest' --tests "org.elasticsearch.gateway.ReplicaShardAllocatorSyncIdIT.testFullClusterRestartPerformNoopRecovery"
-Dtests.seed=1B893998BA12C55E
-Dtests.security.manager=true
-Dtests.locale=ar-DZ
-Dtests.timezone=Asia/Famagusta
-Dcompiler.java=13

Does not reproduce for me. May be just an intermittent error.

stacktrace

Expected: <0>
     but: was <62>
java.lang.AssertionError: 

Expected: <0>
     but: was <62>
@mayya-sharipova mayya-sharipova added >test-failure Triaged test failures from CI :Distributed Indexing/Recovery Anything around constructing a new shard, either from a local or a remote source. labels Jan 31, 2020
@elasticmachine
Copy link
Collaborator

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

@mayya-sharipova
Copy link
Contributor Author

@dnhatn Can you please check it. It can be just an intermittent failure that we can disregard.

@dnhatn
Copy link
Member

dnhatn commented Jan 31, 2020

Thanks Mayya. I will take a look at the failure.

@dnhatn dnhatn mentioned this issue Feb 3, 2020
Merged
dnhatn added a commit that referenced this issue Feb 4, 2020
@dnhatn
Fix assertion in sync flush simulation (#51831)
f4a4e41 
We perform a non-force flush in this test. It can be a noop on replicas 
if indexing are processed out of order. We should assert the IndexWriter
instead of the translog before simulating a sync flush.

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

@dnhatn dnhatn

Labels
:Distributed Indexing/Recovery Anything around constructing a new shard, either from a local or a remote source. >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix assertion in sync flush simulation dnhatn/elasticsearch
3 participants
@mayya-sharipova @dnhatn @elasticmachine