-
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
[CI] CloseIndexIT.testCloseIndex failed #40024
Labels
:Data Management/Indices APIs
APIs to create and manage indices and templates
:Distributed Indexing/Distributed
A catch all label for anything in the Distributed Area. Please avoid if you can.
>test-failure
Triaged test failures from CI
Comments
bizybot
added
>test-failure
Triaged test failures from CI
:Data Management/Indices APIs
APIs to create and manage indices and templates
labels
Mar 14, 2019
Pinging @elastic/es-core-features |
This build appears to have been rotated out from Jenkins. From the build stats kibana, the stack trace is:
Looks like this might be a failure related to sequence numbers and the global checkpoint - adding the distributed team, could someone take a look? |
gwbrown
added
the
:Distributed Indexing/Distributed
A catch all label for anything in the Distributed Area. Please avoid if you can.
label
Mar 15, 2019
Pinging @elastic/es-distributed |
dnhatn
added a commit
that referenced
this issue
May 22, 2019
Flushing at the end of a peer recovery (if needed) can bring these benefits: 1. Closing an index won't end up with the red state for a recovering replica should always be ready for closing whether it performs the verifying-before-close step or not. 2. Good opportunities to compact store (i.e., flushing and merging Lucene, and trimming translog) Closes #40024 Closes #39588
dnhatn
added a commit
that referenced
this issue
May 22, 2019
Flushing at the end of a peer recovery (if needed) can bring these benefits: 1. Closing an index won't end up with the red state for a recovering replica should always be ready for closing whether it performs the verifying-before-close step or not. 2. Good opportunities to compact store (i.e., flushing and merging Lucene, and trimming translog) Closes #40024 Closes #39588
gurkankaymak
pushed a commit
to gurkankaymak/elasticsearch
that referenced
this issue
May 27, 2019
Flushing at the end of a peer recovery (if needed) can bring these benefits: 1. Closing an index won't end up with the red state for a recovering replica should always be ready for closing whether it performs the verifying-before-close step or not. 2. Good opportunities to compact store (i.e., flushing and merging Lucene, and trimming translog) Closes elastic#40024 Closes elastic#39588
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Data Management/Indices APIs
APIs to create and manage indices and templates
:Distributed Indexing/Distributed
A catch all label for anything in the Distributed Area. Please avoid if you can.
>test-failure
Triaged test failures from CI
CloseIndexIT.testCloseIndex failed on
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.x+internalClusterTest/2283/console
Unable to reproduce locally with the following command:
The text was updated successfully, but these errors were encountered: