honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-02-18 19:05:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove extraneous spaces from CCR getting started

Browse Source 
This commit removes some extraneous spaces that were committed to the
cross-cluster replication getting started docs.
This commit is contained in:
Jason Tedor 2018-11-13 06:48:56 -05:00
parent 92fef40dbf
commit cbb16d5ffc
No known key found for this signature in database
GPG Key ID: FA89F05560F16BC5
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/reference/ccr/getting-started.asciidoc
View File

@ -24,7 +24,7 @@ This getting-started guide for {ccr} shows you how to:
https://www.elastic.co/subscriptions[subscriptions] and https://www.elastic.co/subscriptions[subscriptions] and
<<license-management>>. <<license-management>>.
. If the Elastic {security-features} are enabled in your local and remote . 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 clusters, you need a user that has appropriate authority to perform the steps
in this tutorial. in this tutorial.
+ +
@ -40,7 +40,7 @@ see <<security-getting-started>>.
If you are performing these steps in a production environment, take extra care 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 because the `elastic` user has the `superuser` role and you could inadvertently
make significant changes. make significant changes.
Alternatively, you can assign the appropriate privileges to a user ID of your Alternatively, you can assign the appropriate privileges to a user ID of your
choice. On the remote cluster that contains the leader index, a user will need choice. On the remote cluster that contains the leader index, a user will need
@ -87,7 +87,7 @@ privilege.
[[ccr-getting-started-remote-cluster]] [[ccr-getting-started-remote-cluster]]
=== Connecting to a remote cluster === Connecting to a remote cluster
The {ccr} features require that you The {ccr} features require that you
{ref}/modules-remote-clusters.html[connect your local cluster to a remote {ref}/modules-remote-clusters.html[connect your local cluster to a remote
cluster]. In this tutorial, we will connect our local cluster to a remote cluster]. In this tutorial, we will connect our local cluster to a remote
cluster with the cluster alias `leader`. cluster with the cluster alias `leader`.
@ -113,7 +113,7 @@ PUT /_cluster/settings
// TEST[setup:host] // TEST[setup:host]
// TEST[s/127.0.0.1:9300/\${transport_host}/] // TEST[s/127.0.0.1:9300/\${transport_host}/]
<1> Specifies the hostname and transport port of a seed node in the remote <1> Specifies the hostname and transport port of a seed node in the remote
cluster. cluster.
You can verify that the local cluster is successfully connected to the remote You can verify that the local cluster is successfully connected to the remote
cluster. cluster.
@ -274,7 +274,7 @@ POST /server-metrics-copy/_ccr/unfollow
[[ccr-getting-started-auto-follow]] [[ccr-getting-started-auto-follow]]
=== Automatically create follower indices === Automatically create follower indices
The auto-follow feature in {ccr} helps for time series use cases where you want The auto-follow feature in {ccr} helps for time series use cases where you want
to follow new indices that are periodically created in the remote cluster to follow new indices that are periodically created in the remote cluster
(such as daily Beats indices). Auto-following is configured using the (such as daily Beats indices). Auto-following is configured using the
{ref}/ccr-put-auto-follow-pattern.html[create auto-follow pattern API]. With an {ref}/ccr-put-auto-follow-pattern.html[create auto-follow pattern API]. With an