From 69f7b32aba1ccec59aa2274a5dc3de2e25e3cfb6 Mon Sep 17 00:00:00 2001 From: Ian Lee Date: Fri, 3 Jan 2025 16:28:17 -0800 Subject: [PATCH] Update rejected-requests.asciidoc I believe this is a typo, as in our 8.16.1 cluster this field appears to be called `combined_coordinating_and_primary` --- .../troubleshooting/common-issues/rejected-requests.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/troubleshooting/common-issues/rejected-requests.asciidoc b/docs/reference/troubleshooting/common-issues/rejected-requests.asciidoc index 34ef388f2e3c9..83f6962a219ef 100644 --- a/docs/reference/troubleshooting/common-issues/rejected-requests.asciidoc +++ b/docs/reference/troubleshooting/common-issues/rejected-requests.asciidoc @@ -69,7 +69,7 @@ These stats are cumulative from node startup. Indexing pressure rejections appear as an `EsRejectedExecutionException`, and indicate that they were rejected due -to `coordinating_and_primary_bytes`, `coordinating`, `primary`, or `replica`. +to `combined_coordinating_and_primary`, `coordinating`, `primary`, or `replica`. These errors are often related to <>, <> sizing, or the ingest target's @@ -86,4 +86,4 @@ of diagnosing indexing pressure rejections. If {es} regularly rejects requests and other tasks, your cluster likely has high CPU usage or high JVM memory pressure. For tips, see <> and -<>. \ No newline at end of file +<>.