[05:22:00] <marostegui>	 Amir1 federico3 if you can fully complete https://phabricator.wikimedia.org/T391056 for s8, that would unblock me from creating x3 topology. Thanks
[10:33:33] <Amir1>	 marostegui: so it's done on all replicas. After topology change, it shouldn't impact x3 being added there (auto_schema should be okay handling them as long as the candidate master doesn't end up being the master of x3 which I'm sure won't be the case). Doing it on s8 masters is not possible live
[10:34:22] <Amir1>	 what I meant is "you're good to go"
[10:37:04] <marostegui>	 Amir1: ok then thanks
[10:40:22] <Amir1>	 federico3: we don't need to do master of s8 before going to other sections
[10:40:40] <federico3>	 should we move on to another section as you were saying - s5?
[10:41:20] <Amir1>	 yup
[10:41:48] <Amir1>	 we need to do switchover of s8 but I prefer to bundle some more changes before doing that
[11:47:07] <federico3>	 ok, starting s5
[22:27:09] <swfrench-wmf>	 hello data-persistence friends, swift question - is there a recommended "low impact" way to query swift-proxy access logs? specifically, I'd like to examine whether some segment reads from docker registry are receiving 416 responses during a couple of minute-long time windows on the 9th (related to https://phabricator.wikimedia.org/T390251).