Wednesday, 2022-07-20

opendevreviewMatthew Oliver proposed openstack/swift master: formpost: deprecate sha1 signatures  https://review.opendev.org/c/openstack/swift/+/83371305:31
opendevreviewTim Burke proposed openstack/swift master: sharding: Skip shards that can't include any new subdir entries  https://review.opendev.org/c/openstack/swift/+/83739717:03
opendevreviewTim Burke proposed openstack/swift master: ring: Introduce a v2 ring format  https://review.opendev.org/c/openstack/swift/+/83426117:45
kotahello?21:02
seongsoochoHi!21:02
mattoliverMorning21:03
mattoliverHaven't seen timburke yet21:03
timburke#startmeeting swift21:04
opendevmeetMeeting started Wed Jul 20 21:04:00 2022 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.21:04
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:04
opendevmeetThe meeting name has been set to 'swift'21:04
timburkewho's here for the swift meeting?21:04
kotao/21:04
acoleso/21:04
seongsoochoo/21:04
timburkesorry to be late21:05
timburkeas usual, the agenda's at https://wiki.openstack.org/wiki/Meetings/Swift21:05
mattolivero/21:05
timburkefirst up21:05
timburke#topic sha1 deprecations21:05
timburkewe've had these patches in-flight for a while, but i think we're getting close on merging21:05
timburke#link https://review.opendev.org/c/openstack/swift/+/84586221:06
timburkebrings sha1 back to enabled-by-default, but keeps the deprecation warning21:06
timburkefor tempurl21:06
timburke#link https://review.opendev.org/c/openstack/swift/+/83371321:06
timburkeadds sha1 deprecation to formpost, with a lot of common-code extraction21:07
timburkemattoliver's got a +2 on the first, and done a good bit of follow-ups on the second (thanks!)21:08
mattoliverWell we pretty much had to do the same thing twice because they were basically the same. So we should it it property 21:08
timburkedoes anyone feel strongly about wanting to review either of these? otherwise, i'll plan on reviewing the formpost patch with an eye toward landing them both this week21:08
timburkeshortly after merging them, i'd like to get a release out, since we haven't had a release since march21:10
mattoliverI'm good with that, but that probably doesn't count :p 21:10
acolessounds like a good plan21:11
timburkeall right then21:12
kota+121:12
timburke#topic backend ratelimiting21:12
timburkei remember that we had a plan to do some testing in a staging environment -- did we ever get around to that? (mattoliver, i think?)21:12
mattoliveroh yeah, I think our SRE team were going to test that in staging.. not sure where that got too. I'll reach out or even look up the ticket.21:14
timburkecool, thanks -- i just want to make sure it hasn't fallen off our radars21:14
timburke#topic stuck sharding DBs21:14
timburkethis seems to have been an area of a lot of concern since our last meeting21:15
timburke(sorry that it's been so long -- things kept coming up)21:15
timburkei've been doing my best to catch up on patches, maybe acoles or mattoliver could explain the observed issue(s) better, though21:15
mattoliverThis has flushed out 2 different things. 21:16
mattoliver1. The sharder doesn't process deleted undsharded dbs even if they have shards21:16
mattoliver2. our is_delete method isn't really consistant21:16
mattoliverthe first one we have a patch for, and it'll mean these deleted unsharded dbs will actaully get processed21:17
mattoliverI'll find the link in a sec (on my phone)21:17
timburkeand i think there's a 1a. corollary -- an unsharded DB with shards needs to progress to sharded since it won't replicate21:18
timburke#link https://review.opendev.org/c/openstack/swift/+/84954821:18
mattoliverin doing the first one, we also found that we didn't migrate the deleted_timestamp when migrating between the retiring and fresh db. 21:18
mattoliveryeah21:18
timburke^^^ sharder: process deleted DBs21:18
timburke#link https://review.opendev.org/c/openstack/swift/+/84945021:18
timburke^^^ Sharding: Sync container_stat table with fresh db21:18
mattoliverSo those "should" allow deleted shards to be processed and become sharded.21:19
acolesyes, so we noticed that once we fixed sharder to process deleted dbs, it would effectively undelete then :( so that needed a fix too21:20
timburkebetween all three patches, though, we're pretty sure we should resolve the issue, yeah? except for a new issue acoles diagnosed today21:21
acolesyes and yes21:21
timburke(namely, once you've removed all assignments for a device from the container ring, the sharder stops being able to find a device where we can write shard dbs)21:22
mattoliverWe had some objects in the shards in a deleted unsharded container. So with these we now shold move to sharded state, we'll find these objects, process them, and then be really deleted.21:22
mattoliveroh ouch.. yeah, that's a probably21:22
mattoliver*problem21:22
mattoliverSo just need to add the device at 0 weight and the sharder will find it again21:23
timburkenow, i got the impression that there were a bunch of other patches flying around related to the investigation -- i'd appreciate it if owners could go through them this week and either abandon them or leave a comment about how we really should keep pushing on them and why21:24
mattoliveryeah, those are bascially around 2. where is_deleted isn't a complete empty check like .empty. 21:25
timburkei tried to capture them on the agenda -- though i may have missed some (or erroneously flagged some)21:25
mattoliverso more dicussions are needed. 21:25
timburkefair enough. i just want to have a sense of what's still an active area :-)21:26
mattoliverbut yeah we have a different patches floating around we should consolidate21:26
timburkeall right -- i only have one other item for the week21:27
timburke#topic ring v221:27
acolestimburke: ack re abandoning21:27
timburkemattoliver and i are getting pretty happy with where the head of the chain is ending up -- if anyone else wants to take a look, now's the time21:28
timburkeotherwise we'll probably just merge it when we're both happy, like the plan for the sha1 patches21:28
mattoliveryup otherwise I'm going to press the big +A button :) 21:28
timburkeit features a new on-disk format, and new apis for interacting with rings, and plans for extensions -- so i wanted to flag it up as something that might warrant more eyes21:29
timburke#link https://review.opendev.org/c/openstack/swift/+/83426121:30
timburkefor the main patch21:30
timburke#link https://review.opendev.org/c/openstack/swift/+/83462121:31
timburke adds the rebalance history21:31
zaitcevoh I see. I was just about to ask "is this really the main patch".21:31
timburkeand recently i added a repair function for what i could imagine being an easy-to-accidentally-do failure mode (unzipping then naively re-zipping a ring file)21:32
timburke#link https://review.opendev.org/c/openstack/swift/+/84944121:32
timburkeall right, that's all i've got21:33
timburke#topic open discussion21:33
timburkeanyone have other topics to bring up this week?21:33
timburkeall right then21:36
timburkethank you all for coming, and thank you for working on swift!21:36
timburke#endmeeting21:36
opendevmeetMeeting ended Wed Jul 20 21:36:33 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:36
opendevmeetMinutes:        https://meetings.opendev.org/meetings/swift/2022/swift.2022-07-20-21.04.html21:36
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/swift/2022/swift.2022-07-20-21.04.txt21:36
opendevmeetLog:            https://meetings.opendev.org/meetings/swift/2022/swift.2022-07-20-21.04.log.html21:36
mattoliver\o/ breakfast time. thanks everyonw21:37
mattolivergood to see you kota and seongsoocho 21:37
kotathx mattoliver o/21:37
* kota is also going to find breakfast21:38
seongsoochothanks !21:40
opendevreviewTim Burke proposed openstack/swift master: DB Replicator: Add handoff_delete option  https://review.opendev.org/c/openstack/swift/+/82863721:48

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!