# Logstash memory queue events lost

**URL:** <https://discuss.elastic.co/t/logstash-memory-queue-events-lost/375962>\
**Category:** Logstash\
**Created:** [March 15, 2025, 6:15am UTC](https://discuss.elastic.co/t/logstash-memory-queue-events-lost/375962 "2025-03-15T06:15:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mahdi\_Moazami](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mahdi_moazami/32/113304_2.png) [@Mahdi\_Moazami](https://discuss.elastic.co/u/Mahdi_Moazami)\
**Post date:** [March 15, 2025, 6:15am UTC](https://discuss.elastic.co/t/logstash-memory-queue-events-lost/375962/1 "2025-03-15T06:15:57Z")

</div>

Hi there,  
we are using logstash as data pipeline to transfer data from a SQL Server database to Elasticsearch. the pipelines are configured as **memory queued** and sometimes after the data transfer completes, it's incompleted in elasticsearch side meaning like not all of data has been transferred. As I checked the dashboards in data read period time, the logstash server RAM seems having some drops and that moment the pipeline events\_in rate also decreased. does a GC operation or something else causes the memory to be cleared out so leads to data loss when reading data in memory queue mode?

 ![logstash_server_monitoring](https://us1.discourse-cdn.com/elastic/original/3X/7/1/7177e24fdca5d70925722402e90b152c45e0a14c.png)

 ![events_rate](https://us1.discourse-cdn.com/elastic/original/3X/e/7/e7602e445ba3f8ba1fa3c6e3101ac3535de85c07.png)

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [March 15, 2025, 12:49pm UTC](https://discuss.elastic.co/t/logstash-memory-queue-events-lost/375962/2 "2025-03-15T12:49:05Z")

</div>

> [@Mahdi\_Moazami](#):
>
> does a GC operation or something else causes the memory to be cleared out so leads to data loss when reading data in memory queue mode?

No, a GC cycle just cleans up garbage, it does not delete memory that is still in use by logstash. A brief drop in the event processing rate at the same time as a large drop in the heap in use does suggest a full GC, but that's normal.