Skip to content

Commit d934c8c

Browse files
committed
removed unneeded newline
1 parent bde118c commit d934c8c

1 file changed

Lines changed: 0 additions & 2 deletions

File tree

docs/user/production-considerations/task-manager-troubleshooting.asciidoc

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -468,7 +468,6 @@ For details on achieving higher throughput by adjusting your scaling strategy, s
468468
Tasks run for too long, overrunning their schedule
469469

470470
*Diagnosis*:
471-
472471
The <<task-manager-theory-insufficient-throughput,"Insufficient throughtput to handle the scheduled workload">> theory analyzed a hypothetical scenario where both _drift_ and _load_ were unusually high.
473472

474473
Suppose an alternate scenario, where `drift` is high, but `load` is not, such as the following:
@@ -536,7 +535,6 @@ In the hypothetical example above, most likely, this would be resolved by modify
536535
Tasks take multiple attempts to succeed
537536

538537
*Diagnosis*:
539-
540538
A high error rate could cause a task to appear to run late, when in fact it runs on time, but experiences a high failure rate.
541539

542540
Evaluating the health stats above, we can see the following output under `stats.runtime.value.execution.result_frequency_percent_as_number`:

0 commit comments

Comments
 (0)