diff --git a/docs/reference/ccr/auto-follow.asciidoc b/docs/reference/ccr/auto-follow.asciidoc index a7f4b95f42202..830cd6527c2be 100644 --- a/docs/reference/ccr/auto-follow.asciidoc +++ b/docs/reference/ccr/auto-follow.asciidoc @@ -1,7 +1,7 @@ [role="xpack"] [testenv="platinum"] [[ccr-auto-follow]] -=== Automatically following indices +== Automatically following indices beta[] @@ -12,7 +12,7 @@ functionality in {ccr} is aimed at easing this burden. With the auto-follow functionality, you can specify that new indices in a remote cluster that have a name that matches a pattern are automatically followed. -==== Managing auto-follow patterns +=== Managing auto-follow patterns You can add a new auto-follow pattern configuration with the {ref}/ccr-put-auto-follow-pattern.html[create auto-follow pattern API]. When you create diff --git a/docs/reference/ccr/getting-started.asciidoc b/docs/reference/ccr/getting-started.asciidoc index d9684a38762b2..0ca42859fbe9f 100644 --- a/docs/reference/ccr/getting-started.asciidoc +++ b/docs/reference/ccr/getting-started.asciidoc @@ -22,7 +22,7 @@ This getting-started guide for {ccr} shows you how to: . Obtain a license that includes the {ccr} features. See https://www.elastic.co/subscriptions[subscriptions] and - <>. + {stack-ov}/license-management.html[License-management]. . If the Elastic {security-features} are enabled in your local and remote clusters, you need a user that has appropriate authority to perform the steps @@ -36,7 +36,7 @@ to control which users have authority to manage {ccr}. By default, you can perform all of the steps in this tutorial by using the built-in `elastic` user. However, a password must be set for this user before the user can do anything. For information about how to set that password, -see <>. +see {stack-ov}/security-getting-started.html[Tutorial: Getting started with security]. If you are performing these steps in a production environment, take extra care because the `elastic` user has the `superuser` role and you could inadvertently diff --git a/docs/reference/ccr/index.asciidoc b/docs/reference/ccr/index.asciidoc index 1fb9f8661b86f..dfa061f1557db 100644 --- a/docs/reference/ccr/index.asciidoc +++ b/docs/reference/ccr/index.asciidoc @@ -3,9 +3,6 @@ [[xpack-ccr]] = {ccr-cap} -[partintro] --- - beta[] The {ccr} (CCR) feature enables replication of indices in remote clusters to a @@ -23,7 +20,6 @@ This guide provides an overview of {ccr}: * <> * <> --- include::overview.asciidoc[] include::requirements.asciidoc[] diff --git a/docs/reference/ccr/requirements.asciidoc b/docs/reference/ccr/requirements.asciidoc index 877ac9cac7153..562120b99114d 100644 --- a/docs/reference/ccr/requirements.asciidoc +++ b/docs/reference/ccr/requirements.asciidoc @@ -1,7 +1,7 @@ [role="xpack"] [testenv="platinum"] [[ccr-requirements]] -=== Requirements for leader indices +== Requirements for leader indices beta[] @@ -28,7 +28,7 @@ enabled. [float] [[ccr-overview-soft-deletes]] -==== Soft delete settings +=== Soft delete settings `index.soft_deletes.enabled`:: @@ -46,7 +46,7 @@ For more information about index settings, see {ref}/index-modules.html[Index mo [float] [[ccr-overview-beats]] -==== Setting soft deletes on indices created by APM Server or Beats +=== Setting soft deletes on indices created by APM Server or Beats If you want to replicate indices created by APM Server or Beats, and are allowing APM Server or Beats to manage index templates, you need to enable @@ -68,7 +68,7 @@ index template. [float] [[ccr-overview-logstash]] -==== Setting soft deletes on indices created by Logstash +=== Setting soft deletes on indices created by Logstash If you want to replicate indices created by Logstash, and are using Logstash to manage index templates, you need to configure soft deletes on a custom Logstash diff --git a/docs/reference/high-availability.asciidoc b/docs/reference/high-availability.asciidoc new file mode 100644 index 0000000000000..2fdeb535aaf22 --- /dev/null +++ b/docs/reference/high-availability.asciidoc @@ -0,0 +1,33 @@ +[[high-availability]] += Set up a cluster for high availability + +[partintro] +-- +As with any software that stores data, +it is important to routinely back up your data. +{es}'s <> provide high availability +during runtime; +they enable you to tolerate sporadic node loss +without an interruption of service. + +However, replica shards do not protect an {es} cluster +from catastrophic failure. +You need a backup of your cluster— +a copy in case something goes wrong. + + +{es} offers two features to support high availability for a cluster: + +* <>, +which you can use to back up individual indices or entire clusters. +You can automatically store these backups in a repository on a shared filesystem. + +* <>, +which you can use to copy indices in remote clusters to a local cluster. +You can use {ccr} to recover from the failure of a primary cluster +or serve data locally based on geo-proximity. +-- + +:leveloffset: +1 +include::ccr/index.asciidoc[] +:leveloffset: -1 diff --git a/docs/reference/index.asciidoc b/docs/reference/index.asciidoc index d76fa2f2bb310..bfb9dce1f16de 100644 --- a/docs/reference/index.asciidoc +++ b/docs/reference/index.asciidoc @@ -59,12 +59,12 @@ include::monitoring/index.asciidoc[] include::rollup/index.asciidoc[] +include::high-availability.asciidoc[] + include::{xes-repo-dir}/security/index.asciidoc[] include::{xes-repo-dir}/watcher/index.asciidoc[] -include::rest-api/index.asciidoc[] - include::commands/index.asciidoc[] :edit_url: @@ -74,6 +74,8 @@ include::testing.asciidoc[] include::glossary.asciidoc[] +include::rest-api/index.asciidoc[] + include::release-notes/highlights.asciidoc[] include::migration/index.asciidoc[] diff --git a/docs/reference/redirects.asciidoc b/docs/reference/redirects.asciidoc index b76f0fc6d8128..0727dcf116756 100644 --- a/docs/reference/redirects.asciidoc +++ b/docs/reference/redirects.asciidoc @@ -558,4 +558,4 @@ See <>. [role="exclude",id="es-monitoring"] === Monitoring {es} -See <>. \ No newline at end of file +See <>.