Browse Source

[TEST] Fixed delete/50_refresh REST test to work against multiple nodes

delete/50_refresh tests per shard refresh using refresh:true in delete api. We might run into troubles though if we have a replica that gets initialized after a doc was indexed and deleted, without a refresh, as that doc won't be found when searching against that specific replica shard (as a refresh happens automatically before a replica gets exposed as started).
Luca Cavanna 11 years ago
parent
commit
e02635e9c2
1 changed files with 7 additions and 2 deletions
  1. 7 2
      rest-api-spec/test/delete/50_refresh.yaml

+ 7 - 2
rest-api-spec/test/delete/50_refresh.yaml

@@ -6,10 +6,11 @@
           index:    test_1
           body:
               settings:
-                  index.refresh_interval: -1
+                  refresh_interval: -1
+                  number_of_replicas: 0
  - do:
       cluster.health:
-          wait_for_status: yellow
+          wait_for_status: green
 
  - do:
       index:
@@ -58,6 +59,10 @@
           id:      2
           refresh: 1
 
+# If a replica shard where doc 1 is located gets initialized at this point, doc 1
+# won't be found by the following search as the shard gets automatically refreshed
+# right before getting started. This is why this test only works with 0 replicas.
+
  - do:
       search:
           index:   test_1