# Elasticsearch 1.7.3 not adding sync\_id to stale index shards **URL:** \ **Category:** Elasticsearch\ **Created:** [November 12, 2015, 10:20am UTC](https://discuss.elastic.co/t/elasticsearch-1-7-3-not-adding-sync-id-to-stale-index-shards/34398 "2015-11-12T10:20:08Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![rtoma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rtoma/32/44812_2.png) [@rtoma](https://discuss.elastic.co/u/rtoma)\ **Post date:** [November 12, 2015, 10:20am UTC](https://discuss.elastic.co/t/elasticsearch-1-7-3-not-adding-sync-id-to-stale-index-shards/34398/1 "2015-11-12T10:20:08Z")
Hi, We upgraded a ES cluster from 1.4 to 1.7.3 recently. Main reason: getting sync\_id on all stale index shards, making recoveries faster. We use ES for ELK. Logstash creates new indices every day, so after a day rollover a set of indices becomes stale. Documentation says: > Elasticsearch tracks the indexing activity of each shard. Shards that have not received any indexing operations for 5 minutes are automatically marked as inactive. This presents an opportunity for Elasticsearch to reduce shard resources and also perform a special kind of flush, called synced flush. A synced flush performs a normal flush, then adds a generated unique marker (sync\_id) to all shards. We see lots of index shards without a sync\_id (using the \_stats/commit?level=shards API). These indices are absolutely stale: the commit.translog\_id value (a millisecond epoch timestamp) says so. Of course we can trigger this by calling the \_flush/synced API, but I wonder what is happening. Curious. Thanks! ---
**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:39pm UTC](https://discuss.elastic.co/t/elasticsearch-1-7-3-not-adding-sync-id-to-stale-index-shards/34398/2 "2017-07-05T23:39:00Z")
Closed on July 5, 2017, 11:39pm UTC