Skip to content

Commit 1270365

Browse files
Update troubleshoot/elasticsearch/high-cpu-usage.md
Co-authored-by: shainaraskas <[email protected]>
1 parent 2890ffb commit 1270365

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

troubleshoot/elasticsearch/high-cpu-usage.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ If your Elasticsearch cluster contains a large number of shards, you might be fa
107107

108108
Oversharding occurs when there are too many shards, causing each shard to be smaller than optimal. While Elasticsearch doesn’t have a strict minimum shard size, an excessive number of small shards can negatively impact performance. Each shard consumes cluster resources since Elasticsearch must maintain metadata and manage shard states across all nodes.
109109

110-
If you have too many small shards, you can address this by:
110+
If you have too many small shards, you can address this by doing the following:
111111

112112
* Removing empty or unused indices.
113113
* Deleting or closing indices containing outdated or unnecessary data.

0 commit comments

Comments
 (0)