Skip to content
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

Closed
jrodewig opened this issue Dec 20, 2019 · 2 comments · Fixed by #50456
Closed
Assignees
Labels
:Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs >test-failure Triaged test failures from CI

Comments

@jrodewig
Copy link
Contributor

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.

Caused by: java.lang.AssertionError: 
snapshot.shards.successful didn't match expected value:
    snapshot.shards.successful: expected Integer [1] but was Integer [2]
  "stash" : {
    "body" : {
      "snapshot" : {
        "snapshot" : "test_snapshot",
        "uuid" : "1pr60of1RIWn1w2MAjRmRw",
        "version_id" : 8000099,
        "version" : "8.0.0",
        "indices" : [
          "test_index",
          "ilm-history-1-000001"
        ],
        "include_global_state" : true,
        "state" : "SUCCESS",
        "start_time" : "2019-12-20T19:16:11.335Z",
        "start_time_in_millis" : 1576869371335,
        "end_time" : "2019-12-20T19:16:11.535Z",
        "end_time_in_millis" : 1576869371535,
        "duration_in_millis" : 200,
        "failures" : [ ],
        "shards" : {
          "total" : 2,
          "failed" : 0,
          "successful" : 2
        }
      }
    }
  }
}]
@jrodewig jrodewig added :Distributed Coordination/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs >test-failure Triaged test failures from CI labels Dec 20, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (:Distributed/Snapshot/Restore)

@original-brownbear original-brownbear self-assigned this Dec 21, 2019
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
@mayya-sharipova
Copy link
Contributor

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
Build scan: https://gradle-enterprise.elastic.co/s/uqzlfrbi4wq7u

Relevant stacktrace:


org.elasticsearch.xpack.test.rest.XPackRestIT > test {p0=snapshot/10_basic/Create a source only snapshot and then restore it} FAILED |  
-- | --
  | java.lang.AssertionError: Failure at [snapshot/10_basic:21]: expected [2xx] status code but api [cluster.health] returned [408 Request Timeout] [{"cluster_name":"integTest","status":"yellow","timed_out":true,"number_of_nodes":1,"number_of_data_nodes":1,"active_primary_shards":2,"active_shards":2,"relocating_shards":0,"initializing_shards":0,"unassigned_shards":1,"delayed_unassigned_shards":0,"number_of_pending_tasks":0,"number_of_in_flight_fetch":0,"task_max_waiting_in_queue_millis":0,"active_shards_percent_as_number":66.66666666666666}] |  
  | at __randomizedtesting.SeedInfo.seed([D3B89AEE43928B07:5BECA534ED6EE6FF]:0)


Caused by: |  
-- | --
  | java.lang.AssertionError: expected [2xx] status code but api [cluster.health] returned [408 Request Timeout] [{"cluster_name":"integTest","status":"yellow","timed_out":true,"number_of_nodes":1,"number_of_data_nodes":1,"active_primary_shards":2,"active_shards":2,"relocating_shards":0,"initializing_shards":0,"unassigned_shards":1,"delayed_unassigned_shards":0,"number_of_pending_tasks":0,"number_of_in_flight_fetch":0,"task_max_waiting_in_queue_millis":0,"active_shards_percent_as_number":66.66666666666666}] |  
  | at org.junit.Assert.fail(Assert.java:88)


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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants