Issues
- Connection closed unexpectedly errosK8SPXC-1116Resolved issue: K8SPXC-1116
- [BUG] xtradb-operator fails to delete the PVCs and secrets if it crashes and restarts in the middle of deleteStatefulSet()K8SPXC-979Resolved issue: K8SPXC-979
- [WSREP-SST] 2022/01/11 18:06:20 socat[23163] E connect(7, AF=2 10.233.86.195:4444, 16): Connection timed out"}]K8SPXC-937Resolved issue: K8SPXC-937
- Pods Are Not Cleaned Up When Deleting Failed Backup ResourcesK8SPXC-921Resolved issue: K8SPXC-921
- [BUG] xtradb operator does not delete PVC after scaling-down leading to resource leakK8SPXC-918
- [BUG] Operator never creates ssl-internal certificate if crash happens at some particular pointK8SPXC-897Resolved issue: K8SPXC-897
- [BUG] Operator cannot create ssl-internal secret if crash happens at some particular pointK8SPXC-896Resolved issue: K8SPXC-896ege.gunes
- Document of PITR IssueK8SPXC-887Resolved issue: K8SPXC-887dmitriy.kostiuk
- Mark pxc container restarts in logs container outputK8SPXC-804natalia.marukovich
- allow "sleep infinity" on non-debug imagesK8SPXC-791Resolved issue: K8SPXC-791Slava Sarzhan
- mbind: Operation not permittedK8SPXC-788
- Backup to S3 produces error messages even during successful backupK8SPXC-785Resolved issue: K8SPXC-785Slava Sarzhan
- Backup stails in running state after garb ssl connection problemK8SPXC-782Slava Sarzhan
- Manual Crash Recovery interferes with auto recovery even with auto_recovery: falseK8SPXC-757Resolved issue: K8SPXC-757Slava Sarzhan
- ProxySQL can't connect to PXC if allowUnsafeConfiguration = trueK8SPXC-750Resolved issue: K8SPXC-750Andrii Dema
- socat in percona/percona-xtradb-cluster-operator:1.7.0-pxc5.7-backup generates "E SSL_read(): Connection reset by peer"K8SPXC-742Resolved issue: K8SPXC-742Slava Sarzhan
- CronJob backup retry is prevented by is prevented by Retention policyK8SPXC-733Resolved issue: K8SPXC-733dmitriy.kostiuk
- pxc-2 node was only alive node before delete pxc, re-created cluster is not recoveringK8SPXC-728Resolved issue: K8SPXC-728Slava Sarzhan
- [BUG] HAproxy statefulset and services get mistakenly deleted when reading stale `spec.haproxy.enabled`K8SPXC-725Resolved issue: K8SPXC-725Slava Sarzhan
- [BUG] StatefulSet and PVC get mistakenly deleted when reading stale PerconaXtraDBCluster informationK8SPXC-716Resolved issue: K8SPXC-716
- Certificate renewal - PXC fails to restartK8SPXC-706Resolved issue: K8SPXC-706Slava Sarzhan
- HAProxy Stats Page is not displayedK8SPXC-705Resolved issue: K8SPXC-705
- Percona operator TPS and LatencyK8SPXC-703Resolved issue: K8SPXC-703
- restore not starting after failed restore on another clusterK8SPXC-687Resolved issue: K8SPXC-687Andrii Dema
- When using WATCH_NAMESPACES operator fails to setup the webhookK8SPXC-680Resolved issue: K8SPXC-680
- HAProxy considers Donor as a DOWN state, make it configurableK8SPXC-676Resolved issue: K8SPXC-676
- Lost connection to MySQL server during queryK8SPXC-668Resolved issue: K8SPXC-668Slava Sarzhan
- Pxc operator log errors even when cluster is ready and runningK8SPXC-660Resolved issue: K8SPXC-660
- kubectl explain pxc returns empty descriptionK8SPXC-659
- Store custom configuration in SecretsK8SPXC-657Resolved issue: K8SPXC-657Sergey Pronin
- PXC operator leaky abstractionsK8SPXC-646
- PITR ERROR collect binlog files - converting NULL to string is unsupportedK8SPXC-645Resolved issue: K8SPXC-645Bulat Zamalutdinov
- Improve my.cnf (spec.pxc.configuration) options validation, allow to fix problemsK8SPXC-644
- PodDisruptionBudget Problem due to wrong haproxy Statefulset LabelsK8SPXC-642Resolved issue: K8SPXC-642
- Update of secret for proxyadmin user does not work properlyK8SPXC-641Resolved issue: K8SPXC-641Maksim Dudin
- pxc upgrade error: update error: Operation cannot be fulfilled on statefulsets.apps \"db-pxc\": the object has been modified; please apply your changes to the latest version and try againK8SPXC-633Resolved issue: K8SPXC-633Lalit Choudhary
- PITR binlog apply error for the sequence backup-restore-backup-restoreK8SPXC-632Resolved issue: K8SPXC-632Maksim Dudin
- Monitoring xtradb cluster not workingK8SPXC-628Resolved issue: K8SPXC-628
- Tests for PITRK8SPXC-566Resolved issue: K8SPXC-566Maksim Dudin
- Second PerconaXtraDBClusterRestore Always FailsK8SPXC-515Resolved issue: K8SPXC-515natalia.marukovich
40 of 40
Connection closed unexpectedly erros
Done
General
Escalation
General
Escalation
Description
Environment
Kubernetes: self hosted (v1.21.4)
Smart Checklist
Details
Assignee
UnassignedUnassignedReporter
Prathyush RomPrathyush RomNeeds QA
YesComponents
Affects versions
Priority
Medium
Details
Details
Assignee
Unassigned
UnassignedReporter
Prathyush Rom
Prathyush RomNeeds QA
Yes
Components
Affects versions
Priority
Smart Checklist
Smart Checklist
Smart Checklist
Created October 18, 2022 at 4:43 AM
Updated June 27, 2023 at 1:17 PM
Resolved June 27, 2023 at 1:17 PM
Activity
Aaditya DubeyJune 27, 2023 at 1:16 PM
Hi @Prathyush Rom,
We still haven't heard any news from you. So I assume issue is not persists anymore. If you disagree just reply and create a follow-up report.
Aaditya DubeyApril 26, 2023 at 11:58 AM
Hi @Prathyush Rom,
Thank you for the report.
Please let us know if issue still persists.
Slava SarzhanMarch 14, 2023 at 12:14 PM
Hi @Prathyush Rom, do you have this issue now?
Prathyush RomOctober 18, 2022 at 5:25 AM
we are not using any custom haproxy configurations, below are the timeout values from the default configs.
defaults
log global
mode tcp
retries 10
timeout client 28800s
timeout connect 100500
timeout server 28800s
Greetings,
We have got a couple of XtraDB clusters deployed with percona pxc operator v1.7.0 and we have got php applications which leverages rhge XtraDB clusters, the setup is working fine in general, but it throws `Connection closed unexpectedly` errors in our apps every now and then and it has to perform a retry for making it work as seen below, any idea what might be wrong here? the clusters are using HAProxy load balancers, any pointers on fixing this would be much appreciated, thanks!
```
SQL retry 'Connection closed unexpectedly' on: rooms, SELECT * FROM participants WHERE (`user_id` = 4956456743)
```