Friday, 2019-04-12

*** ianychoi has joined #openstack-swift00:01
*** gyee has quit IRC00:15
*** NM has joined #openstack-swift00:37
*** NM has quit IRC00:53
*** NM has joined #openstack-swift00:57
*** NM has quit IRC01:24
*** irclogbot_3 has quit IRC03:01
*** irclogbot_0 has joined #openstack-swift03:02
*** rcernin has quit IRC03:15
*** psachin has joined #openstack-swift03:20
*** rcernin has joined #openstack-swift03:28
*** rcernin has quit IRC03:57
*** rcernin has joined #openstack-swift04:01
*** _d34dh0r53_ has joined #openstack-swift04:29
*** tkajinam has quit IRC05:00
*** tkajinam has joined #openstack-swift05:07
*** psachin has quit IRC05:49
*** psachin has joined #openstack-swift06:05
*** pcaruana has joined #openstack-swift06:41
*** e0ne has joined #openstack-swift06:45
*** e0ne has quit IRC07:21
*** rdejoux has joined #openstack-swift07:33
*** e0ne has joined #openstack-swift07:36
*** e0ne has quit IRC07:52
*** ccamacho has joined #openstack-swift07:53
*** e0ne has joined #openstack-swift07:59
*** e0ne has quit IRC08:55
*** e0ne has joined #openstack-swift09:00
*** rcernin has quit IRC09:30
*** e0ne has quit IRC09:58
*** e0ne has joined #openstack-swift10:03
*** e0ne has quit IRC10:28
*** pcaruana has quit IRC10:31
*** mvkr has joined #openstack-swift11:23
*** pcaruana has joined #openstack-swift11:36
*** e0ne has joined #openstack-swift11:37
*** dhellmann has left #openstack-swift12:10
*** psachin has quit IRC12:11
*** NM has joined #openstack-swift12:22
*** e0ne has quit IRC12:27
*** e0ne has joined #openstack-swift12:41
*** timburke has quit IRC12:46
*** timburke has joined #openstack-swift12:48
*** ChanServ sets mode: +v timburke12:48
*** e0ne has quit IRC12:55
*** e0ne has joined #openstack-swift12:59
*** altlogbot_0 has joined #openstack-swift13:05
*** tkajinam_ has joined #openstack-swift13:25
*** tkajinam has quit IRC13:27
*** altlogbot_0 has quit IRC13:32
*** altlogbot_1 has joined #openstack-swift13:34
*** d34dh0r53 has quit IRC13:35
*** altlogbot_1 has quit IRC13:38
*** altlogbot_3 has joined #openstack-swift13:40
*** e0ne has quit IRC13:42
*** altlogbot_3 has quit IRC14:00
*** thurloat has joined #openstack-swift14:15
*** altlogbot_0 has joined #openstack-swift14:27
*** altlogbot_0 has quit IRC14:29
*** altlogbot_1 has joined #openstack-swift14:31
*** e0ne has joined #openstack-swift14:31
*** altlogbot_1 has quit IRC14:33
*** altlogbot_0 has joined #openstack-swift14:49
*** altlogbot_0 has quit IRC14:51
*** altlogbot_2 has joined #openstack-swift14:53
*** altlogbot_2 has quit IRC14:55
*** altlogbot_1 has joined #openstack-swift14:59
*** ccamacho has quit IRC15:20
*** e0ne has quit IRC15:24
*** psachin has joined #openstack-swift16:01
*** gyee has joined #openstack-swift16:15
*** ndk_ has joined #openstack-swift16:25
*** zaitcev_ is now known as zaitcev16:34
timburkegood morning16:46
zaitcevguys16:54
zaitcevWhat if we have 3 nodes hosting replicas for container X, and 1 reports wrong size for X? Like 915520 objects in 1 node, and 862400 on 2 others (consistent). Is there a way to force a replication to happen short of rm(1) on the wrong node?16:55
zaitcevI think replicatior never knows which one is right. It only looks at the timestamps at the local db, and if they are newer, it updates. So the summary amounts never agree.i16:58
notmynamegood morning17:01
*** e0ne has joined #openstack-swift17:03
*** e0ne has quit IRC17:03
timburkezaitcev, when you get to https://github.com/openstack/swift/blob/2.21.0/test/unit/obj/test_diskfile.py#L293-L343 -- don't trust that the test is right :-(17:05
timburkeon the db question -- what do the sync points look like for the different dbs? do the replicators *think* that they're in sync, or do they (slowly) make progress on them each cycle?17:07
zaitcevtimburke: I don't have first-hand access, so I don't know.17:07
zaitcevtimburke: I only know the last update timestamp, which is the same on all 3. But not the sync points.17:09
zaitcevtimburke, so what is wrong with that test? All I can see is, it divorces the back-end support from the question of what's legal on the wire. So, we have these non-UTF-8 things (including keys), and we do some things when we encounter them. What is the problem?17:16
timburkethings like the "# sanity check, while still mocked, that we did persist unicode" comment followed by tests like "self.assertIsInstance(k, str)"17:21
timburkei think i botched something in https://github.com/openstack/swift/commit/36c429717:21
*** e0ne has joined #openstack-swift17:23
timburkei remember starting to look at diskfile, getting to that failure, getting lost in the various bits of mocking, and deciding to walk away and come back to it later17:23
timburkethat's all17:23
zaitcevbotched in what way? It's the same code verbatim for six.PY217:24
zaitcevsame code!17:24
zaitcevSo rest assured, nothing is bothched yet, except maybe the py3 case17:24
zaitcevAh17:24
timburkesix.text_type and str are different in py217:25
zaitcevYou mean the exact compatibility on the disk, right?17:25
zaitcevBut it's okay, as long as nobody got py3 into production we can fix it all.17:25
zaitcevanyway17:26
timburkeyeah, for sure. we'll definitely be able to get both py2 and py3 reading (and writing? i'm pretty sure?) the same diskfiles -- i'm not too worried about that17:26
zaitcevI'm going to Dallas real quick in the afternoon, I'll be back and work on it while it rains on Saturday.17:26
timburkejust wanted to call out a test that probably needs re-writing17:27
zaitcevI see.17:27
zaitcevI'll try to dig into this properly this time, instead of just pushing things through tox and hoping it works.17:28
*** e0ne has quit IRC17:29
*** early has quit IRC17:32
*** early has joined #openstack-swift17:35
claygzaitcev: I'm in Dallas(ish)!  yes boo rain17:36
claygtimburke: any great ideas about the hardlink to a symlink problem?  I think the simplest form of my current thinking is "given how much versioned writes breaks if names aren't unique - why do we need to use hardlinks again?"17:55
timburkeclayg, i'm starting to think that we should maybe use normal symlinks if we're versioning a symlink, and hard links if it's a normal object...18:00
timburkefwiw, i wanted hard links as a way to (1) provide some assurances about the backing data not changing and (2) have a handy way to write down etag/size so we can fix up listings for the primary container18:00
claygoh right, the listing fixup is huge18:00
claygdammit - i remembered that earlier and then forgot again18:01
timburkeidk -- maybe i'm worrying too much about listings18:02
timburkebut it *seems* like a thing worth preserving if/when we can18:02
*** irclogbot_0 has quit IRC18:08
*** irclogbot_1 has joined #openstack-swift18:11
*** rdejoux has quit IRC18:16
notmynameif you're interested in some of the data pipelines for self driving cars, you'll likely find this video interesting. https://on-demand.gputechconf.com/gtc/2019/video/_/S9649/18:21
notmyname...and there may be some indirect references to swift being a pretty important part of that ;-)18:21
*** psachin has quit IRC18:46
*** NM has quit IRC19:24
*** NM has joined #openstack-swift19:27
openstackgerritTim Burke proposed openstack/swift master: Make staticweb return URL-encoded Location headers  https://review.openstack.org/57190719:38
openstackgerritTim Burke proposed openstack/swift master: Support Unicode in account and user names during func tests  https://review.openstack.org/57190819:38
openstackgerritTim Burke proposed openstack/swift master: Use more pathologically-bad names for func tests  https://review.openstack.org/65194019:38
*** pcaruana has quit IRC20:26
*** NM has quit IRC21:31
openstackgerritTim Burke proposed openstack/swift master: Use more pathologically-bad names for func tests  https://review.openstack.org/65194021:41
*** itlinux has joined #openstack-swift22:06
*** NM has joined #openstack-swift23:53
timburkeholy crap. i just realized that the s3api port will put us over 5k py3 unit tests: http://logs.openstack.org/93/651893/3/check/swift-tox-py37/89f000e/job-output.txt.gz#_2019-04-11_22_42_58_96819423:58
timburkepy27 has ~6800 -- that's like 74%!23:58

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