-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Docs: Use single-node discovery.type for dev example #26289
Docs: Use single-node discovery.type for dev example #26289
Conversation
For the single node, dev example, the `discovery.type=single-node`[1] is a perfect fit and makes the example shorter and more self explanatory. [1] elastic#23595 [2] elastic#23598
cc @Jarpy |
@jasontedor are we ok with this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left a comment.
@@ -49,7 +49,7 @@ Elasticsearch can be quickly started for development or testing use with the fol | |||
|
|||
["source","sh",subs="attributes"] | |||
-------------------------------------------- | |||
docker run -p 9200:9200 -e "http.host=0.0.0.0" -e "transport.host=127.0.0.1" {docker-image} | |||
docker run -p 9200:9200 -e "discovery.type=single-node" {docker-image} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that the transport port should be published too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jasontedor Thanks for the review! This setting would be used only in the dev mode section of the elasticsearch docker documentation.
Since using this discovery.type doesn't allow clusters, what is the importance of setting the transport.tcp.port
or transport.publish_port
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A use-case is to test the usage of the transport client.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah I see you mean adding -p 9300:9300
right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jasontedor Addressed in 42f21a8
Exposing the transport port helps testing of the transport client. Relates: elastic#26289 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
For the single node, dev example, the
discovery.type=single-node
[1] isa perfect fit and makes the example shorter and more self explanatory.
[1] #23595
[2] #23598