-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Watcher: Decouple history index cleaning from monitoring #32041
Comments
Pinging @elastic/es-core-infra |
@hub-cap can we revive this please, the issue of these indices not being cleaned gets magnified in cloud land. You can spin up a small cluster and it will auto destruct itself by filling up disk with watcher.history stuff 🗡 |
@elastic/cloud-pms FYI |
jakelandis
added
the
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
label
Dec 17, 2018
Pinging @elastic/es-core-features |
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this issue
Jan 14, 2019
This commit adds an index lifecycle policy for the `.watch-history-*` indices. This policy is automatically used for all new watch history indices. This does not yet remove the automatic cleanup that the monitoring plugin does for the .watch-history indices, and it does not touch the `xpack.watcher.history.cleaner_service.enabled` setting. Relates to elastic#32041
dakrone
added a commit
that referenced
this issue
Jan 23, 2019
* Use ILM for Watcher history deletion This commit adds an index lifecycle policy for the `.watch-history-*` indices. This policy is automatically used for all new watch history indices. This does not yet remove the automatic cleanup that the monitoring plugin does for the .watch-history indices, and it does not touch the `xpack.watcher.history.cleaner_service.enabled` setting. Relates to #32041
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this issue
Jan 23, 2019
This deprecates the `xpack.watcher.history.cleaner_service.enabled` setting, since all newly created `.watch-history` indices in 7.0 will use ILM to manage their retention. In 8.0 the setting itself and cleanup actions will be removed. Resolves elastic#32041
dakrone
added a commit
that referenced
this issue
Jan 24, 2019
This deprecates the `xpack.watcher.history.cleaner_service.enabled` setting, since all newly created `.watch-history` indices in 7.0 will use ILM to manage their retention. In 8.0 the setting itself and cleanup actions will be removed. Resolves #32041
jimczi
removed
the
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
label
Feb 11, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Monitoring has a
xpack.watcher.history.cleaner_service.enabled
setting to clean out old watcher history index settings.This setting should be correctly parsed on the watcher side of things and also work properly if monitoring is disabled, probably by just switching to ILM soon.
The text was updated successfully, but these errors were encountered: