# Index falling behind after minor version upgrade **URL:** \ **Category:** Elasticsearch\ **Created:** [October 22, 2019, 7:48am UTC](https://discuss.elastic.co/t/index-falling-behind-after-minor-version-upgrade/204599 "2019-10-22T07:48:49Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![JacovanZyl](https://avatars.discourse-cdn.com/v4/letter/j/cc9497/32.png) [@JacovanZyl](https://discuss.elastic.co/u/JacovanZyl)\ **Post date:** [October 22, 2019, 7:48am UTC](https://discuss.elastic.co/t/index-falling-behind-after-minor-version-upgrade/204599/1 "2019-10-22T07:48:49Z")
Good morning, I recently updated minor version from 7.3.1 to 7.3.2 and found that my 2 busiest indexes (index rate 7K e/s) are falling behind by 10 to 20 minutes. They were up to date before the upgrade and I was happily indexing more than 25000 e/s at times. Data / Ingest Nodes: X6 4 vCPU, 30GB Memory, 20GB assigned to JVM and host attached storage. I am also seeing frequent GC at times: {"type": "server", "timestamp": "2019-10-22T07:47:36,422+0000", "level": "INFO", "component": "o.e.m.j.JvmGcMonitorService", "cluster.name": "Name", "node.name": "Node", "cluster.uuid": "ID", "node.id": "Id", "message": "[gc][1101913] overhead, spent [265ms] collecting in the last [1s]" } I checked the hot thread output but do not understand all of it. The output is almost 1000 lines long so I placed it [in a git repo](https://github.com/jaco-van-zyl/hot_thread_output). If you need more info please let me know any assistance would be really appreciated at this point. Regards ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 19, 2019, 7:48am UTC](https://discuss.elastic.co/t/index-falling-behind-after-minor-version-upgrade/204599/2 "2019-11-19T07:48:55Z")
Closed on November 19, 2019, 7:48am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.