Percona Postgres: Primary promotion happened during parameter change and behavior during pod delete forcefully

PostgreSQL Percona Distribution for PostgreSQL
1

Please clarify understanding to the below questions.

  1. We changed the parameter “patroni.leaderLeaseDurationSeconds,” which triggered a pod restart one at a time for both the primary and replica pods. We also observed a failover, where the replica was promoted. Is this expected behavior?

  2. We conducted a test case by forcefully deleting the pod and observed that the primary pod’s role remained unchanged after the restart, but the TimeLine was updated. Is this expected behavior?