Add a resync action to rebuild a broken standby
Bug #1829816 reported by
Stuart Bishop
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PostgreSQL Charm |
Triaged
|
High
|
Unassigned |
Bug Description
The standby database can get out of sync with the master in various cases (eg. extreme lag) and needs to be recovered. We should add an action to do this, which just needs to a) confirm the unit really truely is a standby and b) set the relevant reactive states to trigger a rebuild from the master.
Changed in postgresql-charm: | |
status: | New → Triaged |
importance: | Undecided → High |
To post a comment you must log in.