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

Add readonly action to hot phase #58289

Closed
JohnLyman opened this issue Jun 17, 2020 · 1 comment · Fixed by #64381
Closed

Add readonly action to hot phase #58289

JohnLyman opened this issue Jun 17, 2020 · 1 comment · Fixed by #64381
Assignees
Labels
:Data Management/ILM+SLM Index and Snapshot lifecycle management >enhancement Team:Data Management Meta label for data/management team

Comments

@JohnLyman
Copy link

Similar to #52073 and #56377, it would be desirable to make an index readonly immediately after rollover in the hot phase, before shrink or forcemerge. In no case do I ever want an index to be writeable after it is rolled over, and I would rather have it done as soon as possible. Obviously this only makes sense if there is an accompanying rollover action in the hot phase.

@JohnLyman JohnLyman added >enhancement needs:triage Requires assignment of a team area label labels Jun 17, 2020
@jimczi jimczi added :Data Management/ILM+SLM Index and Snapshot lifecycle management and removed needs:triage Requires assignment of a team area label labels Jun 18, 2020
@elasticmachine
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/ILM+SLM Index and Snapshot lifecycle management >enhancement Team:Data Management Meta label for data/management team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants