Add steps for quickly testing to the READMEs of ILM, Rollup, and CCR.#67213
Add steps for quickly testing to the READMEs of ILM, Rollup, and CCR.#67213cjcenizal merged 3 commits intoelastic:masterfrom
Conversation
cjcenizal
added
chore
Feature:CCR and Remote Clusters
Feature:ILM
v8.0.0
Team:Kibana Management
|
Pinging @elastic/es-ui (Team:Elasticsearch UI) |
alisonelizabeth
left a comment
alisonelizabeth
left a comment
There was a problem hiding this comment.
Thanks for adding this @cjcenizal! This is really helpful. I went through all the steps and everything worked as expected. I left a couple nits, but nothing blocking.
| 3. Start your "local" cluster by running `.es/8.0.0/bin/elasticsearch` and starting Kibana. | ||
| 4. Start your "remote" cluster by running `.es/8.0.0-2/bin/elasticsearch -E cluster.name=europe -E transport.port=9400`. | ||
| 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). |
There was a problem hiding this comment.
Note that these settings are required for testing auto-follow pattern conflicts errors (see below)
I'm not sure what the "see below" is referring to. Should there be more information regarding testing conflict errors?
There was a problem hiding this comment.
Whoops, copy/pasta from #62890. I'll incorporate the information referenced in that PR description. Thanks for catching this!
| * Install sample data (web logs is a good one). | ||
| * Create a rollup job with an index pattern that captures this index (e.g. `k*`). | ||
| * Set frequency to "minute". Clear the latency buffer field. | ||
| * Select the time field which is the same time field selected in the installed index pattern (`timestamp` without an `@` in the case of web logs). |
There was a problem hiding this comment.
Do you think it's worth mentioning the "Time bucket size" field is required?
There was a problem hiding this comment.
Good idea! Will update.
|
CC @nickpeihl I'm adding this info per a conversation you and I had a couple weeks ago. |
4 participants
No description provided.