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

Docs: Use single-node discovery.type for dev example #26289

Merged

Conversation

dliappis
Copy link
Contributor

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] #23595
[2] #23598

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
@dliappis dliappis requested a review from jasontedor August 18, 2017 15:19
@dliappis
Copy link
Contributor Author

cc @Jarpy

@dliappis
Copy link
Contributor Author

dliappis commented Sep 5, 2017

@jasontedor are we ok with this?

Copy link
Member

@jasontedor jasontedor left a 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}
Copy link
Member

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.

Copy link
Contributor Author

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?

Copy link
Member

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.

Copy link
Contributor Author

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?

Copy link
Member

Choose a reason for hiding this comment

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

Yes.

Copy link
Contributor Author

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)
Copy link
Member

@jasontedor jasontedor left a comment

Choose a reason for hiding this comment

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

LGTM.

@dliappis dliappis merged commit b789ce7 into elastic:master Sep 15, 2017
dliappis added a commit that referenced this pull request Sep 15, 2017
For the single node, dev example, the `discovery.type=single-node`[1],[2] 
is a perfect fit and makes the example shorter and more self explanatory.

Also expose the transport port, to help with dev use-cases using the 
transport client.

[1] #23595
[2] #23598

Relates #26289
dliappis added a commit that referenced this pull request Sep 15, 2017
For the single node, dev example, the `discovery.type=single-node`[1],[2] 
is a perfect fit and makes the example shorter and more self explanatory.

Also expose the transport port, to help with dev use-cases using the 
transport client.

[1] #23595
[2] #23598

Relates #26289
dliappis added a commit that referenced this pull request Sep 15, 2017
For the single node, dev example, the `discovery.type=single-node`[1],[2] 
is a perfect fit and makes the example shorter and more self explanatory.

Also expose the transport port, to help with dev use-cases using the 
transport client.

[1] #23595
[2] #23598

Relates #26289
dliappis added a commit that referenced this pull request Sep 15, 2017
For the single node, dev example, the `discovery.type=single-node`[1],[2] 
is a perfect fit and makes the example shorter and more self explanatory.

Also expose the transport port, to help with dev use-cases using the 
transport client.

[1] #23595
[2] #23598

Relates #26289
dliappis added a commit that referenced this pull request Sep 15, 2017
For the single node, dev example, the `discovery.type=single-node`[1],[2] 
is a perfect fit and makes the example shorter and more self explanatory.

Also expose the transport port, to help with dev use-cases using the 
transport client.

[1] #23595
[2] #23598

Relates #26289
@dliappis
Copy link
Contributor Author

Backported to:

6.x: 53069c6
6.0: fefa691
5.6: fc49997
5.5: c251f75
5.4: f3a92b1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants