kibana/x-pack/plugins/cross_cluster_replication
Tyler Smalley b593781009
Jest multi-project configuration (#77894)
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
2020-12-02 11:42:23 -08:00
..
common Update @typescript-eslint to ensure compatibility with TypeScript v3.9 (#74091) 2020-08-05 17:32:19 +02:00
public [CCR] Fix row actions in follower index and auto-follow pattern tables (#84433) 2020-12-01 21:37:56 +01:00
server Hide management sections based on cluster/index privileges (#67791) 2020-09-14 09:30:47 -04:00
jest.config.js Jest multi-project configuration (#77894) 2020-12-02 11:42:23 -08:00
kibana.json Hide management sections based on cluster/index privileges (#67791) 2020-09-14 09:30:47 -04:00
README.md [CCR] Update README.md on how to start 2 clusters for testing (#81487) 2020-11-02 14:30:19 +01:00

Cross-Cluster Replication

Quick steps for testing cross-cluster replication

You can run a local cluster and simulate a remote cluster within a single Kibana directory.

  1. Start your "local" cluster by running yarn es snapshot --license=trial and yarn start to start Kibana.
  2. Start your "remote" cluster by running yarn es snapshot --license=trial -E cluster.name=europe -E transport.port=9400 in a separate terminal tab.
  3. Index a document into your remote cluster by running curl -X PUT http://elastic:changeme@localhost:9201/my-leader-index --data '{"settings":{"number_of_shards":1,"soft_deletes.enabled":true}}' --header "Content-Type: application/json". Note that these settings are required for testing auto-follow pattern conflicts errors (see below).

Now you can create follower indices and auto-follow patterns to replicate the my-leader-index index on the remote cluster that's available at 127.0.0.1:9400.

Auto-follow pattern conflict errors

You can view conflict errors by creating two auto-follow patterns with overlapping patterns (e.g. my* and my-*) that will both capture the my-leader-index index on your remote cluster. Run the curl command to create my-leader-index2 on your remote cluster, since auto-follow patterns don't replicate existing indices.

Now, when you open the details flyout of one of the auto-follow patterns you will see a list of recent errors.

image