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.
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
Draw attention to transport port in remote cluster documentation #43858
Comments
Pinging @elastic/es-docs |
The documentation explicitly says that: |
@jimczi I admit I did somehow skipped going through the Do you mean something like adding another info point with the snippet (see attached picture)? I think that would is a good idea. I would be happy to send a patch but it would quite helpful for me if you could tell me where these docs reside (Elasticsearch docs code seems a bit overwhelming to me as a beginner 😅). Thanks for your quick reply! |
Yes, if you think it is helpful ;)
You can find this doc here. |
Pinging @elastic/es-distributed |
It would be nice to emphasize on the fact that remote cluster connections require another port (not the one Elasticsearch is usually available on).
I am not very clear on how these ports are different but after struggling a lot to set up a cross-cluster search I realised that Elasticsearch exposes port 9300 as well for some things and it is
9300
that needs to be mentioned in theseeds
.I do see that it is being used in the example here - https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-remote-clusters.html. But I didn't realise that
9300
was being used instead of9200
intentionally until I read this comment from Mr. javanna.The text was updated successfully, but these errors were encountered: