mirror of
https://github.com/cozystack/cozystack.git
synced 2026-10-27 23:27:58 +09:00
LastFailedArchiveTime compares the last failed archival with the last successful one, so it resolves as soon as any segment gets through. A cluster whose archiving fails intermittently, or runs slower than it writes WAL, clears that alert every time one upload succeeds while the queue of segments waiting on the Postgres volume keeps growing, until the volume is full and the database stops. That alert is also only a warning. A healthy archiver empties archive_status within seconds of each WAL switch. A queue that has not been empty once in 30 minutes means point in time recovery is falling behind whatever the archiver is reporting, so that is what pages, as critical. Idle clusters and replicas have an empty queue and stay quiet. Assisted-by: LLM Signed-off-by: Alexey Artamonov <aleksei.artamonov@aenix.io>