| *** martial has quit IRC | 00:01 | |
| *** Lucas_Gray has joined #openstack-meeting | 00:12 | |
| *** gyee has quit IRC | 00:20 | |
| *** tetsuro has joined #openstack-meeting | 00:27 | |
| *** yaawang has quit IRC | 01:57 | |
| *** yaawang has joined #openstack-meeting | 01:58 | |
| *** ricolin has joined #openstack-meeting | 02:01 | |
| *** Liang has quit IRC | 02:02 | |
| *** ykatabam has joined #openstack-meeting | 02:14 | |
| *** tetsuro has quit IRC | 02:20 | |
| *** rfolco has quit IRC | 03:00 | |
| *** baojg has quit IRC | 03:10 | |
| *** psachin has joined #openstack-meeting | 03:31 | |
| *** Liang__ has joined #openstack-meeting | 03:31 | |
| *** redrobot has quit IRC | 03:42 | |
| *** mahatic has joined #openstack-meeting | 03:45 | |
| *** rbudden has quit IRC | 03:50 | |
| *** rbudden has joined #openstack-meeting | 03:51 | |
| *** rbudden has quit IRC | 03:51 | |
| *** rbudden has joined #openstack-meeting | 03:52 | |
| *** rbudden has quit IRC | 03:52 | |
| *** rh-jelabarre has quit IRC | 04:25 | |
| *** diurnalist has quit IRC | 04:35 | |
| *** Lucas_Gray has quit IRC | 04:36 | |
| *** diurnalist has joined #openstack-meeting | 05:32 | |
| *** diurnalist has quit IRC | 05:36 | |
| *** vishalmanchanda has joined #openstack-meeting | 05:55 | |
| *** e0ne has joined #openstack-meeting | 06:27 | |
| *** eharney has quit IRC | 06:40 | |
| *** eharney has joined #openstack-meeting | 06:52 | |
| *** ociuhandu has quit IRC | 07:10 | |
| *** ralonsoh has joined #openstack-meeting | 07:29 | |
| *** rcernin has quit IRC | 07:32 | |
| *** ociuhandu has joined #openstack-meeting | 07:36 | |
| *** markvoelker has joined #openstack-meeting | 07:47 | |
| *** markvoelker has quit IRC | 07:52 | |
| *** psahoo has joined #openstack-meeting | 08:03 | |
| *** moguimar has joined #openstack-meeting | 08:08 | |
| *** kaisers has joined #openstack-meeting | 08:11 | |
| *** yaawang has quit IRC | 08:13 | |
| *** yaawang has joined #openstack-meeting | 08:13 | |
| *** tetsuro has joined #openstack-meeting | 08:24 | |
| *** baojg has joined #openstack-meeting | 08:26 | |
| *** cschwede has joined #openstack-meeting | 08:32 | |
| *** tetsuro has quit IRC | 08:48 | |
| *** rcernin has joined #openstack-meeting | 09:11 | |
| *** rcernin has quit IRC | 09:35 | |
| *** Liang__ has quit IRC | 09:40 | |
| *** yaawang has quit IRC | 10:11 | |
| *** yaawang has joined #openstack-meeting | 10:12 | |
| *** yaawang has quit IRC | 10:20 | |
| *** yaawang has joined #openstack-meeting | 10:21 | |
| *** priteau has joined #openstack-meeting | 10:34 | |
| *** Lucas_Gray has joined #openstack-meeting | 10:41 | |
| *** moguimar has quit IRC | 10:41 | |
| *** ricolin has quit IRC | 10:48 | |
| *** raildo has joined #openstack-meeting | 11:29 | |
| *** baojg has quit IRC | 11:49 | |
| *** rcernin has joined #openstack-meeting | 11:50 | |
| *** baojg has joined #openstack-meeting | 11:50 | |
| *** rfolco has joined #openstack-meeting | 11:51 | |
| *** rh-jelabarre has joined #openstack-meeting | 12:00 | |
| *** moguimar has joined #openstack-meeting | 12:02 | |
| *** ociuhandu has quit IRC | 12:03 | |
| *** ociuhandu_ has joined #openstack-meeting | 12:03 | |
| *** baojg has quit IRC | 12:11 | |
| *** baojg has joined #openstack-meeting | 12:12 | |
| *** tosky has joined #openstack-meeting | 12:17 | |
| *** e0ne has quit IRC | 12:33 | |
| *** e0ne has joined #openstack-meeting | 12:37 | |
| *** seba has quit IRC | 12:38 | |
| *** carloss has quit IRC | 12:38 | |
| *** e0ne has quit IRC | 12:39 | |
| *** mordred has quit IRC | 12:40 | |
| *** mahatic has quit IRC | 12:41 | |
| *** seba has joined #openstack-meeting | 12:42 | |
| *** carloss has joined #openstack-meeting | 12:42 | |
| *** mordred has joined #openstack-meeting | 12:45 | |
| *** moguimar has quit IRC | 12:52 | |
| *** moguimar has joined #openstack-meeting | 13:09 | |
| *** armstrong has joined #openstack-meeting | 13:09 | |
| *** rbudden has joined #openstack-meeting | 13:11 | |
| *** baojg has quit IRC | 13:23 | |
| *** baojg has joined #openstack-meeting | 13:24 | |
| *** bnemec has joined #openstack-meeting | 13:30 | |
| *** rcernin has quit IRC | 13:32 | |
| *** sluna has quit IRC | 13:33 | |
| *** sluna has joined #openstack-meeting | 13:33 | |
| *** baojg has quit IRC | 13:41 | |
| *** baojg has joined #openstack-meeting | 13:43 | |
| *** TrevorV has joined #openstack-meeting | 13:43 | |
| *** ricolin has joined #openstack-meeting | 13:43 | |
| *** ZhuXiaoYu has joined #openstack-meeting | 13:53 | |
| *** Liang__ has joined #openstack-meeting | 13:58 | |
| *** Liang__ is now known as LiangFang | 13:59 | |
| *** e0ne has joined #openstack-meeting | 14:00 | |
| *** LiangFang has quit IRC | 14:12 | |
| *** Liang__ has joined #openstack-meeting | 14:14 | |
| *** ykatabam has quit IRC | 14:14 | |
| *** e0ne has quit IRC | 14:22 | |
| *** baojg has quit IRC | 14:22 | |
| *** e0ne has joined #openstack-meeting | 14:23 | |
| *** baojg has joined #openstack-meeting | 14:24 | |
| *** psachin has quit IRC | 14:24 | |
| *** moguimar has quit IRC | 14:38 | |
| *** moguimar has joined #openstack-meeting | 14:43 | |
| *** mlavalle has joined #openstack-meeting | 14:44 | |
| *** rsimai has joined #openstack-meeting | 14:47 | |
| *** Guest23136 has joined #openstack-meeting | 14:47 | |
| *** Guest23136 is now known as redrobot | 14:49 | |
| *** diurnalist has joined #openstack-meeting | 14:58 | |
| *** jmlowe has left #openstack-meeting | 15:04 | |
| *** Liang__ has quit IRC | 15:15 | |
| *** Liang__ has joined #openstack-meeting | 15:19 | |
| *** armstrong has quit IRC | 15:19 | |
| *** Liang__ has quit IRC | 15:23 | |
| *** svyas|afk has joined #openstack-meeting | 15:26 | |
| *** gyee has joined #openstack-meeting | 15:48 | |
| *** moguimar has quit IRC | 15:54 | |
| *** baojg has quit IRC | 15:54 | |
| *** baojg has joined #openstack-meeting | 15:56 | |
| *** zbr|rover is now known as zbr | 15:58 | |
| *** moguimar has joined #openstack-meeting | 16:03 | |
| *** e0ne has quit IRC | 16:15 | |
| *** ricolin has quit IRC | 16:19 | |
| *** Lucas_Gray has quit IRC | 16:24 | |
| *** rsimai has quit IRC | 16:24 | |
| *** Lucas_Gray has joined #openstack-meeting | 16:31 | |
| *** baojg has quit IRC | 16:34 | |
| *** cschwede has quit IRC | 16:41 | |
| *** lbragstad_ has joined #openstack-meeting | 16:54 | |
| *** lbragstad has quit IRC | 16:57 | |
| *** ociuhandu has joined #openstack-meeting | 17:11 | |
| *** ociuhandu_ has quit IRC | 17:14 | |
| *** ociuhandu has quit IRC | 17:16 | |
| *** moguimar has quit IRC | 17:17 | |
| *** e0ne has joined #openstack-meeting | 17:20 | |
| *** ociuhandu has joined #openstack-meeting | 17:22 | |
| *** Lucas_Gray has quit IRC | 17:23 | |
| *** psahoo has quit IRC | 17:25 | |
| *** ociuhandu has quit IRC | 17:26 | |
| *** lbragstad_ has quit IRC | 17:37 | |
| *** lbragstad_ has joined #openstack-meeting | 17:38 | |
| *** lbragstad__ has joined #openstack-meeting | 17:45 | |
| *** lbragstad_ has quit IRC | 17:47 | |
| *** jmasud has quit IRC | 18:00 | |
| *** jmasud has joined #openstack-meeting | 18:00 | |
| *** _erlon_ has joined #openstack-meeting | 18:02 | |
| *** jmasud has quit IRC | 18:07 | |
| *** e0ne has quit IRC | 18:15 | |
| *** jmasud has joined #openstack-meeting | 18:35 | |
| *** ZhuXiaoYu has quit IRC | 18:44 | |
| *** ralonsoh has quit IRC | 18:45 | |
| *** bnemec has quit IRC | 19:03 | |
| *** baojg has joined #openstack-meeting | 19:07 | |
| *** e0ne has joined #openstack-meeting | 19:17 | |
| *** baojg has quit IRC | 19:31 | |
| *** ociuhandu has joined #openstack-meeting | 19:31 | |
| *** baojg has joined #openstack-meeting | 19:32 | |
| *** ociuhandu_ has joined #openstack-meeting | 19:34 | |
| *** ociuhand_ has joined #openstack-meeting | 19:35 | |
| *** ociuhandu has quit IRC | 19:36 | |
| *** ociuhandu_ has quit IRC | 19:38 | |
| *** diurnalist has quit IRC | 19:38 | |
| *** adrianc_ has joined #openstack-meeting | 19:44 | |
| *** ociuhand_ has quit IRC | 19:45 | |
| *** adrianc has quit IRC | 19:47 | |
| *** e0ne has quit IRC | 19:47 | |
| *** TrevorV has quit IRC | 19:59 | |
| *** e0ne has joined #openstack-meeting | 20:04 | |
| *** e0ne has quit IRC | 20:12 | |
| *** diurnalist has joined #openstack-meeting | 20:13 | |
| *** hemna has quit IRC | 20:32 | |
| *** hemna has joined #openstack-meeting | 20:39 | |
| *** priteau has quit IRC | 20:47 | |
| *** zaitcev has joined #openstack-meeting | 20:51 | |
| *** patchbot has joined #openstack-meeting | 20:57 | |
| timburke | #startmeeting swift | 21:00 |
|---|---|---|
| openstack | Meeting started Wed Jul 22 21:00:06 2020 UTC and is due to finish in 60 minutes. The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot. | 21:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 21:00 |
| *** openstack changes topic to " (Meeting topic: swift)" | 21:00 | |
| openstack | The meeting name has been set to 'swift' | 21:00 |
| timburke | who's here for the swift meeting? | 21:00 |
| alecuyer | o/ | 21:00 |
| rledisez | hi o/ | 21:00 |
| seongsoocho | o/ | 21:00 |
| clayg | are we having a 🎉!!!? | 21:01 |
| timburke | agenda's at https://wiki.openstack.org/wiki/Meetings/Swift | 21:01 |
| timburke | #topic releases | 21:02 |
| *** openstack changes topic to "releases (Meeting topic: swift)" | 21:02 | |
| timburke | so i'm realizing that i've been pretty bad about doing releases lately. i feel like i'd mentioned wanting to do a release a month or so ago, but just never got around to it | 21:02 |
| timburke | so now it's been 3 months since 2.25.0 | 21:02 |
| * tdasilva is lurking | 21:03 | |
| timburke | does anyone know of patches we really ought to have before a 2.26.0? | 21:03 |
| *** bnemec has joined #openstack-meeting | 21:04 | |
| clayg | not really, but we should cut 2.26.0 so we can start landing stuff for 2.27.0!! | 21:04 |
| timburke | the only two that come to mind for me are p 742033 and p 739164 | 21:04 |
| patchbot | https://review.opendev.org/#/c/742033/ - swift - py3: Work with proper native string paths in crypt... - 3 patch sets | 21:04 |
| patchbot | https://review.opendev.org/#/c/739164/ - swift - ec: Add an option to write fragments with legacy crc - 1 patch set | 21:04 |
| clayg | yes, both of those are terrible 😥 | 21:05 |
| timburke | but as clayg points out, we can always have another release :-) | 21:05 |
| clayg | i mean the problems the address - the patches are probably 🤩 | 21:05 |
| zaitcev | we're going to have 2.917.0 eventually if this continues | 21:05 |
| timburke | and that last one doesn't entirely make sense without https://review.opendev.org/#/c/738959/ | 21:05 |
| patchbot | patch 738959 - liberasurecode - Be willing to write fragments with legacy crc - 1 patch set | 21:05 |
| timburke | zaitcev, with luck we'll feel like we can drop py2 in the not *so* distant future -- that seems to warrant a 3.0 ;-) | 21:06 |
| clayg | yeah the ec one seems worth some effort to get all the versions to line up | 21:06 |
| clayg | the py3 fix is probably going to be backported stable releases anyway (timburke is doing great with the backports 👏) | 21:06 |
| zaitcev | so, you went with an environment variable after all. | 21:07 |
| clayg | zaitcev: did you have a better idea?! | 21:07 |
| zaitcev | In that case, PyLibEC does not need a change, right? | 21:07 |
| timburke | zaitcev, or rather, i never got around to trying to do it as a new, supported API | 21:08 |
| timburke | correct, pyeclib won't need to change as things stand | 21:08 |
| timburke | (which seems like a point in the env var's favor to me) | 21:09 |
| clayg | ✅ | 21:10 |
| timburke | so i'm not really hearing much in the way of known issues -- is anyone going to be able to review either of those two threads in the near future? or should we just release without them? | 21:10 |
| *** bnemec has quit IRC | 21:11 | |
| timburke | clayg's right about backporting the py3 fix -- i'm definitely planning to take it back to train, and if we get it reviewed soon-ish, i'll include it in the next stable release (which i hope to do concurrent with 2.26.0) | 21:11 |
| clayg | the py3 fix is newer; but i'm less clear on how to effectively review the libec patches | 21:13 |
| timburke | clayg, fwiw, i built a few different versions of libec (i want to say 1.0.9, 1.5.0, 1.6.0, and a new 1.6.1+ that supports the env var) and used LD_PRELOAD to split-brain my proxy and object layers | 21:15 |
| clayg | 🤯 | 21:15 |
| timburke | the tricky part with *really* old libec is making sure you've got a pyeclib that supports it. it took a bit to get it right as i recall | 21:17 |
| clayg | well that sounds miserable | 21:17 |
| mattoliverau | o/ (sorry I'm late) | 21:17 |
| timburke | but i think 1.5.0, 1.6.0, and 1.6.1+ likely all work well enough with master or latest-tag pyeclib | 21:17 |
| clayg | I think i'm more likely to review the encryption/py3 one - can someone offer to help with the libec? | 21:18 |
| *** bnemec has joined #openstack-meeting | 21:18 | |
| timburke | the only reason i went back so far was to confirm that the tool i attached to the bug did the right thing on frags with no CRC | 21:18 |
| timburke | clayg, thanks for picking up the py3 patch. i guess we'll continue kicking the can down the road for the ec work, but i think it's important that we get to a resolution by the end of the cycle | 21:21 |
| timburke | on to updates! | 21:22 |
| timburke | #topic replicaiton networks, saio, and probe tests | 21:22 |
| *** openstack changes topic to "replicaiton networks, saio, and probe tests (Meeting topic: swift)" | 21:22 | |
| *** baojg has quit IRC | 21:22 | |
| timburke | just before the meeting i pushed up fresh versions of some patches that let me run separate replication servers in my saio | 21:23 |
| *** baojg has joined #openstack-meeting | 21:23 | |
| timburke | i mentioned some concerns about the upgrade path in -swift | 21:24 |
| clayg | it's gunna be FINE | 21:26 |
| clayg | ... probably | 21:26 |
| timburke | in particular, since replication servers today can't handle GET/PUT/etc. methods, when p 735751 comes in, there's the potential for a lot of 405s during a rolling upgrade | 21:26 |
| patchbot | https://review.opendev.org/#/c/735751/ - swift - Allow direct and internal clients to use the repli... - 5 patch sets | 21:26 |
| clayg | i mean, anyone running EC has already turned off replication_server = True; so it really only effects account/container servers | 21:26 |
| timburke | in talking it through with clayg, i think it's fairly tractable -- you'd just need to make sure that any configs with replication_server=true have that line cleared -- then you can the server-can-respond-to-all-methods behavior | 21:27 |
| clayg | 🤞 | 21:27 |
| clayg | I mean; we can probably test/verify that once we have vsaio ready to replication server! 💪 | 21:27 |
| *** raildo has quit IRC | 21:28 | |
| timburke | so i bring this up for two reasons: first to raise awareness of the potential upgrade issue, and second to find out how other people are deploying their swifts -- will it even be much of a concern? | 21:29 |
| rledisez | so, we don't use replication_server=True, so it's not a major concern to me. I assume every operator are reading changelog before upgrading | 21:30 |
| timburke | i *did* discover that nvidia (formerly swiftstack) sets replication_server=true on a/c... so, that's a thing we'll need to fix... | 21:30 |
| rledisez | but at least an operator upgrade one node to check everything is fine, so have a clear error message if the config line still exist is also mandatory I think (I mean, process does not start and log an error) | 21:31 |
| clayg | rledisez: well the "error" would be with old code and old configs; once everyone is upgraded it's fine 🤔 | 21:32 |
| timburke | the trouble isn't the upgraded node, though -- it's the *other* ones that only respond to REPLICATE :-( | 21:32 |
| rledisez | ha… I missed that | 21:32 |
| clayg | timburke: I'm pretty sure we can find precedent where the answer was "push out a config that makes sense before you upgrade" - we just need to verify that works; but I think it's fine | 21:32 |
| timburke | cool, i'll keep pushing on that then ;-) | 21:33 |
| rledisez | I'm totally OK with that, if there is a proper upgrade procedure it seems standard in the software industry | 21:33 |
| mattoliverau | can a new upgrade fall back to the client-data-path network on a 405 from a server on a replicated network? | 21:33 |
| clayg | we'll fix our configs; it doesn't effect rledisez; other people probably don't even use replication networks, or if they do they already learned to turn it off because ssync ... or they get some errors while upgrading! | 21:34 |
| clayg | mattoliverau: 🤮 I think timburke was sort of going that path, but with a config option - automatic fallback might have to produce warnings... cruft 🤔 | 21:35 |
| clayg | mattoliverau: but it's a good point! if we're worried enough about the errors fallback to client network would work and shouldn't be much more painful than what we do know... we could probably clean it up eventually! | 21:35 |
| timburke | yeah, it'd be doable -- but i'd worry about the extra complexity and knowing when we could feel safe removing it | 21:35 |
| clayg | timburke: I'm not THAT ^ worried about it - YOU? | 21:36 |
| clayg | mattoliverau: do you know anyone that deploys with replication_server = true? (for a/c server; N.B. replication_server = true is currently *broken* for ec/ssync - which is more or less what we're trying to fix 🤷) | 21:37 |
| timburke | yeah, i think i'm not so worried -- might be worth confirming that we're not going to flood logs with tracebacks or anything, but the upgrade window should be fairly short and it's only disrupting consistency engine work which is used to delays | 21:38 |
| mattoliverau | I wonder if a fallback to the other network is ever really bad.. on link failures and congestion, swift will keep going. I guess we don't want to effect user traffic, and detecting when to fallback could get problematic. | 21:38 |
| clayg | timburke: I think we also have "upgradeimpact: everything is going to replication network" on our side? like you kind of have to really *want* to get in on this? | 21:38 |
| mattoliverau | clayg: I can't think of anyone, but can look into our cloud product to see what we configure (we still have customers running openstack). | 21:39 |
| timburke | i guess another option would be to get the respond-to-all-methods fix in now, then do the move-all-traffic-to-replication-network fix later | 21:39 |
| clayg | mattoliverau: if I opt'd into replication networks it's probably for segregation, and I don't think I'd want errors to push over to client network | 21:39 |
| clayg | mattoliverau: thanks! | 21:39 |
| timburke | (though i'm also kind of happy that these piled up together to force us to acknowledge that the upgrade is a little tricky) | 21:40 |
| clayg | timburke: i think they go together and we regularly introduce changes that will cause upgraded servers to not talk to old versions until they get upgraded 🤷 | 21:40 |
| mattoliverau | clayg: I guess, but self healing and things just working with warnings in the log could be cool :) But sure fair enough | 21:40 |
| timburke | only other question i had was whether we should work toward having saio and probe tests *expecting* an isolated replication network | 21:41 |
| clayg | i mean, it's not even the container-replicator... it's like the *sharder* and ... updater? I think it's fine. | 21:42 |
| timburke | reconciler, reaper, container-sync... | 21:43 |
| timburke | currently, https://review.opendev.org/#/c/741723/ is a hack and a half -- there's literally a comment like `# :vomit:` in there at the moment | 21:44 |
| patchbot | patch 741723 - swift - wip: Allow probe tests to run with separate replic... - 2 patch sets | 21:44 |
| zaitcev | container-sync cannot use replication network by definition, I think. It talks to _other_ cluster. | 21:45 |
| timburke | zaitcev, true, it does -- but it uses internal-client to get the data to send | 21:46 |
| *** ociuhandu has joined #openstack-meeting | 21:46 | |
| clayg | 💡 | 21:46 |
| timburke | making probe tests tolerant of either config seems tricky; if we could assume it to be there, i think it could clean up better | 21:46 |
| *** rh-jlabarre has joined #openstack-meeting | 21:47 | |
| timburke | something to think about, anyway. i want to make sure clayg gets some time to talk about... | 21:47 |
| timburke | #topic waterfall ec | 21:48 |
| *** openstack changes topic to "waterfall ec (Meeting topic: swift)" | 21:48 | |
| timburke | clayg, i saw new patches go up! how's it going? | 21:48 |
| zaitcev | Coincidentally I wrote a little function that does not make the assumption node_id == (my_port - 6010) / 10 | 21:48 |
| clayg | it's kinda stalled out waiting for feedback; the latest patch was just some minor "rename things" | 21:48 |
| clayg | timburke: you had said something like "the per-replica timeout would make more sense if it started at 0 = first parity" or something like that - and that makes sense to me | 21:49 |
| clayg | the fact that first (in replicated) or n-data (in ec) replicated timeouts are "ignored" is kinda dumb | 21:50 |
| clayg | and I can't really imagine a path in the future where they'd be used... so... i just need to figure out how to express something like that in code | 21:50 |
| *** ociuhandu has quit IRC | 21:50 | |
| *** rh-jelabarre has quit IRC | 21:51 | |
| timburke | i think it could also make it so the config won't strictly *need* to be per-policy, though it seems like you'd likely want to tune it differently for different policies | 21:51 |
| clayg | under the hood the `get_timeout(n_replica)` function will probably still grab out of a list... but it'll either be sparce, or have to `+ offset` | 21:51 |
| clayg | oh yeah; i hadn't thought about having global default... hrm | 21:51 |
| clayg | so maybe that's where the next bit of work will be | 21:52 |
| *** ykatabam has joined #openstack-meeting | 21:52 | |
| clayg | timburke: can you confirm you're leaning towards *further* decoupling (remove vistigial-ec from GetOrHeadHandler & remove vistigial-replicated from ECFragGetter) as much as possible - or do you see some path where they go back together? | 21:53 |
| clayg | because that's like a 4th patch I haven't even started on | 21:53 |
| clayg | I did go back and look at some of the EC tests that I "made more robust" and they seem to work (or fail in a reasonable way) with the old code; so I'm pretty confident in maintaining the status quo | 21:54 |
| timburke | i see all of this (and the further cleanup that could be done now that they're separated) as a pretty convincing case that they should stay apart | 21:54 |
| clayg | that is I think everything will work and continue to be just as robust post upgrade if you don't turn on the new timeouts (but I think people will want to turn on the timeouts; just like concurrent_gets) | 21:55 |
| timburke | unless you've gotten a new picture of how they could come back together, anyway | 21:55 |
| timburke | all right, last few minutes | 21:55 |
| timburke | #topic open discussion | 21:56 |
| *** openstack changes topic to "open discussion (Meeting topic: swift)" | 21:56 | |
| timburke | anything else we should bring up today? | 21:56 |
| clayg | ok, so I'll probably leave p 709326 and it pre-req alone; respin 737096 and work onto something ontop of that with more refactoring | 21:56 |
| patchbot | https://review.opendev.org/#/c/709326/ - swift - Enable more concurrency for EC GET - 2 patch sets | 21:56 |
| *** zaitcev has left #openstack-meeting | 21:56 | |
| clayg | shrinking doesn't really work! https://review.opendev.org/#/c/741721/ | 21:56 |
| patchbot | patch 741721 - swift - add swift-manage-shard-ranges shink command - 2 patch sets | 21:56 |
| clayg | at least it's not working well for me when I try to do it manually without auto_shard = true (which is how my clusters are) | 21:56 |
| mattoliverau | oh interesting | 21:57 |
| clayg | so I really want to merge https://review.opendev.org/#/c/741721/ and get that deployed ASAP (it's mostly stealing all the fixes from tim and then putting a cli ontop of it) | 21:57 |
| patchbot | patch 741721 - swift - add swift-manage-shard-ranges shink command - 2 patch sets | 21:57 |
| clayg | also I really want to merge https://review.opendev.org/#/c/742535/ because until I have way to do manual shrinking I have a bunch of overlapping shard ranges and sometimes a bunch of listings get lost | 21:58 |
| patchbot | patch 742535 - swift - container-sharding: Stable overlap order - 1 patch set | 21:58 |
| clayg | i tried to keep both of those neat-and-tight cause I really want these fixes! | 21:58 |
| mattoliverau | I'll fire up a sharding env and have a play with them. | 21:59 |
| clayg | while you have a sharded db up check out https://review.opendev.org/#/c/737056/ too! | 21:59 |
| patchbot | patch 737056 - swift - swift-container-info: Show shard ranges summary - 3 patch sets | 21:59 |
| clayg | I think timburke and I agreed on that one now 🤞 | 22:00 |
| mattoliverau | kk :) | 22:00 |
| timburke | yeah, that was definitely one of the things i noticed while messing with https://review.opendev.org/#/c/738149/ -- shrinking currently needs to be "online" and actively push new info to the shard that should be shrunk | 22:00 |
| patchbot | patch 738149 - swift - Have shrinking and sharded shards save all ranges ... - 5 patch sets | 22:00 |
| timburke | all right, looks like we're out of time | 22:01 |
| timburke | thank you all for coming, and thank you for working on swift! | 22:01 |
| timburke | #endmeeting | 22:01 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" | 22:01 | |
| openstack | Meeting ended Wed Jul 22 22:01:19 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 22:01 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-07-22-21.00.html | 22:01 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-07-22-21.00.txt | 22:01 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-07-22-21.00.log.html | 22:01 |
| *** vishalmanchanda has quit IRC | 22:01 | |
| *** Lucas_Gray has joined #openstack-meeting | 22:32 | |
| *** rcernin has joined #openstack-meeting | 22:52 | |
| *** rcernin has quit IRC | 22:58 | |
| *** mlavalle has quit IRC | 23:00 | |
| *** rcernin has joined #openstack-meeting | 23:02 | |
| *** tosky has quit IRC | 23:03 | |
| *** rcernin has quit IRC | 23:04 | |
| *** rcernin has joined #openstack-meeting | 23:05 | |
| *** Lucas_Gray has quit IRC | 23:09 | |
| *** diurnalist has quit IRC | 23:26 | |
| *** markvoelker has joined #openstack-meeting | 23:27 | |
| *** markvoelker has quit IRC | 23:32 | |
| *** ociuhandu has joined #openstack-meeting | 23:47 | |
| *** ociuhandu has quit IRC | 23:52 | |
| *** number80 has quit IRC | 23:55 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!