[Percona Community Forum] Summary

No dark-mode styles — this email renders the same in a dark client.

A brief summary of [Percona Community Forum][1] since 2026-10-12 02:01:21 UTC

11 New Topics
11 New Users


  
  ### Popular Topics

    [Pmm Mysql agent][2]

      Description:
We have mysql instance,Version: 8.0.39-30.1 (Percona XtraDB Cluster (GPL), Release rel30, Revision 46271a0, WSREP version 26.1.4.3) 
The Mysql instance is one of 3 nodes Xtradb cluster- 
The pMM agent i configured to use  performance_schema and NOT slow queries. 
We notice  the following query :slight_smile: 

Time: 2026-09-23T04:47:45.914410Z
User@Host: pmm[pmm] @  [10.12.163.2]  Id: 17851549
Schema:   Last_errno: 0  Killed: 0
Query_time: 3.061418  Lock_time: 0.000001  Rows_sent: 478  Rows_examined: 478  Rows_affected: 0  Bytes_sent: 24971
Tmp_tables: 0  Tmp_disk_tables: 0  Tmp_table_sizes: 0
Full_scan: Yes  Full_join: No  Tmp_table: No  Tmp_table_on_disk: No
Filesort: No  Filesort_on_disk: No  Merge_passes: 0
No InnoDB statistics available for this query
Log_slow_rate_type: query  Log_slow_rate_limit: 100
SET timestamp=1790138862;
SELECT EVENT_NAME, COUNT_STAR, SUM_TIMER_WAIT
FROM performance_schema.events_waits_summary_global_by_event_name;

Is taking 3.061418 sec. 
How...

    
    [PostgreSQL Percona TDE][3]

      Hello! 
No, currently there’s no way to do this. pg_tde_change_key_provider is meant to change the settings of the key provider - for example if the Vault server’s address changed after taking the backup, or while a server was offline, not to point an existing configuration to a completely different provider type.

    
    [Amazon RDS MySQL: 99% system CPU, mysqld unexpectedly restarted, repeated failures resolved after Stop/Start — what could cause this?][4]

      Hi, sorry to hear you are having issues. Unfortunately RDS can be a black box sometimes. Have you tried opening a support ticket with AWS? they may be able to explain why the surge in %sys. Hard to say without direct access to the underlying operating system.

    
    [Multi-tenant Orchestrator: managing multiple isolated MySQL/MariaDB environments from one deployment][5]

      Hi everyone, 
I’ve been working on a multi-tenant implementation for Orchestrator and I’m looking for feedback from people managing multiple independent MySQL/MariaDB environments. 
The problem I wanted to solve is simple: 
If you manage multiple customers, environments or independent database platforms, running a completely separate Orchestrator deployment for every environment can become operationally expensive. 
My implementation allows a single Orchestrator deployment to manage multiple isolated tenants while keeping: 

independent discovery
independent topology state
independent analysis and recovery
tenant-aware API and CLI
tenant-aware hooks and metrics
ProxySQL integration per tenant
one Raft group, one leader, one HTTP listener and one dashboard

Repository: 


The repository also includes documentation for the multi-tenant architecture, configuration, deployment, upgrades and testing. 
I’m particularly interested in feedback from people managing many clusters, multiple custom...

    
    [Problem with pc.recovery][6]

      I have a mysql8.4.10 cluster of 3 nodes A/B/C with default config pc.wait_prim = true; pc.wait_prim_timeout = PT30S; pc.wait_restored_prim_timeout = PT0S; pc.recovery=true. 
When all nodes power off at almost the same time, 3 nodes will auto choose a bootstrap when they start up later and everything will be ok. 
But if the down time be not the same, it will not process properly. 
When node A power down, it will have 3 members in gvwstate.dat 
After a few seconds, gvwstate.dat in node B/C will have only 2 members。 
Then node B/C also power down. 
Then start 3 nodes at the same time without a bootstrap node. 
All nodes will become non-primary and mysql port will not be up and mysqld will never exit. 
All mysqld will not process any signal. Script mysql.server can not stop/restart the running mysqld. 
I can not set one node to bootstrap since the mysql listen port is not up. 
I have to kill one mysqld and start it with bootstrap, then the cluster will be ok. 
How can I fix this problem? T...

    

  




**New for you**

* [Apologies for delaying Postgres 19 | Percona Community][7] - 1 - [Community website]
* [PXC 8.0 to 8.4 on OpenShift 4.14 now, 4.22 later: which operator version and upgrade path?][8] - 1 - [Percona Operator for MySQL]
* [FOSS 2026 conference in Chernihiv: how it went | Percona Community][9] - 1 - [Community website]
* [One query to audit the PostgreSQL row-level security an AI … | Percona Community][10] - 1 - [Community website]
* [Docker DBA Lab | Percona Community][11] - 1 - [Community website]



[1]: https://forums.percona.com/
[2]: https://forums.percona.com/t/pmm-mysql-agent/41330
[3]: https://forums.percona.com/t/postgresql-percona-tde/41340
[4]: https://forums.percona.com/t/amazon-rds-mysql-99-system-cpu-mysqld-unexpectedly-restarted-repeated-failures-resolved-after-stop-start-what-could-cause-this/41344
[5]: https://forums.percona.com/t/multi-tenant-orchestrator-managing-multiple-isolated-mysql-mariadb-environments-from-one-deployment/41335
[6]: https://forums.percona.com/t/problem-with-pc-recovery/41351
[7]: https://forums.percona.com/t/apologies-for-delaying-postgres-19-percona-community/41346
[8]: https://forums.percona.com/t/pxc-8-0-to-8-4-on-openshift-4-14-now-4-22-later-which-operator-version-and-upgrade-path/41342
[9]: https://forums.percona.com/t/foss-2026-conference-in-chernihiv-how-it-went-percona-community/41331
[10]: https://forums.percona.com/t/one-query-to-audit-the-postgresql-row-level-security-an-ai-percona-community/41334
[11]: https://forums.percona.com/t/docker-dba-lab-percona-community/41333
[12]: https://forums.percona.com/



  This summary is sent from [Percona Community Forum][12] when we haven't seen you in a while. Change [your email settings][13], or [click here][14] to unsubscribe.

[13]: https://forums.percona.com/my/preferences/emails
[14]: https://forums.percona.com/email/unsubscribe/ba780a773b2ff7ec3e73eb6d5939e0dff6fba9288f43e3dcc07fb49504ed6941

Accession

nse/percona/2026-10-19/4362

From

Percona Community Forum · notifications@percona1.discoursemail.com

Sent

19 October 2026 · 02:00 UTC