# Force logging-and-metrics cluster to run curator job **URL:** \ **Category:** Elastic Cloud Enterprise (ECE)\ **Created:** [April 18, 2019, 5:53am UTC](https://discuss.elastic.co/t/force-logging-and-metrics-cluster-to-run-curator-job/177401 "2019-04-18T05:53:48Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![JPT](https://avatars.discourse-cdn.com/v4/letter/j/58f4c7/32.png) [@JPT](https://discuss.elastic.co/u/JPT)\ **Post date:** [April 18, 2019, 5:53am UTC](https://discuss.elastic.co/t/force-logging-and-metrics-cluster-to-run-curator-job/177401/1 "2019-04-18T05:53:49Z")
Hello, we had the situation that our logging-and-metrics cluster get a lot of logs, because some trouble with a cluster. This than resulted in two of three nodes had 100% disk space usage. We tried to restart the cluster but afterwards only a bit more space was free. One node was still on 100% disk usage. So we decided to configure temporary a shorter retention rate: ``` ./elastic-cloud-enterprise.sh set-logging-and-metrics-policy --pattern service-logs-* --days 5 ./elastic-cloud-enterprise.sh set-logging-and-metrics-policy --pattern proxy-logs-* --days 5 ``` The problem was now that we had to wait for the automatic job to clean the older logs in the night. Setup: ECE 2.2 Now my question: Is there any possibility to manually trigger the retention clean-up job? It is very unsatisfying to wait for the job to run automatically. Thank you! Jan ---
**Author:** ![Yuri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuri/32/52458_2.png) [@Yuri](https://discuss.elastic.co/u/Yuri)\ **Post date:** [April 18, 2019, 1:33pm UTC](https://discuss.elastic.co/t/force-logging-and-metrics-cluster-to-run-curator-job/177401/2 "2019-04-18T13:33:03Z")
Hello @JPT, unfortunately that is not possible. However, you can delete indices by sending delete requests to the cluster (there is a handy tool in the admin console UI called Console API. It allows you to send requests to the cluster). Also, you can temporarily add more disk space to a particular node or set of nodes, via "override disk quota" ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/4/b40115f24f24dfbbdb4dd450852a579a18b1eac3.png) ---
**Author:** ![JPT](https://avatars.discourse-cdn.com/v4/letter/j/58f4c7/32.png) [@JPT](https://discuss.elastic.co/u/JPT)\ **Post date:** [April 23, 2019, 6:11am UTC](https://discuss.elastic.co/t/force-logging-and-metrics-cluster-to-run-curator-job/177401/3 "2019-04-23T06:11:09Z")
Hello Yuri, thank you for the explanation. The workaround with temporarily override the disk quota is useful. But deleting the indices manual is not satisfying, because the risk to make a mistake in a manual task is given. Will the behavior be different, when the loggin-and-metrics cluster will be on version 7? Could we then use the Console API to trigger the index lifecycle management? BR, Jan ---
**Author:** ![Yuri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuri/32/52458_2.png) [@Yuri](https://discuss.elastic.co/u/Yuri)\ **Post date:** [April 23, 2019, 8:53pm UTC](https://discuss.elastic.co/t/force-logging-and-metrics-cluster-to-run-curator-job/177401/4 "2019-04-23T20:53:52Z")
ECE 2.2 allows you to upgrade logging cluster. So, If you upgrade that cluster to a version (6.7.0+) that supports index lifetime management, you can use that feature but keep in mind that the curation embedded into ECE will still work too. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 7, 2019, 8:53pm UTC](https://discuss.elastic.co/t/force-logging-and-metrics-cluster-to-run-curator-job/177401/5 "2019-05-07T20:53:55Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.