21:00:15 <timburke> #startmeeting swift
21:00:16 <opendevmeet> Meeting started Wed Sep 22 21:00:15 2021 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:00:16 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:16 <opendevmeet> The meeting name has been set to 'swift'
21:00:25 <timburke> who's here for the swift meeting?
21:04:00 <kota> good morning
21:04:34 <timburke> o/
21:04:48 <kota> timburke: o/
21:04:59 <timburke> looks like it might be a pretty short meeting ;-)
21:05:29 <timburke> as usual, the agenda's at https://wiki.openstack.org/wiki/Meetings/Swift
21:05:48 <timburke> #topic eventlet / 100-continue bug
21:06:07 <timburke> just a heads-up, since i think we mentioned this last week
21:07:13 <timburke> https://github.com/eventlet/eventlet/pull/578 merged
21:07:55 <timburke> this addresses some 400s our clients would occasionally see when re-using a connection where the client sent Expect: 100-continue but then we didn't send a 100 Continue and instead delivered a final response immediately
21:09:26 <timburke> the trouble was we'd see clients try *either* send a body for the request that was attempted *or* start right in on a new request, so the only option left to us to get on a sane path was to close the connection
21:09:41 <timburke> #topic ring v2
21:11:08 <timburke> i added some tests for most of the patches on my chain, but looks like i left a line too long fairly early in the chain. expect a new set of patches coming, but it shouldn't materially change. i think the core of the format changes are ready for review
21:11:36 <timburke> #topic root shard epoch reset
21:11:55 <timburke> my understanding of the current state is that we're planning to try to prevent None epochs from propogating
21:12:17 <timburke> we'll use that to see if we can track down the node that brought it on and from there figure out the root cause of how we got there, and address *that*
21:12:51 <timburke> i was going to confirm with mattoliver that my understanding was correct, but i'm *pretty sure* that's the current plan
21:13:52 <timburke> so we (NVIDIA) might carry https://review.opendev.org/c/openstack/swift/+/809969 (or something close to it) for a bit until we suss out where these None epochs are coming from
21:15:02 <timburke> #topic misplaced objects in sharded containers
21:15:43 <timburke> i'm afraid i still haven't been following along on this enough to feel informed on the state of things
21:16:37 <timburke> i was going to check if the updates on https://review.opendev.org/c/openstack/swift/+/805389 and https://review.opendev.org/c/openstack/swift/+/809317 were indicative of some progress; if nothing else, i suppose it's staying fresh in mattoliver and acoles's minds
21:17:19 <timburke> that's all i had to bring up
21:17:25 <timburke> #topic open discussion
21:19:27 <timburke> all right, i think i'm'a call it
21:19:46 <timburke> thanks for coming, kota -- make me feel like i'm not just talking to myself :-)
21:19:59 <kota> thanks timburke for sharing current status
21:20:06 <timburke> thank you for coming, and thank you for keeping up on swift!
21:20:12 <timburke> #endmeeting