# "operation primary term \[1\] is too old (current \[2\])" **URL:** \ **Category:** Elasticsearch\ **Created:** [January 14, 2022, 10:59pm UTC](https://discuss.elastic.co/t/operation-primary-term-1-is-too-old-current-2/294459 "2022-01-14T22:59:13Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [January 15, 2022, 10:39am UTC](https://discuss.elastic.co/t/operation-primary-term-1-is-too-old-current-2/294459/2 "2022-01-15T10:39:27Z")
The `operation primary term [1] is too old (current [2])` message is a consequence of the node holding the primary shard leaving the cluster and a replica shard being promoted to primary in its place. A ≥30s GC pause would cause the master to consider a node unhealthy and make it leave the cluster. The main question is why did it have a ≥30s GC pause. Perhaps this is snapshot-related, but your steady-state heap usage looks very high anyway so maybe the snapshot just pushed it over the edge. In any case you are running a very old version, long past [EOL](https://www.elastic.co/support/eol), and there have been significant improvements to memory usage in the ~2 years since 7.6 was released, so an upgrade is overdue and strongly recommended. --- _[View the full topic](https://discuss.elastic.co/t/operation-primary-term-1-is-too-old-current-2/294459)._