Monday, 2020-10-26

seongsoochomorning00:21
openstackgerritTakashi Kajinami proposed openstack/swift master: Do not call the close method for list iterator  https://review.opendev.org/75960200:23
kota_morning00:53
* kota_ is thinking the PTG will start on Tuesday morning on Asian/Pacific TZ.00:53
openstackgerritTakashi Kajinami proposed openstack/swift master: Do not require the close method for response iterator  https://review.opendev.org/75960202:37
openstackgerritTakashi Kajinami proposed openstack/swift master: Do not require the close method for response iterator  https://review.opendev.org/75960202:42
*** rcernin has quit IRC03:09
*** rcernin has joined #openstack-swift03:14
timburke:-/ http://lists.openstack.org/pipermail/openstack-discuss/2020-October/018287.html04:56
timburke^^^ best analysis of our current gate failures, i believe04:56
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-swift05:33
kota_libvirt...06:20
*** m75abrams has joined #openstack-swift07:10
*** rcernin has quit IRC07:41
*** rpittau|afk is now known as rpittau07:57
*** rcernin has joined #openstack-swift08:01
*** rcernin has quit IRC08:07
*** rcernin has joined #openstack-swift08:23
*** rcernin has quit IRC08:26
*** rcernin has joined #openstack-swift08:33
*** rcernin has quit IRC09:39
*** rcernin has joined #openstack-swift09:59
*** rcernin has quit IRC10:04
*** rcernin has joined #openstack-swift10:23
*** rcernin has quit IRC10:33
*** rcernin has joined #openstack-swift10:37
*** rcernin has quit IRC10:47
*** rcernin has joined #openstack-swift11:37
*** rcernin has quit IRC11:42
*** persia_ is now known as persia11:52
openstackgerritAlistair Coles proposed openstack/swift master: Add unit test for memcache error limiting with single server  https://review.opendev.org/75943812:28
openstackgerritAlistair Coles proposed openstack/swift master: memcache: make minimum number of servers configurable  https://review.opendev.org/75949312:28
openstackgerritAlistair Coles proposed openstack/swift master: memcache: change strategy for always available servers  https://review.opendev.org/75950212:28
*** cschwede has joined #openstack-swift13:10
*** ChanServ sets mode: +v cschwede13:10
*** rcernin has joined #openstack-swift13:10
claygare we doing it!?  Is this the PTG?  let's have some coffee!13:28
*** rcernin has quit IRC13:35
seongsoochosee you soon!!14:44
*** gyee has joined #openstack-swift15:04
timburke\o/ ptg week!15:24
timburkereminder that we've got an etherpad going at https://etherpad.opendev.org/p/swift-ptg-wallaby and our first video session will be in ~5.5hrs15:25
*** m75abrams has quit IRC15:44
openstackgerritTim Burke proposed openstack/swift master: s3api: Better handle 503s in get_container_info, too  https://review.opendev.org/75973516:30
timburkeacoles, on p 759493 you said "I'm not sure how useful, or even desirable, it is to set minimum_servers > 1" -- should i maybe rework it all so that there's a simple yes/no config for whether error-limitng should be enabled?16:39
patchbothttps://review.opendev.org/#/c/759493/ - swift - memcache: make minimum number of servers configurable - 2 patch sets16:39
timburkei feel like thre's still a case to be made that if i'm dramatically changing how i configure memcached such that each proxy is talking to a single (local) endpoint, it's preferable to have *some* attempt as using memcache rather than mobbing the db layers16:39
timburkeif the memcache errors are manifesting as timeouts, it applies some backpressure to clients which should be helpful. if (as it was in the case that prompted me to write the patch) it's a misconfiguration that causes some actions (say, incr/decr) to fail while others are fine, it's still better to use a degraded memcached than no cache at all16:42
timburke🤔 or maybe i should rework the patch to not even be configurable, and just make it so if you've got exactly one memcached server configured, we skip all error-limiting stuff...16:45
*** dsariel has joined #openstack-swift16:58
*** rpittau is now known as rpittau|afk17:09
timburkeman, this seems to get stranger and stranger: http://lists.openstack.org/pipermail/openstack-discuss/2020-October/018304.html17:11
timburkei just don't quite get how we end up at "tpool + Python 3.6.x + type hinting is fubar"17:12
acolestimburke: I'm in favour of some kind of configurability if only to avoid even considering the change of default behaviour. I think I also mention of making the error limit parameters configurable (or did I imagine that?) in which case that may be sufficient i.e. for your case the error limit duration could be set to zero17:13
acoless/also mention/also saw mention/17:14
timburkeyeah, pretty sure mattoliverau saw that as an immediate red flag that they were all hardcoded17:14
acolestimburke: do you have a schedule of topics for each swift PTG session? or are we going to agree that in the first session?18:25
timburkeno formal schedule yet -- i think it'd be a good thing to kinda work out in the first session18:25
timburkeat the very least, pick a slot for some ops-feedback so i can get an announcement out to the ML18:26
*** tdasilva has joined #openstack-swift19:55
*** ChanServ sets mode: +v tdasilva19:55
mattoliverauMorning, so just to confirm start time, off schedule says 22 utc, but live schedule says 21 utc. So thought I'd confirm which is correct.20:00
mattoliverau*PDF shedule20:00
timburkeshould be 2100 UTC20:02
timburkeand good morning, mattoliverau!20:03
seongsoochomorning !20:10
*** tdasilva_ has joined #openstack-swift20:28
*** ChanServ sets mode: +v tdasilva_20:28
*** tdasilva has quit IRC20:31
*** samueldmq has quit IRC20:45
*** alecuyer has quit IRC20:45
*** samueldmq has joined #openstack-swift20:45
*** alecuyer has joined #openstack-swift20:45
*** rcernin has joined #openstack-swift21:00
zaitcevso, what's the Zoom ID?21:00
timburkeptg time! https://www.openstack.org/ptg/rooms/kilo21:00
zaitcevoh21:00
*** rcernin has quit IRC21:01
*** rcernin has joined #openstack-swift21:01
*** rcernin has quit IRC21:10
timburkeptg etherpad: https://etherpad.opendev.org/p/swift-ptg-wallaby21:19
timburkeclayg, the handoff table idea also makes me think of https://review.opendev.org/#/c/740866/2/swift/common/ring/ring.py21:25
patchbotpatch 740866 - swift - ring: Be willing to query nodes with no assignments - 2 patch sets21:25
*** rcernin has joined #openstack-swift21:35
*** rcernin has quit IRC21:43
timburkethis discussion also reminds me of https://review.opendev.org/#/c/670674/21:47
patchbotpatch 670674 - swift - WIP: Allow ring lookups via a service - 2 patch sets21:47
ormandjhttps://docs.openstack.org/swift/latest/overview_ring.html#history third paragraph was the reasoning "latency"21:49
ormandji definitely think it's worth revisiting, times have changed :)21:50
*** rcernin has joined #openstack-swift22:00
*** rcernin has quit IRC22:06
*** rcernin has joined #openstack-swift22:22
*** rcernin has quit IRC22:22
*** rcernin has joined #openstack-swift22:22
*** rcernin has quit IRC22:32
*** rcernin has joined #openstack-swift22:33
*** timur has quit IRC22:42
*** timur has joined #openstack-swift22:50
*** tkajinam has quit IRC22:55
*** tkajinam has joined #openstack-swift22:55
timburkethanks ormandj!23:08
timburkeha! "ring changes are currently infrequent enough that manual control was sufficient"23:08

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