[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-19 02:15:32 UTC

7 New Topics
14 New Users


  
  ### Popular Topics

    [Xbcloud get incorrect (truncated) files][2]

      # xbcloud get s3://rmas/project-middleware-100/mysql-382/middleware-backup-6055 --s3-endpoint=‘http://s3.middleware.bj’ --s3-access-key=‘XXXXXX’ --s3-secret-key=‘XXXXXXXX’ --s3-region=‘Beijing’  --parallel=10 | xbstream -x -C /tmp/backup --parallel=10; 
error: http request failed: Couldn’t resolve host name 
error: http request failed: Couldn’t resolve host name 
261020 03:32:46 xbcloud: Successfully connected. 
261020 03:32:46 xbcloud: [0] Downloading project-middleware-100/mysql-382/middleware-backup-6055/xtrabackup_slave_info.00000000000000000000. 
261020 03:32:46 xbcloud: [0] Downloading project-middleware-100/mysql-382/middleware-backup-6055/xtrabackup_logfile.00000000000000000000. 
261020 03:32:46 xbcloud: [0] Downloading project-middleware-100/mysql-382/middleware-backup-6055/xtrabackup_tablespaces.00000000000000000000. 
261020 03:32:46 xbcloud: [0] Downloading project-middleware-100/mysql-382/middleware-backup-6055/xtrabackup_info.00000000000000000000. 
261020 03:32:46 xbcloud:...

    
    [Three Days in Prague with the Percona MongoDB Team | Percona Community][3]

      Our MongoDB team at Percona works remotely, spread across many countries and time zones. Most days that works well, but once in a while it helps to be in the same room. In October we met in Prague for three days to plan next year, look at how we work, and spend some time together away from our laptops. 

This is a companion discussion topic for the original entry at https://percona.community/blog/2026/10/19/three-days-in-prague-with-the-percona-mongodb-team/

    
    [Prove your PostgreSQL restore before a Kubernetes migration | Percona Community][4]

      A migration plan can name every component and still leave the useful question unanswered: if the move fails, can the application work again? A dump file is not that answer. A restore into a new database, followed by the checks the application actually needs, is. 

This is a companion discussion topic for the original entry at https://percona.community/blog/2026/10/20/prove-postgresql-restore-before-kubernetes-migration/

    
    [Primary killed by Docker stop timeout on host reboot vs. hardware crash: data loss and recovery behavior (PSMDB 8.0)][5]

      Hello, 
I have a 4-node MongoDB replica set: 

Node 1: Primary
Node 2: Secondary
Node 3: Secondary
Node 4: Hidden

PBM agents run on all nodes. 
MongoDB runs in Docker containers: 

percona/percona-server-mongodb:8.0.19-7

Additional details 

PBM 2.13.0, PITR enabled (the oplog slicer runs on the hidden node), daily logical backups.
Default write concern is the implicit one (getDefaultRWConcern returns w: "majority", source implicit).
Containers are managed with Docker Compose, restart: always.
Hosts are rebooted sequentially at night (hidden node first, then the other members, one at a time). No explicit rs.stepDown() is performed before the reboot of the node that is currently primary.

What we observed 
With Docker’s default stop timeout (10 seconds), when the host running the primary was rebooted, Docker sent SIGTERM to the mongod container and then SIGKILL after 10 seconds. In the mongod logs of the old primary we saw it entering quiesce mode (“The server is in quiesce mode and w...

    
    [Backing up a small PSMDB 8.0 replica set in Docker without PBM and NFS: recommended approaches?][6]

      Hello, 
I’m looking for pointers and opinions on the simplest reliable way to back up a MongoDB replica set without using PBM and a shared NFS storage. 
Current setup 

Percona Server for MongoDB 8.0.19-7, running in Docker containers (percona/percona-server-mongodb:8.0.19-7)
4-node replica set: Primary, 2 Secondaries, 1 Hidden member
Two independent replica sets on the same hosts, both small: a logical backup is about 200 MB for the larger one and under 10 MB for the smaller one; a physical backup is about 2 GB
Today: PBM 2.13.0 with filesystem storage on an NFS share, PITR enabled, daily logical and weekly physical backups
The NFS server runs on the hidden node itself, so backups live on a member of the cluster they protect
All VMs are covered by a daily VM-level backup (snapshot based). We do not control the exact time each VM is backed up, only the global job.

Why we are considering a change 
PBM works, but the NFS part added complexity and caused real issues: 

containers startin...

    

  




**New for you**

* [PXC operator 1.20.0: custom user reconcile loops forever (view definer, error 4006) and repeated CREATE DATABASE aborts app transactions][7] - 1 - [Percona Operator for MySQL]
* [Make pg_stat_monitor stable again! | Percona Community][8] - 1 - [Community website]



[1]: https://forums.percona.com/
[2]: https://forums.percona.com/t/xbcloud-get-incorrect-truncated-files/41355
[3]: https://forums.percona.com/t/three-days-in-prague-with-the-percona-mongodb-team-percona-community/41353
[4]: https://forums.percona.com/t/prove-your-postgresql-restore-before-a-kubernetes-migration-percona-community/41359
[5]: https://forums.percona.com/t/primary-killed-by-docker-stop-timeout-on-host-reboot-vs-hardware-crash-data-loss-and-recovery-behavior-psmdb-8-0/41357
[6]: https://forums.percona.com/t/backing-up-a-small-psmdb-8-0-replica-set-in-docker-without-pbm-and-nfs-recommended-approaches/41358
[7]: https://forums.percona.com/t/pxc-operator-1-20-0-custom-user-reconcile-loops-forever-view-definer-error-4006-and-repeated-create-database-aborts-app-transactions/41363
[8]: https://forums.percona.com/t/make-pg-stat-monitor-stable-again-percona-community/41352
[9]: https://forums.percona.com/



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

[10]: https://forums.percona.com/my/preferences/emails
[11]: https://forums.percona.com/email/unsubscribe/33bec01f1a7123ae41169ebc14e36faf616915891acd1a5f4258cf64dd8aeae4

Accession

nse/percona/2026-10-26/4996

From

Percona Community Forum · notifications@percona1.discoursemail.com

Sent

26 October 2026 · 02:00 UTC