-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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] Rest text p0=snapshot/10_basic/Create a source only snapshot and then restore it
failure
#50450
Labels
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
>test-failure
Triaged test failures from CI
Comments
Pinging @elastic/es-distributed (:Distributed/Snapshot/Restore) |
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this issue
Dec 23, 2019
We are matching on the exact number of shards in this test, but may run into snapshotting more than the single index created in it due to auto-created indices like `.watcher`. Fixed by making the test only take a snapshot of the single index used by this test. Closes elastic#50450
original-brownbear
added a commit
that referenced
this issue
Dec 23, 2019
We are matching on the exact number of shards in this test, but may run into snapshotting more than the single index created in it due to auto-created indices like `.watcher`. Fixed by making the test only take a snapshot of the single index used by this test. Closes #50450
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this issue
Dec 23, 2019
We are matching on the exact number of shards in this test, but may run into snapshotting more than the single index created in it due to auto-created indices like `.watcher`. Fixed by making the test only take a snapshot of the single index used by this test. Closes elastic#50450
original-brownbear
added a commit
that referenced
this issue
Dec 23, 2019
We are matching on the exact number of shards in this test, but may run into snapshotting more than the single index created in it due to auto-created indices like `.watcher`. Fixed by making the test only take a snapshot of the single index used by this test. Closes #50450
SivagurunathanV
pushed a commit
to SivagurunathanV/elasticsearch
that referenced
this issue
Jan 23, 2020
We are matching on the exact number of shards in this test, but may run into snapshotting more than the single index created in it due to auto-created indices like `.watcher`. Fixed by making the test only take a snapshot of the single index used by this test. Closes elastic#50450
The test failed on 7.x, but it may be just a simple timeout. Log: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+7.x+matrix-java-periodic/ES_BUILD_JAVA=openjdk13,ES_RUNTIME_JAVA=openjdk13,nodes=general-purpose/484/console Relevant stacktrace:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
>test-failure
Triaged test failures from CI
Received this build failure during the push of an unrelated docs change (a311018)
Failure: https://gradle-enterprise.elastic.co/s/v5h5hntmwkiqy/tests/fcijb24gqtmnc-cqpxjyuvwnxpc
Based on the results, it looks like two snapshots were restored instead of one as expected.
The text was updated successfully, but these errors were encountered: