Skip to content

[7.x] Allocate new indices on "hot" or "content" tier depending on data stream inclusion (#62338)#62557

Merged
dakrone merged 4 commits intoelastic:7.xfrom
dakrone:backport/7.x/pr-62338
Sep 17, 2020
Merged

[7.x] Allocate new indices on "hot" or "content" tier depending on data stream inclusion (#62338)#62557
dakrone merged 4 commits intoelastic:7.xfrom
dakrone:backport/7.x/pr-62338

Conversation

@dakrone
Copy link
Copy Markdown
Member

@dakrone dakrone commented Sep 17, 2020

Backports the following commits to 7.x:

…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
@elasticmachine
Copy link
Copy Markdown
Collaborator

Pinging @elastic/es-core-features (:Core/Features/Features)

@elasticmachine elasticmachine added the Team:Data Management (obsolete) DO NOT USE. This team no longer exists. label Sep 17, 2020
Transport clients can cause the role map to be reset back to the built in roles
@dakrone dakrone merged commit 9bb7ce0 into elastic:7.x Sep 17, 2020
@dakrone dakrone deleted the backport/7.x/pr-62338 branch September 17, 2020 19:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport Team:Data Management (obsolete) DO NOT USE. This team no longer exists. v7.10.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants