Issues
- Add Option to Limit SST Retry AttemptsK8SPXC-1619
- PS80 Jenkins need to create a jenkins user and store its credentials in the same jenkins serverPKG-626Alex Miroshnychenko
- Galera support in pt-table-checksumPT-2441
- PITR cannot be used for recovery if backup schedules are added after creating a pg databaseEVEREST-1985
- Add doc how to migrate to CRD 1K8SPSMDB-1342Anastasia Alexandrova
- Implement checking pop-up window which advises users to migrate to PMM 3PMM-13918
- Creating more than one backup schedule in pg database displays an errorEVEREST-1984tigran.papikyan
- OIDC: verify JWT claimsPSMDB-1657Konstantin Trushin
- OIDC: verify JWT signaturePSMDB-1656Konstantin Trushin
- Add additional security group to pmm3-aws-staging instances for Nomad functionalityPMM-13917talha.rizwan
- libstdc++.so.6(GLIBCXX_3.4.30) is missing for al2023PKG-625Vadim Yalovets
- Support Startup Probes for Database PodsK8SPXC-1618
- Investigate and Fix Failures in Everest QA ROSA WorkflowEVEREST-1983
- Allow enabling PG extensionsEVEREST-1982
- Remove patch versions from OpenShift in docsCLOUD-902Anastasia Alexandrova
- CVEs in pmm 2.44.0 docker imagesPMM-13915Nurlan Moldomurov
- Create a test which enables external access to databaseEVEREST-1981Tomislav Plavcic
- Unsupported database version cannot be upgraded and blocks pg operator upgradeEVEREST-1980rasika.chivate
- [UI] DB engine upgrade wrongly updates backup schedule timeEVEREST-1979Fábio Da Silva
- Migrate pbm-site-check job to work with Hetzner cloudPKG-622Alex Miroshnychenko
- Migrate pbm-release-test-run job to work with Hetzner cloudPKG-621Alex Miroshnychenko
- Migrate pbm-pkg-upgrade job to work with Hetzner cloudPKG-620Alex Miroshnychenko
- Migrate pbm-pkg-upgrade-parallel job to work with Hetzner cloudPKG-619Alex Miroshnychenko
- Migrate pbm-pkg-install job to work with Hetzner cloudPKG-618Alex Miroshnychenko
- Migrate pbm-pkg-install-parallel job to work with Hetzner cloudPKG-617Alex Miroshnychenko
- Migrate pbm-functional-tests job to work with Hetzner cloudPKG-616Alex Miroshnychenko
- Migrate pbm-functional-tests-full job to work with Hetzner cloudPKG-615Alex Miroshnychenko
- Migrate pbm-e2e-tests job to work with Hetzner cloudPKG-614Alex Miroshnychenko
- Migrate pbm-docker job to work with Hetzner cloudPKG-613Alex Miroshnychenko
- Migrate pbm-docker-arm job to work with Hetzner cloudPKG-612Alex Miroshnychenko
- Migrate pdmdb job to work with Hetzner cloudPKG-611Alex Miroshnychenko
- Migrate pdmdb-upgrade job to work with Hetzner cloudPKG-610Alex Miroshnychenko
- Migrate pdmdb-upgrade-parallel job to work with Hetzner cloudPKG-609Alex Miroshnychenko
- Migrate pdmdb-site-check job to work with Hetzner cloudPKG-608Alex Miroshnychenko
- Migrate pdmdb-setup job to work with Hetzner cloudPKG-607Alex Miroshnychenko
- Migrate pdmdb-setup-parallel job to work with Hetzner cloudPKG-606Alex Miroshnychenko
- Migrate pdmdb-parallel job to work with Hetzner cloudPKG-605Alex Miroshnychenko
- Migrate pdmdb-multi job to work with Hetzner cloudPKG-604Alex Miroshnychenko
- Migrate pdmdb-multi-parallel job to work with Hetzner cloudPKG-603Alex Miroshnychenko
- Migrate psmdb job to work with Hetzner cloudPKG-602Alex Miroshnychenko
- Migrate psmdb-upgrade job to work with Hetzner cloudPKG-601Alex Miroshnychenko
- Migrate psmdb-upgrade-parallel job to work with Hetzner cloudPKG-600Alex Miroshnychenko
- Migrate psmdb-tarball job to work with Hetzner cloudPKG-599Alex Miroshnychenko
- Migrate psmdb-tarball-pro-functional job to work with Hetzner cloudPKG-598Alex Miroshnychenko
- Migrate psmdb-tarball-multi job to work with Hetzner cloudPKG-597Alex Miroshnychenko
- Migrate psmdb-tarball-functional job to work with Hetzner cloudPKG-596Alex Miroshnychenko
- Migrate psmdb-tarball-all-setups job to work with Hetzner cloudPKG-595Alex Miroshnychenko
- Migrate psmdb-tarball-all-os job to work with Hetzner cloudPKG-594Alex Miroshnychenko
- Migrate psmdb-site-check job to work with Hetzner cloudPKG-593Alex Miroshnychenko
- Migrate psmdb-regression job to work with Hetzner cloudPKG-592Alex Miroshnychenko
50 of
Add Option to Limit SST Retry Attempts
General
Escalation
General
Escalation
Description
Environment
None
Details
Assignee
UnassignedUnassignedReporter
Juan ArrutiJuan ArrutiNeeds QA
YesAffects versions
Priority
Medium
Details
Details
Assignee
Unassigned
UnassignedReporter
Juan Arruti
Juan ArrutiNeeds QA
Yes
Affects versions
Priority
Smart Checklist
Smart Checklist
Smart Checklist
Created 45 minutes ago
Updated 45 minutes ago
Hi,
When SST fails several times in a row due to a software bug, for example, it can hardly be fixed by itself without intervention.
Meanwhile, SST runs continuously, consuming resources such as network bandwidth and affecting the donor's performance.
The Kubelet's --backoff-max-restart-delay is set to 5 minutes by default, which can be too short between restart attempts. This can lead to repeated SST retries in a short timeframe, potentially impacting cluster performance.
Ideally, nodes should have a configurable limit on SST attempts. After a few failed retries, they could stop requesting SST to avoid putting additional pressure on the cluster.
Thanks!