-
Notifications
You must be signed in to change notification settings - Fork 25k
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
[CI] InternalEngineTests testMergeThreadLogging failing #90071
Labels
:Distributed Indexing/Engine
Anything around managing Lucene and the Translog in an open shard.
low-risk
An open issue or test failure that is a low risk to future releases
Team:Distributed (Obsolete)
Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
>test-failure
Triaged test failures from CI
Comments
DaveCTurner
added
:Distributed Indexing/Engine
Anything around managing Lucene and the Translog in an open shard.
>test-failure
Triaged test failures from CI
labels
Sep 14, 2022
Pinging @elastic/es-distributed (Team:Distributed) |
elasticsearchmachine
added
the
Team:Distributed (Obsolete)
Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
label
Sep 14, 2022
tlrx
added a commit
to tlrx/elasticsearch
that referenced
this issue
Oct 6, 2022
tlrx
added a commit
that referenced
this issue
Oct 10, 2022
tlrx
added a commit
to tlrx/elasticsearch
that referenced
this issue
Oct 10, 2022
elasticsearchmachine
pushed a commit
that referenced
this issue
Oct 10, 2022
Reopening with a new failure on the main branch (8.10)
|
volodk85
added
the
low-risk
An open issue or test failure that is a low risk to future releases
label
Oct 23, 2023
tlrx
added a commit
to tlrx/elasticsearch
that referenced
this issue
Nov 27, 2023
The test has to wait for all merge thread log messages (include Lucene ones) to be seen before reset the log level and stop the appender. Previous attempt wasn't enough: the test failure in elastic#90071 (comment) shows that Lucene's merge scheduler thread can log after the Elasticsearch one, and if the appender has been closed in the meanwhile it can fail the test. This change ensure that the appender saw the Merge Scheduler end message before resetting the log level and close the engine. Closes elastic#90071
leemthompo
pushed a commit
to leemthompo/elasticsearch
that referenced
this issue
Nov 27, 2023
The test has to wait for all merge thread log messages (include Lucene ones) to be seen before reset the log level and stop the appender. Previous attempt wasn't enough: the test failure in elastic#90071 (comment) shows that Lucene's merge scheduler thread can log after the Elasticsearch one, and if the appender has been closed in the meanwhile it can fail the test. This change ensure that the appender saw the Merge Scheduler end message before resetting the log level and close the engine. Closes elastic#90071
elasticsearchmachine
pushed a commit
that referenced
this issue
Nov 27, 2023
The test has to wait for all merge thread log messages (include Lucene ones) to be seen before reset the log level and stop the appender. Previous attempt wasn't enough: the test failure in #90071 (comment) shows that Lucene's merge scheduler thread can log after the Elasticsearch one, and if the appender has been closed in the meanwhile it can fail the test. This change ensure that the appender saw the Merge Scheduler end message before resetting the log level and close the engine. Closes #90071
timgrein
pushed a commit
to timgrein/elasticsearch
that referenced
this issue
Nov 30, 2023
The test has to wait for all merge thread log messages (include Lucene ones) to be seen before reset the log level and stop the appender. Previous attempt wasn't enough: the test failure in elastic#90071 (comment) shows that Lucene's merge scheduler thread can log after the Elasticsearch one, and if the appender has been closed in the meanwhile it can fail the test. This change ensure that the appender saw the Merge Scheduler end message before resetting the log level and close the engine. Closes elastic#90071
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.
low-risk
An open issue or test failure that is a low risk to future releases
Team:Distributed (Obsolete)
Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
>test-failure
Triaged test failures from CI
Also seen in a local run of
./gradlew :server:test
but doesn't easily reproduce, even when running many iterations in a loop.Build scan:
https://gradle-enterprise.elastic.co/s/kbbpmnbim32ck/tests/:server:test/org.elasticsearch.index.engine.InternalEngineTests/testMergeThreadLogging
Reproduction line:
./gradlew ':server:test' --tests "org.elasticsearch.index.engine.InternalEngineTests.testMergeThreadLogging" -Dtests.seed=A7B12EB0B151C9B5 -Dtests.locale=es-PA -Dtests.timezone=Europe/Tiraspol -Druntime.java=17
Applicable branches:
main
Reproduces locally?:
No
Edit to add: eventually this failed for me after a couple of thousand iterations on a machine that was concurrently running
stress-ng --timeout 0 --cpu 16
Failure history:
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.index.engine.InternalEngineTests&tests.test=testMergeThreadLogging
Failure excerpt:
The text was updated successfully, but these errors were encountered: