# Deployment down because of an ml job

**URL:** <https://discuss.elastic.co/t/deployment-down-because-of-an-ml-job/379712>\
**Category:** Elasticsearch\
**Created:** [July 2, 2025, 1:42pm UTC](https://discuss.elastic.co/t/deployment-down-because-of-an-ml-job/379712 "2025-07-02T13:42:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![vmesis](https://avatars.discourse-cdn.com/v4/letter/v/edb3f5/32.png) [@vmesis](https://discuss.elastic.co/u/vmesis)\
**Post date:** [July 2, 2025, 1:42pm UTC](https://discuss.elastic.co/t/deployment-down-because-of-an-ml-job/379712/1 "2025-07-02T13:42:06Z")

</div>

Hello everyone,  
Recently, I had an issue with my deployment. I create an outliner detection jobs and it run out of memory. However, before I could stop it or reconfigure it the deployment went down.

I already tried to load a precedent snapshot but kibana is also down so I cannot acces the "Snapshot & restore" and the request from the API console doesn't return anything except error.  
I've also tried to temporaly increase the RAM but the change failed.

I contacted the support team but I've only got an automatic response that it'll be look upon within 3 business day. I can't afford to wait this long so if anyone have a suggestion I'll gladly accept it !

Thank you for your understanding.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [July 2, 2025, 3:16pm UTC](https://discuss.elastic.co/t/deployment-down-because-of-an-ml-job/379712/2 "2025-07-02T15:16:25Z")

</div>

Hi @vmesis Welcome to the community.

Did you open the ticket as a Sev 1? I suspect you opened it as a Sev 3.

I would close that ticket and open an new Sev 1 Ticket with Cluster Down / Red in the Subject

I would not try to go straight to Snapshot and Restore, you cluster needs to be healthy before you could do that.

We are not support here so we can not really help with underlying deployment issues

---

<div class="post-metadata">

**Author:** ![vmesis](https://avatars.discourse-cdn.com/v4/letter/v/edb3f5/32.png) [@vmesis](https://discuss.elastic.co/u/vmesis)\
**Post date:** [July 2, 2025, 3:34pm UTC](https://discuss.elastic.co/t/deployment-down-because-of-an-ml-job/379712/3 "2025-07-02T15:34:42Z")

</div>

Hi @stephenb, thanks for your reply.  
Indeed, I opened it as a Sev 3 but not on purpose. I tried to open a case directly from the support page but the technical support button is grey and deactivated. I'll add that I have the subscription for this.  
So instead, I sent an email directly to the support and it have been put in Sev 3 automatically.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [July 2, 2025, 3:40pm UTC](https://discuss.elastic.co/t/deployment-down-because-of-an-ml-job/379712/4 "2025-07-02T15:40:33Z")

</div>

Perhaps someone else in your organization can use the support portal to properly open a ticket.

You may not be added as a support contact.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [July 2, 2025, 8:37pm UTC](https://discuss.elastic.co/t/deployment-down-because-of-an-ml-job/379712/5 "2025-07-02T20:37:11Z")

</div>

I think you are getting a little help now...