You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: server/src/main/java/org/elasticsearch/cluster/routing/allocation/shards/ShardsAvailabilityHealthIndicatorService.java
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -532,7 +532,7 @@ public void increment(
532
532
// computations to the maxAffectedResourcesCount. The main negative side effect of this is that
533
533
// we might miss some diagnoses. We are willing to take this risk, and users can always
534
534
// use the allocation explain API for more details or increase the maxAffectedResourcesCount.
535
-
// Since we have two `SharAllocationCounts` instances (primaries and replicas), we technically
535
+
// Since we have two ShardAllocationCounts instances (primaries and replicas), we technically
536
536
// do 2 * maxAffectedResourcesCount computations, but the added complexity of accurately
537
537
// limiting the number of calls doesn't outweigh the benefits, as the main goal is to limit
538
538
// the number of computations to a constant rather than a number that grows with the cluster size.
@@ -543,7 +543,7 @@ public void increment(
543
543
}
544
544
caseINITIALIZING -> {
545
545
initializing++;
546
-
if (verbose && initializing <= maxAffectedResourcesCount) {
0 commit comments