Issues
- 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
- Migrate psmdb-parallel job to work with Hetzner cloudPKG-591Alex Miroshnychenko
- Migrate psmdb-multi job to work with Hetzner cloudPKG-590Alex Miroshnychenko
50 of
Galera support in pt-table-checksum
General
Escalation
General
Escalation
Description
Environment
None
Details
Assignee
UnassignedUnassignedReporter
Michaël de GrootMichaël de GrootPriority
HighComponents
Affects versions
Needs QA
Yes
Details
Details
Assignee
Unassigned
UnassignedReporter
Michaël de Groot
Michaël de GrootPriority
Components
Affects versions
Needs QA
Yes
Smart Checklist
Smart Checklist
Smart Checklist
Created 9 hours ago
Updated 9 hours ago
According to the documentation, Galera cluster is supported. I think this requires some clarification as to me it seems that this is not correct.
At 2 different customers, one running Percona Server 8.0.41-32.1, the other running MariaDB 10.6, I experienced that when running pt-table-checksum on a Galera cluster with a replica that the cluster would hang, and the entire cluster was stuck until the node where pt-table-checksum is running is killed -9.
With both occurrences, I executed this on a reader node. On the writer node I saw pt-table-checksum chunks running indefinitely and other transactions on that same table waiting for innodb locks.
I intended to check the replica, so I did not check if the checksum table on the other cluster node was useful.
The documentation states that the tool is supported. It does not state that the tool is supposed to primarily run on a specific node. This report is to share that executing it on a reader node does not work. If this is the case, and the tool only works on the writer, then this should be taken into account:
The cluster cannot have DML on the table(s) that are being checked on the cluster nodes where the tool is replicating to
The tool cannot work on round-robin clusters
When using different cluster nodes on
If the situation that I am describing is supported, then there is a bug already present for a few years. As said, I did not test the tool on the writer node.
In any case, I think the documentation should be updated in the section about Galera clusters where the replica of the cluster is described, and that the only safe way to execute it is to disable galera replication with --set-vars=”wsrep_on=0” as parameter.
Thank you for taking this issue in consideration,
Michaël