[06:59:19] <taavi>	 could someone confirm if what I'm seeing on whhttps://phabricator.wikimedia.org/T301993#7931168 is normal or not?
[06:59:27] <taavi>	 bah, https://phabricator.wikimedia.org/T301993#7931168
[09:02:53] <marostegui>	 taavi: yes, cause the first domain_id is 0 and it gets stored
[09:04:42] <taavi>	 marostegui: ok! is the command I posted on a few commens above correct too?
[09:05:12] <marostegui>	 taavi: yes, that's correct
[10:27:27] <marostegui>	 jynus: db2102 won't run s2 anymore right? https://gerrit.wikimedia.org/r/c/operations/puppet/+/791564 I will clean it up from orchestrator if that's the case
[10:28:22] <jynus>	 no, I thought it got removed automatically after a week if not done manually?
[10:28:36] <jynus>	 wait
[10:28:46] <jynus>	 that would be db2101
[10:31:07] <marostegui>	 yes sorry 101
[10:31:50] <marostegui>	 it gets removed automatically, but I was scanning orchestrator in general, so I will get it removed manually so it is "clean"
[10:32:16] <jynus>	 yes, sorry, I updated zarcillo but don't read orchestrator too often
[10:32:22] <marostegui>	 nah no worries
[10:32:38] <marostegui>	 done
[11:16:26] <Amir1>	 marostegui: I'm a bit confused about this :( https://phabricator.wikimedia.org/T299421#7934073 
[11:16:38] <Amir1>	 the join order is correct so it really shouldn't take long
[11:18:39] <marostegui>	 will check later 
[11:18:56] <Amir1>	 thanks
[12:24:08] <jynus>	 BTW, I saw this last week https://www.percona.com/blog/dump-performance-comparison-mysqldump-vs-mysql-shell-utilities-vs-mydumper/ - I wonder if anyone has experience with zstd compression?
[12:25:08] <jynus>	 no version of debian has mydumper >=0.11.3, but I was wondering if it was worth researching it
[14:21:22] <taavi>	 and toolsdb is now using gtid replication :-)
[14:22:22] <Amir1>	 \o/
[15:46:42] <icinga-wm>	 PROBLEM - MariaDB sustained replica lag on m1 on db1117 is CRITICAL: 152.4 ge 2 https://wikitech.wikimedia.org/wiki/MariaDB/troubleshooting%23Replication_lag https://grafana.wikimedia.org/d/000000273/mysql?orgId=1&var-server=db1117&var-port=13321
[15:47:26] <icinga-wm>	 PROBLEM - MariaDB sustained replica lag on m1 on db2078 is CRITICAL: 206.4 ge 2 https://wikitech.wikimedia.org/wiki/MariaDB/troubleshooting%23Replication_lag https://grafana.wikimedia.org/d/000000273/mysql?orgId=1&var-server=db2078&var-port=13321
[15:56:19] <icinga-wm>	 RECOVERY - MariaDB sustained replica lag on m1 on db2078 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=db2078&var-port=13321
[16:10:47] <icinga-wm>	 RECOVERY - MariaDB sustained replica lag on m1 on db1117 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=db1117&var-port=13321
[16:16:12] <Amir1>	 This one is not me but I think I put too short downtime for some of the schema changes, if a depooled host alarms, don't be alarmed