Wednesday, 2019-08-14

*** rcernin has joined #openstack-swift00:08
*** zaitcev has quit IRC00:22
viks___clayg: Ok.. thanks00:24
*** zaitcev has joined #openstack-swift00:35
*** ChanServ sets mode: +v zaitcev00:35
*** gyee has quit IRC00:48
*** rcernin has quit IRC00:58
*** spsurya has joined #openstack-swift01:05
*** rcernin has joined #openstack-swift01:14
*** baojg has joined #openstack-swift01:17
*** BjoernT_ has joined #openstack-swift01:44
*** BjoernT_ has quit IRC01:46
*** BjoernT has quit IRC01:47
*** zaitcev has quit IRC02:07
*** zaitcev has joined #openstack-swift02:21
*** ChanServ sets mode: +v zaitcev02:21
*** BjoernT has joined #openstack-swift02:22
*** zaitcev has quit IRC02:35
*** BjoernT has quit IRC02:46
*** zaitcev has joined #openstack-swift02:49
*** ChanServ sets mode: +v zaitcev02:49
kota_hello world02:56
mattoliverauo/03:02
*** ccamacho has joined #openstack-swift03:06
kota_mattoliverau: o/03:25
*** psachin has joined #openstack-swift03:33
*** zaitcev has quit IRC03:34
*** gkadam has joined #openstack-swift03:41
*** gkadam has quit IRC03:41
*** gkadam has joined #openstack-swift03:43
*** zaitcev has joined #openstack-swift03:45
*** ChanServ sets mode: +v zaitcev03:45
*** gkadam has quit IRC04:00
*** manuvakery has joined #openstack-swift04:46
*** zaitcev has quit IRC06:02
*** zaitcev has joined #openstack-swift06:16
*** ChanServ sets mode: +v zaitcev06:16
*** rcernin has quit IRC06:16
*** rcernin has joined #openstack-swift06:31
*** ccamacho has quit IRC07:10
*** tesseract has joined #openstack-swift07:10
*** e0ne has joined #openstack-swift07:22
*** rcernin has quit IRC07:56
*** tkajinam has quit IRC08:11
*** rcernin has joined #openstack-swift08:23
*** rcernin has quit IRC08:29
*** rcernin has joined #openstack-swift08:38
*** zaitcev has quit IRC09:01
*** rcernin has quit IRC09:04
*** zaitcev has joined #openstack-swift09:14
*** ChanServ sets mode: +v zaitcev09:14
*** tdasilva has joined #openstack-swift09:25
*** ChanServ sets mode: +v tdasilva09:25
*** baojg has quit IRC10:15
*** baojg has joined #openstack-swift10:16
*** zaitcev has quit IRC11:04
*** zaitcev has joined #openstack-swift11:17
*** ChanServ sets mode: +v zaitcev11:17
*** manuvakery has quit IRC11:39
*** rcernin has joined #openstack-swift12:35
*** zaitcev_ has joined #openstack-swift12:39
*** ChanServ sets mode: +v zaitcev_12:39
*** rcernin has quit IRC12:40
*** zaitcev has quit IRC12:43
*** BjoernT has joined #openstack-swift13:19
*** BjoernT has quit IRC13:23
*** BjoernT has joined #openstack-swift13:23
*** dsariel has joined #openstack-swift13:31
claygtdasilva: nice find on the account_acls prior art!13:39
claygtdasilva: in fact, I just realized the next patch in the chain does puts use_symlinks in /info because i'm working on making func tests bifricate13:40
claygI'm not sure we need to have func tests pass/skip w/o static_link=True?13:41
tdasilvaclayg: I think we might in the future13:41
clayg🤔 ???13:41
tdasilvaclayg: if I were for example to run the master func tests against an older swift13:41
tdasilvanot sure how likely that is...in the case of the multinode-rolling-upgrade gate tests, it's the opposite13:42
tdasilvawhere we run an "older" previous release func tests against "master" swift13:43
tdasilvaso maybe not...13:43
tdasilvaclayg: I had that idea of expanding the multinode-rolling-upgrade tests to run like a setup and verify set of tests and in that case we always use newer tests. So in that case it would be nice to be able to test for static_link=true13:45
tdasilvaclayg: see p https://review.opendev.org/#/c/626663/13:46
patchbotpatch 626663 - swift - Add rolling upgrade tests - 7 patch sets13:46
claygtdasilva: that is brilliant and amazing! 😍13:52
tdasilvaclayg: heh, my hope is that it will be useful for testing py2 to py3 upgrade13:55
openstackgerritThiago da Silva proposed openstack/swift master: Add params to get_*_metadata internal client methods  https://review.opendev.org/67641414:15
ormandjheya folks, what are people doing to cleanup orphan segments in +segments folders when clients die?14:20
ormandjwe've unfortunately seen a lot of bad clients/connections/etc that lead to partial chunked data sitting in a +segments (s3 compat layer access) without metadata associated with it14:21
*** zaitcev_ is now known as zaitcev14:24
*** BjoernT_ has joined #openstack-swift14:35
*** BjoernT has quit IRC14:36
*** ianychoi has joined #openstack-swift15:20
*** dsariel has quit IRC15:32
*** zaitcev_ has joined #openstack-swift15:36
*** ChanServ sets mode: +v zaitcev_15:36
*** zaitcev has quit IRC15:40
*** diablo_rojo has joined #openstack-swift15:48
*** tesseract has quit IRC15:56
openstackgerritThiago da Silva proposed openstack/swift master: fix ec overview doc formatting  https://review.opendev.org/67644616:01
*** fungi has quit IRC16:42
*** fungi has joined #openstack-swift16:43
*** e0ne has quit IRC16:51
*** diablo_rojo has quit IRC16:52
*** mrjk has quit IRC16:54
*** psachin has quit IRC16:57
*** tdasilva has quit IRC16:58
*** diablo_rojo has joined #openstack-swift17:05
*** mrjk has joined #openstack-swift17:08
*** diablo_rojo has quit IRC17:10
*** diablo_rojo has joined #openstack-swift17:12
*** spsurya has quit IRC17:14
*** tdasilva has joined #openstack-swift17:23
*** ChanServ sets mode: +v tdasilva17:23
*** diablo_rojo has quit IRC17:24
*** diablo_rojo has joined #openstack-swift17:24
*** diablo_rojo has quit IRC17:51
*** tdasilva has quit IRC17:53
*** zaitcev__ has joined #openstack-swift17:54
*** ChanServ sets mode: +v zaitcev__17:54
*** zaitcev_ has quit IRC17:57
*** gyee has joined #openstack-swift18:06
*** e0ne has joined #openstack-swift18:08
*** diablo_rojo has joined #openstack-swift18:08
*** e0ne has quit IRC18:10
*** diablo_rojo has quit IRC18:19
openstackgerritMerged openstack/swift master: s3api: Translate 503 to S3-style 503s  https://review.opendev.org/67490118:26
ormandjwhat ec_type are most people settling on nowadays?18:34
*** zaitcev__ has quit IRC18:46
claygwe've been using isa-l forever18:53
claygin fact I think all swiftstack clusters do - never had any isa-l specific issue18:55
ormandjthat's great to know, thanks clayg. what data/parity mix did you end up determining worked best for you? i'm in the middle of trying to figure out what direction i want to go18:58
ormandji didn't really see any best practices for that/segment size as well in the docs, and figured i'd get a good starting point before i start trying to benchmark/calculate durability/etc18:59
*** zaitcev__ has joined #openstack-swift19:00
*** ChanServ sets mode: +v zaitcev__19:00
DHEdepends on your needs. more parity is more resilient but increases capacity requirements. that can be offset with more fragments but CPU usage goes up and more network connections are required19:01
ormandjsure, and gotta balance recovery times vs. failure rates/etc to make sure you get the durability you need19:02
DHEI'm leaning towards 10-20 data fragments and 3-5 parity fragments...19:02
DHEand probably isa-l with cauchy (sp?) due to the rs_vand issue with 5+ parity fragments19:02
ormandji just figure there's at least a wet-finger-in-the-wind range people are finding works well on most typical deployments, which are gonna be spinny disks on some number of servers, some local some wan19:02
claygone thing you have to watch out in small or mid-size clusters is the write amplification under heavy concurrency with clients - 100 concurrent PUTs on a 20+5 can make 2500 backend connections, you need to think about your per-disk write queue depth19:08
ormandjthat's a good callout19:10
*** tdasilva has joined #openstack-swift19:13
*** ChanServ sets mode: +v tdasilva19:13
ormandjclayg:  thanks for the protips19:30
*** zaitcev_ has joined #openstack-swift19:31
*** ChanServ sets mode: +v zaitcev_19:31
*** zaitcev__ has quit IRC19:34
openstackgerritMerged openstack/swift master: Add params to get_*_metadata internal client methods  https://review.opendev.org/67641420:14
*** e0ne has joined #openstack-swift20:14
*** diablo_rojo has joined #openstack-swift20:20
*** diablo_rojo has quit IRC20:37
*** diablo_rojo has joined #openstack-swift20:37
*** diablo_rojo has quit IRC20:41
*** diablo_rojo has joined #openstack-swift20:48
kota_morning20:56
mattoliverauMorning20:59
timburkemeeting time!21:00
*** dsariel has joined #openstack-swift21:00
timburkeclayg, zaitcev_, rledisez, alecuyer ^^^21:01
*** diablo_rojo has quit IRC21:04
*** diablo_rojo has joined #openstack-swift21:09
*** e0ne has quit IRC21:11
*** e0ne has joined #openstack-swift21:13
*** e0ne has quit IRC21:13
kota_it looks like the original error is `No such file or directory`21:36
rledisezkota_: yeah, that's right21:36
tdasilvaright, it looks like it is trying to rename from 0dbdb93b1ef1360902c56454414f0d221565777702.34279#0.data to 0dbdb93b1ef1360902c56454414f0d221565777702.34279#0#d.data21:37
kota_so imo we should dig the point to touch real file...21:37
kota_maybe rename_vfile method21:38
rledisezdig you check that the original file exists in the KV?21:38
rledisez*did21:38
rledisezeg: by making a fuse mount?21:39
tdasilvarledisez: no21:40
rlediseztdasilva: swift-mount-losf /some/mount/path21:41
tdasilvaah! nice21:42
rledisezyou'll be able to navigate (readonly) in the KV21:42
rledisezand running some commande like swift-object-info21:42
rledisezthere is a flag to enable to delete objects, but it's a bad idea to use it ;)21:42
tdasilvahehe, ok21:43
mattoliverauoh wow, cool! Nice tool21:44
kota_hmm, rledisez suggest a way to debug so I'm going to look for my breakfast to get fresh brain21:44
rlediseztake your time kota_, i'm about to leave21:45
tdasilvaand i'm about to go to sleep :)21:45
rlediseztake your time too tdasilva, a good night provides better debug skills ;)21:46
tdasilvarledisez, kota_ hopefully we'll have more feedback next week21:46
tdasilvarledisez: Darrel is running the tests internally i'm just relaying info..21:47
tdasilvaI have my losf saio, but haven't run into this yet, will keep trying to reproduce21:47
claygwhat'd i miss!?21:47
zaitcev_a meeting21:56
timburkebasically, you guys are doing great work :-)22:01
timburkekeep it up!22:01
*** diablo_rojo has quit IRC22:05
*** diablo_rojo has joined #openstack-swift22:05
openstackgerritMerged openstack/swift master: fix ec overview doc formatting  https://review.opendev.org/67644622:17
openstackgerritMerged openstack/swift master: py3: port test/functional/test_versioned_writes.py  https://review.opendev.org/67571022:17
openstackgerritMerged openstack/swift stable/stein: s3api: Allow clients to upload with UNSIGNED-PAYLOAD  https://review.opendev.org/67543722:17
openstackgerritMerged openstack/swift stable/stein: Fix quarantine when object path is not a directory  https://review.opendev.org/67543522:17
zaitcev_timburke: do you happen to know as PTL when Train branches?22:21
timburkezaitcev_, https://releases.openstack.org/train/schedule.html indicates that we should have a final release around the first week of october or so22:23
timburkethat's somewhat separate from the actual branch getting created; i forget exactly when that would happen -- probably another week or two after?22:23
timburkeout of curiosity, why?22:24
zaitcev_Our automated systems will start building py3 based release then.22:40
*** BjoernT_ has quit IRC22:40
timburke👍22:41
*** tkajinam has joined #openstack-swift22:50
*** zaitcev_ has quit IRC22:59
*** tyreymer has joined #openstack-swift23:05
*** zaitcev_ has joined #openstack-swift23:13
*** ChanServ sets mode: +v zaitcev_23:13
openstackgerritMerged openstack/swift stable/stein: reconciler: Enqueue right work for shard containers  https://review.opendev.org/67543323:14
*** diablo_rojo has quit IRC23:18
*** diablo_rojo has joined #openstack-swift23:18
*** diablo_rojo has quit IRC23:31
*** tyreymer has quit IRC23:41
openstackgerritTim Burke proposed openstack/swift master: py3: fix up listings on sharded containers  https://review.opendev.org/67116723:47
openstackgerritTim Burke proposed openstack/swift master: py3: fix up swift-orphans  https://review.opendev.org/67093223:52

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