Wednesday, 2024-07-10

DeHackEdopened as a bug report, and included the code I'm using00:48
opendevreviewMerged openstack/swift master: Use entry_points for server executables  https://review.opendev.org/c/openstack/swift/+/91836502:35
opendevreviewASHWIN A NAIR proposed openstack/swift master: object-server: return 503 not 404 if meta or data file unlinked  https://review.opendev.org/c/openstack/swift/+/90967417:57
opendevreviewASHWIN A NAIR proposed openstack/swift master: object-server: return 503 not 404 if meta or data file unlinked  https://review.opendev.org/c/openstack/swift/+/90967418:02
opendevreviewASHWIN A NAIR proposed openstack/swift master: object-server: return 503 not 404 if meta or data file unlinked  https://review.opendev.org/c/openstack/swift/+/90967418:13
kotagood morning20:56
timburkekota, o/20:57
fulecoHello o/20:57
kotao/20:57
timburke#startmeeting swift21:00
opendevmeetMeeting started Wed Jul 10 21:00:15 2024 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
opendevmeetThe meeting name has been set to 'swift'21:00
timburkewho's here for the swift meeting?21:00
kotao/21:00
fulecoI'm here21:00
mattolivero/21:01
timburkeas usual, the agenda's at21:01
timburke#link https://wiki.openstack.org/wiki/Meetings/Swift21:01
timburkefirst up, just a few status updates21:01
timburke#topic account-reaper and sharded containers21:02
timburke#link https://bugs.launchpad.net/swift/+bug/207039721:02
patch-botBug #2070397 - Account reaper do not reap sharded containers (New)21:02
timburkei still haven't even started on a probe test for it :-(21:02
timburkeif anyone else would like to take a stab at it, you'd be more than welcome -- otherwise, i'll try to use this meeting to keep it on my radar21:03
timburke#topic cooperative tokens21:03
mattoliverOh, because it won't shrink the empty shards21:03
timburkemattoliver, i think it goes deeper than that -- i think it can't even list the objects to delete21:04
mattoliverOh, it's talking to the broker, so not getting objects21:04
mattoliverDamn, yeah Oh course! Good find21:04
timburkeyeah, direct_client to get around the 410...21:04
timburke#link https://review.opendev.org/c/openstack/swift/+/89017421:05
patch-botpatch 890174 - swift - common: add memcached based cooperative token mech... - 33 patch sets21:05
timburkelooks like jianjian has gotten some reviews and things keep moving forward21:05
mattoliverYup, I've been living at it21:06
mattoliver*looking 21:06
timburkethanks mattoliver! i also seem to remember hearing good things about it as we've been cautiously trying it out in prod, but i don't have any numbers at my fingertips right now21:07
mattoliver(Sorry visitors sleeping my my office, so on my phone for meeting, so auto correct going to be a pain)21:07
timburkeno worries :-)21:07
timburke#topic pkg_resources warnings in editable installs21:07
timburkefirst patch merged!21:07
timburke#link https://review.opendev.org/c/openstack/swift/+/91836521:07
patch-botpatch 918365 - swift - Use entry_points for server executables (MERGED) - 4 patch sets21:07
timburkethanks mattoliver and zaitcev!21:08
mattoliverWell we've rolled it out to 1/2 of prod and initial numbers look awesome and promising (re coop)21:08
timburkenext in the chain is still fairly mechanical21:08
timburke#link https://review.opendev.org/c/openstack/swift/+/92215121:08
patch-botpatch 922151 - swift - Use entry_points for a bunch more executables - 4 patch sets21:08
mattoliverNps, will work my way up the chain21:08
mattoliverThat next one is a big one 😀21:09
timburkeas we get further out, more code ends up moving, so i expect them to trigger more discussion21:09
timburke#topic ISO timestamps and swift-drive-audit21:10
timburkeDeHackEd brought this to our attention21:10
timburke#link https://bugs.launchpad.net/swift/+bug/207260921:10
patch-botBug #2072609 - swift-drive-audit does not handle ISO timestamps in logs (New)21:10
timburkeand even provided a fix in the bug report21:10
timburkei'll aim to get a patch up later today, if anyone can spare some review cycles21:11
mattoliverOh nice21:11
mattoliverYup, just ping me to remind me21:12
timburke👍21:12
timburkenext up21:12
timburke#topic multi-policy containers21:12
timburkefuleco, how's it going? anything else you need from us in the short term?21:12
fulecoSo for this we are still running some testing and it's been working good until now21:13
fulecoI think we're in good shape as it is, just gonna take us some time to wrap it up and send upstream21:13
mattoliverCool21:13
timburke🎉21:13
timburkeall right then, last item i've got21:14
timburke#topic operator-driven node exclusion21:14
timburkezigo brought my attention to this message on the ML (thanks, i probably would have missed it otherwise!)21:15
timburke#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/IZUXNXUQFKBZIP6YIOQJMLXPK5RI6M45/21:15
timburkecore idea is to give operators the ability to tell proxies to ignore specific backend nodes, and dynamically manipulate that ignore list21:16
mattoliverOh interesting, I haven't read it yet, bit what they auto adding things to error limitted nodes or something21:16
mattoliverLol, so yes21:17
mattoliverMaybe.. I should look21:17
mattoliverI guess I'd like to know the usecase21:18
timburkekind of, but not exactly. it's a sticky flag and requires some process to clear it when the node's back up/should receive traffic21:18
timburkemy read has been that there are at least a couple different use-cases21:19
mattoliverOk, so a "better" or more global error limitted list maybe.21:19
timburkethere's flagging known-failed devices that you're in the process of replacing -- and even once the device is replaced and remounted, you might want to avoid proxies talking to it so it can focus on incoming rsyncs21:20
mattoliverWe have discussed in the past the ability to disable nodes in the ring, but this sounds more dynamic, which is good.21:20
mattoliverKk, interesting I guess best if a give it a read rather then speculating. Because I wonder how the sticky flag will work etc. 21:22
timburkeyeah, i was thinking that it might work well in the ring file, too -- there seemed to be some concern about the time required to propagate configs though21:22
timburkei think the cardinality is expected to be pretty small, so everything's written in a flat file, one ip:port to exclude per line21:23
mattoliverOk, but sp long as we're sure it'll be small, in swift things tend to grow :😜 21:24
mattoliverI did have that global error limitor patch that uses memcache.. so could do something similar. 21:24
timburkebut yeah, it definitely felt related (but decidedly different!) to some other ideas we've had over the years, like ring v2 and clayg's overseer21:24
mattoliverYeah21:25
timburkethe concern about config propagation time kind of makes me want to pick up https://review.opendev.org/c/openstack/swift/+/670674 again and give it some gossip protocol...21:26
patch-botpatch 670674 - swift - WIP: Allow ring lookups via a service - 3 patch sets21:26
timburkeanyway, i wanted to make sure that other people saw the conversation21:27
timburkethat's all i've got for this week21:27
timburke#topic open discussion21:27
timburkeanything else we should bring up this week?21:27
mattoliverWell I'm still reorienting after vacation. Am playing with not hashing memcache key prefixes (so I can play with prefix routing) in the memcache layer.. but that still early work. 21:28
mattoliverAnd just want to have a patch in our back pocket incase it's needed.21:29
mattoliverWill push something up to gerrit soon but it'll be wip21:30
mattoliverWell I should say, optionally not hashing prefixes. I wouldn't just change behaviour. We use mcrouter, so could be really interesting for us. 21:31
timburkesounds good -- would that be an update to https://review.opendev.org/c/openstack/swift/+/890139 or a new patch?21:32
patch-botpatch 890139 - swift - proxy-server: use a prefixed shard range cache key - 1 patch set21:32
mattoliverYeah, update that, and modernise21:34
timburke👍21:34
mattoliverSeems swift has moved on a little in the way memcache keys work :)21:35
mattoliverAnd we (swift) have some summer school students working on some stuff. They've pushed up some patches and also plan to tackle some sharper and storage policy index ops tooling for us21:35
mattoliver*sigh* sharder 21:35
timburkeoh yeah! should we go ahead and merge https://review.opendev.org/c/openstack/swift/+/921664 ? i'm kind of inclined to21:35
patch-botpatch 921664 - swift - add object-count quota for accounts in middleware - 3 patch sets21:35
mattoliverThanks timburke 21:36
mattoliverYeah, I might go merge that 😀21:36
mattoliverThere is also a reaper patch21:36
timburkehttps://review.opendev.org/c/openstack/swift/+/92283321:36
patch-botpatch 922833 - swift - Periodic reaper recon dump showing current progress - 5 patch sets21:36
timburke(which i should be sure to take a look at)21:36
mattoliverYup thanks! 21:36
mattoliverThere is a follow up to the quota one if anyone is interesting in writing 😀21:37
mattoliverBasically moving the api to x-account-quota namespace and store  in sysmeta 21:38
mattoliverThat's all I can think of atm 21:39
timburkeall right, i think i'll call it early then21:39
timburkethank you all for coming, and thank you for working on swift!21:39
timburke#endmeeting21:39
opendevmeetMeeting ended Wed Jul 10 21:39:59 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:39
opendevmeetMinutes:        https://meetings.opendev.org/meetings/swift/2024/swift.2024-07-10-21.00.html21:39
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/swift/2024/swift.2024-07-10-21.00.txt21:39
opendevmeetLog:            https://meetings.opendev.org/meetings/swift/2024/swift.2024-07-10-21.00.log.html21:39
indianwhocodeso/ - too late , will just catch up on the msgs22:03
opendevreviewClay Gerrard proposed openstack/swift master: Delete s3api MPU segments when expiring the manifest  https://review.opendev.org/c/openstack/swift/+/80070123:01
opendevreviewClay Gerrard proposed openstack/swift master: DNM expirer: new options to control task iteration  https://review.opendev.org/c/openstack/swift/+/91471323:01
opendevreviewClay Gerrard proposed openstack/swift master: Configurable object_expirer_task_container_per_day  https://review.opendev.org/c/openstack/swift/+/92045223:01
opendevreviewClay Gerrard proposed openstack/swift master: refactor: remove iter_task_accounts_to_expire  https://review.opendev.org/c/openstack/swift/+/91963923:01
opendevreviewClay Gerrard proposed openstack/swift master: Parallel distirbuted task container iteration  https://review.opendev.org/c/openstack/swift/+/91836623:01

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