# Replication Action objects in heap dump?

**URL:** <https://discuss.elastic.co/t/replication-action-objects-in-heap-dump/60727>\
**Category:** Elasticsearch\
**Created:** [September 16, 2016, 3:04pm UTC](https://discuss.elastic.co/t/replication-action-objects-in-heap-dump/60727 "2016-09-16T15:04:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![YanMQB](https://avatars.discourse-cdn.com/v4/letter/y/bbe5ce/32.png) [@YanMQB](https://discuss.elastic.co/u/YanMQB)\
**Post date:** [September 16, 2016, 3:04pm UTC](https://discuss.elastic.co/t/replication-action-objects-in-heap-dump/60727/1 "2016-09-16T15:04:25Z")

</div>

I am analyzing some heap dumps from systems that crashed and there are some missing chunks of information regarding what happened that I'm trying to figure out.

My question comes down any hidden meanings of the TransportShardReplicationOperationAction objects showing up in the heap dump. I have seen a large number of these objects piled up in both the EsThreadPoolExecutor and in the TransportService. I had thought these might be suggesting that a node in the system went down/offline and these were caused by the cluster trying to recover. Are there other reasons these objects would be showing up?

These heap dumps are from ES 1.5

---

<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 5, 2017, 10:19pm UTC](https://discuss.elastic.co/t/replication-action-objects-in-heap-dump/60727/2 "2017-07-05T22:19:33Z")

</div>

Closed on July 5, 2017, 10:19pm UTC