# ES size\_in\_bytes massively increasing for one node, along with search latency

**URL:** <https://discuss.elastic.co/t/es-size-in-bytes-massively-increasing-for-one-node-along-with-search-latency/17999>\
**Category:** Elasticsearch\
**Created:** [June 9, 2014, 5:52pm UTC](https://discuss.elastic.co/t/es-size-in-bytes-massively-increasing-for-one-node-along-with-search-latency/17999 "2014-06-09T17:52:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shaun\_Hall](https://avatars.discourse-cdn.com/v4/letter/s/f9ae1b/32.png) [@Shaun\_Hall](https://discuss.elastic.co/u/Shaun_Hall)\
**Post date:** [June 9, 2014, 5:52pm UTC](https://discuss.elastic.co/t/es-size-in-bytes-massively-increasing-for-one-node-along-with-search-latency/17999/1 "2014-06-09T17:52:39Z")

</div>

Hi all,

We saw an interesting issue today in our ES cluster -- at around 11am, we  
saw the size\_in\_bytes (from \_stats, under store) on one node rocket whilst  
it shrunk on all the other nodes, and during this period, query latency on  
this node alone was much higher than all the other nodes, with several  
worryingly high peaks.

Some info on our cluster:

- Running version 0.90.4
- There are 5 nodes -- 1 was the master at the time
- We have around 50 indices, each one has 5 shards, with replication  
factor 1.
- Running on latest Oracle JVM, version 1.7

The graphs below show the change in size\_in\_bytes on all nodes along with  
the query latency (from a simple curl) and the document count on each node.

I've checked the which indices we were writing to in the period and there  
is no bias for writing into particular shards residing on any node more  
than another.

There's nothing in the logs with the default logging.yml to cause suspicion.

Does anyone have any idea what might have caused this? I've got plenty of  
other data collected so can provide other stats if you think it would help.

Many Thanks,  
Shaun

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/02cc208c-91ed-44d8-ba01-54e6bbc93df0%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/02cc208c-91ed-44d8-ba01-54e6bbc93df0%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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 6, 2017, 1:23am UTC](https://discuss.elastic.co/t/es-size-in-bytes-massively-increasing-for-one-node-along-with-search-latency/17999/2 "2017-07-06T01:23:45Z")

</div>