Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[CCR] Update README.md on how to start 2 clusters for testing #81487

Merged
merged 7 commits into from
Nov 2, 2020
Merged

[CCR] Update README.md on how to start 2 clusters for testing #81487

merged 7 commits into from
Nov 2, 2020

Conversation

yuliacech
Copy link
Contributor

Summary

When testing navigation issues in CCR, I noticed that the instructions in README.md no longer work to start 2 clusters locally.

  • Clusters need to be started with trial licensed activated
  • "Remote" cluster is not accepting the default password used in instructions

I could only make it work with a local Elasticsearch repository.

@yuliacech yuliacech requested a review from a team as a code owner October 22, 2020 14:17
@yuliacech yuliacech added Feature:CCR and Remote Clusters release_note:skip Skip the PR/issue when compiling release notes Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more v7.11.0 v8.0.0 labels Oct 22, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui (Team:Elasticsearch UI)

@yuliacech
Copy link
Contributor Author

@elasticmachine merge upstream

1 similar comment
@yuliacech
Copy link
Contributor Author

@elasticmachine merge upstream

@yuliacech
Copy link
Contributor Author

@elasticmachine merge upstream

alisonelizabeth
alisonelizabeth reviewed Oct 29, 2020
View reviewed changes
Copy link
Contributor

@alisonelizabeth alisonelizabeth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for updating this @yuliacech! I'm curious what changed to cause the expired license message now.

If you want to avoid downloading the ES repo, I think this would also work:

1. yarn es snapshot --license trial -E cluster.name="europe" -E http.port=9201 -E path.data=/tmp/es -E transport.port=9400
2. yarn es snapshot --license trial (in a separate tab)

Let me know what you think.

"Remote" cluster is not accepting the default password used in instructions

Can you explain this? It didn't look like the password was changed in the diff, but I might have missed it 😄 .

@yuliacech
Copy link
Contributor Author

@elasticmachine merge upstream

@yuliacech
Copy link
Contributor Author

Hi @alisonelizabeth , thanks a lot for your suggestion! I tested locally and indeed, it works with running yarn es snapshot in a separate tab for a "remote" cluster. I think the default password is now random, that is why it was not working for me when using the old command .es/8.0.0/bin/elasticsearch. When running yarn es, a keystore with a bootstrap password is used, I guess. (docs)

cjcenizal
cjcenizal reviewed Oct 30, 2020
View reviewed changes
x-pack/plugins/cross_cluster_replication/README.md Outdated
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"`.
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 source --license=trial -E cluster.name=europe -E transport.port=9400` in a separate terminal tab.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be worth noting here that the ES repo needs to be cloned into a sibling directory to Kibana, in order for this to work.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I actually missed this, I need to revert this command back to yarn es snapshot. I was able to run 2 clusters without the ES repo.

alisonelizabeth
alisonelizabeth approved these changes Oct 30, 2020
View reviewed changes
Copy link
Contributor

@alisonelizabeth alisonelizabeth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks for fixing this!

@yuliacech
Copy link
Contributor Author

@elasticmachine merge upstream

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@yuliacech yuliacech merged commit ff0e9e4 into elastic:master Nov 2, 2020
@yuliacech yuliacech mentioned this pull request Nov 2, 2020
Merged
yuliacech added a commit to yuliacech/kibana that referenced this pull request Nov 2, 2020
@yuliacech @kibanamachine
[CCR] Update README.md on how to start 2 clusters for testing (elasti…
b29312b 
…c#81487)

* Update Cross cluster replication README.md on how to start 2 Elasticsearch clusters for local testing.

* Update README.md for an easier CCR local testing setup

* Fix the command for a remote cluster

Co-authored-by: Kibana Machine <[email protected]>
phillipb added a commit to phillipb/kibana that referenced this pull request Nov 2, 2020
@phillipb
Merge branch 'master' of github.com:elastic/kibana into bootstrap-nod…
297c082 
…e-details-overlay

* 'master' of github.com:elastic/kibana: (72 commits)
  [CCR] Update README.md on how to start 2 clusters for testing (elastic#81487)
  [APM] Scale transaction rate correctly (elastic#82155)
  Upgrade to hapi version 18 (elastic#80468)
  [Uptime] Remove custom handling of license enabling (elastic#82019)
  [Telemetry] Remove `from` and `to` timestamps from usage stats APIs (elastic#81579)
  Enable send to background in Vega (elastic#82229)
  Enable send to background in Timelion (elastic#82232)
  [Actions & Connectors] removes Connector flyouts after usage (elastic#82126)
  Add derivative function (elastic#81178)
  [Discover] Deangularize context_app.html, part 3 (elastic#81838)
  [Visualize] Vis listing page breaks on unknown vis type (elastic#82018)
  Rename `batchSize` parameter to `batch_size` to be consisten with the API namings guidelines. (elastic#82123)
  Minor edits in Single Metric Viewer (elastic#82159)
  [Actions] Fix type contract (elastic#82168)
  Upgrade EUI to v30.1.1 (elastic#81499)
  Skip failing ES snapshot test (elastic#82207)
  Skip ES snapshot failing suite (elastic#82206)
  [Alerting UI] Grouped list of alert types using producers in Types filter of Alerts tab (elastic#81876)
  [Maps] convert vector style component to typescript round 1 (elastic#81961)
  Fix link to upgrade assistant (elastic#82138)
  ...
yuliacech added a commit that referenced this pull request Nov 2, 2020
@yuliacech @kibanamachine
[CCR] Update README.md on how to start 2 clusters for testing (#81487) (
2ad6513 
#82279)

* Update Cross cluster replication README.md on how to start 2 Elasticsearch clusters for local testing.

* Update README.md for an easier CCR local testing setup

* Fix the command for a remote cluster

Co-authored-by: Kibana Machine <[email protected]>

Co-authored-by: Kibana Machine <[email protected]>
@yuliacech yuliacech deleted the ccr_readme branch December 3, 2020 10:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@cjcenizal cjcenizal cjcenizal left review comments

@alisonelizabeth alisonelizabeth alisonelizabeth approved these changes

Assignees
No one assigned
Labels
Feature:CCR and Remote Clusters release_note:skip Skip the PR/issue when compiling release notes Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more v7.11.0 v8.0.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@yuliacech @elasticmachine @kibanamachine @cjcenizal @alisonelizabeth