# Pitr container not exiting after hitting failure

**URL:** <https://forums.percona.com/t/pitr-container-not-exiting-after-hitting-failure/40671>\
**Category:** Percona Operator for MySQL\
**Created:** [April 18, 2026, 8:16pm UTC](https://forums.percona.com/t/pitr-container-not-exiting-after-hitting-failure/40671 "2026-04-18T20:16:53Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yash\_Daga](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/yash_daga/32/22569_2.png) [@Yash\_Daga](https://forums.percona.com/u/Yash_Daga)\
**Post date:** [April 18, 2026, 8:16pm UTC](https://forums.percona.com/t/pitr-container-not-exiting-after-hitting-failure/40671/1 "2026-04-18T20:16:53Z")

</div>

Setup:  
3 node percona pxc cluster with the following percona images  
Operator: 1.19.0  
Cluster: 8.0.42-33.1  
Xtrabackup: 8.0.35-34.1

I was trying PITR, during which the restore job succeeded, but the pitr job failed because it hit the max\_allowed\_packet limit.

I had a couple of questions:

1. The PITR container didn’t exit after failing and I had to manually delete the pod for it to retry, is there a way to avoid this?
2. How can i prevent hitting the max\_packet\_size limit while performing PITR since the max value for max\_allowed\_packet is 1Gb and we have max txn size as 2Gb?

---

<div class="post-metadata">

**Author:** ![Yash\_Daga](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/yash_daga/32/22569_2.png) [@Yash\_Daga](https://forums.percona.com/u/Yash_Daga)\
**Post date:** [May 5, 2026, 11:21am UTC](https://forums.percona.com/t/pitr-container-not-exiting-after-hitting-failure/40671/2 "2026-05-05T11:21:29Z")

</div>

@matthewb @Ege_Gunes

---

<div class="post-metadata">

**Author:** ![Ege\_Gunes](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ege_gunes/32/4595_2.png) [@Ege\_Gunes](https://forums.percona.com/u/Ege_Gunes)\
**Post date:** [May 5, 2026, 3:24pm UTC](https://forums.percona.com/t/pitr-container-not-exiting-after-hitting-failure/40671/3 "2026-05-05T15:24:29Z")

</div>

@Yash_Daga for 1, do you have pitr job logs?

---

<div class="post-metadata">

**Author:** ![Ege\_Gunes](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ege_gunes/32/4595_2.png) [@Ege\_Gunes](https://forums.percona.com/u/Ege_Gunes)\
**Post date:** [May 5, 2026, 3:26pm UTC](https://forums.percona.com/t/pitr-container-not-exiting-after-hitting-failure/40671/4 "2026-05-05T15:26:22Z")

</div>

Created [Jira](https://perconadev.atlassian.net/browse/K8SPXC-1876) to track this.

---

<div class="post-metadata">

**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\
**Post date:** [May 5, 2026, 3:45pm UTC](https://forums.percona.com/t/pitr-container-not-exiting-after-hitting-failure/40671/5 "2026-05-05T15:45:11Z")

</div>

Unfortunately, Atlassian doesn’t provide the necessary data via the link to unauthorized users (or websites/bots), and there’s no plugin for this in Discourse, so I set it up so that at least the full URL is displayed.  
[https://perconadev.atlassian.net/browse/K8SPXC-1876](https://perconadev.atlassian.net/browse/K8SPXC-1876)

---

<div class="post-metadata">

**Author:** ![Yash\_Daga](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/yash_daga/32/22569_2.png) [@Yash\_Daga](https://forums.percona.com/u/Yash_Daga)\
**Post date:** [May 6, 2026, 2:29pm UTC](https://forums.percona.com/t/pitr-container-not-exiting-after-hitting-failure/40671/6 "2026-05-06T14:29:58Z")

</div>

Hi @Ege_Gunes thanks for the response.

Unfortunately, I don’t have those logs currently, I’ll try to see if I can retry this workflow and get this error.  
I did found this from back when we got this error, though:  
`mysql> SELECT logged, prio, error_code, data FROM performance_schema.error_log ORDER BY logged DESC LIMIT 20\G ***************************1. row*************************** logged: 2026-04-17 13:00:51.213911 prio: Note error_code: MY-010914 data: Aborted connection 2486 to db: 'unconnected' user: 'xtrabackup' host: 'mysqlcluster-pxc-0.mysqlcluster-pxc.percona-operator.svc.cluster.local' (Got a packet bigger than 'max_allowed_packet' bytes). ***************************2. row*************************** logged: 2026-04-17 13:00:42.417551 prio: Note error_code: MY-010914 data: Aborted connection 69 to db: 'mysql' user: 'xtrabackup' host: 'mysqlcluster-pxc-0.mysqlcluster-pxc.percona-operator.svc.cluster.local' (Got an error reading communication packets).`

---

<div class="post-metadata">

**Author:** ![Ege\_Gunes](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ege_gunes/32/4595_2.png) [@Ege\_Gunes](https://forums.percona.com/u/Ege_Gunes)\
**Post date:** [May 6, 2026, 2:35pm UTC](https://forums.percona.com/t/pitr-container-not-exiting-after-hitting-failure/40671/7 "2026-05-06T14:35:58Z")

</div>

pitr job hanging is worrying, I’ll try to simulate going over max packet size to see what happens.
