Allocate new indices on "hot" or "content" tier depending on data stream inclusion #62338
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…eam inclusion This commit changes the default allocation on the "hot" tier to allocating the newly created index to the "hot" tier if it is part of a new or existing data stream, and to the "content" tier if it is not part of a data stream. Overriding any of the `index.routing.allocation.(include|exclude|require).*` settings continues to cause the initial allocation not to be set (no change in behavior). Relates to elastic#60848
|
Pinging @elastic/es-core-features (:Core/Features/Features) |
elasticmachine
added
the
Team:Data Management
18 tasks
andreidan
approved these changes
Sep 16, 2020
...plugin/core/src/test/java/org/elasticsearch/xpack/cluster/routing/allocation/DataTierIT.java
Outdated
Show resolved
Hide resolved
...plugin/core/src/test/java/org/elasticsearch/xpack/cluster/routing/allocation/DataTierIT.java
Show resolved
Hide resolved
andreidan
reviewed
Sep 16, 2020
...s/src/internalClusterTest/java/org/elasticsearch/xpack/datastreams/DataTierDataStreamIT.java
Outdated
Show resolved
Hide resolved
andreidan
reviewed
Sep 16, 2020
...s/src/internalClusterTest/java/org/elasticsearch/xpack/datastreams/DataTierDataStreamIT.java
Outdated
Show resolved
Hide resolved
|
@elasticmachine run elasticsearch-ci/packaging-sample-windows (CI timed out trying to download gradle) |
1 similar comment
|
@elasticmachine run elasticsearch-ci/packaging-sample-windows (CI timed out trying to download gradle) |
|
@elasticmachine update branch |
|
@elasticmachine update branch |
|
@elasticmachine update branch |
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this pull request
Sep 17, 2020
…eam inclusion (elastic#62338) This commit changes the default allocation on the "hot" tier to allocating the newly created index to the "hot" tier if it is part of a new or existing data stream, and to the "content" tier if it is not part of a data stream. Overriding any of the index.routing.allocation.(include|exclude|require).* settings continues to cause the initial allocation not to be set (no change in behavior). Relates to elastic#60848
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit changes the default allocation on the "hot" tier to allocating the newly created index
to the "hot" tier if it is part of a new or existing data stream, and to the "content" tier if it is
not part of a data stream.
Overriding any of the
index.routing.allocation.(include|exclude|require).*settings continues tocause the initial allocation not to be set (no change in behavior).
Relates to #60848