Skip to content

Conversation

@edsavage
Copy link
Contributor

@edsavage edsavage commented Nov 5, 2025

Add a daily maintenance task to roll over .ml-state indices if the index size exceeds a configurable default size (default 50GB).

This replaces the previous method of using ILM to manage the state indices, as that was not a workable solution for serverless.

This builds on the work done in PR #136065 which provides similar functionality for results indices.

edsavage and others added 30 commits October 6, 2025 15:20
Add a rollover check for the AD results indices to the nightly ML maintenance task.

The concrete AD reults indices now have a six digit suffix. This is necessary to keep track of rollover behaviour and to determine which index is the "latest" in the series.

WIP
edsavage and others added 13 commits October 20, 2025 16:08
* Added the ability to set results_index_rollover_max_size to -1B to configure the nightly maintenance task not to trigger indices rollover
Add a daily maintenance task to roll over .ml-state indices if the index size exceeds a configurable default size (default 50GB).

This replaces the previous method of using ILM to manage the state indices, as that was not a workable solution for serverless.

This builds on the work done in PR elastic#136065 which provides similar functionality for results indices.
@elasticsearchmachine elasticsearchmachine added v9.3.0 needs:triage Requires assignment of a team area label labels Nov 5, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Nov 5, 2025

@github-actions
Copy link
Contributor

github-actions bot commented Nov 5, 2025

ℹ️ Important: Docs version tagging

👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version.

We use applies_to tags to mark version-specific features and changes.

Expand for a quick overview

When to use applies_to tags:

✅ At the page level to indicate which products/deployments the content applies to (mandatory)
✅ When features change state (e.g. preview, ga) in a specific version
✅ When availability differs across deployments and environments

What NOT to do:

❌ Don't remove or replace information that applies to an older version
❌ Don't add new information that applies to a specific version without an applies_to tag
❌ Don't forget that applies_to tags can be used at the page, section, and inline level

🤔 Need help?

@edsavage edsavage marked this pull request as draft November 5, 2025 03:58
@edsavage edsavage added >enhancement :ml Machine learning and removed needs:triage Requires assignment of a team area label labels Nov 5, 2025
@elasticsearchmachine
Copy link
Collaborator

Hi @edsavage, I've created a changelog YAML for you.

Add a daily maintenance task to roll over .ml-state indices if the index size exceeds a configurable default size (default 50GB).

This replaces the previous method of using ILM to manage the state indices, as that was not a workable solution for serverless.

This builds on the work done in PR elastic#136065 which provides similar functionality for results indices.

WIP
@edsavage edsavage closed this Nov 5, 2025
@edsavage edsavage deleted the manage_ad_state_indices branch November 5, 2025 22:54
@edsavage edsavage restored the manage_ad_state_indices branch November 5, 2025 22:56
@edsavage edsavage deleted the manage_ad_state_indices branch November 5, 2025 22:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants