-
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
Failure in CloseWhileRelocatingShardsIT #49403
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
DaveCTurner
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
Nov 20, 2019
Pinging @elastic/es-distributed (:Distributed/Recovery) |
dnhatn
added a commit
that referenced
this issue
Nov 22, 2019
If some replica is performing a file-based recovery, then the check assertNoSnapshottedIndexCommit would fail. We should increase the timeout for this check so that we can wait until all recoveries done or aborted. Closes #49403
dnhatn
added a commit
that referenced
this issue
Nov 24, 2019
If some replica is performing a file-based recovery, then the check assertNoSnapshottedIndexCommit would fail. We should increase the timeout for this check so that we can wait until all recoveries done or aborted. Closes #49403
dnhatn
added a commit
that referenced
this issue
Nov 24, 2019
If some replica is performing a file-based recovery, then the check assertNoSnapshottedIndexCommit would fail. We should increase the timeout for this check so that we can wait until all recoveries done or aborted. Closes #49403
dnhatn
added a commit
that referenced
this issue
Nov 24, 2019
If some replica is performing a file-based recovery, then the check assertNoSnapshottedIndexCommit would fail. We should increase the timeout for this check so that we can wait until all recoveries done or aborted. Closes #49403
dnhatn
added a commit
that referenced
this issue
Nov 25, 2019
If some replica is performing a file-based recovery, then the check assertNoSnapshottedIndexCommit would fail. We should increase the timeout for this check so that we can wait until all recoveries done or aborted. Closes #49403
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This build failed as follows:
The text was updated successfully, but these errors were encountered: