# Write queue continue to rise

**URL:** https://discuss.elastic.co/t/write-queue-continue-to-rise/213652
**Category:** Elasticsearch
**Created:** [January 3, 2020, 5:28am UTC](https://discuss.elastic.co/t/write-queue-continue-to-rise/213652 "2020-01-03T05:28:14Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![Armin\_Braun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/armin_braun/32/20092_2.png) [@Armin\_Braun](https://discuss.elastic.co/u/Armin_Braun)
#### Post date: [January 3, 2020, 12:17pm UTC](https://discuss.elastic.co/t/write-queue-continue-to-rise/213652/3 "2020-01-03T12:17:14Z")

</div>

Linking your other thread here @ITzhangqiang

> [@Index writer memory Continue to rise](https://discuss.elastic.co/t/index-writer-memory-continue-to-rise/213514):
>
> hi，all： I have a question that has puzzled me for a long time。 One node in the cluster has too much index writer memory (other node is fline), and it keeps going up,and it lead to index throttling . And then I adjusted index.refresh.interval from 30s to 10s , but the situation has not improved much。 I also found this issued node's refresh queue has a large back-up， [image] why index writer cost so much memory?I found nothing in log As index writer memory continues to rise，in t…

I think these two things are connected. As I said there and @HenningAndersen here, we'll need the full `jstack` output to track down the dead-lock.

---

_[View the full topic](https://discuss.elastic.co/t/write-queue-continue-to-rise/213652)._