@@ -90,7 +90,7 @@ public void testHistoryUUIDIsGenerated() throws Exception {
9090 .put (IndexMetadata .INDEX_NUMBER_OF_SHARDS_SETTING .getKey (), 1 )
9191 .put (IndexMetadata .INDEX_NUMBER_OF_REPLICAS_SETTING .getKey (), 1 )
9292 // if the node with the replica is the first to be restarted, while a replica is still recovering
93- // then delayed allocation will kick in. When the node comes back, the master will search for a copy
93+ // then delayed allocation will kick in. When the node comes back, the cluster-manager will search for a copy
9494 // but the recovering copy will be seen as invalid and the cluster health won't return to GREEN
9595 // before timing out
9696 .put (INDEX_DELAYED_NODE_LEFT_TIMEOUT_SETTING .getKey (), "100ms" );
@@ -158,7 +158,7 @@ public void testRecoveryWithConcurrentIndexing() throws Exception {
158158 .put (IndexMetadata .INDEX_NUMBER_OF_SHARDS_SETTING .getKey (), 1 )
159159 .put (IndexMetadata .INDEX_NUMBER_OF_REPLICAS_SETTING .getKey (), 2 )
160160 // if the node with the replica is the first to be restarted, while a replica is still recovering
161- // then delayed allocation will kick in. When the node comes back, the master will search for a copy
161+ // then delayed allocation will kick in. When the node comes back, the cluster-manager will search for a copy
162162 // but the recovering copy will be seen as invalid and the cluster health won't return to GREEN
163163 // before timing out
164164 .put (INDEX_DELAYED_NODE_LEFT_TIMEOUT_SETTING .getKey (), "100ms" )
@@ -256,7 +256,7 @@ public void testRelocationWithConcurrentIndexing() throws Exception {
256256 .put (IndexMetadata .INDEX_NUMBER_OF_SHARDS_SETTING .getKey (), 1 )
257257 .put (IndexMetadata .INDEX_NUMBER_OF_REPLICAS_SETTING .getKey (), 2 )
258258 // if the node with the replica is the first to be restarted, while a replica is still recovering
259- // then delayed allocation will kick in. When the node comes back, the master will search for a copy
259+ // then delayed allocation will kick in. When the node comes back, the cluster-manager will search for a copy
260260 // but the recovering copy will be seen as invalid and the cluster health won't return to GREEN
261261 // before timing out
262262 .put (INDEX_DELAYED_NODE_LEFT_TIMEOUT_SETTING .getKey (), "100ms" )
@@ -266,7 +266,7 @@ public void testRelocationWithConcurrentIndexing() throws Exception {
266266 indexDocs (index , 0 , 10 );
267267 ensureGreen (index );
268268 // make sure that no shards are allocated, so we can make sure the primary stays on the old node (when one
269- // node stops, we lose the master too, so a replica will not be promoted)
269+ // node stops, we lose the cluster-manager too, so a replica will not be promoted)
270270 updateIndexSettings (index , Settings .builder ().put (INDEX_ROUTING_ALLOCATION_ENABLE_SETTING .getKey (), "none" ));
271271 break ;
272272 case MIXED :
@@ -330,7 +330,7 @@ public void testRecovery() throws Exception {
330330 .put (IndexMetadata .INDEX_NUMBER_OF_SHARDS_SETTING .getKey (), 1 )
331331 .put (IndexMetadata .INDEX_NUMBER_OF_REPLICAS_SETTING .getKey (), 1 )
332332 // if the node with the replica is the first to be restarted, while a replica is still recovering
333- // then delayed allocation will kick in. When the node comes back, the master will search for a copy
333+ // then delayed allocation will kick in. When the node comes back, the cluster-manager will search for a copy
334334 // but the recovering copy will be seen as invalid and the cluster health won't return to GREEN
335335 // before timing out
336336 .put (INDEX_DELAYED_NODE_LEFT_TIMEOUT_SETTING .getKey (), "100ms" )
@@ -448,7 +448,7 @@ public void testRecoveryClosedIndex() throws Exception {
448448 .put (IndexMetadata .INDEX_NUMBER_OF_SHARDS_SETTING .getKey (), 1 )
449449 .put (IndexMetadata .INDEX_NUMBER_OF_REPLICAS_SETTING .getKey (), 1 )
450450 // if the node with the replica is the first to be restarted, while a replica is still recovering
451- // then delayed allocation will kick in. When the node comes back, the master will search for a copy
451+ // then delayed allocation will kick in. When the node comes back, the cluster-manager will search for a copy
452452 // but the recovering copy will be seen as invalid and the cluster health won't return to GREEN
453453 // before timing out
454454 .put (INDEX_DELAYED_NODE_LEFT_TIMEOUT_SETTING .getKey (), "100ms" )
0 commit comments