Wednesday, 2023-05-24

opendevreviewMatthew Oliver proposed openstack/swift master: Pass db_state to container-update and async_pending  https://review.opendev.org/c/openstack/swift/+/87681105:15
opendevreviewMatthew Oliver proposed openstack/swift master: Pass db_state to container-update and async_pending  https://review.opendev.org/c/openstack/swift/+/87681107:14
opendevreviewMerged openstack/swift master: Remove hard dependency on netifaces  https://review.opendev.org/c/openstack/swift/+/87322211:34
edausqhello timburke, sorry for the delay, here is the bug report with "xattr -l": https://bugs.launchpad.net/swift/+bug/202066712:28
opendevreviewRomain de Joux proposed openstack/swift master: Encode header in latin-1 with wsgi_to_bytes  https://review.opendev.org/c/openstack/swift/+/88424016:00
edausq^ we have tested (manual functional tests) this patch, on both python2 and python3 clusters: no issue after ssync replication16:02
timburkeedausq, nice! thanks! it makes sense from glancing at it -- i can look at fixing up unit tests, maybe add some non-ascii metadata to a probe test or two18:23
opendevreviewTim Burke proposed openstack/swift master: Drop more translations  https://review.opendev.org/c/openstack/swift/+/88331520:58
timburke#startmeeting swift21:01
opendevmeetMeeting started Wed May 24 21:01:34 2023 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
opendevmeetThe meeting name has been set to 'swift'21:01
timburkewho's here for the swift meeting?21:01
mattolivero/21:03
kotao/21:03
zaitcevo/ ...21:05
timburkesorry, distracted for a sec21:05
timburkeas usual, the agenda's over at21:05
timburke#link https://wiki.openstack.org/wiki/Meetings/Swift21:05
timburkefirst up21:06
timburke#topic non-cooperative EC PUTs21:06
timburke#link https://review.opendev.org/c/openstack/swift/+/88336721:06
timburkehas merged! thanks acoles for running down the issue21:06
mattoliver\o/21:07
timburkein retrospect, it's kind of surprising it took us this long to bump into it21:07
timburkenext21:07
timburke#topic netifaces21:08
timburke#link https://review.opendev.org/c/openstack/swift/+/87322221:08
timburkehas also merged! thanks to everybody for reviewing it21:08
mattolivernice21:08
timburke(honestly, it got more eyes on it than i was expecting)21:08
timburkei'll rebase the follow-up to fully remove netifaces soon, but we'll still give ops some time to see the warning and file a bug before actually looking to merge21:10
timburke#link https://review.opendev.org/c/openstack/swift/+/88303521:10
mattoliveryeah good plan21:10
timburke#topic ssync metadata corruption on py321:11
timburkeedausq wrote up21:11
timburke#link https://bugs.launchpad.net/swift/+bug/202066721:11
timburkeand there's even a fix already proposed21:12
timburke#link https://review.opendev.org/c/openstack/swift/+/88424021:12
mattoliveroh cool, love it when ovh find something! they always also propose a solution!21:13
timburkei'll try to take a look at fixing up unit tests for next week, maybe enhance some probe tests to exercise it21:13
timburkeunfortunately, i'm not sure there's much we can do to address corrupted data...21:15
timburke*maybe* you could compare meta across different replicas? as long as one of them still has the original meta, you might be able to tell what it was supposed to be...21:17
timburkei think it might also be the sort of thing where it continues to get worse over time -- if there have been a bunch of rebalances, the bug could trigger multiple times, increasing the size of the metadata each time...21:19
timburkeall the more reason i want to look at reproing in a probe test21:20
timburkeall right, that's all i've got for this week21:20
timburke#topic open discussion21:20
mattoliveryeah, probe test would be a good start in anycase21:21
timburkeanything else we should bring up?21:21
mattoliverWe have stats being emitted when sharding happens so we can track timings (thanks JianJian)21:21
mattoliverbut there was a bug where timing_since couldn't read Timestamp objects. So fixed it (both ways). The more accepted approach is type casting the epoch to a float in: https://review.opendev.org/c/openstack/swift/+/883788 21:23
mattoliverBut to test it, I went and created a FakeStatsdClient and added it to the debug_logger. So there is quite a bit of test churn21:23
mattoliverThanks zaitcev for reviewing! 21:23
zaitcevIt was nothing.21:23
mattoliverso a bunch of churn but I think it makes testing better, we know actually run the statsd methods and just don't ever open the socket and send the data.21:24
mattoliverOnly other thing I had (or can think of, of to the top of my head this morning) was I still have the py2 no-op tracing patch at the end of my tracing chain.21:26
mattoliverReal question is, when (as an upstream project) are we going to rip out py2.21:27
mattoliverie, maybe it's just too crazy so we can just wait, or is mocking out otel classes something we want to carry until we do?21:27
mattoliverNot expecting an answer t o that right now, just something to think about at least :) 21:28
timburkethe moment it's not super painful for me (downstream) to do it 😁21:28
zaitcevsorry ttyl21:28
timburkespeaking of, though -- i'm happy to report that we've moved all of our swift services to py3 in our largest swift cluster!21:29
kotaexcellent21:29
mattoliver\o/21:29
mattoliveralso why it made me think of it. The reason for the latest patch that is.21:30
mattolivermaybe I don't need it anymore ;) 21:30
timburkenow we just need to worry about the management plane...21:30
timburkei should rebase https://review.opendev.org/c/openstack/swift/+/85359021:31
mattoliveryeah, well if we can just stop worrying about py2 and even if that means slowly moving out the py2 isms over time. I can just ignore py2 failing to run tracing and let it fail to find otel21:32
mattoliveranyway food for thought21:34
timburkeoh, whoa -- https://review.opendev.org/c/openstack/swift/+/883050 took a different approach than i was thinking to deal with the problem, mattoliver -- i would've just done the lazy imports, then error hard at runtime if you tried to configure tracing when the package isn't available21:35
mattoliverthere is just too much tracing-isms and context managers in the code. 21:36
mattoliverbut yeah, maybe I over engineered :P21:36
timburkeah, fair enough21:36
timburkeall right, i think i'll call it21:38
timburkethank you all for coming, and thank you for working on swift!21:38
timburke#endmeeting21:38
opendevmeetMeeting ended Wed May 24 21:38:52 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:38
opendevmeetMinutes:        https://meetings.opendev.org/meetings/swift/2023/swift.2023-05-24-21.01.html21:38
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/swift/2023/swift.2023-05-24-21.01.txt21:38
opendevmeetLog:            https://meetings.opendev.org/meetings/swift/2023/swift.2023-05-24-21.01.log.html21:38

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