renamed a variable for clarity

Author: masseyke

server/src/main/java/org/elasticsearch/ingest/SamplingService.java

@@ -298,16 +298,16 @@ public void clusterChanged(ClusterChangedEvent event) {
                         .map(p -> (SamplingMetadata) p.custom(SamplingMetadata.TYPE))
                         .map(SamplingMetadata::getIndexToSamplingConfigMap)
                         .orElse(Map.of());
-                    Set<String> removedIndexNames = new HashSet<>(oldSampleConfigsMap.keySet());
-                    removedIndexNames.removeAll(newSampleConfigsMap.keySet());
+                    Set<String> indicesWithRemovedConfigs = new HashSet<>(oldSampleConfigsMap.keySet());
+                    indicesWithRemovedConfigs.removeAll(newSampleConfigsMap.keySet());
                     /*
                      * These index names no longer have sampling configurations associated with them. So we remove their samples. We are OK
                      * with the fact that we have a race condition here -- it is possible that in maybeSample() the configuration still
                      * exists but before the sample is read from samples it is deleted by this method and gets recreated. In the worst case
                      * we'll have a small amount of memory being used until the sampling configuration is recreated or the TTL checker
                      * reclaims it. The advantage is that we can avoid locking here, which could slow down ingestion.
                      */
-                    for (String indexName : removedIndexNames) {
+                    for (String indexName : indicesWithRemovedConfigs) {
                         logger.debug("Removing sample info for {} because its configuration has been removed", indexName);
                         samples.remove(new ProjectIndex(projectId, indexName));
                     }