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

Watcher: Decouple history index cleaning from monitoring #32041

Closed
spinscale opened this issue Jul 13, 2018 · 4 comments
Closed

Watcher: Decouple history index cleaning from monitoring #32041

spinscale opened this issue Jul 13, 2018 · 4 comments

Comments

@spinscale
Copy link
Contributor

spinscale commented Jul 13, 2018

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.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@JalehD
Copy link

JalehD commented Dec 12, 2018

@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 🗡

@JalehD
Copy link

JalehD commented Dec 12, 2018

@elastic/cloud-pms FYI

@jakelandis jakelandis added the :Data Management/ILM+SLM Index and Snapshot lifecycle management label Dec 17, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

@talevy talevy self-assigned this Jan 2, 2019
@dakrone dakrone self-assigned this Jan 9, 2019
@talevy talevy removed their assignment Jan 9, 2019
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 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
Projects
None yet
Development

No branches or pull requests

8 participants