Changes

Tim-Brooks · Jul 20, 2020 · 692053a · 692053a
1 parent 0daf58f
commit 692053a
Show file tree

Hide file tree

Showing 2 changed files with 11 additions and 12 deletions.
diff --git a/docs/reference/cluster/nodes-stats.asciidoc b/docs/reference/cluster/nodes-stats.asciidoc
@@ -2121,7 +2121,7 @@ Contains statistics for the cumulative indexing load since the node started.
 (integer)
 Bytes consumed by indexing requests in the coordinating or primary stage. This
 value is not the sum of coordinating_bytes and primary_bytes as a node can reuse
-the coordinating bytes if the primary is executed locally.
+the coordinating bytes if the primary stage is executed locally.
 
 `coordinating_bytes`::
 (integer)

diff --git a/docs/reference/index-modules/indexing-pressure.asciidoc b/docs/reference/index-modules/indexing-pressure.asciidoc
@@ -1,19 +1,18 @@
 [[index-modules-indexing-pressure]]
 == Indexing pressure
 
-Indexing documents into Elasticsearch introduces system load in the form of
-memory and CPU load. Each indexing operation includes coordinating, primary, and
-replica stages. These stages can be performed across multiple nodes in the
-cluster. If too much indexing work is introduced into the system, the cluster
-can become saturated. This can adversely impact other components of the system
-such as searches, cluster coordination, background processing, etc.
+Indexing documents into {es} introduces system load in the form of memory and
+CPU load. Each indexing operation includes coordinating, primary, and replica
+stages. These stages can be performed across multiple nodes in a cluster.
 
-Indexing pressure is primarily generated by external operations such as indexing
-requests or internally by mechanisms such recoveries and cross-cluster
-replication.
+Indexing pressure can build up through external operations, such as indexing
+requests, or internal mechanisms, such as recoveries and {ccr}. If too much
+indexing work is introduced into the system, the cluster can become saturated.
+This can adversely impact other operations, such as search, cluster
+coordination, and background processing.
 
-Elasticsearch internally monitors indexing load. When the load exceeds
-certain limits, new indexing work will be rejected.
+To prevent these issues, {es} internally monitors indexing load. When the load
+exceeds certain limits, new indexing work is rejected
 
 [discrete]
 [[indexing-stages]]