iSharkFly-Docs
/
opensearch-docs-cn
mirror of https://github.com/iSharkFly-Docs/opensearch-docs-cn
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Few more I missed 

Signed-off-by: Liz Snyder <elizabsn@amazon.com>
This commit is contained in:
Liz Snyder 2022-01-18 11:23:16 -08:00
parent 1e198c0da9
commit f1e3686e81
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_replication-plugin/get-started.md
View File

@ -52,7 +52,7 @@ plugins.security.nodes_dn:
```
## Example setup
Save this sample file as `docker-compose.yml` and run `docker-compose up` to start two single-node clusters on the same network:
To start two single-node clusters on the same network, save this sample file as `docker-compose.yml` and run `docker-compose up`:
```yml
version: '3'

4
_replication-plugin/index.md
View File

@ -10,8 +10,8 @@ redirect_from:
# Cross-cluster replication
The cross-cluster replication plugin lets you replicate indexes, mappings, and metadata from one OpenSearch cluster to another. Cross-cluster replication has the following benefits:
- By replicating your indexes, you ensure that you can continue to handle search requests in the event of an outage.
- Replicating data across geographically distant data centers minimizes the distance between the data and the application server, reducing expensive latencies.
- By replicating your indexes, you ensure that you can continue to handle search requests if there's an outage.
- Replicating data across geographically distant data centers minimizes the distance between the data and the application server. This reduces expensive latencies.
- You can replicate data from multiple smaller clusters to a centralized reporting cluster, which is useful when it's inefficient to query across a large network.
Replication follows an active-passive model where the follower index (where the data is replicated) pulls data from the leader (remote) index.