Skip to content

Conversation

@ywelsch
Copy link
Contributor

@ywelsch ywelsch commented May 23, 2019

in order for it to be removed in 8.0

@ywelsch ywelsch added >non-issue :Core/Infra/Core Core issues without another label v7.3.0 labels May 23, 2019
@ywelsch ywelsch requested a review from DaveCTurner May 23, 2019 08:11
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

Copy link
Contributor

@DaveCTurner DaveCTurner left a comment

Choose a reason for hiding this comment

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

LGTM

@ywelsch
Copy link
Contributor Author

ywelsch commented May 23, 2019

@elasticmachine run elasticsearch-ci/bwc

@ywelsch ywelsch merged commit f57fdc5 into elastic:7.x May 23, 2019
pull bot pushed a commit to scher200/elasticsearch that referenced this pull request May 23, 2019
This setting, which prior to Elasticsearch 5 was enabled by default and caused all kinds of
confusion, has since been disabled by default and is not recommended for production use. The
preferred way going forward is for users to explicitly specify separate data folders for each started
node to ensure that each node is consistently assigned to the same data path.

Relates to elastic#42426
gurkankaymak pushed a commit to gurkankaymak/elasticsearch that referenced this pull request May 27, 2019
This setting, which prior to Elasticsearch 5 was enabled by default and caused all kinds of
confusion, has since been disabled by default and is not recommended for production use. The
preferred way going forward is for users to explicitly specify separate data folders for each started
node to ensure that each node is consistently assigned to the same data path.

Relates to elastic#42426
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Core/Infra/Core Core issues without another label >non-issue v7.3.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants