[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-09-14 00:21:59 UTC

8 New Topics
12 New Users


  
  ### Popular Topics

    [Question about pt-online-schema-change and performance_schema][2]

      log_warnings is not 11. 
It is a cluster of 4 nodes, and mariadb-upgrade had not been run on one of the nodes. I think it is the cause: I dropped and re-created index, no error anymore.

    
    [Vibe Coding a Database Lab: How I Built DBCanvas to Stop … | Percona Community][3]

      Percona gives us room to work on our own AI-assisted projects, and I used mine to fix a problem I kept running into. Every time I wanted to try a new database feature, debug something tricky, or reproduce a customer issue, I ended up rebuilding much of the same infrastructure: DNS, TLS, Docker networking, database topologies, users and test data. Over the years, I wrote scripts to automate this but I still found myself copying and pasting post-installation steps from one lab to the next. 

This is a companion discussion topic for the original entry at https://percona.community/blog/2026/09/16/vibe-coding-a-database-lab/

    
    [Percona XtraDB 84 - Clone SST joiner aborts with “Operation not permitted” on Ubuntu 24.04: mv -n exits 1 under errexit when datadir already has *.pem][4]

      Project: PXC 
Component: SST (clone) 
Affects version: 8.4.10-10 (code path also present on 8.0 and trunk branches) 
Severity: a node that previously belonged to the cluster cannot rejoin via clone SST 
Summary
On Ubuntu 24.04, a node that has already been part of the cluster cannot rejoin through wsrep_sst_method=clone. The joiner script exits with status 1, and mysqld reports it as SST script aborted with error 1 (Operation not permitted). The “Operation not permitted” text is only strerror(1); no permission problem is involved. 
The cause is in scripts/wsrep_sst_clone.sh: 

The script runs with set -o nounset -o errexit (line 97 on the 8.4 branch).
The joiner cleans the datadir with find ... -regex $cpat -prune -o -exec rm -rfv {}. The default cpat contains .*\.pem$, so *.pem files in the datadir are preserved (lines 1023-1024).
mysqld --initialize-insecure runs into a temporary datadir. It generates private_key.pem and public_key.pem, the RSA key pair used by caching_sha2_password.
...

    
    [Percona Search for MongoDB 1.70.3-1 is now available as Technical Preview][5]

      On behalf of the entire product and engineering team for MongoDB at Percona, I’m pleased to share that we’re starting a Technical Preview with version 1.70.3-1. 
This is a Technical Preview. Please don’t run it in production yet. 
Specifically, this version may not fully work with the rest of the Percona software for MongoDB: 

Percona Backup for MongoDB (PBM) doesn’t yet cover search indexes.
Percona Operator for MongoDB search support, recently released in 1.23.0, is currently in tech preview and limited to 1 search node. More automation is coming in the next version.
Percona Monitoring and Management doesn’t have search dashboards yet, but they’re coming!

Point it at a copy of your data. Then share with us where it breaks for you. 
Percona Search for MongoDB requires Percona Server for MongoDB 8.3, which we shipped as a Technical Preview recently - the first Percona release carrying the $search, $searchMeta, $vectorSearch, $rankFusion and $scoreFusion stages that the search process...

    
    [Question About PITR Continuity][6]

      Hi, the scenario is technically feasible. PBM will resume saving oplog from the proper position after full backup is done (there should be no gaps). One thing to keep in mind is oplog apply is single threaded, so applying a large batch of oplog could take significant amount of time. This is why the most recent full backup is always recommended as the base backup when doing PITR. 
For your particular use case perhaps it is better to use Percona ClusterSync for MongoDB to continuously replicate data (it handles initial data copy as well)

    

  




**New for you**

* [Prove the Backup: A Percona Distribution for PostgreSQL … | Percona Community][7] - 1 - [Community website]
* [Help shape PMM navigation (5 minutes, anonymous test)][8] - 1 - [Percona Monitoring and Management (PMM)]
* [PostgreSQL as a Workflow Engine: Building Reliable … | Percona Community][9] - 1 - [Community website]



[1]: https://forums.percona.com/
[2]: https://forums.percona.com/t/question-about-pt-online-schema-change-and-performance-schema/41275
[3]: https://forums.percona.com/t/vibe-coding-a-database-lab-how-i-built-dbcanvas-to-stop-percona-community/41266
[4]: https://forums.percona.com/t/percona-xtradb-84-clone-sst-joiner-aborts-with-operation-not-permitted-on-ubuntu-24-04-mv-n-exits-1-under-errexit-when-datadir-already-has-pem/41268
[5]: https://forums.percona.com/t/percona-search-for-mongodb-1-70-3-1-is-now-available-as-technical-preview/41271
[6]: https://forums.percona.com/t/question-about-pitr-continuity/41270
[7]: https://forums.percona.com/t/prove-the-backup-a-percona-distribution-for-postgresql-percona-community/41263
[8]: https://forums.percona.com/t/help-shape-pmm-navigation-5-minutes-anonymous-test/41277
[9]: https://forums.percona.com/t/postgresql-as-a-workflow-engine-building-reliable-percona-community/41269
[10]: https://forums.percona.com/



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

[11]: https://forums.percona.com/my/preferences/emails
[12]: https://forums.percona.com/email/unsubscribe/3c1b54b434d8e323c437ab3b3ce6a6f17ac80b8d91142c2a94faa85be6f13fe9

Accession

nse/percona/2026-09-21/2039

From

Percona Community Forum · notifications@percona1.discoursemail.com

Sent

21 September 2026 · 00:00 UTC