# Pods restart after upgrade to Operator 1.21.0

**URL:** <https://forums.percona.com/t/pods-restart-after-upgrade-to-operator-1-21-0/39627>\
**Category:** Percona Operator for MongoDB\
**Tags:** percona, mongodb, new-release\
**Created:** [October 27, 2025, 4:01pm UTC](https://forums.percona.com/t/pods-restart-after-upgrade-to-operator-1-21-0/39627 "2025-10-27T16:01:21Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![Julio\_Pasinatto](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/julio_pasinatto/32/17643_2.png) [@Julio\_Pasinatto](https://forums.percona.com/u/Julio_Pasinatto)\
**Post date:** [October 30, 2025, 10:51am UTC](https://forums.percona.com/t/pods-restart-after-upgrade-to-operator-1-21-0/39627/10 "2025-10-30T10:51:48Z")

</div>

Hi, thanks @shepz @Islam_Saka

We discovered a connection leak issue in version **1.21.0** , and we will release a hotfix soon, as discussed in this topic: [Percona Operator for MongoDB endlessly spawning connections until OOMKilled](https://forums.percona.com/t/percona-operator-for-mongodb-endlessly-spawning-connections-until-oomkilled/39634)  
It’s likely that the number of connections keeps increasing until it reaches your configured memory limits, causing the pods to restart.

---

_[View the full topic](https://forums.percona.com/t/pods-restart-after-upgrade-to-operator-1-21-0/39627)._