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

Prohibit creation of rollup jobs in clusters that have never used rollup. #108381

Closed
martijnvg opened this issue May 7, 2024 · 3 comments · Fixed by #108624
Closed

Prohibit creation of rollup jobs in clusters that have never used rollup. #108381

martijnvg opened this issue May 7, 2024 · 3 comments · Fixed by #108624
Labels
:StorageEngine/Rollup Turn fine-grained time-based data into coarser-grained data Team:StorageEngine >tech debt

Comments

@martijnvg
Copy link
Member

martijnvg commented May 7, 2024

The rollup feature was never GA-ed and is still tech preview. It has been deprecated since 8.11.0 in favor of downsampling. At some point the rollup functionality will be removed. In order to prepare for the removal of rollup, the creation of rollup in clusters with no rollup usage will be prohibited. To avoid any new usages of rollup while it is scheduled to be removed.

@martijnvg martijnvg added :StorageEngine/Rollup Turn fine-grained time-based data into coarser-grained data >tech debt labels May 7, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-storage-engine (Team:StorageEngine)

martijnvg added a commit to martijnvg/elasticsearch that referenced this issue May 14, 2024
This change will add logic to the put rollup api that fails if no rollup job is active and no rollup index exists in the cluster.

The logic first check whether there is an active rollup persistent task if there are no active rollup persistent tasks, then it checks whether any rollup index exists. The latter check is an expensive check, but assuming that it only runs as part of the pu rollup job api and only when there are no rollup jobs, this should be ok.

All tests that invoke the pu rollup job api will need to be adjusted to create a dummy index that has rollup mapping metadata. Otherwise, tests can't create a rollup job.

Closes elastic#108381
@rayafratkina
Copy link

cc @alisonelizabeth

Do we want to do something in the Kibana management UI to prevent users from creating new rollup jobs?
Should we display some message in the UI about the upcoming deprecation?

martijnvg added a commit that referenced this issue May 21, 2024
This change will add logic to the put rollup api that fails if no rollup job is active and no rollup index exists in the cluster.

The logic first check whether there is an active rollup persistent task if there are no active rollup persistent tasks, then it checks whether any rollup index exists. The latter check is an expensive check, but assuming that it only runs as part of the put rollup job api and only when there are no rollup jobs, this should be ok.

All tests that invoke the put rollup job api will need to be adjusted to create a dummy index that has rollup mapping metadata. Otherwise, tests can't create a rollup job.

Closes #108381
@martijnvg
Copy link
Member Author

@rayafratkina Apologies for the late reply. Maybe my memory isn't correct, but I thought we already highlight that rollup is deprecated?

I think the UI should highlight that rollup is deprecated (if we haven't done already) and will be removed. Additionally I think it makes sense to warn users that creating a rollup job in an cluster with no rollup usage will fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:StorageEngine/Rollup Turn fine-grained time-based data into coarser-grained data Team:StorageEngine >tech debt
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants