[11:17:09] dhinus: I'm sorry that I'm creating conflicts with your work, but I have a few patches starting from https://gerrit.wikimedia.org/r/1153123 that are needed to run maintain-views on x3 [11:41:12] taavi: no worries, let's sync in a moment when I'm back at my pc [12:31:43] taavi: back, my cookbook run is stopped, do you want to run yours? [12:32:43] I'm reviewing your patch [12:33:06] dhinus: hm? I don't have a cookbook to run, I have patches that need reviews and are going to conflict with your dry-run/testing patches [12:34:10] I mean, do you want to merge your patch + run maintain-views to apply it? [12:34:43] if you run maintain-views with --database it should complete more quickly than for me [12:34:57] we can merge it, sure. but I already ran it on clouddb1016 to test that it works, and 1020 is still being setup by data-persistence [12:35:12] https://phabricator.wikimedia.org/T390954#10879207 is the current status of that project [12:35:28] ok so no rush actually, it's only that your changes to maintain-views.py overlap with my other refactoring? [12:35:33] yes [12:35:36] ok got it :) [12:36:10] then I will retry my full "maintain-views" on all dbs for T390767 [12:36:11] T390767: Remove the compatibility layer of block schema in wikireplicas - https://phabricator.wikimedia.org/T390767 [12:36:15] well, there is some rush since I want to get the new section in service so that our users will get updated results :-) [12:36:26] i think your cookbook will fail unless my patches are merged [12:36:46] hmmm why? will it not just ignore the new section? [12:37:06] the config file lists the section as existing, so unless my patch is applied it'll try to read the non-existent dblist [12:37:20] right [12:37:27] (for moving traffic, in theory that's just https://gerrit.wikimedia.org/r/c/operations/puppet/+/1149605. but I wanted to get your approval before merging it) [12:37:51] yep, let's try to get both your patches merged then [12:38:20] in addition to the one patch to unbreak maintain-views, that stack has two more that make working with multiple sections much nicer but are not strictly necessary [12:38:44] ok, want to give +1s and I'll merge then? [12:38:45] should we wait until 1020 is ready before merging the traffic patch? https://gerrit.wikimedia.org/r/c/operations/puppet/+/1149605 [12:43:33] both options are possible, merging it now would send everything to 1016 [12:53:18] ok I was lost in all the config layers. I see that x3 in clouddb1020 is depooled in conftool [12:56:19] all +1d [13:06:58] huh, why is the 1016 service now down on the haproxy side? [13:07:34] I saw marostegui added a downtime, let's ask in #-data-persistence [13:07:52] T390954 [13:07:53] T390954: Set up x3 replication to wikireplicas - https://phabricator.wikimedia.org/T390954 [14:55:19] FYI I depoooled clouddb1019:s4 to run maintain-views, there are some old queries that are stuck in "Killed" [14:55:29] I'll leave it depooled for a while and see if they eventually terminate [18:01:30] clouddb1019 is repooled, more details in T390767 [18:01:31] T390767: Remove the compatibility layer of block schema in wikireplicas - https://phabricator.wikimedia.org/T390767 [19:24:38] Hello need a little help deciding what do with this toolforge membership request https://toolsadmin.wikimedia.org/tools/membership/status/1940. Seems to know what tool they want to contribute to and the maintainers (though I can imagine it is somehow easy to find the name of a tool and it’s maintainers somewhere online), but the account was created like 29hrs ago and has no activities whats so ever. [19:41:20] Raymond_Ndibe: I think I would approve them. They could have looked up https://toolsadmin.wikimedia.org/tools/id/insights-hub, but I'd guess it is a legit request.