Skip to content

Commit

Permalink
Don't Assert Ack on when Publish Timeout is 0 in Test (elastic#38077)
Browse files Browse the repository at this point in the history
* Publish timeout is set to `0` so out of order processing of states on the node can lead to a `false` ack response
  * See elastic#30672
* Closes elastic#36813
  • Loading branch information
original-brownbear committed Jan 31, 2019
1 parent 9f026bb commit ae9f4df
Showing 1 changed file with 4 additions and 4 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -333,12 +333,12 @@ public void testDelayedMappingPropagationOnReplica() throws Exception {

// Force allocation of the primary on the master node by first only allocating on the master
// and then allowing all nodes so that the replica gets allocated on the other node
assertAcked(prepareCreate("index").setSettings(Settings.builder()
prepareCreate("index").setSettings(Settings.builder()
.put(IndexMetaData.SETTING_NUMBER_OF_SHARDS, 1)
.put(IndexMetaData.SETTING_NUMBER_OF_REPLICAS, 1)
.put("index.routing.allocation.include._name", master)).get());
assertAcked(client().admin().indices().prepareUpdateSettings("index").setSettings(Settings.builder()
.put("index.routing.allocation.include._name", "")).get());
.put("index.routing.allocation.include._name", master)).get();
client().admin().indices().prepareUpdateSettings("index").setSettings(Settings.builder()
.put("index.routing.allocation.include._name", "")).get();
ensureGreen();

// Check routing tables
Expand Down

0 comments on commit ae9f4df

Please sign in to comment.