Skip to content

[DOCS] Update node descriptions for default distribution #42812

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

Merged
merged 3 commits into from
Jun 13, 2019

Conversation

lcawl
Copy link
Contributor

@lcawl lcawl commented Jun 3, 2019

This PR updates https://www.elastic.co/guide/en/elasticsearch/reference/master/modules-node.html such that it's clearer that the initial examples don't apply to the default distribution.

It requires elastic/docs#917

It also cleans up some outstanding disparities in the dedicated node definitions related to #25210

@lcawl lcawl added >docs General docs changes :Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) v8.0.0 v7.2.0 v7.0.2 v7.3.0 v6.8.1 v7.1.2 labels Jun 3, 2019
@lcawl lcawl requested a review from pmusa June 3, 2019 17:57
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

Copy link
Contributor

@pmusa pmusa left a comment

Choose a reason for hiding this comment

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

I am not sure I am the right person to review this PR. From my understanding we were avoiding using the term x-pack, specially in the context of installing. The sentences are weird because x-pack is a gray area. You can use ML in basic (There is the data visualizer and import data though). Maybe calling out that the node.ml setting should not be used in the OSS version.

@@ -131,8 +132,9 @@ cluster.remote.connect: false <4>
<4> Disable {ccs} (enabled by default).

ifdef::include-xpack[]
NOTE: These settings apply only when {xpack} is not installed. To create a
dedicated data node when {xpack} is installed, see <<modules-node-xpack,{xpack} node settings>>.
NOTE: By default, when you install {es}, {xpack} is installed.These settings
Copy link
Contributor

Choose a reason for hiding this comment

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

it is missing a space after installed.

@@ -159,8 +161,9 @@ cluster.remote.connect: false <4>
<4> Disable {ccs} (enabled by default).

ifdef::include-xpack[]
NOTE: These settings apply only when {xpack} is not installed. To create a
dedicated ingest node when {xpack} is installed, see <<modules-node-xpack,{xpack} node settings>>.
NOTE: By default, when you install {es}, {xpack} is installed.These settings
Copy link
Contributor

Choose a reason for hiding this comment

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

same here.

@lcawl lcawl added the WIP label Jun 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) >docs General docs changes v6.8.1 v7.0.2 v7.1.2 v7.2.0 v7.3.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants