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.

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

Closed
akki opened this issue Jul 2, 2019 · 6 comments
Closed

Draw attention to transport port in remote cluster documentation #43858

akki opened this issue Jul 2, 2019 · 6 comments
Labels
:Distributed/Network Http and internode communication implementations >docs General docs changes

Comments

@akki
Copy link
Contributor

akki commented Jul 2, 2019

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 the seeds.

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 of 9200 intentionally until I read this comment from Mr. javanna.

@jimczi jimczi added the >docs General docs changes label Jul 2, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-docs

@jimczi
Copy link
Contributor

jimczi commented Jul 2, 2019

It would be nice to emphasize on the fact that remote cluster connections require another port (not the one Elasticsearch is usually available on).

The documentation explicitly says that:
All the communication required between different clusters goes through the transport layer.
The linked documentation explains what the transport module is and how the communication is handle in this module. However I guess that it would help to repeat that the transport port should be used on the first mention of seeds in the snippet examples. Would you be interested to provide a patch for this ?

@akki
Copy link
Contributor Author

akki commented Jul 2, 2019

@jimczi I admit I did somehow skipped going through the transport layer link when it was mentioned in the docs.

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!

Remote_clusters___Elasticsearch_Reference__7_2____Elastic

@jimczi
Copy link
Contributor

jimczi commented Jul 2, 2019

Do you mean something like adding another info point with the snippet (see attached picture)? I think that would is a good idea.

Yes, if you think it is helpful ;)

I would be happy to send a patch but it would quite helpful for me if you could tell me where these docs reside

You can find this doc here.

@akki
Copy link
Contributor Author

akki commented Jul 2, 2019

@jimczi - #43883

@tlrx tlrx added the :Distributed/Network Http and internode communication implementations label Jul 3, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed/Network Http and internode communication implementations >docs General docs changes
Projects
None yet
Development

No branches or pull requests

4 participants