-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
IndexShardTests.testDocStats fails sporadically #32766
Labels
:Distributed Indexing/Engine
Anything around managing Lucene and the Translog in an open shard.
>test-failure
Triaged test failures from CI
v6.5.0
v7.0.0-beta1
Comments
alpar-t
added
:Search/Search
Search-related issues that do not fall into other categories
>test-failure
Triaged test failures from CI
v7.0.0
v6.5.0
labels
Aug 10, 2018
Pinging @elastic/es-search-aggs |
ywelsch
added
:Distributed Indexing/Engine
Anything around managing Lucene and the Translog in an open shard.
and removed
:Search/Search
Search-related issues that do not fall into other categories
labels
Aug 14, 2018
Pinging @elastic/es-distributed |
This looks related to #32241 |
andyb-elastic
added a commit
that referenced
this issue
Aug 15, 2018
andyb-elastic
added a commit
that referenced
this issue
Aug 15, 2018
Another one of these on master https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+intake/2528/console |
andrershov
pushed a commit
to andrershov/elasticsearch
that referenced
this issue
Aug 16, 2018
testDocStats test is flaky and sometimes its failing on jenkins on and failure is not reproducible locally. The reason for this failure is in timing. If number of deleted documents is greater than 33% of inserted documents, Lucene will schedule segments merge if TieredMergePolicy is used (it's not the case for LogMergePolicy, but ES is only using TieredMergePolicy). If this merge is performed before stats are retrieved - we will get 0 for deleted counter. So basically this counter could be either 0 or numOfDeletedDocs at this point, but this is too loose assertion and we decided to remove it at all. Closes elastic#32766
andrershov
added a commit
that referenced
this issue
Aug 17, 2018
testDocStats test is flaky and sometimes it's failing on jenkins and failure is not reproducible locally. The reason for this failure is in timing. If the number of deleted documents is greater than 33% of inserted documents, Lucene will schedule segments to merge if TieredMergePolicy is used (it's not the case for LogMergePolicy, but ES is only using TieredMergePolicy). If this merge is performed before stats are retrieved - we will get 0 for "deleted" counter. So basically this counter could be either 0 or numOfDeletedDocs at this point, but this is the too loose assertion and we decided to remove it at all. Closes #32766
andrershov
added a commit
that referenced
this issue
Aug 17, 2018
testDocStats test is flaky and sometimes it's failing on jenkins and failure is not reproducible locally. The reason for this failure is in timing. If the number of deleted documents is greater than 33% of inserted documents, Lucene will schedule segments to merge if TieredMergePolicy is used (it's not the case for LogMergePolicy, but ES is only using TieredMergePolicy). If this merge is performed before stats are retrieved - we will get 0 for "deleted" counter. So basically this counter could be either 0 or numOfDeletedDocs at this point, but this is the too loose assertion and we decided to remove it at all. Closes #32766
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
v6.5.0
v7.0.0-beta1
Example build failure:
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+periodic/2518/console
Reproduction line (does not reproduce locally):
Example relevant log:
Frequency: First failure dates back to February, with another isolated failure on 26th of June, then spikes on July 26-27 with 7 failures across branches and much more on PR builds. Failed at least once per day in the last couple of days.
The text was updated successfully, but these errors were encountered: