You are browsing a read-only backup copy of Wikitech. The live site can be found at wikitech.wikimedia.org
Postgres: Difference between revisions
imported>Krinkle (Created page with "{{Stub-links}}") |
imported>Hnowlan (Added brief note on POSTGRES_HOT_STANDBY_DELAY.) |
||
| Line 1: | Line 1: | ||
== Monitoring == | |||
=== POSTGRES_HOT_STANDBY_DELAY === | |||
This alert indicates that a replica has fallen behind the master database in replication. This is not immediately a cause for panic, as a host can recover assuming it is not left out of replication for long. However, the postgres logs should be examined and connectivity between individual replicas and the master should also be checked. | |||
If many or all hosts in the maps cluster are issuing this alert, it could be the case that the OSM dataset is being refreshed - during this operation it is likely that hosts will fall behind as large numbers of changes happen on the master during import. Check the cluster masters for import processes - generally this is a passing problem and will self-resolve over time. [[Service restarts#maps|Avoid restarting postgres]] hosts while the <code>osm-replicate</code> or <code>osmosis</code> processes are running on the master. | |||
{{Stub-links}} | {{Stub-links}} | ||
Revision as of 13:17, 7 January 2021
Monitoring
POSTGRES_HOT_STANDBY_DELAY
This alert indicates that a replica has fallen behind the master database in replication. This is not immediately a cause for panic, as a host can recover assuming it is not left out of replication for long. However, the postgres logs should be examined and connectivity between individual replicas and the master should also be checked.
If many or all hosts in the maps cluster are issuing this alert, it could be the case that the OSM dataset is being refreshed - during this operation it is likely that hosts will fall behind as large numbers of changes happen on the master during import. Check the cluster masters for import processes - generally this is a passing problem and will self-resolve over time. Avoid restarting postgres hosts while the osm-replicate or osmosis processes are running on the master.
Related pages
- Puppet (← links)
- Service restarts (← links)
- Postgresql (redirect page) (← links)
- PostgreSQL (redirect page) (← links)
- Openstreetmap Databases (← links)
- Cumin (← links)
- Netbox (← links)
- Maps/OSM Database Legacy (← links)
- User:MSantos/Maps/OSM Database (← links)