Skip to content

Commit 6cf3c5d

Browse files
authored
Merge pull request #23426 from mburke5678/logging-es-storage
Add note on long term index storage
2 parents 3f07da9 + 7090048 commit 6cf3c5d

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

modules/cluster-logging-about-elasticsearch.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,14 +3,16 @@
33
// * logging/cluster-logging.adoc
44

55
[id="cluster-logging-about-elasticsearch_{context}"]
6-
= About the logstore
6+
= About the log store
77

88
{product-title} uses link:https://www.elastic.co/products/elasticsearch[Elasticsearch (ES)] to organize the log data from Fluentd into datastores, or _indices_.
99

1010
Elasticsearch subdivides each index into multiple pieces called _shards_, which it spreads across a set of Elasticsearch nodes in an Elasticsearch cluster.
1111
You can configure Elasticsearch to make copies of the shards, called _replicas_. Elasticsearch also spreads these replicas across
1212
the Elasticsearch nodes. The *ClusterLogging* Custom Resource (CR) allows you to specify the replication policy to provide data redundancy and resilience to failure. You can also define how long indices should be retained using a retention policy in the Cluster Logging CR.
1313

14+
The cluster logging Elasticsearch instance is optimized and tested for short term storage of approximately seven days. If you want to retain your logs over a longer term, it is recommended that you move the data to a third-party storage system.
15+
1416
[NOTE]
1517
====
1618
The number of primary shards for the index templates is equal to the number of Elasticsearch data nodes.

0 commit comments

Comments
 (0)