21:00:37 #startmeeting swift 21:00:37 Meeting started Wed Jun 30 21:00:37 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:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:37 The meeting name has been set to 'swift' 21:00:45 who's here for the swift meeting? 21:01:11 o/ 21:01:39 o/ 21:03:59 pretty sure mattoliver is out sick -- we'll see if clayg and zaitcev end up chiming in later ;-) 21:04:10 o/ 21:04:11 as usual, the agenda's at https://wiki.openstack.org/wiki/Meetings/Swift 21:04:33 #topic swift-bench and py2 21:05:13 so a while back i proposed that we drop py2 support from swift-bench: https://review.opendev.org/c/openstack/swift-bench/+/741553 21:05:39 ...and then i promptly forgot to push on getting it merged at all :P 21:06:26 i saw that there's a new patch up for swift-bench (https://review.opendev.org/c/openstack/swift-bench/+/798941) -- and the py2 job seems broken 21:06:31 i see. it's updated in Jul 2020 21:07:23 so i thought i'd check in to see whether anyone objects to dropping support there 21:09:53 sounds like i'm good to merge it :-) 21:10:04 +1 21:10:04 on to updates! 21:10:18 #topic sharding 21:11:06 it seems like acoles and i are getting close to agreement on https://review.opendev.org/c/openstack/swift/+/794582 to prevent small tail shards 21:11:59 were there any other follow-ups to that work we should be paying attention to? or other streams of work related to sharding? 21:13:47 IIRC mattoliver had some follow up patch(es) for tiny tails but I don't recall exactly what 21:14:20 maybe to add an 'auto' option, IDK 21:16:52 sounds about right. and there's the increased validation on sharder config options -- https://review.opendev.org/c/openstack/swift/+/797961 21:17:42 i think that's about it for sharding -- looking forward to avoiding those tail shards :-) 21:17:50 #topic relinker 21:18:33 we (nvidia) are currently mid part-power increase 21:18:55 and acoles wrote up https://bugs.launchpad.net/swift/+bug/1934142 while investigating some issues we saw 21:20:55 basically, the reconciler has been busy writing out tombstones everywhere, which can cause fomr relinking errors as multiple reconcilers can try to write the same tombstone at the same time 21:21:12 we're fortunate that the issue has only manifested with tombstones, as a result of the circumstances of the reconciler workload we had and the policy for which we were doing part power increase 21:21:28 Oh I see. I was just thinking about it. 21:22:39 its relatively easy to reason about tolerating a tombstone with different inode, data files would probably require more validation that 'same filename' 21:22:48 a fix is currently up at https://review.opendev.org/c/openstack/swift/+/798849 that seems reasonable, with a follow-up to remove some now-redundant checks at https://review.opendev.org/c/openstack/swift/+/798914 21:23:34 timburke: if we feel happy about the follow up I reckon I should squash the two 21:24:23 we're basically relaxing the previous checks rather than adding another 21:24:45 i think i am, at any rate. i also think i'd be content to skip getting the timestamp out of metadata 21:25:32 yeah, that was my usual belt n braces :) 21:26:29 surely the auditor includes a timestamp-from-metadata vs timestamp-from-file-name check, right? 21:26:50 idk 21:27:53 ok i'll rip out the metadata check and squash the two 21:28:08 👍 21:28:15 #topic dark data watcher 21:28:26 i saw acoles did some reviews! 21:28:30 Yes 21:28:32 thanks :-) 21:28:32 yes! 21:28:37 Indeed. 21:28:39 well just one 21:29:03 iirc i was happy apart from some minor fixes 21:30:24 I squashed that already but now I'm looking at remaining comments, like the one about when X-Timestamp is present and if an object can exist without one. 21:31:29 zaitcev: i think its ok, the x-timestamp should be there if the auditor passes the diskfile to watcher 21:32:48 and if the auditor *doesn't* check for it, it *should* and idk that the watcher necessarily needs to be defensive against it being missing 21:33:36 ok 21:34:35 all right, that's all i had to bring up 21:34:39 #topic open discussion 21:34:54 what else should we be talking about? 21:35:32 Hackathon :-) 21:38:10 i love that idea -- unfortunately, i don't think it's something we can do yet 21:38:41 short of a virtual one, at any rate 21:39:03 exactly 21:39:12 Pete Zaitcev proposed openstack/swift master: Make dark data watcher ignore the newly updated objects https://review.opendev.org/c/openstack/swift/+/788398 21:39:34 speaking of -- looks like we've got dates for the next PTG: http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023370.html 21:39:45 Oct 18-22, still all-virtual 21:40:49 ack 21:41:51 * kota will register it 21:41:54 I'm just back from a mini vacation at South Padre. Seen a few people in masks. Maybe one in 20. 21:42:12 yeah, but you're in TX ;-) 21:42:50 The island is overflowing. I guess the international vacationing still not working. People even try to surf, although obviously the wave is pitiful in the Gulf absent a storm. 21:42:51 i just check; my company's guidelines for travel are currently matching their guidelines for office re-opening, which is "not yet" 21:43:04 ok 21:43:37 all right, let's let kota get on with his morning :-) 21:43:38 is the us even allowing aliens in ? without quarantine? 21:44:18 thank you all for coming, and thank you for working on swift! 21:44:23 #endmeeting