# Preventing / Throttling of excessive document spam from buggy forwarding agent / service

**URL:** <https://discuss.elastic.co/t/preventing-throttling-of-excessive-document-spam-from-buggy-forwarding-agent-service/235100>\
**Category:** Elasticsearch\
**Created:** [June 1, 2020, 1:20am UTC](https://discuss.elastic.co/t/preventing-throttling-of-excessive-document-spam-from-buggy-forwarding-agent-service/235100 "2020-06-01T01:20:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dandy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dandy/32/16643_2.png) [@Dandy](https://discuss.elastic.co/u/Dandy)\
**Post date:** [June 1, 2020, 1:20am UTC](https://discuss.elastic.co/t/preventing-throttling-of-excessive-document-spam-from-buggy-forwarding-agent-service/235100/1 "2020-06-01T01:20:38Z")

</div>

I have a scenario where a buggy service spammed about 3,000x more logs then expected and basically caused a massive cascading issue where document bulk tasks were taking 20minutes+ to process and incoming logs were just completely delayed as a result.

I am wondering, does ES have a mechanism wherein we can throttle services to X docs at a time per index even if that is something that is manually ran as a result, is there an API to do this?

Would closing an index effective kill existing write tasks and reject future documents trying to write to that index?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 29, 2020, 1:20am UTC](https://discuss.elastic.co/t/preventing-throttling-of-excessive-document-spam-from-buggy-forwarding-agent-service/235100/2 "2020-06-29T01:20:42Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.