# Channel closed while still aggregating message

**URL:** <https://discuss.elastic.co/t/channel-closed-while-still-aggregating-message/363295>\
**Category:** Elasticsearch\
**Created:** [July 17, 2024, 4:10pm UTC](https://discuss.elastic.co/t/channel-closed-while-still-aggregating-message/363295 "2024-07-17T16:10:35Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)\
**Post date:** [July 29, 2024, 9:54pm UTC](https://discuss.elastic.co/t/channel-closed-while-still-aggregating-message/363295/4 "2024-07-29T21:54:08Z")

</div>

Ah that makes sense. A code sample still could be helpful here. Some resources that could be helpful here as follows:

- [A channel closed while connecting - Common causes and quick fixes](https://opster.com/es-errors/a-channel-closed-while-connecting/)
- [Addressing Filebeat's memory leak and performance issues with high log volume - #12 by strawgate](https://discuss.elastic.co/t/addressing-filebeats-memory-leak-and-performance-issues-with-high-log-volume/354929/12)

---

_[View the full topic](https://discuss.elastic.co/t/channel-closed-while-still-aggregating-message/363295)._