Monday, 2015-08-31

homattoliverau: morning!00:02
*** m_kazuhiro has joined #openstack-swift00:29
*** haomaiwang has quit IRC00:35
*** nakagawamsa has joined #openstack-swift00:48
*** kota_ has joined #openstack-swift00:52
*** ChanServ sets mode: +v kota_00:52
kota_good morning00:53
*** chlong has joined #openstack-swift00:55
mattoliveraukota_: morning00:59
kota_mattoliverau: morning :)00:59
*** wbhuber_ has joined #openstack-swift01:20
hokota_: morning!01:21
*** wbhuber has quit IRC01:22
*** marzif__ has joined #openstack-swift01:33
*** marzif_ has quit IRC01:37
*** haomaiwang has joined #openstack-swift01:40
*** aix_ has joined #openstack-swift01:41
*** aix has quit IRC01:42
*** chlong has quit IRC01:49
*** kota_ has quit IRC02:04
*** Shihta has joined #openstack-swift02:15
*** Shihta has left #openstack-swift02:15
*** kota_ has joined #openstack-swift02:24
*** ChanServ sets mode: +v kota_02:24
openstackgerritpaul luse proposed openstack/swift: Better error handling for EC PUT path when client goes away  https://review.openstack.org/21133802:42
pelusemorning guys02:46
pelusekota_, mattoliverau if you have a chance during my evening here could you take a look at patch 21133802:46
patchbotpeluse: https://review.openstack.org/#/c/211338/02:46
kota_peluse: morning and thnaks for approving my patch.02:47
peluseit keeps a lot of ugly 503s out of the logs during perf runs (heavy loads) which causes our benchmark team a lot of heartburn :)02:47
pelusekota_, welcome!  I've been waiting for that one, good stuff02:47
mattoliveraupeluse: I'll try at take a look beofre I end for the day :)02:47
pelusethanks!  its pretty small/simple02:47
pelusefamous last words....02:48
kota_mattoliverau, peluse: me too.02:48
pelusethanks!!  I'm outta here....02:48
mattoliveraupeluse: enjoy the rest of your weekend02:48
*** jrichli has quit IRC02:57
*** haomaiwang has quit IRC03:03
*** haomaiw__ has joined #openstack-swift03:03
*** jroll has quit IRC03:26
*** jroll has joined #openstack-swift03:31
*** I has joined #openstack-swift03:35
*** I is now known as Guest2505903:36
*** ppai has joined #openstack-swift03:36
*** links has joined #openstack-swift03:40
*** Guest25059 has quit IRC03:49
*** haigang has joined #openstack-swift03:49
openstackgerritJohn Dickinson proposed openstack/swift: Updated CHANGELOG, AUTHORS, and .mailmap for 2.4.0 release.  https://review.openstack.org/21868103:58
notmynamekota_: thanks. fixed ^^03:58
kota_notmyname: you're welocome^^04:00
*** hrou has joined #openstack-swift04:06
*** kei_yama has quit IRC04:07
*** kei_yama_ has joined #openstack-swift04:07
*** km_ has joined #openstack-swift04:09
*** km has quit IRC04:09
*** _hrou_ has joined #openstack-swift04:40
*** hrou has quit IRC04:41
*** _hrou_ has quit IRC04:47
*** SkyRocknRoll has joined #openstack-swift04:47
*** ig0r__ has joined #openstack-swift04:58
*** ig0r_ has quit IRC04:59
*** haigang has quit IRC05:23
*** dimasot has joined #openstack-swift05:25
*** proteusguy_ has quit IRC05:34
*** haigang has joined #openstack-swift05:47
*** proteusguy_ has joined #openstack-swift05:47
openstackgerritMatthew Oliver proposed openstack/swift-specs: Large containers (Sharding) - Pivot/Split Tree  https://review.openstack.org/21873806:12
*** pushkarajthorat has joined #openstack-swift06:21
*** trifon has joined #openstack-swift06:23
*** haigang has quit IRC06:27
*** haigang has joined #openstack-swift06:28
*** haigang has quit IRC06:29
*** mahatic has joined #openstack-swift06:36
*** haigang has joined #openstack-swift06:36
*** SkyRocknRoll has quit IRC06:54
*** trifon has quit IRC07:03
*** pushkarajthorat has quit IRC07:04
*** kei_yama_ has quit IRC07:13
*** kei_yama has joined #openstack-swift07:13
*** rledisez has joined #openstack-swift07:14
*** pushkarajthorat has joined #openstack-swift07:14
*** SkyRocknRoll has joined #openstack-swift07:19
*** marcusvrn_ has quit IRC07:25
*** pushkarajthorat has quit IRC07:31
*** pushkarajthorat has joined #openstack-swift07:32
*** geaaru has joined #openstack-swift07:40
*** baojg has joined #openstack-swift07:40
*** pushkarajthorat has left #openstack-swift07:41
*** SkyRocknRoll_ has joined #openstack-swift08:13
*** jistr has joined #openstack-swift08:15
*** aix_ has quit IRC08:32
*** aix has joined #openstack-swift08:33
*** haigang has quit IRC08:44
*** haigang has joined #openstack-swift08:44
*** haigang has quit IRC08:50
*** haigang has joined #openstack-swift08:52
dimasothello all08:58
dimasotI found at proxy the next ccomment "import swiftclient08:59
dimasotimport time08:59
dimasotconn = swiftclient.client.Connection(authurl='http://159.8.75.222:5000/v2.0',user="swift", key="passw0rd",tenant_name="service",auth_version='2')08:59
dimasothttp_conn = conn.http_connection()08:59
dimasotprint conn.put_object(container='test', obj='test.test6', contents="test6")08:59
dimasotprint http_conn.getresponse()08:59
dimasottime.sleep(5)08:59
dimasotprint conn.put_object(container='test', obj='test.test6', contents="test6")08:59
dimasotprint http_conn.getresponse()08:59
dimasotconn.close()08:59
dimasotsorry wrong copy/past08:59
*** sanchitmalhotra has joined #openstack-swift09:02
dimasotI fount teh following comment # Sending an etag with if-none-match isn't currently supported09:02
dimasotat swift/proxy/controllers/obj.py09:03
dimasotdoes it means that 100 continue does supported?09:03
*** sanchitmalhotra1 has quit IRC09:04
dimasotis there an open bug on this issue?09:05
*** chenhuayi has joined #openstack-swift09:13
*** haigang has quit IRC09:20
*** baojg has quit IRC09:23
*** sanchitmalhotra1 has joined #openstack-swift09:30
*** sanchitmalhotra has quit IRC09:33
*** haigang has joined #openstack-swift09:33
*** ig0r_ has joined #openstack-swift09:37
*** marzif__ has quit IRC09:38
*** baojg has joined #openstack-swift09:38
*** marzif__ has joined #openstack-swift09:38
*** ig0r__ has quit IRC09:39
*** aix has quit IRC09:49
*** baojg has quit IRC10:00
*** mahatic has quit IRC10:00
*** marzif__ has quit IRC10:12
*** haigang has quit IRC10:14
*** haigang has joined #openstack-swift10:15
*** aix has joined #openstack-swift10:18
*** sanchitmalhotra has joined #openstack-swift10:30
*** sanchitmalhotra1 has quit IRC10:32
*** m_kazuhiro has quit IRC10:35
*** m_kazuhiro has joined #openstack-swift10:36
*** marzif__ has joined #openstack-swift10:47
*** sanchitmalhotra1 has joined #openstack-swift10:56
*** sanchitmalhotra has quit IRC10:58
*** mahatic has joined #openstack-swift11:09
*** sanchitmalhotra has joined #openstack-swift11:12
*** sanchitmalhotra1 has quit IRC11:14
*** haomaiw__ has quit IRC11:15
*** sanchitmalhotra has quit IRC11:18
*** nakagawamsa has quit IRC11:20
*** sanchitmalhotra has joined #openstack-swift11:22
*** _hrou_ has joined #openstack-swift11:27
*** _hrou_ has quit IRC11:36
*** sanchitmalhotra has quit IRC11:38
*** marzif__ has quit IRC11:42
*** openstackgerrit has quit IRC11:46
*** openstackgerrit has joined #openstack-swift11:47
*** kairo has joined #openstack-swift11:58
*** kairo has quit IRC12:00
*** kairo has joined #openstack-swift12:01
*** km_ has quit IRC12:02
*** ppai_ has joined #openstack-swift12:02
*** ppai has quit IRC12:04
openstackgerritMerged openstack/swift: Fix EC GET backend stream iteration state  https://review.openstack.org/19904312:05
*** m_kazuhi_ has joined #openstack-swift12:05
*** m_kazuhiro has quit IRC12:05
*** petertr7_away is now known as petertr712:09
*** kei_yama has quit IRC12:21
*** wbhuber_ has quit IRC12:27
*** haomaiwa_ has joined #openstack-swift12:37
*** ccavanna_ has quit IRC12:43
*** m_kazuhi_ has quit IRC12:43
*** annegentle has joined #openstack-swift12:44
*** ppai_ has quit IRC12:50
*** kota_ has quit IRC12:53
*** dimasot has quit IRC12:55
*** SkyRocknRoll_ has quit IRC13:01
*** AndreiaKumpera has joined #openstack-swift13:04
*** dustins has joined #openstack-swift13:04
*** CR7_ has joined #openstack-swift13:05
*** wbhuber has joined #openstack-swift13:21
*** SkyRocknRoll_ has joined #openstack-swift13:23
*** _hrou_ has joined #openstack-swift13:28
*** trifon has joined #openstack-swift13:30
*** links has quit IRC13:30
*** SkyRocknRoll_ has quit IRC13:32
*** esker has quit IRC13:47
*** esker has joined #openstack-swift13:48
*** bill_az has joined #openstack-swift13:49
*** annegentle has quit IRC13:49
*** breitz has quit IRC13:50
*** breitz has joined #openstack-swift13:50
*** jkugel has joined #openstack-swift13:51
*** janonymous has joined #openstack-swift13:58
*** trifon has quit IRC14:03
*** Kennan has quit IRC14:03
*** Kennan2 has joined #openstack-swift14:03
*** jroll has quit IRC14:09
*** jroll has joined #openstack-swift14:09
*** annegentle has joined #openstack-swift14:19
*** CR7_ has quit IRC14:24
*** ccavanna has joined #openstack-swift14:24
*** jlhinson has joined #openstack-swift14:30
*** jrichli has joined #openstack-swift14:37
*** jkremer has joined #openstack-swift14:48
*** petertr7 is now known as petertr7_away14:51
*** jistr is now known as jistr|call14:57
*** nexusz99 has joined #openstack-swift14:57
*** petertr7_away is now known as petertr714:59
*** lcurtis has joined #openstack-swift15:00
*** gyee has joined #openstack-swift15:07
*** dimasot has joined #openstack-swift15:10
*** vinsh has joined #openstack-swift15:16
*** nexusz99 has quit IRC15:21
mahaticgood evening15:23
jrichlimahatic: good evening.  How are you?15:24
*** wshao_ has joined #openstack-swift15:24
mahaticjrichli: Morning! good now :) thanks15:25
*** [1]dimasot has joined #openstack-swift15:26
jrichlimahatic: good to hear you are feeling better.15:28
*** dimasot has quit IRC15:28
*** [1]dimasot is now known as dimasot15:28
*** minwoob has joined #openstack-swift15:29
janonymousjrichli mahatic : Texas cowboys :)15:29
*** haomaiwa_ has quit IRC15:29
mahaticjrichli: :) how is it going? Saw your progress on COPY (on trello), cool!15:31
mahaticjamielennox: I'm no texas cowboy :D15:31
*** david-ly_ has joined #openstack-swift15:31
mahaticjanonymous: ^15:31
janonymoushehe :)15:31
janonymousyou gud ?15:32
mahaticyup, thanks15:32
*** david-ly_ is now known as david-lyle_15:33
*** [1]dimasot has joined #openstack-swift15:33
jrichlimahatic: yes, I was happy to get a little farther.  but there are still things to test and figure out.15:33
*** david-lyle has quit IRC15:33
mahaticyeah, true15:33
*** david-lyle_ is now known as david-lyle15:35
*** hseipp has joined #openstack-swift15:36
*** dimasot has quit IRC15:36
*** [1]dimasot is now known as dimasot15:36
*** hseipp has quit IRC15:36
*** hseipp has joined #openstack-swift15:37
*** trifon has joined #openstack-swift15:41
openstackgerritjanonymous proposed openstack/swift: pep8 fix: assertEquals -> assertEqual  https://review.openstack.org/20964515:43
*** zaitcev has joined #openstack-swift15:48
*** ChanServ sets mode: +v zaitcev15:48
*** jistr|call is now known as jistr15:53
*** annegentle has quit IRC15:59
*** wshao_ has quit IRC15:59
*** chsc has joined #openstack-swift16:03
dimasothi all16:06
dimasotI have some problems with 100-continue16:07
dimasotI saw that there was some old bug that should be resolved that relates to my issue https://bugs.launchpad.net/openstack-api-site/+bug/130167716:07
openstackLaunchpad bug 1301677 in openstack-api-site " Add "If-None-Match: *" support to PUT" [Medium,Fix released] - Assigned to Diane Fleming (diane-fleming)16:07
*** rledisez has quit IRC16:08
*** mfalatic has joined #openstack-swift16:09
dimasotbut it looks like that feature still does not works for me16:10
*** jistr has quit IRC16:13
zaitcevI don't know if I have the time to look properly, but what is the actual symptom? Do you get 412 or not?16:17
zaitcevIf not, then what happens? It hangs waiting for the body, sends 100-continue instead, or what?16:18
zaitcev(presuming the object already exists)16:18
*** lyrrad has joined #openstack-swift16:20
*** jlhinson_ has joined #openstack-swift16:22
*** jlhinson has quit IRC16:22
openstackgerritjanonymous proposed openstack/swift: pep8 fix: assertNotEquals -> assertNotEqual  https://review.openstack.org/21893716:23
*** mahatic has quit IRC16:29
notmynamegood morning16:33
*** lifeless has quit IRC16:34
*** annegentle has joined #openstack-swift16:35
notmynamehmm... interesting https://review.openstack.org/#/c/217710/16:36
*** mahatic has joined #openstack-swift16:37
openstackgerritJohn Dickinson proposed openstack/swift: Updated CHANGELOG, AUTHORS, and .mailmap for 2.4.0 release.  https://review.openstack.org/21868116:40
notmynamepeluse: around?16:40
*** rjaiswal has joined #openstack-swift16:41
*** lifeless has joined #openstack-swift16:41
*** _hrou_ has quit IRC16:47
*** mahatic has quit IRC16:56
openstackgerritJohn Dickinson proposed openstack/swift: Updated CHANGELOG, AUTHORS, and .mailmap for 2.4.0 release.  https://review.openstack.org/21868116:57
*** geaaru has quit IRC17:16
*** aix has quit IRC17:21
*** jlhinson_ has quit IRC17:32
*** hseipp has quit IRC17:34
*** SkyRocknRoll has quit IRC17:34
*** [1]dimasot has joined #openstack-swift17:35
*** dimasot has quit IRC17:37
*** [1]dimasot is now known as dimasot17:37
*** janonymous has quit IRC17:39
torgomaticmattoliverau: interesting; what are the RPC ops folks going to do with the ring analyzer?17:42
*** ig0r__ has joined #openstack-swift17:43
*** CaioBrentano has joined #openstack-swift17:44
* torgomatic wrote it primarily for use as a code-review-assistance tool17:45
*** ig0r_ has quit IRC17:46
dimasotzaitcev: I uploaded the same file twice by swiftclient command:  print conn.put_object(container='test', obj='100.test', contents=f, headers = {'if-none-match':"*","Expect": "100-continue"})17:47
dimasotwhere f is the file heandler17:47
dimasotthe first uploaded succed and the second failed with [Errno 32] Broken pipe17:48
dimasotthe file is big >900MB17:48
*** aix has joined #openstack-swift17:48
dimasotwhen instead the file I use some short srting as a content the first succed the second failed as expected with 412 and others failed with 405 even it I try to upload new objects17:50
dimasotI tried it for 4 uploads in a line17:50
openstackgerritJohn Dickinson proposed openstack/swift: Updated CHANGELOG, AUTHORS, and .mailmap for 2.4.0 release.  https://review.openstack.org/21868117:53
claygohai17:57
claygjrichli: yeah the footer encryption sounds like maybe the wonky memcache footer stuff?  Like maybe in the copy the name change is causing the memcace lookup for the footers to not do the right thing?17:58
jrichliclayg: im in a call, but will rely in a min18:01
*** panbalag has joined #openstack-swift18:02
*** panbalag has left #openstack-swift18:02
*** chenhuayi has quit IRC18:08
*** dimasot has quit IRC18:14
*** dimasot has joined #openstack-swift18:15
*** petertr7 is now known as petertr7_away18:23
*** petertr7_away is now known as petertr718:25
*** mvandijk has joined #openstack-swift18:29
*** [1]dimasot has joined #openstack-swift18:29
*** dimasot has quit IRC18:33
*** gyee has quit IRC18:33
*** [1]dimasot is now known as dimasot18:33
jrichliclayg: I wasn't aware of a name change.  I know the object path will change for versioning, but I was thinking the PATH_INFO was the same in this case.  But I will do some debugging in fake_footers to see whats happening.18:40
jrichliclayg: I was still curious what part of the system is failing to set user-metadata because the etag is binary data18:40
*** panbalag has joined #openstack-swift18:41
*** ig0r__ has quit IRC18:48
openstackgerritMichael Barton proposed openstack/swift: go: replicator fix  https://review.openstack.org/21898418:55
*** jlhinson has joined #openstack-swift18:59
pelusehey I'm switching from windows to os/x (finally), anyone have a favorite IRC client they swear by?  Or any other tools I would be stupid not to check out?19:07
*** eranrom has joined #openstack-swift19:11
*** hrou has joined #openstack-swift19:12
*** aerwin has joined #openstack-swift19:17
vinshpeluse: I settled on LimeChat.19:21
vinshThis was when I went ubuntu->mac os for primary laptop.19:21
vinsh100% of the day is spent working ssh'd into all linux nodes :)19:22
pelusevinsh, thanks I'll check it out.  I've been on a mac for years but stuck w/windows spending most of the day ssh'd into linux so go figure... spilled water on my system and had to get a new one so figured I'd ditch one OS :)19:27
vinsh:)19:27
vinshthe pluses about my mac outweigh the minuses.  But thats for a whole nother channel ;)19:28
*** petertr7 is now known as petertr7_away19:28
*** eranrom has quit IRC19:45
*** petertr7_away is now known as petertr719:48
dimasothi, when I am trying to use if-none-match and continue-100 headers for a big enought objects I got [Errno 32] Broken pipe instead responce 41219:51
dimasotbig enought is bigger then 1 MB19:51
*** DericHorn-HP has joined #openstack-swift19:52
dimasotin addition for small objects I got 412 for the first repetition and then I got 405 for a while - even for new objects19:52
dimasotis it a known issue? or should I open a bug related to this issue? should it be a single bug that describes both behaviours or one bug per issue?19:54
dimasotin addition to use it for contaiiner_sync purpose we need to extend it to support eTag also because 'if-none-math:*' would not be enought19:55
claygisn't 405 method not allowed?19:56
clayg409 would be timestamp conflict - but I think that's translated to a 20219:56
dimasotyep, this wa svery strange to me too to get such a responce19:56
claygreally the x-if-match isn't quite as good as the timestamp match - just because the body matches doesn't mean the metadata does - i'm not sure if the symantics should keep a request from syncing "mearly" for the same etag - only timestamp will do (I believe)19:57
dimasotyes, today when I am suncing the same object by container_sync I see 409 at object server and 202 at proxy19:57
claygwell that part sounds right19:57
dimasotbut at that case I move the smae object again over th ewire19:57
claygdimasot: I think the issue may come down to pipelining19:58
claygdimasot: torgomatic and I were discussing this just this morning (related to a ssync change) - I think if .getexpect doesn't give you back 100 you have to tear down the connection and make a new one before you can send another request19:58
dimasotI see19:59
claygit sucks... but I'm not sure rfc 2616 allows another option - and almost cirtainly eventlet.wsgi.server is not going to accept a piplined request behind a 4XX on a request that was supposed to include a body19:59
dimasotso it resolves teh 405 issue19:59
dimasotbut what about [Errno 32] Broken pipe instead 4112?20:00
claygdimasot: yeah I suppose if it's reads some random amount of content-length off the wire and the next line is the middle of something else... it would be some kind "wtf is this request" response?20:00
claygdimasot: which end is finding the closed socket?  the client maybe?  some sort of timeout waiting at getexpect perhaps?20:00
*** david-lyle has quit IRC20:01
dimasotI uploaded the same object twice with 60 seconds delay between the uploads20:02
dimasotif the seconf one was without if-none-match header both of then was successful20:02
claygdimasot: seperate connections?20:02
dimasotbut if I add the if-non-match header to the second one I got [Errno 32] Broken pipe20:02
claygdimasot: well you definately need to send the x-timestamp if you're not going to send if-match20:03
dimasotthe same one, I can try the separate connection also20:03
openstackgerritJoel Wright proposed openstack/python-swiftclient: Log and report trace on service operation fails  https://review.openstack.org/17169220:03
claygdimasot: yeah that doesn't make much sense - i don't think I see why if-none-match would cause the server to shutdown the connection...20:04
claygdimasot: I do think the server should not process the request - but it might should eat the bytes if the client tries to send them20:04
dimasotso to summarize you suggest to use a saparate connection for each upload and then you expect I will get 412 regardless to the object size20:04
claygdimasot: well - I just think that if getexpect returns anything besides 100 you need to close the connection before you can try sending the next object - as long as getexpect is returning 100 i think you can (should?) keep using the same connection20:05
dimasotthe good thing was that I did not see network trafic for the second request (when I use if-none-match)20:05
*** david-lyle has joined #openstack-swift20:06
dimasotok, I see20:06
notmynamepeluse: I also use LimeChat (and I like it)20:06
*** petertr7 is now known as petertr7_away20:06
dimasotand now related to extendig if-none-match by eTag20:06
*** biyiklioglu has joined #openstack-swift20:07
dimasotit looks like proxy kills all the request where if-none-match != *20:07
dimasotbut the object server supports both * and eTag20:08
dimasotso it looks like allowing of eTag bypassing at proxy will resolve this eTag related issue, or I miss something?20:09
claygdimasot: I don't think i follow your explination - nor do I think the proxy should be closing the connection - I think if you're pipling with expect-100 continue things will break20:10
clayg"but the object server supports both * and eTag" < I don't know what that means20:10
clayg"allowing of eTag bypassing at proxy" < I don't know what that means20:10
dimasotobject server returns 412 for both cases: if-none-match == * or if-none-match == eTag of stored object20:11
dimasothttps://github.com/openstack/swift/blob/master/swift/obj/server.py#L55120:12
claygdimasot: if you're doing container_sync stuff don't use if-none-match - x-timestamp is the right way to get a expect-100 request to bail early if the object has already been sent20:12
dimasotbut proxy failes all the request with if-none-match != *20:13
dimasothttps://github.com/openstack/swift/blob/master/swift/proxy/controllers/obj.py#L67720:13
dimasotso today if I set if-none-math to any value except * I will get 400 responce20:14
claygdimasot: that's true20:14
claygdimasot: but don't use if-none-match for contaienr_sync - use x-timestamp20:14
dimasotbut for container_sync we want to avoid movig the same data over wire multiple times on one hand, but on another we want to sync between the containers and copy the latest version of object20:15
dimasotbut at today's implementation I already use x-timestamp20:16
claygdimasot: well I don't think the existing if-match support for PUT will be sufficient to avoid the former - but to avoid syncing an object twice x-timestamp would be near ideal20:16
dimasotbut it does not protect me from moving object data between container server to remote proxy server20:16
claygdimasot: I'm not sure if "todays" version supports 100-continue correctly tho20:17
dimasotit just saves teh proxy to object network (at remote cluster)20:17
dimasotI see20:17
claygdimasot: yeah but I think that's mostly in how the client is handling 100-continue - not so much if-match vs. x-timestamp20:17
dimasotso you suggest to use 100-continue with x-timestamp20:17
claygdimasot: I think that is the best plan20:18
dimasotnow, I see20:18
dimasotyep, sound like a plan20:18
dimasoton, now I need to dig into th ecode to see what is required to support such an option20:19
dimasotshould I open a bug or something on this issue to notify that I working on it?20:19
*** rjaiswal has quit IRC20:20
dimasotclayg: thank you for you help20:22
claygdimasot: np, I don't think "support arbitrary etag on if-none-match" makes much sense right now - I think container-sync not doing the right thing WRT pipelined 100-Continue is a bug - but I don't think filing it is as important as digging in understanding what's broke getting a patch up and helping people get it tested/reviewed/merged20:33
clayg... but maybe a bug (and failing test case) are helpful in *that* process?20:33
dimasotI see, so I will start from adding 100-continue to the x-timestamp and then will try to find/resolve the pipelined 100-Continue issue20:38
dimasotthansk again20:38
*** oddsam91 has joined #openstack-swift20:39
*** gyee has joined #openstack-swift20:43
*** dimasot has quit IRC20:44
openstackgerritJoel Wright proposed openstack/python-swiftclient: Log and report trace on service operation fails  https://review.openstack.org/17169220:48
*** bkopilov has quit IRC20:48
*** bkopilov has joined #openstack-swift20:53
oddsam91Hi there, Is there someone in here who can help me out. I'm looking to verify if my swift cluster is actually consuming more data or if there's some failure in the clean up processes.20:54
*** bkopilov has quit IRC21:00
*** esker has quit IRC21:01
openstackgerritJoel Wright proposed openstack/python-swiftclient: Log and report trace on service operation fails  https://review.openstack.org/17169221:03
*** annegentle has quit IRC21:04
*** joeljwright has joined #openstack-swift21:07
*** ChanServ sets mode: +v joeljwright21:07
notmynameoddsam91: I'm not sure I follow what you're asking21:09
oddsam91Well I'm noticing that over the past few months the average amount of disk space used is trending upwards at a rate that doesn't seem to be consistent with natural growth/higher usage of the cluster.21:10
oddsam91So I'm trying to find if there's something swift isn't cleaning up.21:11
notmynameoddsam91: how are you tracking the disk space?21:11
oddsam91df -h21:11
oddsam91well, I mean I'm using collectd21:11
notmynameand what are you comparing that to? I mean, how do you know that `df -h` is something that is out of line?21:12
oddsam91http://imgur.com/EZ9WS8m21:17
claygoddsam91: looks like a fairly liner growth curve?  are your users not expected to have been adding new data?21:18
claygnightly backups maybe?  new vm images?  new assets?  what makes you think the growth isn't organic and somehow disassociated with client usage?21:19
*** esker has joined #openstack-swift21:19
claygoddsam91: GREAT graph BTW!  up and to the left == good21:19
clayger... to the right - one of those is good21:19
oddsam91Haha, thanks. I'm not convinced this is actual growth though. But no, my swift cluster is supposed to cycle out all data older than 36 hours.21:19
joeljwright:)21:20
*** bkopilov has joined #openstack-swift21:20
claygoddsam91: ah... so lots of expiring objects?21:20
oddsam91right21:20
joeljwrightare you using X_EXPIRE_AFTER?21:20
oddsam91X-Delete-At21:20
joeljwrightand large objects?21:20
claygoddsam91: k, well you better check on the expirer then21:20
joeljwrightbecause you could be leaving the segments on disk21:20
oddsam91We have a max file size of 50Mb enforced at a different level21:20
claygredbo: dfg_: glange: hurricanerix: what is alex's handle?21:21
notmynameclayg: allen (alan)?21:21
hurricanerixclayg: alan?  it's aerwin21:21
oddsam91I did locate tombstone files that have never been cleaned up circa Dec 2013 when the cluster was stood up.21:21
claygoddsam91: grrrr... lp bug #130172821:23
openstackLaunchpad bug 1301728 in OpenStack Object Storage (swift) "tombstone (.ts) object will never be deleted if the hash_suffix exists in the hashes.pkl " [Undecided,In progress] https://launchpad.net/bugs/1301728 - Assigned to Brian Cline (briancline)21:23
oddsam91But I'm fairly certain the expirer is able to keep up. I did some spot checking around the different containers using the swift api and I didn't find a single file whose X-Delete-At header was in the past21:23
oddsam91yeah I did run into that one in my 100+ google searches21:23
clayghurricanerix: notmyname: yes *allan* - oddsam91 aerwin knows everything there is to know about dealing with an expirer that's backed up21:23
claygoddsam91: oh21:23
oddsam91I'm using an xfs file system would those 0 byte .ts file actually consume disk space21:23
claygoddsam91: sure inodes are a thing21:24
*** esker has quit IRC21:24
redboand dirents21:24
oddsam91df -i reports only ~36% of the inodes are consumed21:24
claygredbo: yes even more so the wasted hashdirs :'(21:24
redboyeah21:24
*** esker has joined #openstack-swift21:24
claygoddsam91: yeah not os much that you would run out - just that yeah having tombstones not getting cleaned up is sort of stupid and annoying21:24
oddsam91Agreed. Just not sure if I can point to that and say  "ah that's the cause for increased disk usage"21:25
claygI think the latest plan on that bug was to make the auditer just use reclaim age to make the tombstones & hashdirs go away - leaving the hashes.pkl entry alone - maybe - I acctually forget what the plan is21:25
*** dustins has quit IRC21:26
oddsam91(Of course it probably doesn't  help if I'm running 1.4.0)21:26
oddsam91latest swift is like 10+ minor versions ahead of my install21:26
claygoddsam91: ok, so if it's not expired data files - is it the unreclaimed tombstones?  Like have you tried deleting a hashes.pkl in a part here and there and watching the tombstones get reaped - is that freeing up disk space?21:27
claygoddsam91: we're 2.0 baby!21:27
oddsam91I haven't tried anything destructive yet. However, I can say at least some disk space is being reclaimed if you notice in the graph I posted a while back, there significant dips on the weekends (which system utilization is much, much lower).21:29
oddsam91the resolution is too low to see the daily cleanup but there's still about 8% points of disk space reclaimed every night21:29
oddsam91~119GB per store21:30
claygoddsam91: "daily cleanup" - like something besdies the expirer?21:30
*** wbhuber has quit IRC21:31
*** jkremer has quit IRC21:31
oddsam91No it's just the expirer. But I say daily cleanup because we've set the expire time to be 36 hours after upload. Which is approximately 9pm the next day.21:31
oddsam91So it sorta all happens at once21:32
claygoic21:33
joeljwrightoddsam91: I have seen behaviour like this caused by uploading SLO/DLO with the python-swiftclient, because the expiry headers are only set on the manifest files21:33
claygjoeljwright: ^ good idea!21:34
oddsam91Uploads are from a php client.21:34
oddsam91which, arguably, could be worse lol21:34
joeljwrightit's worth checking if you're creating any large objects21:34
oddsam91what do you define as large?21:35
joeljwrightand if so, whether the x-delete-at header is being set on the segments21:35
oddsam91Max *should* be 50mb21:35
joeljwrightanything using SLO/DLO21:35
*** annegentle has joined #openstack-swift21:35
oddsam91I'm not sure what SLO/DLO is21:35
joeljwrighthttp://docs.openstack.org/developer/swift/overview_large_objects.html21:35
oddsam91Ah I see21:36
oddsam91I can't imagine we're using this.21:36
joeljwrightok, that was my best guess :D21:36
oddsam91I now understand what you mean by segments21:36
joeljwrightyou can find out by looking for objects with either 'x-object-manifest' or 'x-static-large-object' headers21:37
joeljwrightbut if you're enforcing <50Mb before upload it shouldn't be that21:37
*** annegent_ has joined #openstack-swift21:38
oddsam91Ah gotcha. right21:39
oddsam91http://pastebin.com/GsbqGnH621:39
oddsam91here's an object's metadata that was just uploaded21:39
*** annegentle has quit IRC21:40
joeljwrightwell that looks like a simple 26M zip file21:40
joeljwrightif you never see those two headers, then unfortunately it can't be the thing I suggested21:41
oddsam91Right.21:41
oddsam91So the 0 byte .ts files (while annoying) aren't a cause for increased disk usage (just increased inode usage) correcT?21:42
joeljwrightthat one I can't answer confidently21:43
claygoddsam91: well no - the inodes and dirents do take up space on the disk (by way of filesystem metadata)21:44
claygoddsam91: it's not *much* space - but it can add up21:44
claygoddsam91: you could see how much (if any) it's impacting your deployment by cleaning some up21:44
oddsam91besides doing an rm -rf /mnt/path/to/objects/*/*/*/*.ts what's the best way of doing this?21:45
claygoddsam91: the easiest way I can think of to clean them up is to delete a hashes.pkl in a part some where - this will trigger some load (by way of REPLICATE requests, which will do listdirs and such) - but it's going to be fairly nominal21:45
clayg^ redbo you got a better way to trigger a rehash/reclaim of a bunch of tombstones?21:45
oddsam91Oh and in a single day, (one storage node out of three):21:46
oddsam91350152 DELETE21:46
oddsam91580504 GET21:46
oddsam91420575 PUT21:46
claygoddsam91: well there's *some* growth there if PUT > DELETE :)21:46
oddsam91If I had what is used to be I'd be able to know for sure.21:46
clayg*assuming more or less consistent object size :P21:46
oddsam91I'd say on avg no increase in object size21:46
oddsam91clayg: I just processed what you said about growth, that does make some sense. But most of our deletes happen in the pm so it'll go up later tonight. I'll check yesterday's log21:49
oddsam91Well thursdays log21:50
oddsam911628305 DELETE21:51
oddsam91 776958 GET21:51
oddsam91 528974 PUT21:51
*** biyiklioglu has quit IRC21:51
*** CaioBrentano has quit IRC21:55
claygoddsam91: well *that's* going in the wrong direction :P21:55
oddsam91Definitely. Especially when the graph is going the other way.21:56
claygi'm just sayin' you need to add moar data!21:57
claygnotmyname always says the DELETE verb was a mis-feature21:57
*** joeljwright has quit IRC21:59
oddsam91clayg: well sounds like the collective next best move would be to delete a few hashes.pkl and see what happens to disk usage?22:00
oddsam91It also sounds like aerwin may be able to help further?22:00
*** ccavanna has quit IRC22:01
claygoddsam91: well idk, not if the expirer is keeping up already - then that's not really the issue22:01
oddsam91Maybe I suck at verifying if the expirer is truly keeping. How might I verify that properly?22:02
aerwinoddsam91: one thing you can do is go through the .expiring_objects account and see if there are any objects in containers with timestamp before now.22:07
aerwinThat will tell you how far behind you are, if you are behind22:07
oddsam91Ah! Let me try that22:08
oddsam91should I do that via the api or the file system/22:08
aerwinI use the Swiftly DirectClient to handle the requests.22:09
oddsam91I've just been doing curl requests directly22:10
*** chsc has quit IRC22:11
oddsam91I've g2g but I'll check into the .expiring_objects account tomorrow. Is there something documenting this account besides source code?22:12
aerwinNot as far as I can tell. This is all I have been able to find. http://docs.openstack.org/developer/swift/overview_expiring_objects.html22:13
oddsam91That's what I just found. I might hit you guys up tomorrow with more questions. Thanks for all the help/support22:13
aerwinBut, I am working on submitting a spec to change the way the expiring of objects works as a whole.22:14
aerwinYour welcome.22:14
oddsam91Considering I'm still on 1.4.0, it maybe more effort to upgrade to a new version of swift than just wiping out all the data in the cluster.22:14
oddsam91But I'd prefer not to go nuclear.22:14
aerwinI can understand that idea.22:15
oddsam91Thanks again!22:15
*** oddsam91 has quit IRC22:15
*** jkugel has quit IRC22:16
*** wbhuber has joined #openstack-swift22:17
*** garthb has joined #openstack-swift22:19
mattoliverauMorning22:22
peluseyo22:22
*** jrichli has quit IRC22:23
aerwinmattoliverau: o/22:23
mattoliverauaerwin: hey man! yes please spec us with you expiring objects fix, then if you don't have time to implement we'll find someone (even if its me) :)22:28
*** jlhinson has quit IRC22:29
*** annegent_ has quit IRC22:32
*** annegentle has joined #openstack-swift22:32
aerwinWell I am back to CFile so I am focused on getting this fixed. :)22:33
*** flwang1 has joined #openstack-swift22:38
flwang1cschwede: ping22:41
*** resker has joined #openstack-swift22:43
*** esker has quit IRC22:47
*** resker has quit IRC22:48
*** esker has joined #openstack-swift22:48
garthbHello looking for some help on fixing a devstack swift issue and uploading cirros images...22:49
garthbHere's one of the uploads that's failing: openstack --os-token 374ce3ff7672466aa485e21934aedba0 --os-url http://10.50.177.1:9292 image create cirros-0.3.4-x86_64-uec-kernel --public --container-format aki --disk-format aki22:50
garthbHere's a pointer to 2 paste files for s-proxy.log and g-api.log: http://paste.openstack.org/show/435921/ and http://paste.openstack.org/show/435922/22:51
garthbThe upload fails with ERROR: openstack 500 Internal Server Error: Failed to upload image 3936ee83-7195-43e1-ad04-869b733259c2 (HTTP 500)22:51
garthbIt works when run from the command line immediately after devstack bails...22:52
garthbany suggestions / pointers would be greatly appreciated...spent several hrs exploring google, launchpad, etc. no luck22:53
*** annegentle has quit IRC23:04
flwang1garthb: i'm not a swift guy but glance23:08
flwang1so, does your glance service and swift service works fine separately?23:09
*** hrou has quit IRC23:09
garthbflwang1 yes I believe so...I'm able to manually run the upload after stack.sh fails...23:11
garthbflwang1 i.e. openstack --os-token 374ce3ff7672466aa485e21934aedba0 --os-url http://10.50.177.1:9292 image create cirros-0.3.4-x86_64-uec-kernel --public --container-format aki --disk-format aki23:11
*** lcurtis has quit IRC23:13
*** tanee has quit IRC23:16
*** tanee has joined #openstack-swift23:16
*** km has joined #openstack-swift23:17
flwang1just reviewed the 2 logs, seems it's swift error. can you run those swift command manually?23:18
garthbflwang1 I just unstacked and stacked...one moment, I'll give those swift commands a manual try...23:22
*** kei_yama has joined #openstack-swift23:31
notmynameFYI I'll be turning the crank on the release machinery tonight. swift 2.4.023:32
mattoliveraunotmyname: \o/23:32
garthbflwang1 curl -i http://10.50.177.1:8080/v1/AUTH_9a92a5007f8a4fd3892feea8147816ab/glance -I -H "X-Auth-Token: 0921030cfcab48f8a1ae6c8a91f220b1"...23:39
garthbflwang1 fails with authorization error manually as well...23:39
flwang1garthb: you need some help from the swift guys :)23:40
garthbflwang1: yeah, I suspected the same...thanks for taking a look though23:42
*** kota_ has joined #openstack-swift23:45
*** ChanServ sets mode: +v kota_23:45
kota_morning23:46
mattoliveraukota_: morning23:48
mattoliveraugarthb: hmm, looks like the account server isn't working properly, it isn't just not running otherwise I'd expect a Connection Refused. Is the account server running or something else running on the account servers port?23:49
hogood morning!23:51
*** DericHorn-HP has quit IRC23:54
garthbmattoliverau: hmmm...I don't see it in the ps list...I see a bunch of other swift servers though...23:55
garthbmattoliverau: can I try manually starting it with /usr/bin/python /usr/local/bin/swift-account-server /etc/swift/account-server/1.conf?23:56
mattoliveraugarthb: I don't use devstack (well not in a while), can you run: swift-init account start?23:57
mattoliverauthat is if swift has been installed to the system properly23:57
mattoliveraugarthb:  does it specify a port in /etc/swift/account-server/1.conf?23:58
garthbmattoliverau: That fails with Exception: Could not bind to 0.0.0.0:6012 after trying for 30 seconds23:58
mattoliveraugarthb: right somethign else is using the port23:58
mattoliveraugarthb: netstat -ntlp23:59
garthbmattoliverau: /etc/swift/account-server/1.conf specifies port 601223:59
mattoliveraugarthb: does netstat show something else using the port?23:59

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