maxmustermann/kibana
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
kibana/x-pack/plugins/cross_cluster_replication
History
CJ Cenizal ba4e0d259b
Migrate CCR to new ES JS client. (#100131) 
* Update SectionError component to render error root causes correctly.
* Fix 404 error rendering.
* Add test for follower index update API route.
2021-06-01 16:26:01 -07:00
..
common Elastic License 2.0 (#90099) 2021-02-03 18:12:39 -08:00
public Migrate CCR to new ES JS client. (#100131) 2021-06-01 16:26:01 -07:00
server Migrate CCR to new ES JS client. (#100131) 2021-06-01 16:26:01 -07:00
jest.config.js Elastic License 2.0 (#90099) 2021-02-03 18:12:39 -08:00
kibana.json Extract License service from CCR and Watcher into license_api_guard plugin in x-pack (#95973) 2021-04-15 14:54:49 -07:00
README.md Migrate CCR to new ES JS client. (#100131) 2021-06-01 16:26:01 -07:00
tsconfig.json Extract License service from CCR and Watcher into license_api_guard plugin in x-pack (#95973) 2021-04-15 14:54:49 -07:00

README.md

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. Ensure Kibana isn't running so it doesn't load up any data into your cluster. Run yarn es snapshot --license=trial to install a fresh snapshot. Wait for ES to finish setting up.
  2. Create a "remote" copy of your ES snapshot by running: cp -R .es/8.0.0 .es/8.0.0-2.
  3. Start your "remote" cluster by running .es/8.0.0-2/bin/elasticsearch -E cluster.name=europe -E transport.port=9400.
  4. Run yarn start to start Kibana.
  5. 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