XLOG generation peak
All times in UTC. - 5:39pm: PagerDuty alert: "Postgres is generating XLOG too fast, expect this to cause replication lag" https://gitlab.pagerduty.com/incidents/PGXBWQH - 5:44pm: Peak corroborated. Already starting to trend down ![Captura_de_pantalla_2018-01-21_a_la_s__14.43.50](/uploads/21dede2b9c6900d58ad8efe6d20c15b3/Captura_de_pantalla_2018-01-21_a_la_s__14.43.50.png) Some other anormalities at the time: - Postgres IO Utilization ![Captura_de_pantalla_2018-01-21_a_la_s__14.49.23](/uploads/70a26a37958be35a3ed4f5d31b1db8aa/Captura_de_pantalla_2018-01-21_a_la_s__14.49.23.png) - NFS timeout peak for nfs-file-12 ![Captura_de_pantalla_2018-01-21_a_la_s__14.48.53](/uploads/1acdf02d00ad98c2f0b568ec349bdfde/Captura_de_pantalla_2018-01-21_a_la_s__14.48.53.png) - 5:49pm: Alert resolved. XLOG generation levels back to normal: ![Captura_de_pantalla_2018-01-21_a_la_s__14.56.41](/uploads/c12aac76f3e1412905c5fa3e6e3823bc/Captura_de_pantalla_2018-01-21_a_la_s__14.56.41.png) /cc @gl-infra
issue