Wednesday, 2021-09-08

opendevreviewMatthew Oliver proposed openstack/swift master: Sharding: SR without an epoch can't merge over one with an epoch  https://review.opendev.org/c/openstack/swift/+/80782406:39
mattoliver^ haven't decided if that's the best way forward for that. But we've seen an interesting "reset" root own_shard_range happen in prod only a few times, but enough to think about the cause. 06:41
*** elodilles_pto is now known as elodilles08:44
*** timburke__ is now known as timburke20:04
timburkeit's been quiet lately -- my usual 2-week dashboard is rather short ;-) https://review.opendev.org/dashboard/?title=The%20Fortnight%20That%20Was&foreach=-age:2week&Landed%20(Server)=is:merged%20project:openstack/swift&Landed%20(Client)=is:merged%20project:openstack/python-swiftclient&Active%20(Server)=is:open%20project:openstack/swift&Active%20(Client)=is:open%20project:openstack/python-swiftclient&Abandoned%20(Server)=is:abandoned%20pr20:04
timburkeoject:openstack/swift&Abandoned%20(Client)=is:abandoned%20project:openstack/python-swiftclient20:04
timburke:-( stupid line breaks20:05
timburkethe interesting bit is https://review.opendev.org/dashboard/?title=The%20Fortnight%20That%20Was&foreach=-age:2week&Landed%20(Server)=is:merged%20project:openstack/swift&Landed%20(Client)=is:merged%20project:openstack/python-swiftclient&Active%20(Server)=is:open%20project:openstack/swift&Active%20(Client)=is:open%20project:openstack/python-swiftclient right now, anyways20:05
*** elodilles is now known as elodilles_pto20:12
timburkealmost meeting time!20:51
timburkeour agenda's prety light, as is the recent patch activity, so it might be a fairly short one20:52
mattoliverMorning, oh I like a good dashboard :) 20:57
kotamorning20:59
mattoliverkota: o/21:02
kotamattoliver: o/21:02
* kota is now checking https://wiki.openstack.org/wiki/Meetings/Swift for meeting...21:02
mattoliverwe do have one. timburke said so a few minutes ago. he's obviously distracted :)21:03
kotaall right, thx21:03
timburke#startmeeting swift21:04
opendevmeetMeeting started Wed Sep  8 21:04:01 2021 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
timburkesorry, i *was* distracted ;-)21:04
timburkewho's here for the swift meeting?21:04
kotahello21:04
mattolivero/21:04
timburkei think acoles is out, and we'll just see as we go whether clayg and zaitcev (and anyone else) are around21:05
timburkeas usual, the agenda's at https://wiki.openstack.org/wiki/Meetings/Swift21:05
timburke#topic PTG21:06
-opendevstatus- NOTICE: The Gerrit service on review.opendev.org is going offline momentarily for a host migration and zuul upgrade, downtime should be only a few minutes.21:06
timburkejust a reminder to add any topics you want to discuss to the etherpad21:06
timburke#link https://etherpad.opendev.org/p/swift-ptg-yoga21:06
mattoliverahh, that'll explain why I couldn't get to gerrit just now21:06
kotalol21:07
mattoliverI think I added a few. But no doubt there are more and we still need to add the normal ones like opps feedback :)21:07
timburkewe're a little more than a month away; it'll be good to see everyone again (even if just via video chat)21:07
timburke#topic ring v221:08
zaitcevI added that little e-mail from Arkady21:08
zaitcevto the Etherpad.21:09
timburkethanks zaitcev!21:09
timburkei don't know that we've proposed any new patches for ring v2 yet, but i've got a chain that i've started on; hopefully i'll have it to a state that i'm happy to push it up in another week or two21:10
timburkewhile i was doing that, i wrote up some history of ring formats (as best as i could make out): https://gist.github.com/tipabu/435fc63f1aa76d6b346956571a39366521:10
mattoliveroh nice a gist, I'll take a look. we did have  https://review.opendev.org/c/openstack/swift/+/803665 which implemented a part of it as POC to see how it looked. But looking forward to seeing what you've done esp post etherpad. 21:11
mattoliverI think that was right can't get into gerrit to double check :P21:12
timburkehuh. worked for me -- "ring: store actual ring replica count to better deserialize"21:12
mattoliveroh its back! 21:13
mattoliverlooking forward to working out this v2 serialization format, because it'll open the doors to last_primary improvements we can add to things21:14
timburkeyeah, that's my thinking, too: we can make a few different things a good bit smarter if they've got some ring history21:15
timburke#topic sharder and reconciler21:15
timburke#link https://review.opendev.org/c/openstack/swift/+/80074821:15
mattoliverNot as much progress here as I'd like in the last week or so21:16
timburkeno worries -- i just wanted to check in on it and see what we can do to help get it moving again21:16
mattoliverreconciler does things a little different. and we were spitballing ways to make the root -> shard SPI migrations act similarly21:16
mattoliverI left a suggestion in the patch discussion.. and now waiting on others to comment.21:17
mattoliverbut Al's on vacation.. so kinda got stalled.21:17
mattoliverhopefully have an update next week :)21:17
timburkesounds good. and i'll try to load up the problem in my head and get a useful review out :-)21:18
mattoliverthanks :)21:18
timburkeone last-minute topic21:19
timburke#topic reviewed but not merged patches21:20
timburkei've got a few patches w/ a +2 but no +A: https://review.opendev.org/q/project:openstack/swift+label:Code-Review%252B2+is:open+-age:52w21:20
timburkeanybody want to call for more eyes on some of those, or should we just merge them?21:21
timburkethe query params patch still has me nervous, but i think the others are probably good to go? but then, i'm biased21:21
zaitcevWhy nervous? Security?21:22
mattoliverThe fact that they have a +2 means they're in good shape. Only worry is, was the +A not added because the reviewer wasn't 100% sure? I'm leaning towards just landing them. But I'll give them a parse over today and land or comment.21:23
zaitcevYes. I wrote "The scenarios Tim is considering are concerning, but fortunately the allowed_headers list is empty by default." Now I cannot remember a blessed thing about that patch. What did I mean exactly ....21:24
mattoliverlol21:24
zaitcevAlways write it down!21:24
zaitcevThe EC watcher is no big deal, I can just land it now.21:25
zaitcevOh, righ21:27
zaitcevI see why. It has no tests.21:27
timburkeswitch it to a -1 then ;-) i can work on adding some21:28
zaitcevI meant to signal "fine by me, but you guys are always so strict about tests, so I'll leave it with just +2 for now".21:28
timburkei do have some security concerns on the tempurl patch, yeah. the default is secure, but the motivation for the patch makes me think that it's likely people will allow multipart-manifest, which seems to have a security impact21:29
timburkeall right, that's all i've got21:30
timburke#topic open discussion21:30
timburkeanything else we should talk about this week?21:30
mattolivermaybe hold off on the tempurl and let's discuss it at PTG maybe?21:31
mattoliverwe can brainstorm security impact maybe21:31
zaitcevGoing back to right history gist, we have a "History" section in https://docs.openstack.org/swift/latest/overview_ring.html21:31
zaitcevIs this something worth rolling into one document or whatevs21:31
zaitcevs/right /ring /21:32
timburkeyeah, probably a good idea. i can work on getting a docs patch up21:32
mattolivermade some interesting progress on the opentracing integration into swift. https://review.opendev.org/c/openstack/swift/+/803879 our SREs have been playing with it. And it's really nice visualising swift requests across a cluster. Start seeing paterns and hopefully ares to fix. 21:34
mattoliverI'll show some traces at PTG maybe :)21:34
zaitcevYeah, it's our world... Whenever our something small and useful pops, it turns into this whole thing. EC watcher needs tests, gists can be more useful in docs, etc.21:34
timburkealways more work to be done :-)21:35
timburkeall right, seems like we can let kota and mattoliver get on with their mornings21:37
timburkethank you all for coming, and thank you for working on swift!21:37
timburke#endmeeting21:37
opendevmeetMeeting ended Wed Sep  8 21:37:51 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:37
opendevmeetMinutes:        https://meetings.opendev.org/meetings/swift/2021/swift.2021-09-08-21.04.html21:37
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/swift/2021/swift.2021-09-08-21.04.txt21:37
opendevmeetLog:            https://meetings.opendev.org/meetings/swift/2021/swift.2021-09-08-21.04.log.html21:37
mattoliverthanks timburke21:38
mattoliveroh.. meeting is over but just thought about something. but nothing meeting worthy, so just leave it here for people to think about. 21:40
mattoliverwe've had a sharded root container's epoch reset again in prod. It's only happened 3 times, and seems to be the same container. Only edgecase I can come up with is a put to a handoff that gets a defaulted own_shard_range that then merges over the other primaries.. but haven't been able to prove it. I wonder if something like: https://review.opendev.org/c/openstack/swift/+/807824 would help. ie, once a container gets an epoch (shards)21:41
mattoliverit never looses it, so make an epoch check in merge_shard_ranges21:41

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