# Elasticsearch Log message "deleted shard reason \[no longer used\]" version 2.1.1 **URL:** \ **Category:** Elasticsearch\ **Created:** [January 8, 2016, 11:19am UTC](https://discuss.elastic.co/t/elasticsearch-log-message-deleted-shard-reason-no-longer-used-version-2-1-1/38717 "2016-01-08T11:19:53Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![ggiessl](https://avatars.discourse-cdn.com/v4/letter/g/8dc957/32.png) [@ggiessl](https://discuss.elastic.co/u/ggiessl)\ **Post date:** [January 8, 2016, 11:19am UTC](https://discuss.elastic.co/t/elasticsearch-log-message-deleted-shard-reason-no-longer-used-version-2-1-1/38717/1 "2016-01-08T11:19:53Z")
Hi Community! We are getting debug log messages on our 4-node test environment under heavy index load: * * * ## [2016-01-08 11:28:59,363][DEBUG][indices] [node4] [index\_2016-01-02][10] deleted shard reason [no longer used] [2016-01-08 11:28:59,363][DEBUG][cluster.service] [node4] processing [indices\_store ([[index\_2016-01-02][10]] active fully on other nodes)]: took 0s no change in cluster\_state [2016-01-08 11:28:59,363][DEBUG][cluster.service] [node4] processing [indices\_store ([[index\_2015-12-29][1]] active fully on other nodes)]: execute [2016-01-08 11:28:59,364][DEBUG][indices] [node4] [index\_2015-12-29][1] deleted shard reason [no longer used] [2016-01-08 11:28:59,364][DEBUG][cluster.service] [node4] processing [indices\_store ([[index\_2015-12-29][1]] active fully on other nodes)]: took 0s no change in cluster\_state [2016-01-08 11:28:59,364][DEBUG][cluster.service] [node4] processing [indices\_store ([[index\_2016-01-02][11]] active fully on other nodes)]: execute [2016-01-08 11:28:59,365][DEBUG][indices] [node4] [index\_2016-01-02][11] deleted shard reason [no longer used] [2016-01-08 11:28:59,365][DEBUG][cluster.service] [node4] processing [indices\_store ([[index\_2016-01-02][11]] active fully on other nodes)]: took 0s no change in cluster\_state [2016-01-08 11:28:59,365][DEBUG][cluster.service] [node4] processing [indices\_store ([[index\_2016-01-02][9]] active fully on other nodes)]: execute [2016-01-08 11:28:59,366][DEBUG][indices] [node4] [index\_2016-01-02][9] deleted shard reason [no longer used] [2016-01-08 11:28:59,366][DEBUG][cluster.service] [node4] processing [indices\_store ([[index\_2016-01-02][9]] active fully on other nodes)]: took 0s no change in cluster\_state [2016-01-08 11:28:59,366][DEBUG][cluster.service] [node4] processing [indices\_store ([[index\_2016-01-02][4]] active fully on other nodes)]: execute We are creating one index per day, only the index of the current day receives new data. Old indices are open (searchable), but static. Now, we are wondering what the above messages mean. We are not expecting any "shard activity" especially on static indices. As we didn't find any documentation about "no longer used" shards, I would very much appreciate any input on how to interpet those logs. We are not experiencing problems, I would just like to understand what is happening on the cluster. Thanks and best regards, Gerhard ---
**Author:** ![dakrone](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dakrone/32/23351_2.png) [@dakrone](https://discuss.elastic.co/u/dakrone)\ **Post date:** [January 8, 2016, 10:18pm UTC](https://discuss.elastic.co/t/elasticsearch-log-message-deleted-shard-reason-no-longer-used-version-2-1-1/38717/2 "2016-01-08T22:18:08Z")
When a shard is being relocated between nodes, before deleting it from the source node (where it is being relocated _away_ from) the node reaches out to check that it is fully active on the target nodes. These messages are the shard being deleted now that the other node(s) have confirmed that they have the shard and that it is active. It's likely that your cluster is just relocating shards between the nodes. ---
**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, 11:25pm UTC](https://discuss.elastic.co/t/elasticsearch-log-message-deleted-shard-reason-no-longer-used-version-2-1-1/38717/3 "2017-07-05T23:25:49Z")