# Logstash throttling/caching **URL:** \ **Category:** Logstash\ **Created:** [July 6, 2017, 12:18pm UTC](https://discuss.elastic.co/t/logstash-throttling-caching/92095 "2017-07-06T12:18:37Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![dandrestor](https://avatars.discourse-cdn.com/v4/letter/d/7cd45c/32.png) [@dandrestor](https://discuss.elastic.co/u/dandrestor)\ **Post date:** [July 6, 2017, 12:18pm UTC](https://discuss.elastic.co/t/logstash-throttling-caching/92095/1 "2017-07-06T12:18:37Z")
Hello, I'm using Logstash with a `pipe` input and an `elasticsearch` output. I know that my ES cluster has had availability problems recently. There were _brief_ periods when the cluster was unavailable, and I want to ascertain if events were lost. In the logstash logs I can see stuff like the following: > [2017-07-06T02:15:08,696][INFO][logstash.outputs.elasticsearch] retrying failed action with response code: 429 ({"type"=\>"es\_rejected\_execution\_exception", "reason"=\>"rejected execution of org.elasticsearch.transport.TransportService$6@151e135d on EsThreadPoolExecutor[bulk, queue capacity = 50, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@5e1ca942[Running, pool size = 6, active threads = 6, queued tasks = 50, completed tasks = 10293316]]"}) > [2017-07-06T02:15:08,696][ERROR][logstash.outputs.elasticsearch] Retrying individual actions > [2017-07-06T02:15:08,696][ERROR][logstash.outputs.elasticsearch] Action There is no other event like "retried action was dropped, too many retries". However, I'm not sure what this means - is the retry successful, at some point, or is the data lost? Thanks! Dan ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [July 9, 2017, 7:25pm UTC](https://discuss.elastic.co/t/logstash-throttling-caching/92095/2 "2017-07-09T19:25:44Z")
I think you can assume that the events eventually reached ES, unless you restarted Logstash while events were still in flight (_unless_ you also enabled the rather new persistent queue feature). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 6, 2017, 7:25pm UTC](https://discuss.elastic.co/t/logstash-throttling-caching/92095/3 "2017-08-06T19:25:58Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.