# Transform kills the whole cluster

**URL:** <https://discuss.elastic.co/t/transform-kills-the-whole-cluster/237294>\
**Category:** Elasticsearch\
**Created:** [June 16, 2020, 12:17pm UTC](https://discuss.elastic.co/t/transform-kills-the-whole-cluster/237294 "2020-06-16T12:17:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![liorg2](https://avatars.discourse-cdn.com/v4/letter/l/ed8c4c/32.png) [@liorg2](https://discuss.elastic.co/u/liorg2)\
**Post date:** [June 16, 2020, 12:17pm UTC](https://discuss.elastic.co/t/transform-kills-the-whole-cluster/237294/1 "2020-06-16T12:17:17Z")

</div>

Hi I'm using elastic cloud ([cloud.elastic.co](http://cloud.elastic.co))

I'm not sure if that's the correct category, but I want to run a transform for the past 6 month, and it's killing the cpu. the whole cluster becomes unresponsive (queries, kibana ..)

is there any option to tell the transform to run "slowly"..?  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/e/aed3b9e2d17288e6d8be64b66138a2e6748062d5.png)

---

<div class="post-metadata">

**Author:** ![Hendrik\_Muhs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hendrik_muhs/32/25802_2.png) [@Hendrik\_Muhs](https://discuss.elastic.co/u/Hendrik_Muhs)\
**Post date:** [June 16, 2020, 1:21pm UTC](https://discuss.elastic.co/t/transform-kills-the-whole-cluster/237294/2 "2020-06-16T13:21:15Z")

</div>

Unfortunately not yet, throttling will be part of `7.8`, check the `docs_per_second` [setting](https://www.elastic.co/guide/en/elasticsearch/reference/7.8/put-transform.html) in the docs.

I can not give you a date when `7.8` will be available, but it should not be far off.

---

<div class="post-metadata">

**Author:** ![liorg2](https://avatars.discourse-cdn.com/v4/letter/l/ed8c4c/32.png) [@liorg2](https://discuss.elastic.co/u/liorg2)\
**Post date:** [June 16, 2020, 2:46pm UTC](https://discuss.elastic.co/t/transform-kills-the-whole-cluster/237294/3 "2020-06-16T14:46:15Z")

</div>

ok, i'll run it at night for now. thanks you guys for your hard work

---

<div class="post-metadata">

**Author:** ![Hendrik\_Muhs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hendrik_muhs/32/25802_2.png) [@Hendrik\_Muhs](https://discuss.elastic.co/u/Hendrik_Muhs)\
**Post date:** [June 29, 2020, 8:25pm UTC](https://discuss.elastic.co/t/transform-kills-the-whole-cluster/237294/5 "2020-06-29T20:25:12Z")

</div>

It seems to me that your cluster has some general performance problems or is simply under-powered with this task.

To further analyze this problem it seems better to ask support.

Logging queries that `transform` does, is a good approach. You can take the query from the log and execute it in dev console and see how fast it performs there. I guess it will be slow, too.

Transform can only go as fast as aggregations + bulk indexing.

---

<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:** [July 27, 2020, 8:37pm UTC](https://discuss.elastic.co/t/transform-kills-the-whole-cluster/237294/6 "2020-07-27T20:37:48Z")

</div>

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