# Suddenly Elastic Failure (Graphs Included)

**URL:** <https://discuss.elastic.co/t/suddenly-elastic-failure-graphs-included/139338>\
**Category:** Elasticsearch\
**Created:** [July 10, 2018, 11:54am UTC](https://discuss.elastic.co/t/suddenly-elastic-failure-graphs-included/139338 "2018-07-10T11:54:51Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![devday](https://avatars.discourse-cdn.com/v4/letter/d/9dc877/32.png) [@devday](https://discuss.elastic.co/u/devday)\
**Post date:** [July 10, 2018, 11:54am UTC](https://discuss.elastic.co/t/suddenly-elastic-failure-graphs-included/139338/1 "2018-07-10T11:54:52Z")

</div>

Hi,

We are experiencing a strange problem.  
Everything with Elastic Search is fine but we get sudden deaths now and again.  
This may happen once a week or once a month or twice a day.  
During this time, I do not believe the index count or query count is unusual.

I've attached the graphs

 ![es](https://us1.discourse-cdn.com/elastic/original/3X/8/1/8127f68d4d5b47f64e1e5c0c30123f0fe402589a.jpg)

You can see the current rate of indexing and searching is not abnormal.  
However, if you look at the "rate of opened http connections", this rocketed at 10:20.  
The "search thread pool queue by size by node" also rocketed to \> 1000 at this time.  
This caused all nodes to go offline and ES to become unresponsive.

Has anyone had this and do you know the cause of such issues?

Any help will be much appreciated,  
Dev

---

<div class="post-metadata">

**Author:** ![devday](https://avatars.discourse-cdn.com/v4/letter/d/9dc877/32.png) [@devday](https://discuss.elastic.co/u/devday)\
**Post date:** [July 10, 2018, 11:56am UTC](https://discuss.elastic.co/t/suddenly-elastic-failure-graphs-included/139338/2 "2018-07-10T11:56:06Z")

</div>

Hi,

Just to follow up - the graph eneds at 11:00 as the node was unreachable.  
However, we just need to look at the time before and around 10:20 when the issue happened and ES was unresponsive.

Dev

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [July 10, 2018, 12:02pm UTC](https://discuss.elastic.co/t/suddenly-elastic-failure-graphs-included/139338/3 "2018-07-10T12:02:18Z")

</div>

Is there anything in the Elasticsearch logs around that time? Which version are you using?

---

<div class="post-metadata">

**Author:** ![devday](https://avatars.discourse-cdn.com/v4/letter/d/9dc877/32.png) [@devday](https://discuss.elastic.co/u/devday)\
**Post date:** [July 10, 2018, 12:04pm UTC](https://discuss.elastic.co/t/suddenly-elastic-failure-graphs-included/139338/4 "2018-07-10T12:04:44Z")

</div>

Hi Christian,

Thank you for getting back to me.  
We're on version 5.3.2.  
I don't have access to the logs as we are using a hosted service provider.

Any initial thoughts?

Dev

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [July 10, 2018, 12:25pm UTC](https://discuss.elastic.co/t/suddenly-elastic-failure-graphs-included/139338/5 "2018-07-10T12:25:58Z")

</div>

Without logs I have no idea what is going on.

---

<div class="post-metadata">

**Author:** ![devday](https://avatars.discourse-cdn.com/v4/letter/d/9dc877/32.png) [@devday](https://discuss.elastic.co/u/devday)\
**Post date:** [July 10, 2018, 1:20pm UTC](https://discuss.elastic.co/t/suddenly-elastic-failure-graphs-included/139338/6 "2018-07-10T13:20:05Z")

</div>

Hi Christian,

I've requested the logs,

Dev

---

<div class="post-metadata">

**Author:** ![devday](https://avatars.discourse-cdn.com/v4/letter/d/9dc877/32.png) [@devday](https://discuss.elastic.co/u/devday)\
**Post date:** [July 12, 2018, 1:16pm UTC](https://discuss.elastic.co/t/suddenly-elastic-failure-graphs-included/139338/7 "2018-07-12T13:16:50Z")

</div>

Hi Christian,

I am still trying to get the logs but to no avail right now.

Dev

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [July 12, 2018, 1:21pm UTC](https://discuss.elastic.co/t/suddenly-elastic-failure-graphs-included/139338/8 "2018-07-12T13:21:33Z")

</div>

Have you looked at [Elastic Cloud](https://www.elastic.co/cloud/elasticsearch-service), which comes with monitoring and access to logs via the UI?

---

<div class="post-metadata">

**Author:** ![devday](https://avatars.discourse-cdn.com/v4/letter/d/9dc877/32.png) [@devday](https://discuss.elastic.co/u/devday)\
**Post date:** [July 12, 2018, 1:56pm UTC](https://discuss.elastic.co/t/suddenly-elastic-failure-graphs-included/139338/9 "2018-07-12T13:56:02Z")

</div>

Hi Christian,

Yes we do use Elastic Cloud.  
But for this particular client, we are using Qbox.

Regards,  
Dev

---

<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:** [August 9, 2018, 1:56pm UTC](https://discuss.elastic.co/t/suddenly-elastic-failure-graphs-included/139338/10 "2018-08-09T13:56:04Z")

</div>

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