[14:56:51] <icinga-wm>	 PROBLEM - MariaDB sustained replica lag on s4 on db1160 is CRITICAL: 2 ge 2 https://wikitech.wikimedia.org/wiki/MariaDB/troubleshooting%23Replication_lag https://grafana.wikimedia.org/d/000000273/mysql?orgId=1&var-server=db1160&var-port=9104
[14:59:09] <icinga-wm>	 RECOVERY - MariaDB sustained replica lag on s4 on db1160 is OK: (C)2 ge (W)1 ge 0 https://wikitech.wikimedia.org/wiki/MariaDB/troubleshooting%23Replication_lag https://grafana.wikimedia.org/d/000000273/mysql?orgId=1&var-server=db1160&var-port=9104
[15:00:34] <taavi>	 hey, apparently db1154 (s5 sanitarium master) is not replicating, causing replag on the s5 cloud replicas
[18:53:12] <marostegui>	 taavi: it is running a long schema change 
[18:53:52] <taavi>	 marostegui: ok, makes sense, thanks
[18:54:22] <taavi>	 is there some tool I can use to tell if that's happening on a particular host?
[18:56:42] <marostegui>	 taavi: probably SAL is the best one to know when a host is depooled for a schema change