Thursday, 2019-10-31

*** gyee has quit IRC00:07
*** renich has joined #openstack-swift01:14
*** nanzha has joined #openstack-swift01:14
*** diablo_rojo has quit IRC02:18
*** diablo_rojo has joined #openstack-swift02:33
*** tkajinam has quit IRC03:04
*** diablo_rojo has quit IRC03:05
*** psachin has joined #openstack-swift03:33
*** tkajinam has joined #openstack-swift04:14
*** nanzha has quit IRC05:30
*** nanzha has joined #openstack-swift05:31
*** zaitcev_ has joined #openstack-swift05:51
*** ChanServ sets mode: +v zaitcev_05:51
*** zaitcev has quit IRC05:55
*** ccamacho has quit IRC06:39
*** tesseract has joined #openstack-swift06:45
*** renich has quit IRC06:56
*** nanzha has quit IRC06:57
*** nanzha has joined #openstack-swift07:09
openstackgerritThiago da Silva proposed openstack/swift master: Set new lower-bound for several packages  https://review.opendev.org/69212407:15
*** pcaruana has joined #openstack-swift07:50
*** nanzha has quit IRC08:02
*** nanzha has joined #openstack-swift08:14
*** rdejoux has joined #openstack-swift08:31
*** tkajinam has quit IRC08:39
*** ccamacho has joined #openstack-swift08:51
*** rpittau|afk is now known as rpittau08:52
*** mikecmpbll has joined #openstack-swift09:00
*** ccamacho has quit IRC09:09
*** nanzha has quit IRC09:57
*** nanzha has joined #openstack-swift09:57
*** rpittau is now known as rpittau|bbl11:00
*** tkajinam has joined #openstack-swift11:17
*** ccamacho has joined #openstack-swift11:30
*** FlorianFa has joined #openstack-swift12:13
openstackgerritThiago da Silva proposed openstack/swift master: Set new lower-bound for several packages  https://review.opendev.org/69212412:49
*** tkajinam has quit IRC13:06
*** rpittau|bbl is now known as rpittau13:16
*** psachin has quit IRC13:35
*** nanzha has quit IRC15:05
*** nanzha has joined #openstack-swift15:06
*** renich has joined #openstack-swift15:12
*** FlorianFa has quit IRC15:54
*** mikecmpbll has quit IRC16:01
*** mikecmpbll has joined #openstack-swift16:02
openstackgerritThiago da Silva proposed openstack/swift master: WIP: New Object Versioning mode  https://review.opendev.org/68238216:14
*** nanzha has quit IRC16:20
*** rdejoux has quit IRC16:21
openstackgerritGilles Biannic proposed openstack/swift master: Stop retrying every deletes in container-sync  https://review.opendev.org/69172916:22
*** tesseract has quit IRC16:33
*** renich has quit IRC16:35
*** renich has joined #openstack-swift16:36
*** gyee has joined #openstack-swift16:50
*** mikecmpbll has quit IRC16:55
*** mikecmpbll has joined #openstack-swift16:58
*** rpittau is now known as rpittau|afk17:14
*** mikecmpbll has quit IRC17:33
*** renich has quit IRC18:07
claygtimburke: I disagree with your suggestion to return a list to indicate an "acceptable" http error was raised - we now have a function that will return None, a tuple, or raise at least 4 different kinds of exceptions that we know about18:09
claygtimburke: Also "acceptable_statuses" is a terrible name for this new behavior - since any is_success status is allowed in *this* context by default SimpleClient now has an interface that *smells* like InternalClient's acceptable_statuses but is wildly different18:11
timburkeeh? we either return a list (because that's the only thing base_request returns) or we raise -- where are you seeing None?18:12
claygcheck the default values for acceptable_statuses on e.g. InternalClient.get_account_info - just sayin' cc gmann18:12
timburkeclayg, i don't think that's Gilles ;-)18:12
claygoops!18:12
claygi see, we never fall out of the loop - yeah that helps18:13
timburkei *do* think that we should have a way to say "these statuses are not exceptional" though, very much like internal_client. i originally thought that it *did* work like internal_client (in part because we're *in the internal_client module*!) and was disappointed that it didn't18:14
claygthat loop should probably read `while True:` - i don't know what the type of err.info() vs. conn.info()18:14
timburkeboth HTTPMessages -- basically, all the headers from the response (but not the status code :-( )18:15
claygI think simple client was just thin enough that we didn't want to create a seperate module to hang it off at the time18:15
clayglol @ not the status code18:15
timburkei think we could set it easily enough, and in both cases18:16
timburke*separately* (and maybe this would be enough for Gilles's problem) we should *almost certainly* prevent SimpleClient from retrying on *client* errors18:17
claygI don't think we're going to make SimpleClient.retry_request work anything like InternalClient.make_request - not sure why we latched onto acceptable_statuses as a concept except that we're in the same module and didn't realize we have different classes/interfaces18:17
claygoh, sure I like that pleanty - just have it raise 4XX immediately and only do backoff on 5XX and other kinds of http/socket errors 👍18:18
claygso with splitting the the HTTPError - then all we have to do is `if attempts > retries or is_client_error(e): raise` - no new kwarg18:19
timburkeand the 409 behavior could be a separate patch18:19
*** mvkr has quit IRC18:20
claygI see no reason to add the string to pull - i may not understand the situation with 409 - should it not get re-raised immediately like 404?18:20
claygin sync we just say `if err.http_status in (...)`?18:21
timburke👍18:21
timburkei was mainly just thinking that they seem like orthogonal fixes -- i probably shouldn't have brought it up on the bug, was just kinda thinking out loud18:22
claygI'm having a bit of trouble with `test/probe/test_object_expirer.py:TestObjectExpirer.test_expirer_doesnt_make_async_pendings` - anyone in a environment to spot check master, or have seen that recently?  I haven't looked into it.  Might be evironmental.18:26
claygI don't really see the 404 vs 409 as orthogonal - I think you hit the nail on the head - retry_request shouldn't be using the same backoff/retry logic for socket errors that it's using for client errors18:28
clayghow interesting that it doesn't have any authentication handling - is that because of something in realms!?18:29
claygWHO USES CONTAINER SYNC 🤣18:29
*** renich has joined #openstack-swift18:32
timburkei was thinking more about the fact that 409 is treated as a failure and prevents sync_point2 from advancing -- that's orthogonal from the retry behavior issue18:37
*** paladox has quit IRC18:52
*** paladox has joined #openstack-swift18:55
*** diablo_rojo has joined #openstack-swift19:51
rledisezclayg: we do use container-sync, and we are going to work to improve it cause customers are asking for it (note: Gilles is from my team)19:55
timburkequick question -- did we *always* have py27 support? i know we supported py26 through 2.3.0, but the earliest mention i see in the changelog for py27 was way back in 1.4.0 and it just says "Fixed a Python 2.7 compatibility problem."19:55
timburkei guess my question is, was the scope of that problem "absolutely nothing works"? 🤣19:56
timburkerledisez, you should get him to come on irc :-)19:59
rlediseztimburke: i'll tell him :)20:01
claygrledisez: 🤗20:07
*** diablo_rojo has quit IRC20:31
mattoliverauDid we ever land those container sync improvements from Eran years ago?20:40
*** pcaruana has quit IRC21:31
mattoliveraumorning21:49
*** renich has quit IRC21:55
*** renich has joined #openstack-swift22:32
*** threestrands has joined #openstack-swift22:42
*** tkajinam has joined #openstack-swift23:00

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!