Wednesday, 2017-11-15

*** abhitechie has joined #openstack-swift00:05
thurloatin the example proxy-server.conf, the keystone pipeline is missing "listing_formats" middleware, is this omission on purpose, or naw?00:08
timburkeit's an omission, but it doesn't really matter; the proxy server will auto-insert it if it isn't present00:10
timburkewe've gotta be able to still work with an old config, after all00:11
notmynameoversight00:11
notmynamealmost certainly00:11
*** wes_dillingham has quit IRC00:31
*** wes_dillingham has joined #openstack-swift00:35
thurloati'll include it anyway :)00:36
thurloatgoing through our confs with a comb before the upgrade from 1.13.hack to 2.16.000:37
timburkewhooo! it's gonna be a great upgrade :-)00:42
notmynameno meeting this week, neither 0700 nor 210000:52
notmynameacoles: kota_: mattoliverau: rledisez: mahatic: jungleboyj: ^00:52
mattoliveraunotmyname: kk00:53
mattoliveraurledisez is still in Australia somewhere. So assume he's on leave anyway :)00:54
notmynamecool00:54
jungleboyjnotmyname: cool. I just got back. Trying to recover and catch up.00:59
jungleboyjmattoliverau: I have no idea how you have done this repeatedly in the past.00:59
mattoliveraujungleboyj: lol, do it 4 times a year for about 4 years and it gets easier.. or rather, it becomes the new normal, not really easier ;p01:01
mattoliveraujust imbrance the jetlag.. let it become one with you :P01:02
jungleboyjI have all respect for you. Can't concentrate today too save my life.01:04
*** cshastri has joined #openstack-swift01:13
*** tovin07_ has joined #openstack-swift01:16
kota_good morning.01:22
kota_notmyname: ack for no meeting. thanks for sharing01:22
*** m_kazuhiro has joined #openstack-swift01:23
*** gyee_ has quit IRC01:23
*** tovin07__ has joined #openstack-swift01:24
*** tovin07_ has quit IRC01:28
*** tovin07__ has quit IRC01:28
*** tovin07_ has joined #openstack-swift01:30
*** wes_dillingham has quit IRC01:34
*** links has joined #openstack-swift02:03
*** threestrands has joined #openstack-swift02:09
*** itlinux has joined #openstack-swift02:11
*** itlinux has quit IRC02:17
*** m_kazuhiro_ has joined #openstack-swift02:24
m_kazuhiro_good morning02:25
m_kazuhirooops I logged in irc twice.02:27
*** m_kazuhiro_ has quit IRC02:27
*** JimCheung has quit IRC02:35
*** JimCheung has joined #openstack-swift02:35
*** JimCheung has quit IRC02:39
*** tovin07__ has joined #openstack-swift02:42
*** tovin07_ has quit IRC02:44
*** caiobrentano has quit IRC02:48
*** Sukhdev has quit IRC02:51
*** tovin07 has joined #openstack-swift02:53
*** tovin07__ has quit IRC02:56
-openstackstatus- NOTICE: Due to an unexpected outage with Zuul (1 hour), you'll need to recheck any jobs that were in progress. Sorry for the inconvenience.02:57
*** tovin07 has quit IRC02:58
*** itlinux has joined #openstack-swift03:15
*** two_tired has joined #openstack-swift03:16
kongtimburke: are you still around?03:27
kongi found the root cause of the issue, our nginx cache is filled up occa03:27
kongoccasionally, which cause 206 received in client side03:28
kongand swift client is trying to using 'accept-ranges' to fetch all the bytes, finally, the file size is correct, but md5 check failed03:28
kongi did md5sum on the downloaded object, it is different with the object etag in swift03:29
kongi am confused03:29
kongor anyone else can help?03:31
kongthe swift client debug log: http://dpaste.com/0CD9FQZ03:32
*** rcernin has quit IRC03:34
*** tovin07_ has joined #openstack-swift03:35
*** rcernin has joined #openstack-swift03:36
*** abhitechie has quit IRC03:38
*** kei_yama has quit IRC03:38
kongi'm not sure https://bugs.launchpad.net/swift/+bug/1717401 is related03:46
openstackLaunchpad bug 1717401 in OpenStack Object Storage (swift) "Client(curl) gets partial content while proxy-server got ChunkRead timeout " [High,Fix released]03:46
*** ^andrea^ has quit IRC03:47
kongi will be offline in a few minutes, please if anyone has some suggestion or hints, leave message to me, thanks!03:48
*** janonymous has joined #openstack-swift03:49
*** ukaynar has joined #openstack-swift03:56
*** kei_yama has joined #openstack-swift04:00
*** abhitechie has joined #openstack-swift04:15
*** m_kazuhiro has quit IRC04:26
*** psachin has joined #openstack-swift04:28
*** m_kazuhiro has joined #openstack-swift04:35
mahaticnotmyname: ack on the no meeting, thanks04:35
jungleboyjmattoliverau:  Also, the fact that I became useful at 6 pm after being useless all day!  Yikes!05:12
*** itlinux has quit IRC05:27
*** abhitechie has quit IRC05:47
*** two_tired has quit IRC05:55
*** ukaynar has quit IRC06:33
*** ukaynar has joined #openstack-swift06:34
*** abhitechie has joined #openstack-swift06:34
*** threestrands has quit IRC06:34
*** ukaynar has quit IRC06:38
*** ukaynar has joined #openstack-swift06:38
*** gabor_antal_ has joined #openstack-swift06:40
*** ukaynar_ has joined #openstack-swift06:43
*** ukaynar has quit IRC06:43
*** gabor_antal has quit IRC06:43
*** ukaynar_ has quit IRC06:47
*** ukaynar has joined #openstack-swift06:47
*** ukaynar has quit IRC06:52
*** ukaynar has joined #openstack-swift06:52
*** ukaynar has quit IRC06:56
*** ukaynar has joined #openstack-swift06:57
*** abhitechie has quit IRC06:59
*** ukaynar has quit IRC07:01
*** ukaynar has joined #openstack-swift07:01
*** ukaynar has quit IRC07:06
*** ukaynar_ has joined #openstack-swift07:06
*** ukaynar_ has quit IRC07:10
*** ukaynar has joined #openstack-swift07:10
*** spectr has joined #openstack-swift07:13
*** SkyRocknRoll has quit IRC07:15
*** ukaynar_ has joined #openstack-swift07:15
*** ukaynar has quit IRC07:15
*** ukaynar_ has quit IRC07:19
*** rcernin has quit IRC07:20
*** ukaynar has joined #openstack-swift07:20
*** ukaynar has quit IRC07:24
*** ukaynar has joined #openstack-swift07:24
*** armaan has joined #openstack-swift07:28
*** ukaynar_ has joined #openstack-swift07:29
*** ukaynar has quit IRC07:29
*** hoonetorg has quit IRC07:30
*** cshastri has quit IRC07:32
*** ukaynar_ has quit IRC07:33
*** ukaynar has joined #openstack-swift07:34
*** m_kazuhiro has quit IRC07:35
*** cshastri has joined #openstack-swift07:38
*** ukaynar has quit IRC07:38
*** spectr has quit IRC07:38
*** ukaynar has joined #openstack-swift07:38
*** ukaynar has quit IRC07:43
*** hoonetorg has joined #openstack-swift07:43
*** ukaynar has joined #openstack-swift07:43
*** ukaynar has quit IRC07:47
*** ukaynar has joined #openstack-swift07:48
*** pcaruana has joined #openstack-swift07:51
*** ukaynar has quit IRC07:52
*** ukaynar has joined #openstack-swift07:52
*** ukaynar has quit IRC07:57
*** ukaynar_ has joined #openstack-swift07:57
*** PagliaccisCloud has quit IRC08:01
*** ukaynar has joined #openstack-swift08:01
*** ukaynar_ has quit IRC08:02
*** abhitechie has joined #openstack-swift08:03
*** PagliaccisCloud has joined #openstack-swift08:05
*** ukaynar has quit IRC08:06
*** ukaynar has joined #openstack-swift08:06
*** ukaynar_ has joined #openstack-swift08:11
*** ukaynar has quit IRC08:11
*** ukaynar_ has quit IRC08:15
*** ukaynar has joined #openstack-swift08:15
*** tesseract has joined #openstack-swift08:17
*** ukaynar has quit IRC08:20
*** ukaynar has joined #openstack-swift08:20
*** ukaynar has quit IRC08:24
*** ukaynar has joined #openstack-swift08:25
*** tovin07_ has quit IRC08:25
*** oshritf has joined #openstack-swift08:28
*** ukaynar_ has joined #openstack-swift08:29
*** ukaynar has quit IRC08:29
*** SkyRocknRoll has joined #openstack-swift08:32
*** oshritf has quit IRC08:34
*** ukaynar has joined #openstack-swift08:34
*** ukaynar_ has quit IRC08:34
*** oshritf has joined #openstack-swift08:36
*** kei_yama has quit IRC08:36
*** oshritf has quit IRC08:38
*** ukaynar has quit IRC08:38
*** ukaynar has joined #openstack-swift08:39
*** oshritf has joined #openstack-swift08:40
*** geaaru has joined #openstack-swift08:43
*** ukaynar_ has joined #openstack-swift08:43
*** ukaynar has quit IRC08:44
*** ukaynar_ has quit IRC08:47
*** ukaynar has joined #openstack-swift08:48
*** oshritf has quit IRC08:52
*** ukaynar_ has joined #openstack-swift08:52
*** ukaynar has quit IRC08:52
*** ukaynar has joined #openstack-swift08:57
*** ukaynar_ has quit IRC08:57
*** ukaynar has quit IRC09:01
*** ukaynar has joined #openstack-swift09:02
*** gkadam has joined #openstack-swift09:02
*** ukaynar has quit IRC09:06
*** ukaynar has joined #openstack-swift09:06
*** oshritf has joined #openstack-swift09:07
*** zenpwner has joined #openstack-swift09:08
*** klrmn has quit IRC09:09
*** ukaynar_ has joined #openstack-swift09:11
*** ukaynar has quit IRC09:11
*** cbartz has joined #openstack-swift09:13
*** abhitechie has quit IRC09:13
*** ukaynar_ has quit IRC09:15
*** ukaynar has joined #openstack-swift09:16
acolesgood morning09:17
acolesnotmyname: ack no meeting, thanks09:17
*** ukaynar has quit IRC09:20
*** ukaynar has joined #openstack-swift09:20
*** ukaynar_ has joined #openstack-swift09:25
*** ukaynar has quit IRC09:25
*** ukaynar has joined #openstack-swift09:29
*** ukaynar_ has quit IRC09:30
*** ukaynar has quit IRC09:34
*** ukaynar has joined #openstack-swift09:34
*** ukaynar has quit IRC09:39
*** ukaynar has joined #openstack-swift09:39
*** ukaynar has quit IRC09:43
*** ukaynar has joined #openstack-swift09:43
*** oshritf has quit IRC09:48
*** ukaynar_ has joined #openstack-swift09:48
*** ukaynar has quit IRC09:48
*** ukaynar_ has quit IRC09:53
*** ukaynar has joined #openstack-swift09:53
*** jarbod_ has joined #openstack-swift09:54
*** abhitechie has joined #openstack-swift09:54
*** ukaynar_ has joined #openstack-swift09:57
*** ukaynar has quit IRC09:57
*** oshritf has joined #openstack-swift09:58
*** ukaynar_ has quit IRC10:02
*** ukaynar has joined #openstack-swift10:02
*** ukaynar has quit IRC10:06
*** ukaynar has joined #openstack-swift10:06
*** ukaynar_ has joined #openstack-swift10:11
*** ukaynar has quit IRC10:11
*** zenpwner has quit IRC10:15
*** ukaynar_ has quit IRC10:15
*** ukaynar has joined #openstack-swift10:16
*** mat128 has joined #openstack-swift10:20
*** ukaynar has quit IRC10:20
*** ukaynar has joined #openstack-swift10:20
*** ukaynar_ has joined #openstack-swift10:25
*** ukaynar has quit IRC10:25
bob_cheeseymorning all, i'm currently looking at reworking our SSL termination in front of the proxy servers to use haproxy and I was looking fora definitive list of verbs I need to allow through. at the moment i've got GET, PUT, POST, DELETE and HEAD10:27
bob_cheeseyhave i missed any?10:27
*** ukaynar_ has quit IRC10:29
*** ukaynar has joined #openstack-swift10:30
*** ukaynar has quit IRC10:34
*** ukaynar has joined #openstack-swift10:34
* kota_ is playing with Proxy-FS, trying to install that into my SAIO10:37
kota_good morning acoles10:37
*** ukaynar_ has joined #openstack-swift10:39
*** ukaynar has quit IRC10:39
kota_hmm... it looks the build succeeded but not working yet. though a bunch of warnings appeared in the log :/10:40
acolesbob_cheesey: COPY https://developer.openstack.org/api-ref/object-store/10:40
bob_cheeseyah wonderful, thanks acoles!10:41
*** ukaynar_ has quit IRC10:44
*** ukaynar has joined #openstack-swift10:44
acolesbob_cheesey: also, OPTIONS10:46
acoleshmmm, that doesn't seem to be documented in API docs. mentioned here https://docs.openstack.org/swift/latest/cors.html10:47
*** ukaynar has quit IRC10:48
*** ukaynar has joined #openstack-swift10:48
acoleskota_: o/10:49
bob_cheeseyacoles: thanks for that!10:51
*** ukaynar has quit IRC10:52
*** ukaynar has joined #openstack-swift10:53
kota_ah, maybe `make install` in regression_test.py requires super user privilege.10:55
*** baruna has joined #openstack-swift10:55
kota_... no? hmm... interesting10:56
*** ukaynar has quit IRC10:57
*** ukaynar has joined #openstack-swift10:57
*** ukaynar has quit IRC11:02
*** ukaynar has joined #openstack-swift11:02
*** armaan has quit IRC11:04
*** armaan has joined #openstack-swift11:04
*** mvk has quit IRC11:05
*** ukaynar has quit IRC11:06
*** ukaynar has joined #openstack-swift11:07
*** ukaynar_ has joined #openstack-swift11:11
*** ukaynar has quit IRC11:11
*** ukaynar_ has quit IRC11:16
*** ukaynar has joined #openstack-swift11:16
*** ukaynar has quit IRC11:20
*** ukaynar has joined #openstack-swift11:21
*** cshastri has quit IRC11:22
kota_hmm... it looks making vfs is missing SAMBA_PATH and the VERSION file to include.11:23
*** ukaynar has quit IRC11:25
*** ukaynar has joined #openstack-swift11:25
konghi guys, is this the expected 'Range' request behavior: http://dpaste.com/3HQXPRR11:28
kongi specified the range bytes: 0-1159721451, but the downloaded file size is 115972187711:28
*** ukaynar has quit IRC11:30
*** ukaynar has joined #openstack-swift11:30
*** mvk has joined #openstack-swift11:32
*** ukaynar has quit IRC11:34
kota_OMG, another regression_test.py found in jrpcclient dir11:34
*** ukaynar has joined #openstack-swift11:35
kota_and something missing (e.g. conf) for the script.11:36
*** ukaynar_ has joined #openstack-swift11:39
*** ukaynar has quit IRC11:39
kota_k, let's deep dive more tomorrow.11:40
*** ukaynar has joined #openstack-swift11:44
*** ukaynar_ has quit IRC11:44
*** ukaynar has quit IRC11:48
*** ukaynar has joined #openstack-swift11:49
*** ukaynar has quit IRC11:53
*** ukaynar has joined #openstack-swift11:53
mattoliveraukong: have you looked at the file? It might be coming back as a muli-part mime. So we extra data for mime boundaries etc.. I'd go check but am in bed :)11:57
*** ukaynar has quit IRC11:57
*** ukaynar has joined #openstack-swift11:58
*** ukaynar has quit IRC12:02
*** ukaynar has joined #openstack-swift12:02
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873612:05
kongmattoliverau: thanks for the response, the actual problem we are suffering is http://dpaste.com/0CD9FQZ12:05
kongafter multi-range download, the md5 check failed :-(12:06
*** ukaynar has quit IRC12:07
*** ukaynar_ has joined #openstack-swift12:07
*** ianychoi has quit IRC12:07
*** ukaynar_ has quit IRC12:12
*** ukaynar has joined #openstack-swift12:12
*** ukaynar has quit IRC12:16
*** ukaynar has joined #openstack-swift12:16
*** abhitechie has quit IRC12:19
*** ukaynar has quit IRC12:21
*** ukaynar has joined #openstack-swift12:21
acoleskong: that looks like this bug which should be fixed in latest release https://bugs.launchpad.net/python-swiftclient/+bug/164202112:22
openstackLaunchpad bug 1642021 in python-swiftclient "download with Range header yields error message" [Medium,Fix released]12:22
*** ukaynar_ has joined #openstack-swift12:26
*** ukaynar has quit IRC12:26
*** ukaynar has joined #openstack-swift12:30
*** ukaynar_ has quit IRC12:30
*** ukaynar has quit IRC12:35
*** ukaynar has joined #openstack-swift12:35
*** armaan has quit IRC12:39
*** ukaynar_ has joined #openstack-swift12:39
*** ukaynar has quit IRC12:40
*** ukaynar_ has quit IRC12:44
*** ukaynar has joined #openstack-swift12:44
*** ukaynar has quit IRC12:49
*** ukaynar has joined #openstack-swift12:49
*** ukaynar has quit IRC12:53
*** ukaynar has joined #openstack-swift12:53
*** ukaynar has quit IRC12:58
*** ukaynar has joined #openstack-swift12:58
*** ukaynar has quit IRC13:02
*** ukaynar has joined #openstack-swift13:03
*** ianychoi has joined #openstack-swift13:05
*** ukaynar has quit IRC13:07
*** ukaynar has joined #openstack-swift13:07
*** wes_dillingham has joined #openstack-swift13:09
*** ukaynar has quit IRC13:12
*** ukaynar has joined #openstack-swift13:12
*** janonymous has quit IRC13:12
*** ukaynar has quit IRC13:16
*** ukaynar_ has joined #openstack-swift13:17
*** mat128 has quit IRC13:17
*** guimaluf has quit IRC13:18
*** ukaynar_ has quit IRC13:21
*** ukaynar has joined #openstack-swift13:21
*** links has quit IRC13:22
*** links has joined #openstack-swift13:24
*** ukaynar has quit IRC13:26
*** ukaynar has joined #openstack-swift13:26
*** ukaynar has quit IRC13:30
*** ukaynar has joined #openstack-swift13:30
*** ukaynar has quit IRC13:35
*** ukaynar_ has joined #openstack-swift13:35
*** armaan has joined #openstack-swift13:38
*** ukaynar_ has quit IRC13:40
*** ukaynar has joined #openstack-swift13:40
*** oshritf has quit IRC13:44
*** oshritf has joined #openstack-swift13:44
*** ukaynar_ has joined #openstack-swift13:44
*** ukaynar has quit IRC13:44
*** ukaynar_ has quit IRC13:49
*** ukaynar has joined #openstack-swift13:49
*** links has quit IRC13:53
*** ukaynar has quit IRC13:53
*** ukaynar has joined #openstack-swift13:54
*** mabrams has joined #openstack-swift13:55
*** ukaynar has quit IRC13:58
*** ukaynar has joined #openstack-swift13:58
*** ukaynar has quit IRC14:03
*** ukaynar_ has joined #openstack-swift14:03
*** ukaynar_ has quit IRC14:07
*** ukaynar has joined #openstack-swift14:07
*** ukaynar has quit IRC14:12
*** ukaynar has joined #openstack-swift14:12
*** ukaynar has quit IRC14:16
*** ukaynar has joined #openstack-swift14:17
*** ukaynar_ has joined #openstack-swift14:21
*** ukaynar has quit IRC14:21
*** ukaynar_ has quit IRC14:26
*** ukaynar has joined #openstack-swift14:26
*** ukaynar has quit IRC14:30
*** ukaynar has joined #openstack-swift14:31
*** ukaynar has quit IRC14:35
*** ukaynar has joined #openstack-swift14:35
*** armaan has quit IRC14:37
*** ukaynar_ has joined #openstack-swift14:40
*** ukaynar has quit IRC14:40
*** ukaynar_ has quit IRC14:45
*** ukaynar has joined #openstack-swift14:45
*** ukaynar_ has joined #openstack-swift14:49
*** ukaynar has quit IRC14:49
*** ukaynar_ has quit IRC14:53
*** ukaynar has joined #openstack-swift14:54
*** mat128 has joined #openstack-swift14:55
*** ukaynar has quit IRC14:58
*** ukaynar has joined #openstack-swift14:58
*** armaan has joined #openstack-swift15:01
*** armaan has quit IRC15:03
*** ukaynar_ has joined #openstack-swift15:03
*** armaan has joined #openstack-swift15:03
*** ukaynar has quit IRC15:04
*** mabrams has quit IRC15:07
*** ukaynar_ has quit IRC15:08
*** ukaynar has joined #openstack-swift15:08
*** links has joined #openstack-swift15:11
*** ukaynar has quit IRC15:12
*** ukaynar has joined #openstack-swift15:12
*** baruna has quit IRC15:14
*** ukaynar has quit IRC15:17
*** ukaynar has joined #openstack-swift15:17
*** vint_bra has joined #openstack-swift15:19
*** ukaynar has quit IRC15:22
*** ukaynar_ has joined #openstack-swift15:22
*** ukaynar_ has quit IRC15:26
*** ukaynar has joined #openstack-swift15:26
*** ukaynar has quit IRC15:30
*** ukaynar has joined #openstack-swift15:31
*** ukaynar_ has joined #openstack-swift15:35
*** ukaynar has quit IRC15:36
*** klrmn has joined #openstack-swift15:39
*** ukaynar_ has quit IRC15:40
*** itlinux has joined #openstack-swift16:01
*** chsc has joined #openstack-swift16:37
*** chsc has joined #openstack-swift16:37
*** vint_bra has quit IRC16:39
*** ukaynar has joined #openstack-swift16:47
*** oshritf has quit IRC16:49
*** links has quit IRC17:00
*** psachin has quit IRC17:02
*** tesseract has quit IRC17:03
*** cbartz has quit IRC17:07
*** d0ugal has quit IRC17:12
*** SkyRocknRoll_ has joined #openstack-swift17:14
*** JimCheung has joined #openstack-swift17:16
*** vint_bra has joined #openstack-swift17:16
*** klrmn has quit IRC17:17
*** mat128 has quit IRC17:17
*** vint_bra has quit IRC17:24
*** gyee_ has joined #openstack-swift17:34
*** gkadam has quit IRC17:37
*** SkyRocknRoll_ has quit IRC17:40
timburkeidk, that swiftclient bug's mainly talking about if you include a `-H Range: bytes=X-Y` header on the cli17:51
*** SkyRocknRoll_ has joined #openstack-swift17:53
*** SkyRocknRoll_ has quit IRC18:01
timburkekong: fwiw, that swiftclient log tells us we made a request for the whole object, got a 200 (which told us it should be 4205802364 bytes), read 1096938176 bytes, then the connection dropped18:04
timburkedid another request for just the bytes starting from 1096938176, was told to expect 3108864188 (which together with the bytes we have gets us back to the original total size), but we can only read 1091629760 bytes before the connection dies18:04
timburkewe retry again, and again, and each time the invariant <range lower bound> + <response content length> == <original content length>, which is good18:05
timburkei suppose there's a chance we're not calculating the range lower-bound correctly? i'd be curious about the size of the downloaded file -- if that didn't match the expected size, it may point to a bug in swiftclient. if it *does*... maybe whatever caused the dropped connection also corrupted some in-flight data?18:05
timburkeon the curl result, i'm curious what extra output you'd get with a --verbose flag -- i'm guessing curl would give some sort of warning about not receiving as many bytes as it was expecting18:06
timburkei suppose that's what the -S was about... hadn't used that before... i might have to look into it some more...18:09
*** klrmn has joined #openstack-swift18:11
*** pcaruana has quit IRC18:11
*** JimCheung has quit IRC18:12
*** JimCheung has joined #openstack-swift18:13
*** mat128 has joined #openstack-swift18:13
*** SkyRocknRoll_ has joined #openstack-swift18:17
*** mvk has quit IRC18:17
*** samueldmq has quit IRC18:19
*** samueldmq has joined #openstack-swift18:19
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient master: Updated from global requirements  https://review.openstack.org/8925018:30
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873618:33
*** geaaru has quit IRC18:41
*** SkyRocknRoll_ has quit IRC18:46
*** itlinux has quit IRC18:54
*** SkyRocknRoll_ has joined #openstack-swift19:03
*** mvk has joined #openstack-swift19:06
*** d0ugal has joined #openstack-swift19:21
*** Sukhdev has joined #openstack-swift19:28
*** itlinux has joined #openstack-swift19:30
*** JimCheung has quit IRC19:51
*** JimCheung has joined #openstack-swift19:52
*** JimCheung has quit IRC19:56
*** flwang has quit IRC20:12
*** itlinux has quit IRC20:19
*** d0ugal_ has joined #openstack-swift20:25
*** flwang has joined #openstack-swift20:25
*** d0ugal has quit IRC20:26
*** JimCheung has joined #openstack-swift20:38
*** Sukhdev has quit IRC20:39
*** itlinux has joined #openstack-swift20:40
*** d0ugal_ has quit IRC20:40
*** d0ugal has joined #openstack-swift20:40
*** d0ugal has quit IRC20:40
*** d0ugal has joined #openstack-swift20:40
*** armaan has quit IRC20:40
*** JimCheung has quit IRC20:42
tdasilvano meeting today, right?20:50
*** wes_dillingham has quit IRC20:51
*** SkyRocknRoll_ has quit IRC20:52
*** d0ugal has quit IRC20:52
*** armaan has joined #openstack-swift20:55
*** itlinux has quit IRC21:00
*** oshritf has joined #openstack-swift21:01
*** spetersen has joined #openstack-swift21:04
*** JimCheung has joined #openstack-swift21:18
*** itlinux has joined #openstack-swift21:19
*** armaan has quit IRC21:31
*** threestrands has joined #openstack-swift21:32
*** threestrands has quit IRC21:32
*** threestrands has joined #openstack-swift21:32
*** oshritf has quit IRC21:33
spetersenWe replaced full drives with larger ones in just one zone in order to help alleviate a situation with full disks.  After initiating the rebalance we have not been able to find certain objects.  We know they exist and we can find the "missing" objects using the old object.ring.gz and swift-get-nodes.  QUESTION: Will replication eventually move the "missing" objects into the proper place or do we need to do21:33
spetersensomething manually?21:33
claygthe other replicas should be able to service the READ requests... unless I guess if the other replica(s?) was on the devices you pulled out to make room for the larger ones?21:37
claygspetersen: the replicators should be working to repair all assigned partition replicas to full health - you just distribute the new rings and the replicators will do the work - but depending on the tuning and available io it could take a while... you might want to monitor it closely.21:39
*** JimCheung has quit IRC21:40
claygsomething like https://gist.github.com/clayg/5d3b3ca13dea15f6a48efaa3cea92d7d might give you some additional insight to whats going on with the partition movement21:41
*** itlinux has quit IRC21:42
kongtimburke: the downloaded file size is correct, no error shown for curl :-(21:45
kongacoles: thanks for the bug link, but i don't think it's the same issue with us. We are downloading the whole object, and swift client retries for several times (because of a known issue of our nginx) using multi-range request. The md5 check for the downloaded file failed although the file size is expected.21:48
kongcan anyone help me please?21:49
spetersenThanks Clayg!  To clarify, the other replicas do exist on different zones and a different partition number, we can download them using the old ring file, the object exists in zone 2 and 3 but not 1 because we replaced those drives with new larger ones (which is expected).  If we use the current ring the locations provided by "swift-get-nodes -a" do not contain the object.  Do you think they will "magically"21:59
spetersenappear in the new locations in the future?21:59
spetersenThanks Clayg!  To clarify, the other replicas do exist on different zones and a different partition number, we can download them using the old ring file, the object exists in zone 2 and 3 but not 1 because we replaced those drives with new larger ones (which is expected).  If we use the current ring, the locations provided by "swift-get-nodes -a" do not contain the object.  Do you think they will "magically"22:00
spetersenappear in the new locations in the future?22:00
spetersenI think this may be similar to this issue you commented on back in 2013, https://answers.launchpad.net/swift/+question/23197222:01
spetersenThat old article is regarding missing accounts where as ours is regarding objects.22:02
claygsounds like it - that's what rebalance does... it takes one of the replicas of a partition and assigns it to a different device that has more room.  From the proxy the request to the object will find the other object from the other replicas (in zone 2 & 3) while the one in zone 1 is being replicated to the new host... https://www.youtube.com/watch?v=ger20cqOypE&feature=youtu.be&t=114022:02
spetersenbasically what we are noticing is that Swift is not seeing the replicas (even though they are there) We were able to find them using the old ring, however using the new ring if you try to get the file it will 404 because it thinks the copies should be in partition 'a' when they are in partition 'b' we looked through all of the handoff locations as well and where the file is actually located isn't in there22:11
speterseneither22:11
*** itlinux has joined #openstack-swift22:11
claygso a rebalance shouldn't *change* the partition of a given object - replication won't move an object from one partition to different one - replication/rebalance only moves partitions from node to another22:17
spetersenok, well I guess we have a problem then because the newly generated ring file is stating the objects live on a different partition number than the old ring file.22:18
claygspetersen: yeah that's pretty weird22:19
claygthat can happen if you change your hash_path_suffix/prefix in swift.conf - or maybe also if you change the part power22:19
claygbut you *should* be using the same old builder you used originally, adding the new devices - and then rebalance22:19
spetersenI made a mistake, the partition number is the same using the old ring and the current ring.22:20
claygoh that's good news!22:20
claygso maybe swift-get-nodes -p <part#> from old and new ring - try to figure out which replica moved and make sure the other replicas are still on the same nodes22:21
*** SkyRocknRoll has quit IRC22:22
*** itlinux has quit IRC22:23
spetersenMy mistake, the only difference is which drive it thinks the partition lives on.22:23
*** rcernin has joined #openstack-swift22:23
claygok, that sounds good - but again - only one of the replicas of the partition should have moved22:23
*** SkyRocknRoll has joined #openstack-swift22:25
spetersenDoes it make a difference that we also changed the weight on some drives on the other nodes?22:28
claygno - that's great - a single rebalance would still only move one replica22:32
clayghave you been able to verify if *some* of the devices a given partition is assigned were the same in the old ring?22:32
spetersenCan I paste the output of swift-get-nodes -p for the old and the current ring?22:34
claygsure!22:34
*** mvk has quit IRC22:35
spetersen[root@swift-r1z2n1 swift]# swift-get-nodes /tmp/object.ring.gz -p 22522:43
spetersenAccount  None22:43
spetersenContainerNone22:43
spetersenObject   None22:43
spetersenPartition22522:43
spetersenHash     None22:43
spetersenServer:Port Device192.168.99.106:6000 r1z4n1-d322:43
spetersenServer:Port Device192.168.99.105:6000 swift-r1z3n1-d922:43
spetersenServer:Port Device192.168.99.103:6000 swift-r1z2n1-d1922:43
spetersenServer:Port Device192.168.99.102:6000 r1z1n1-d26 [Handoff]22:44
*** itlinux has joined #openstack-swift22:44
spetersenServer:Port Device192.168.99.106:6000 r1z4n1-d6 [Handoff]22:44
spetersenServer:Port Device192.168.99.103:6000 r1z2n1-d5 [Handoff]22:44
spetersencurl -g -I -XHEAD "http://192.168.99.106:6000/r1z4n1-d3/225/None"22:44
spetersencurl -g -I -XHEAD "http://192.168.99.105:6000/swift-r1z3n1-d9/225/None"22:44
spetersencurl -g -I -XHEAD "http://192.168.99.103:6000/swift-r1z2n1-d19/225/None"22:44
spetersencurl -g -I -XHEAD "http://192.168.99.102:6000/r1z1n1-d26/225/None" # [Handoff]22:44
spetersencurl -g -I -XHEAD "http://192.168.99.106:6000/r1z4n1-d6/225/None" # [Handoff]22:44
spetersencurl -g -I -XHEAD "http://192.168.99.103:6000/r1z2n1-d5/225/None" # [Handoff]22:44
spetersenUse your own device location of servers:22:44
spetersensuch as "export DEVICE=/srv/node"22:44
spetersenssh 192.168.99.106 "ls -lah ${DEVICE:-/srv/node*}/r1z4n1-d3/objects/225"22:44
spetersenssh 192.168.99.105 "ls -lah ${DEVICE:-/srv/node*}/swift-r1z3n1-d9/objects/225"22:44
spetersenssh 192.168.99.103 "ls -lah ${DEVICE:-/srv/node*}/swift-r1z2n1-d19/objects/225"22:44
spetersenssh 192.168.99.102 "ls -lah ${DEVICE:-/srv/node*}/r1z1n1-d26/objects/225" # [Handoff]22:44
spetersenssh 192.168.99.106 "ls -lah ${DEVICE:-/srv/node*}/r1z4n1-d6/objects/225" # [Handoff]22:44
spetersenssh 192.168.99.103 "ls -lah ${DEVICE:-/srv/node*}/r1z2n1-d5/objects/225" # [Handoff]22:44
spetersennote: `/srv/node*` is used as default value of `devices`, the real value is set in the config file on each storage node.22:44
spetersen[root@swift-r1z2n1 swift]#22:44
spetersenAnd the new ring22:44
spetersen[root@swift-r1z2n1 swift]# swift-get-nodes object.ring.gz -p 22522:44
spetersenAccount  None22:44
spetersenContainerNone22:44
spetersenObject   None22:44
spetersenPartition22522:44
spetersenHash     None22:44
spetersenServer:Port Device192.168.99.106:6000 r1z4n1-d322:44
spetersenServer:Port Device192.168.99.105:6000 r1z3n1-d2222:44
spetersenServer:Port Device192.168.99.102:6000 r1z1n1-d2822:45
spetersenServer:Port Device192.168.99.103:6000 r1z2n1-d26 [Handoff]22:45
spetersenServer:Port Device192.168.99.106:6000 r1z4n1-d6 [Handoff]22:45
spetersenServer:Port Device192.168.99.102:6000 r1z1n1-d26 [Handoff]22:45
spetersencurl -g -I -XHEAD "http://192.168.99.106:6000/r1z4n1-d3/225/None"22:45
spetersencurl -g -I -XHEAD "http://192.168.99.105:6000/r1z3n1-d22/225/None"22:45
spetersencurl -g -I -XHEAD "http://192.168.99.102:6000/r1z1n1-d28/225/None"22:45
spetersencurl -g -I -XHEAD "http://192.168.99.103:6000/r1z2n1-d26/225/None" # [Handoff]22:45
spetersencurl -g -I -XHEAD "http://192.168.99.106:6000/r1z4n1-d6/225/None" # [Handoff]22:45
spetersencurl -g -I -XHEAD "http://192.168.99.102:6000/r1z1n1-d26/225/None" # [Handoff]22:45
spetersenUse your own device location of servers:22:45
spetersensuch as "export DEVICE=/srv/node"22:45
spetersenssh 192.168.99.106 "ls -lah ${DEVICE:-/srv/node*}/r1z4n1-d3/objects/225"22:45
spetersenssh 192.168.99.105 "ls -lah ${DEVICE:-/srv/node*}/r1z3n1-d22/objects/225"22:45
spetersenssh 192.168.99.102 "ls -lah ${DEVICE:-/srv/node*}/r1z1n1-d28/objects/225"22:45
spetersenssh 192.168.99.103 "ls -lah ${DEVICE:-/srv/node*}/r1z2n1-d26/objects/225" # [Handoff]22:45
spetersenssh 192.168.99.106 "ls -lah ${DEVICE:-/srv/node*}/r1z4n1-d6/objects/225" # [Handoff]22:45
spetersenssh 192.168.99.102 "ls -lah ${DEVICE:-/srv/node*}/r1z1n1-d26/objects/225" # [Handoff]22:45
spetersennote: `/srv/node*` is used as default value of `devices`, the real value is set in the config file on each storage node.22:45
spetersen[root@swift-r1z2n1 swift]#22:45
*** d0ugal has joined #openstack-swift22:51
*** mat128 has quit IRC22:54
claygspetersen: use a gist or pastebin next time please :D23:01
claygspetersen: it looks like both rings think the partition was/in on r1z4n1-d323:02
claygyou might confirm that - if it's true the proxy should be able to find any objects from that device23:02
claygbut it also looks like 2 of the 3 replicas of the part changed between old and new ring - that shouldn't happen with a single rebalance - or even multiple rebalanace in a short period if you have a sane min_part_hours23:03
*** wes_dillingham has joined #openstack-swift23:12
spetersenwell, I saw that as well, you would think the object would exist in r1z4n1-d3 but for whatever reason it does not live on that device.23:15
*** itlinux has quit IRC23:15
spetersenWe did find the objects with the old ring, here swift-r1z3n1-d9 and here swift-r1z2n1-d1923:16
*** glyn has joined #openstack-swift23:29
*** spetersen has quit IRC23:30
clayginteresting...23:30
claygyeah so the replicators on those nodes should be wanting to replicate out to the correct primary locations23:31
claygyou can turn up the replicator concurrency - make sure you rsync has enough max connections - then maybe turn on handoffs_first mode23:31
claygtuning is a thing23:31
glynhi folks, just wondering if anyone can provide any input on whether there is a point at which the number of objects in a single container starts to have negative impacts on performance or reliability?23:31
claygit's not so much the number as how fast you're doing updates - a container that adds 10K and removes 10K objects every day is way worse than a container with 10M objects that isn't having any more new data written to it23:33
*** kei_yama has joined #openstack-swift23:34
claygthat says - shoot for 4M - 10M is ok, 100M is bad - but it mostly effects how quickly the consistency engine can cycle - which can lead to annoying problems with like... some object getting added but not showing up in the container listing for a long while depending... it can get to a tipping point where it never catches up if you just poor 1K/s updates into it without ever stopping.  That's where the rate23:35
clayglimit middleware came from23:35
glynclayg: thanks for that. Is this included in any of the official documentation?23:36
claygnah, it depends a lot on the hardware and the usage patterns and expectations... I think everyone that uses swift has their own opinions about what's reasonable.23:37
*** ianychoi has quit IRC23:37
glynah, ok23:37
claygmattoliverau: will tell you just to wait for the new deep containers feature he's working on - it's all pivot tables and magic23:38
claygi guess timburke and acoles are helping ;)23:38
*** chsc has quit IRC23:38
*** abhitechie has joined #openstack-swift23:40
mattoliverauyeah, soon it wont be an issue cause we'll shard up the container databases so they never get too big for the backend. And the world will be a better place23:40
*** JimCheung has joined #openstack-swift23:40
mattoliverauand clayg's right, it's all pivots and ranges all the way down :P23:41
*** JimCheung has quit IRC23:45

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