# Failed to execute pipeline for a bulk request but low CPU and memory **URL:** \ **Category:** Elasticsearch\ **Created:** [November 7, 2017, 3:10pm UTC](https://discuss.elastic.co/t/failed-to-execute-pipeline-for-a-bulk-request-but-low-cpu-and-memory/106710 "2017-11-07T15:10:00Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![xixo](https://avatars.discourse-cdn.com/v4/letter/x/e68b1a/32.png) [@xixo](https://discuss.elastic.co/u/xixo)\ **Post date:** [November 7, 2017, 3:10pm UTC](https://discuss.elastic.co/t/failed-to-execute-pipeline-for-a-bulk-request-but-low-cpu-and-memory/106710/1 "2017-11-07T15:10:00Z")
Hi everyone, I have a cluster with 3 dedicated masters and 17 data nodes. Several Logstash servers are sending events to the Elastic cluster using the load balancing provided by Logstash. I see this error in some elastic nodes: > [2017-11-07T15:01:41,740][ERROR][o.e.a.b.TransportBulkAction] [node08] failed to execute pipeline for a bulk request > org.elasticsearch.common.util.concurrent.EsRejectedExecutionException: rejected execution of org.elasticsearch.ingest.PipelineExecutionService$2@55d30f9a on EsThreadPoolExecutor[bulk, queue capacity = 200, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@2e2300f0[Running, pool size = 8, active threads = 8, queued tasks = 231, completed tasks = 17927703]] It looks like that elastic node is over its capacity, but the CPU, RAM and disk usage are not at 100%. Also, almost all nodes are under the 10% of CPU. Why I have queued tasks if there are available resources?. What is happening?. Thanks. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 5, 2017, 3:10pm UTC](https://discuss.elastic.co/t/failed-to-execute-pipeline-for-a-bulk-request-but-low-cpu-and-memory/106710/2 "2017-12-05T15:10:05Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.