From d934c8cc9672d944d4a4eae3d242403d8d563cd6 Mon Sep 17 00:00:00 2001 From: Gidi Meir Morris Date: Wed, 3 Mar 2021 18:50:15 +0000 Subject: [PATCH] removed unneeded newline --- .../task-manager-troubleshooting.asciidoc | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/user/production-considerations/task-manager-troubleshooting.asciidoc b/docs/user/production-considerations/task-manager-troubleshooting.asciidoc index d19a28cf04f9..5c67c8076b62 100644 --- a/docs/user/production-considerations/task-manager-troubleshooting.asciidoc +++ b/docs/user/production-considerations/task-manager-troubleshooting.asciidoc @@ -468,7 +468,6 @@ For details on achieving higher throughput by adjusting your scaling strategy, s Tasks run for too long, overrunning their schedule *Diagnosis*: - The <> theory analyzed a hypothetical scenario where both _drift_ and _load_ were unusually high. 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 Tasks take multiple attempts to succeed *Diagnosis*: - 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. Evaluating the health stats above, we can see the following output under `stats.runtime.value.execution.result_frequency_percent_as_number`: