Friday, 2015-03-27

*** ho has joined #openstack-swift00:02
*** zhill has quit IRC00:02
*** Tahmina has quit IRC00:03
*** annegentle has joined #openstack-swift00:06
openstackgerritSamuel Merritt proposed openstack/swift: EC: don't mix different fragment archives  https://review.openstack.org/16818500:09
torgomatic"don't cross the streams"00:09
*** km has joined #openstack-swift00:11
*** kei_yama has joined #openstack-swift00:11
*** rmcall has quit IRC00:12
*** kota_ has joined #openstack-swift00:29
*** reed has quit IRC00:29
*** reed has joined #openstack-swift00:30
*** reed has quit IRC00:30
*** reed has joined #openstack-swift00:31
openstackgerritSamuel Merritt proposed openstack/swift: EC: don't mix different fragment archives  https://review.openstack.org/16818500:38
openstackgerritClay Gerrard proposed openstack/swift: Add Fragment Index filter support to ssync  https://review.openstack.org/16518800:59
openstackgerritClay Gerrard proposed openstack/swift: wip: ec reconstructor probe test  https://review.openstack.org/16429100:59
openstackgerritClay Gerrard proposed openstack/swift: Erasure Code Reconstructor  https://review.openstack.org/13187200:59
*** annegentle has quit IRC01:14
*** annegentle has joined #openstack-swift01:17
*** vinsh has joined #openstack-swift01:37
*** vinsh has quit IRC01:43
*** vinsh has joined #openstack-swift01:43
*** vinsh has quit IRC01:47
*** annegentle has quit IRC01:48
*** Gues_____ has joined #openstack-swift01:48
*** happyeveryday has joined #openstack-swift01:50
*** happyeveryday has quit IRC01:58
*** haigang has joined #openstack-swift02:00
*** rmcall has joined #openstack-swift02:08
*** kota_ has quit IRC02:08
*** rmcall_ has joined #openstack-swift02:11
*** rmcall has quit IRC02:12
*** rmcall_ is now known as rmcall02:12
*** haomaiwang has joined #openstack-swift02:14
*** zaitcev has quit IRC02:18
*** rmcall has quit IRC02:22
* charz our jenkins is petty busy, ha02:24
*** haigang has quit IRC02:29
*** tsg has quit IRC02:29
*** haigang has joined #openstack-swift02:30
*** Gues_____ has quit IRC02:47
*** annegentle has joined #openstack-swift02:48
*** gyee has quit IRC02:50
*** Gues_____ has joined #openstack-swift02:53
*** annegentle has quit IRC02:54
*** devlaps has quit IRC02:54
*** panbalag has quit IRC03:11
notmynamecharz: is it causing problems? is the test cluster able to handle it?03:14
charznotmyname: so far so good. It looks good for now.03:15
notmynameok03:15
charznotmyname: Just got some pushover notification when some build fail.03:16
charznotmyname: I'm monitoring on it.03:16
notmynamethanks!03:16
charznotmyname: my pleasure03:17
mattoliverauYour 3rd party testing gets to firetest this week :)03:23
*** tsg has joined #openstack-swift03:26
claygman it's surprising how prolific the assumption get get_by_index will always return a policy instance is03:32
claygthe ECObjectController unlike the ReplicatedObjectController really can't deal with a unknown policy index03:33
claygwhere as the replicated policy can always just the default object.ring.gz and move forward - the ec controller needs a whole bunch of important policy spicific configuration to get the right number of fragments laid out with the right bits03:34
claygI'm not sure if I'm leaning toward raising an error in the proxy on unknown policy (like if the container_info has 2 cached, but this proxy hasn't been restarted yet)03:35
claygor if I should require a replicated policy so we know we can do something useful with the bytes03:35
notmynameand then punt to the reconciler to sort it out later?03:36
claygnotmyname: yeah of course - that's sort of the way the replicated object controller was designed03:36
notmynameright. just walking through that path in my head03:36
claygI think raising an error would make sense as well - but for GETs too?  404 seems reasonable there - eventual consistency and all03:37
notmynameso on object PUT, if the container server has a policy index that the proxy doesn't know about, either fall back to replicated storage or raise an error. is that the whole of it?03:39
claygin the object server we decided to raise 400 - which I'm not even entirely sure doesn't just go stright out to the client03:39
notmyname* fall back to the default policy03:39
notmynamethat doesn't sound right03:40
claygyeah i was thinking default - there was something that freaked me out there... PUT x-copy-from: crazy-unknown-policy-index would 40403:40
notmyname4xx is like saying, "hey client, you know that object you wanted me to store in that container? well you're doing it bad and should feel bad"03:41
notmynameI mean, if we found the container info (to even get a policy index at all), then we know that the index is valid, right?03:42
claygyeah I don't think it was intentional to have it make it's way out of the proxy - I think I got confused thinking 400's worked like 404's and the proxy could work around it03:43
claygnotmyname: yeah we don't let you get rid of policy indexes03:44
claygif we find it in the cache *someone* knows what to do with it03:44
claygbut if you don't (you being either a object-server or proxy-server) - what can you do?03:44
claygwhen there was only one type of policy and they were all perfect replicas there really was no "wrong thing" you could do - you just do your thing03:45
claygnotmyname: yeah anyway I think finding a server that doesn't know about a policy index is a server error03:48
notmynameyeah, I agree.03:48
claygmaybe a 501?  503 (chill out i'm HUPing right now)03:48
claygalso the proxy has a better chance of working around a backend 5XX than a 4XX - that was my bad03:49
claygeasy fix for the object servers - I'm less jazzed about returning a 5XX to the client - but if we stick the object in the wrong spot - or go looking for it in the wrong spot - it's only *barely* helping03:49
clayg... I think03:49
*** annegentle has joined #openstack-swift03:50
notmyname503 I think03:50
notmynameyou're typing exactly what I'm thinking03:51
notmynameyeah, on the one hand I think the error reveals an operation issue: configs are fully deployed before requests start using them03:51
claygyeah I think "deprecated" was the wrong word for the policy config option that enables you to avoid this problem03:51
notmynameon the other, you can't do that atomically03:51
claygif you roll out your swift.conf and rings - with the policy turned off - then you can rolling enable the policy in swift.conf and even if someone has a stale config - at least they know what to do with it03:52
notmynameah, right03:52
claygin this way you can make sure everyone knows about policy before you allow the first container to be created03:52
notmynameso yeah. "deprecated" isn't a great word there. "disabled" might be slightly better03:52
claygin fairness - we didn't strongly encourage this operational practice - but I think we're going to have to03:53
notmynameya, I was just wondering about where this sort of info will be written down03:53
notmynameie docs03:53
claygnotmyname: I think someone wanted to reserve "disabled" for making it like you couldn't write new objects - currently deprecated just prevents it from being listed in info - or creating new containers with the policy - existing containers continue to work03:53
notmynameah03:54
claygnotmyname: I think there's an existing section in the storage policy part of the admin guide that sort of hints that doing something like this might be a good idea03:54
notmyname"someone" ;-)03:54
claygnotmyname: maybe it was me?03:54
notmynamelol03:54
claygnotmyname: I honestly don't recall03:54
notmynameI think it's funny because it's not like every one of us didn't have an opportunity to comment. it's owned by everyone now :-)03:54
*** annegentle has quit IRC03:55
clayghttp://docs.openstack.org/developer/swift/overview_policies.html#deprecating-policies03:55
claygsecond paragraph - you can also use deprecated...03:56
claygstill kinda dancing around the edge - rolling policy introduction is gunna have to be a thing03:56
clayghow did we not know!03:56
claygwell shit - now we have to come up with words03:57
notmynameeh, it's not that bad. stronger words are needed, yes, but mostly it's clarifying what's there instead of new stuff altogether03:58
claygoh... yeah I guess that's true03:58
claygsee we built the right THING we just named it wrong03:58
notmynamewe did everything but the hard problem? ;-)03:58
claygI'd rather be doing it right and looking the fool than doing it wrong and looking good03:58
claygtypical03:59
clayglazy03:59
notmynamelol03:59
notmynamenext you'll tell me that "account" and "user" were terrible choices too!03:59
claygno i'm used to it now03:59
notmynameor a container-updater that walks object data03:59
claygobviously it's updating the containers04:00
claygi'll probably just start calling resturants that are closed "deprecated" and it'll totally be fine04:00
notmynamelol04:00
claygok, 503's all around - I'll put something in the body about your cluster operator is doing it wrong04:01
mattoliverauWow, I go to lunch and that's when the channel gets interesting... Typical :p04:03
claygmattoliverau: we were waiting for you to leave04:03
claygmattoliverau: you think we should mix in the all the refactoring as we go?04:03
mattoliverauClosed restaurants == deprecated.. Love it! Lol04:03
claygmattoliverau: way back in the day i naively thougth we could work on the refactoring on master informed by the abstractions we were building in EC04:04
claygbut then it turned out that EC was hard (who knew?)04:04
claygstupid fragment indexes and commit requests04:05
mattoliverauLol, yeah.. Some stuff if hard, other is similar but different.. Making refactoring a pain04:06
claygmattoliverau: I think historically we've not done the best dealing with refactoring - we're probably better at it now04:06
claygmattoliverau: but just at tdasilva how hard it is to merge "clean ups"04:07
claygmattoliverau: it's all like "hey I move a bunch of a code around because assteically I think it's better" - "oh yeah, what does it do" - "ideally?  nothing.  probably some bugs in there tho."04:07
*** annegentle has joined #openstack-swift04:08
claygmattoliverau: I'm not sure merging a bunch of duplicated code just to develop it's isolation is better in the long run - but it's the idea I had04:09
mattoliverauThanks for you response of the review.. Let's get get stuff in, keep it logical, easy separated.. Duplication is a pain but there will be a ride off. I'm in the opinion of let's get EC working nicely along side Repl.. We and iterate in master later (famous last words) but especially when a new diskfile/policy is added and we need to start attacking 304:09
claygI think someone said it was a good idea - probably acoles_away - and he's smart04:09
claygI think torgomatic told me I'm crazy - but he often thinks I'm doing it wrong04:09
mattoliverauLol04:10
claygmattoliverau: a'ight - well don't think I'm picking on you04:10
claygmattoliverau: you looked at some shit I threw up and said "hey duplicated code sucks" and I was all like "yeah I know but *reasons* wah wah wah"04:11
mattoliverauI think at this, the 11th hour, let's not do too many more crazy refactors.. Cause that could damage repl04:11
claygdoesn't make me right04:11
claygjust means we've got an argument worth having04:11
claygnotmyname: *why* did never capture chucks' swift design principles somewhere!  I feel like I could use them right about now04:12
mattoliverauIf we all thought the same way, we'd have no real innovation ;) plus arguments are fun :p04:12
claygmattoliverau: there was one about you're not done with the design until you've argued about it - or something04:12
mattoliverauHa, awesome04:13
* clayg shouts call out into the abyss for crieth04:13
*** annegentle has quit IRC04:13
claygwas that in atlanta?  hong kong?04:15
notmynameclayg: https://etherpad.openstack.org/p/juno_swift_core_principles04:15
claygoh yippee!04:15
*** ppai has joined #openstack-swift04:17
*** Gues_____ has quit IRC04:19
clayggah now I remember why we stalled out - we couldn't decide where to stick it :\04:21
notmynameshould be in https://github.com/openstack/swift/blob/master/CONTRIBUTING.md04:22
*** ppai has quit IRC04:23
notmynameok, I've got a really early start tomorrow. I've got to take care of some other things before bed, so I'm logging off04:24
claygnotmyname: thanks for all the help!04:24
mattoliveraunotmyname: night! I'll be online to help out tomorrow, so see you then.04:25
*** ppai has joined #openstack-swift04:36
clayghow can I know if i'm mark downing correctly?04:43
openstackgerritClay Gerrard proposed openstack/swift: Add Swift Design Principles to CONTRIBUTING.md  https://review.openstack.org/16822104:46
*** reed has quit IRC05:03
*** ppai has quit IRC05:05
*** kota_ has joined #openstack-swift05:11
*** annegentle has joined #openstack-swift05:19
*** ppai has joined #openstack-swift05:20
*** annegentle has quit IRC05:24
*** tsg has quit IRC05:30
*** jamielennox is now known as jamielennox|away05:41
*** nshaikh has joined #openstack-swift05:42
*** SkyRocknRoll has joined #openstack-swift05:53
*** annegentle has joined #openstack-swift06:20
*** annegentle has quit IRC06:25
*** dmorita has quit IRC07:02
*** chlong has quit IRC07:16
openstackgerritYuan Zhou proposed openstack/swift: EC: Allow proxy to read from all SN in EC policy  https://review.openstack.org/16825407:42
claygoh eventlet you owe me fucking 3 hours07:45
claygi was remembering to this guy in the office about this one time Douglas Crockford came to RAX to do a tech talk - he said a lot of interesting things07:46
claygbut one thing I rember was him postulating that being good at programming acctually requires you to be slightly broken07:47
claygmost humans avoid pain07:47
openstackgerritYuan Zhou proposed openstack/swift: EC: Allow proxy to read from all SN in EC policy  https://review.openstack.org/16825408:02
*** anticw has quit IRC08:07
*** anticw has joined #openstack-swift08:09
*** admin6 has joined #openstack-swift08:17
openstackgerritYuan Zhou proposed openstack/swift: EC: Allow proxy to read from all SN in EC policy  https://review.openstack.org/16825408:21
*** annegentle has joined #openstack-swift08:22
*** admin6 has quit IRC08:24
*** admin6 has joined #openstack-swift08:24
*** annegentle has quit IRC08:27
openstackgerritClay Gerrard proposed openstack/swift: Extract EC PUT to ECObjController  https://review.openstack.org/16495008:34
claygeverybody likes writing new tests in proxy.test_sever - I don't even like to have that file open in my editor for fear it might eat up all my memory or startup some sockets ans spawn skynet on my laptop08:38
claygi'll see you guys later in the morning08:39
claygit's Friday!08:39
*** jistr has joined #openstack-swift08:40
*** Cipher45 has quit IRC08:50
*** Cipher45 has joined #openstack-swift08:51
*** Cipher45 has joined #openstack-swift08:51
*** Cipher45 has quit IRC08:53
*** Cipher45 has joined #openstack-swift08:53
*** Cipher45 has joined #openstack-swift08:53
*** jordanP has joined #openstack-swift08:53
mattoliverauclayg: night man08:57
*** acoles_away is now known as acoles09:04
acolesmorning09:05
acolesmattoliverau: evening ;)09:05
mattoliverauacoles: hey morning!09:08
acolesmattoliverau: just catching up on the overnight fun, so what did you and clayg conclude about duplicate code ?09:13
acolesmattoliverau: my take is first thing we do after major release is refactor, introduce bugs and find em before next release ;)09:14
mattoliverauIts good for now :) keeps the code paths separate and easy to read, worry about possible refactor later09:14
mattoliverauSo like you said ;)09:14
acolesmattoliverau: cool. have a good weekend. are you gonna watch the cricket final?09:16
mattoliverauGetting late and failing at setting up container syncing between 2 saios... Must be time for dinner and a break to clear my head09:16
acolesmattoliverau: i see its an all down-under affair09:16
*** mmcardle has joined #openstack-swift09:19
mattoliverauacoles: probably, but first I'll be online in the morning to help out as much as I can pre end of US day... Well inject some sarcasm anyway :p09:20
*** Akshat has joined #openstack-swift09:21
AkshatHi09:21
acolesmattoliverau: :D i'm never sure if they understand that ;)09:21
*** ppai has quit IRC09:21
AkshatI did a swift installation, but getting very bad PUT performance09:21
AkshatI see an error in logs09:21
Akshatobject-server: ERROR container update failed09:22
Akshatany pointers will be helpful09:23
mattoliverauacoles: me neither.. Its half the fun :p09:23
*** kota_ has quit IRC09:23
acolesAkshat: that error would suggest that the object server(s) are timing out connecting to container servers. check the container servers are running and that the object servers can route http to them.09:27
Akshatthey are09:27
AkshatI am facing this error intermittently09:27
Akshatnot continuos09:27
Akshatthey are runing on same machine09:27
Akshatjust diiferent ports09:27
AkshatI am getting 50tps for 75KB PUT09:29
Akshatthough I have very huge servers09:30
Akshatnot sure what is blocking it09:30
Akshat@acoles...what could be blocking according to you09:30
acolesAkshat: although its logged as an error the object server is designed to recover, the failed update will be queued for later retry. that can happen when the container server is heavily loaded09:31
Akshatif I do a top09:31
AkshatI dont see it consuming 1 cpu09:31
AkshatI have a 32 core machine09:31
*** joeljwright has joined #openstack-swift09:32
Akshatnot sure what could be wrong09:32
acolesAkshat: sorry i have to go to a meeting now09:32
Akshatoh09:32
Akshatwhen can we reconviene09:32
AkshatHi Joel09:34
*** ppai has joined #openstack-swift09:35
*** ho has quit IRC09:45
*** foexle has joined #openstack-swift09:46
*** silor has joined #openstack-swift09:50
AkshatHi09:56
AkshatI need help with swift09:56
*** ppai has quit IRC09:56
*** annegentle has joined #openstack-swift10:23
*** haomaiwang has quit IRC10:24
*** annegentle has quit IRC10:29
Akshathi10:40
*** kei_yama has quit IRC10:45
*** haigang has quit IRC10:48
ctennisAkshat: look in the swift logs for a transaction id (starting with tx...) for a specific operation that is failing to work properly, and follow that through the logs to see where the bottleneck is.11:17
*** erlon has joined #openstack-swift11:18
AkshatI can see txn11:20
Akshatwhic all logs should ai follow it11:20
ctenniseverywhere in your system11:21
ctennishow many drives/nodes do you have?11:21
*** annegentle has joined #openstack-swift11:24
*** km has quit IRC11:25
*** haypo has joined #openstack-swift11:26
*** annegentle has quit IRC11:29
openstackgerritMerged openstack/swift: Multiple Fragment Archive support for suffix hashes  https://review.openstack.org/15963711:34
*** Akshat has quit IRC11:46
*** admin6 has left #openstack-swift11:47
*** Cipher45 has quit IRC12:14
*** Cipher45 has joined #openstack-swift12:15
*** Cipher45 has joined #openstack-swift12:15
*** annegentle has joined #openstack-swift12:22
*** annegentle has quit IRC12:23
*** fthiagogv has joined #openstack-swift12:26
*** panbalag has joined #openstack-swift12:50
openstackgerritThiago da Silva proposed openstack/swift: Select policy when running functional test  https://review.openstack.org/16759513:00
*** nshaikh has quit IRC13:19
*** jrichli has joined #openstack-swift13:22
*** annegentle has joined #openstack-swift13:24
*** mahatic has joined #openstack-swift13:27
*** annegentle has quit IRC13:29
*** SkyRocknRoll has quit IRC13:37
*** annegentle has joined #openstack-swift13:43
*** Akshat has joined #openstack-swift13:54
Akshatctennis ...I have 8 nodes, 184 drives13:57
ctennisok Akshat, jus follow the transaction logs and see where the bottleneck is..everythig is logged and timed.13:57
AkshatI only see logs in syslog13:58
Akshatany other place I can see them13:58
AkshatI don't find that txn id anywhere else13:58
ctennisswift sends everything to syslog, not sure how your setup is, depends on where you have things set to log to14:00
*** annegentle has quit IRC14:07
*** Trixboxer has joined #openstack-swift14:17
*** vinsh has joined #openstack-swift14:18
*** fthiagogv has quit IRC14:26
*** vinsh has quit IRC14:27
openstackgerritAlistair Coles proposed openstack/swift: Make ECDiskFile require a fragment index  https://review.openstack.org/16807614:27
*** vinsh has joined #openstack-swift14:28
*** G________ has joined #openstack-swift14:32
*** annegentle has joined #openstack-swift14:32
*** vinsh has quit IRC14:32
*** reed has joined #openstack-swift14:33
*** AbyssOne is now known as a1|away14:40
*** mahatic has quit IRC14:47
*** vinsh has joined #openstack-swift14:53
*** lpabon has joined #openstack-swift14:56
openstackgerritAlistair Coles proposed openstack/swift: Make ECDiskFile require a fragment index  https://review.openstack.org/16807614:56
*** Akshat has quit IRC15:01
*** pokoli has joined #openstack-swift15:01
*** vinsh has quit IRC15:01
*** pokoli has left #openstack-swift15:03
*** annegentle has quit IRC15:04
*** annegentle has joined #openstack-swift15:05
*** Akshat has joined #openstack-swift15:05
*** rdaly2 has joined #openstack-swift15:06
*** G________ has quit IRC15:08
*** devlaps has joined #openstack-swift15:10
*** Cipher45 has left #openstack-swift15:11
*** reed has quit IRC15:14
*** G________ has joined #openstack-swift15:16
*** Akshat has quit IRC15:17
*** fifieldt has quit IRC15:21
*** lpabon has quit IRC15:26
*** mahatic has joined #openstack-swift15:28
*** mahatic has quit IRC15:28
*** G________ has quit IRC15:29
*** gyee has joined #openstack-swift15:29
*** haomaiwang has joined #openstack-swift15:39
*** mahatic has joined #openstack-swift15:44
*** dencaval has quit IRC15:52
*** tsg has joined #openstack-swift15:57
openstackgerritAlistair Coles proposed openstack/swift: Make ECDiskFile require a fragment index  https://review.openstack.org/16807615:59
*** foexle has quit IRC16:05
*** G________ has joined #openstack-swift16:05
*** annegentle has quit IRC16:06
*** chuck_ is now known as zul16:19
*** zul has quit IRC16:19
*** zul has joined #openstack-swift16:19
*** G________ has quit IRC16:22
claygmorning16:26
*** G________ has joined #openstack-swift16:26
acolesclayg: its friday! multi-fi-hash-thingy landed16:26
*** Akshat has joined #openstack-swift16:27
claygoh thank goodness!16:27
acolesclayg: so are you awake enough to take a question?16:28
clayglet's get this party started!16:28
claygi have COFFEEEEEEEEEEYYYYYYYYY16:28
acolesthats the spirit!16:28
*** haypo has left #openstack-swift16:28
acolesclayg: i am working on https://review.openstack.org/#/c/165188/8 and looking at yield_hashes16:29
acolesclayg: i had this conversation with peluse a while back - if we end up with a stray .data that is newer than anything else in the obj dir but has no durable, we don't want to yield that from yield_hashes do we?16:30
claygacoles: I just glanced at https://review.openstack.org/#/c/168076/4 but I get the feeling I'm going to love it16:30
claygacoles: correct - only yield out .data that is durable16:30
acolesclayg: cool i love an easily reached agreement :)16:31
claygacoles: one exception might be if we have a way to sync suffixes - then the reciever might want a way to somehow know that it has some data for fi X and tell the remote end to... magic16:31
acolesclayg: so i *think* its broken right now but if it is i will fix and write tests to prove16:31
claygacoles: perfect!16:31
acolesnext question:16:31
acoles(can you tell i have been waiting!)16:32
claygacoles: acctually i'd love to have you help me fixup the validate something something in the middle of the cleanup_list_dir something - it's ugly - did you see it?16:32
claygi sort of don't remember16:32
AkshatHi16:32
Akshatwhat can be done to improve the performance for swift16:33
AkshatI am getting a really bad performance16:33
acolesclayg: yeah i'm going to cleannup all that16:33
claygAkshat: did you fix the errors?16:33
acolesclayg: the power of gather_ondisk_files will be unleashed :)16:33
AkshatI could not find that txn id16:33
Akshatstill seeing object-server: ERROR container update failed16:33
claygacoles: whoa16:33
Akshatin syslogs16:33
Akshatand a very bad tps16:34
claygAkshat: yeah that makes put hit a timeout - slows things down quite a bit16:34
claygAkshat: yup - at least you know what you need to fix16:34
Akshatwhat is the cause of that error16:34
Akshatand how to fix it16:34
claygit means the object server can't talk to the container server - it'll normally say something more about - timeout - econnrefused - 4XX/5XX something like this16:34
Akshatyup...in debug I seen something like greenlet econnrefused16:35
Akshatbut could not figure out any root cause for it16:35
Akshator how to fix it.16:35
claygacoles: wait - were you asking a "next question"16:35
acolesclayg: next question,  https://review.openstack.org/#/c/168076/4 is going to break stuff if i rebase the chain onto it16:36
acolesclayg: yes!16:36
claygAkshat: oh nice - yeah that's easy the container servers aren't listening where the proxy is telling the object server to expect them to be16:36
acolesclayg: all stuff that could be fixed but wasted effort if we don't like 168076 so what do you suggest?16:36
claygacoles: yeah but i love that chain16:37
Akshatclayg: what could be the possible reason, could it be replication16:37
claygbut I *do* like that change16:37
claygAkshat: nah - probably just network - do you have replication ports in your rings?16:37
Akshatclayg: can proxy point to handoff node for containers16:37
claygAkshat: can you swift-ring-builder container.builder - and try to talk to one of those servers form the object server with curl16:38
acolesclayg: k, well i'll stuck working on the yield_hashes/ssync patch 165188 then take a look at the rebase16:38
patchbotacoles: https://review.openstack.org/#/c/165188/16:38
Akshatwait lemme try the commands16:38
claygAkshat: the proxy will talk to handoff containers - but it always sends down the primaies to the object server for write update16:38
*** tsg has quit IRC16:39
acolesclayg: s/stuck/stick/16:39
claygacoles: ok - well let me review the fix name_to_ts and maybe we can rebase it on 165188 and fix from the recon down or something?16:39
claygi want to work on recon tests anyway - so trying to maintain some failing tests would probably highlight to me grossest parts16:40
claygI like this plan!16:40
claygtoday is going to be a good day!16:40
*** Akshat has quit IRC16:40
acolesclayg: ok. now the bad news...16:40
acoles...just kidding16:41
claygmattoliverau: cschwede: tdasilva: torgomatic: can you guys rock the proxy today?  patch 164950 is sort of aonnoyingly good and has some questionable diffs because I'm looking at these files against master and trying to rip out cruft built up over the development of feature/ec16:41
patchbotclayg: https://review.openstack.org/#/c/164950/16:41
claygacoles: oh nice16:41
claygoh shit!  i just call the reconstructor recon :'(16:41
claygdamit peluse ^^^16:42
claygmaybe it should be the recoder?16:42
cschwedeclayg: looking16:42
acolesthe 'fixerupper'16:42
claygswift-init object-fixer once -nv16:43
acoles+116:44
claygyeah but re-EC-doer is like recoder but like dyslexic16:44
claygacoles: so - there is no bad news?16:46
claygcschwede: oh i feel like I tricked you - not annoyingly good - annoyingly BIG - there's nothing good about a moving a bunch of code in the proxy - but I'm pretty sure some parts of it are good - mostly the lots and lots of new tests and the random bug fixes i found writing the tests16:49
*** silor has quit IRC16:49
claygawww - you guys - come on!  https://review.openstack.org/#/c/168221/16:50
acolesclayg: no tests, no +216:51
*** Akshat has joined #openstack-swift16:51
acoles:)16:51
acolesi wanna see a spec first16:51
Akshatclayg: I did tried curl16:51
Akshatfetching contents of a container from object server16:51
Akshatit looks to be working fine16:51
Akshatclayg: Also I see this error intermittently16:52
claygmaybe the rings on the proxy are stale - i'm not sure if the reconnrefused trace back includes the ip and port of the container server - be really nice if it did :\16:54
cschwedeclayg: i’ll need some more time for the obj.py review in patch 164950, no blocker so far. unfortunately my coworking space closes soon, thus i have to interrupt the review16:54
patchbotcschwede: https://review.openstack.org/#/c/164950/16:54
Akshatits the same ring all across16:54
Akshatclayg: I verified the cksum16:55
Akshatits the same16:55
claygcschwede: no problem - any thing you can throw out would be helpful - my eyes were glossing over last night and today is new challenges!16:55
claygAkshat: well dag nab it16:56
Akshatclayg: sorry din't get you16:57
claygwell there's no good reason for it to work from the object server with curl and not from the object server process16:58
claygso we're probably not talking to the same node/ip/port with curl as the object-server process is reading from the headers16:58
Akshatclayg: the data in ring shows to be reachable16:59
Akshatwhat best can be done to debug this17:00
claygyah but what does the error message say?17:00
Akshat#012Traceback (most recent call last):#012  File "/usr/local/lib/python2.7/dist-packages/swift/obj/server.py", line 194, in async_update#012    full_path, headers_out)#012  File "/usr/local/lib/python2.7/dist-packages/swift/common/bufferedhttp.py", line 157, in http_connect#012    ipaddr, port, method, path, headers, query_string, ssl)#012  File "/17:00
Akshatusr/local/lib/python2.7/dist-packages/swift/common/bufferedhttp.py", line 189, in http_connect_raw#012    conn.endheaders()#012  File "/usr/lib/python2.7/httplib.py", line 969, in endheaders#012    self._send_output(message_body)#012  File "/usr/lib/python2.7/httplib.py", line 829, in _send_output#012    self.send(msg)#012  File "/usr/lib/python2.717:00
Akshat/httplib.py", line 791, in send#012    self.connect()#012  File "/usr/local/lib/python2.7/dist-packages/swift/common/bufferedhttp.py", line 108, in connect#012    return HTTPConnection.connect(self)#012  File "/usr/lib/python2.7/httplib.py", line 772, in connect#012    self.timeout, self.source_address)#012  File "/usr/local/lib/python2.7/dist-pack17:00
Akshatages/eventlet/green/socket.py", line 60, in create_connection#012    raise error(msg)#012error: [Errno 111] ECONNREFUSED (txn: tx3866e75241e84b78b5ad0-0055151c5717:00
Akshatexact error17:00
*** haomaiw__ has joined #openstack-swift17:02
Akshatis curl command to fetch contents of the container good enough to validate17:02
claygAkshat: nope, there's a line above that17:02
claygERROR container update failed with -> then it has the ip:port/dev17:02
AkshatERROR container update failed with 10.65.53.242:6001/sdn (saving for async update later): Timeout (3s) (txn: tx14298e16edc849a289f2e-00551504ba)17:03
*** haomaiwang has quit IRC17:04
*** annegentle has joined #openstack-swift17:04
*** Trixboxer has quit IRC17:04
claygyeah ok, so and `curl http://10.65.53.242:6001/sdn` returns something about 4XX bad path?17:06
clayg*from the host that logged that line*17:06
*** btorch has quit IRC17:10
*** jistr has quit IRC17:13
openstackgerritThiago da Silva proposed openstack/swift: Add Swift Design Principles to CONTRIBUTING.md  https://review.openstack.org/16822117:13
*** G________ has quit IRC17:14
*** nshaikh has joined #openstack-swift17:18
claygyeah that's what i'm talking about!17:19
openstackgerritThiago da Silva proposed openstack/swift: Document SWIFT_TEST_POLICY for regular functional tests  https://review.openstack.org/16795817:22
*** RayAngelone has joined #openstack-swift17:23
acolestdasilva: ^^ thanks!17:23
tdasilvaacoles: hope it is ok, it was just a minor fix, so I thought it would not mind17:24
tdasilvas/it/you17:24
*** nshaikh has quit IRC17:27
*** jeblair is now known as denethor17:27
*** denethor is now known as jeblair17:27
*** cebruns has quit IRC17:30
acolestdasilva: no not at all its helpful. funny thing is that iirc i spotted that i had left the word 'would' out before pushing first version, but i then put it in wrong place :)17:31
claygtdasilva: maybe I should add "seplling is not a prioitry" - or maybe that's just me :\17:32
tdasilvaacoles, clayg: haha17:32
claygdocs are required - probably spelling and grammer is optional17:33
tdasilvathat works17:33
tdasilva:P17:33
acolesclayg: s/grammer/grammar/ ;)17:33
tdasilvaclayg: have we considered moving the EC classes in controllers/obj.py to a different file?17:34
clayglol!17:34
claygtdasilva: i fucking tried and my stupid register trick didn't work anymore unless I could find someone to impor the file and execute it!17:34
claygalthough now I'm thinking adding it to __init__ sort of like we do with the proxy controllers would work17:34
*** btorch has joined #openstack-swift17:35
claygtdasilva: i was acctually thinking it'd be sorta hawt to see everything (policy, controller, diskfilemanager) moved under a common module - like all the ec in one place!17:35
claygI have this idea with these @register hooks that someone could acctually just ship a storage policy and hook it in with entry point17:36
tdasilvaclayg: btw: I like the idea of the router, I think it will be helpful if we introduce new subclasses besides ec and replication ;)17:36
tdasilvayes!17:36
claygi thought you would :)17:36
tdasilvahehe17:36
*** haomaiwa_ has joined #openstack-swift17:40
*** haomaiw__ has quit IRC17:40
Akshatclayg: I am out of network right now17:44
Akshatwill try the curl you specified and update you17:44
*** jordanP has quit IRC17:45
*** haomaiwa_ has quit IRC17:53
claygacoles: I'm changing up the parse_on_disk_filename17:53
acolesclayg: in patch 165188 there's a bunch of tests that moved an i think as a result have not picked up the changes to dev paths17:54
patchbotacoles: https://review.openstack.org/#/c/165188/17:54
claygchanges to dev paths?17:55
acolesclayg: like on feature ec they are /srv/sda1 and in 165188 they are /srv/dev/17:55
*** haomaiwang has joined #openstack-swift17:55
claygso... they're failing?17:55
acolesthe return values to mocked get_dev_path17:55
acolesidk why they got changed17:56
* clayg is way lost17:56
acolesbut do we want to change them back again17:56
acolesclayg: yeah i am lost too :/17:56
acolesclayg: i remember peluse grumbling about having to change some stuff like that17:57
claygoh i dont' know why those tests were *originally* mocking get_dev_path - i probably just didn't notice it when i copy pasted them17:57
claygacoles: maybe they just need to turn off mount check and use self.existing_dev1 (or something else that creates a real directory)17:58
acolesclayg: its just that when i compare the moved tests with the originals on feature/ec there's a ton of diffs and i was hoping there wold be none (you just relocated from the DiskFileMixin to DiskFileManagerMixin18:00
acoles)18:00
acoleshmmm18:01
Akshatclayg: I tried curl http://10.65.53.241:6001/sdc18:05
Akshatit gives me invalid url18:05
AkshatError was ERROR container update failed with 10.65.53.241:6001/sdc (saving for async update later): Timeout (3s) (txn: txc49b77bd7808406597127-005515999a18:05
claygacoles: i don't care about diff count in the tests - lots of tests diff makes it look like we're trying :D18:06
*** haomaiwang has quit IRC18:06
claygwell now hold on - Akshat the Timeout isn't the same as econnrefused is it?18:07
clayga) the 3s timeout is the node timeout (by default) - so that means the object-server made the connection and the container wasn't able to respond18:07
AkshatIf I see the debug log...trace says econnrefused18:08
claygb) i don't think an ECONREFUSED would be logged as a timeout - i waited for an ack for x seconds and didn't hear anything is different from I talked to this host and he said he won't accept connections on that port18:08
claygwhat?18:08
claygAkshat: are you sure those are the same reqeust?  can you put a large snippit form the logs in a paste somewhere?18:09
claygpaste/gist18:09
Akshatsure18:09
openstackgerritAlistair Coles proposed openstack/swift: Add Fragment Index filter support to ssync  https://review.openstack.org/16518818:16
acolesclayg: ^^ i cleaned up yield_hashes and there's a TODO where 168076 will allow more cleanup, i *think* this wants rebasing on patch 168076 so 168076 is start of chain18:16
patchbotacoles: https://review.openstack.org/#/c/168076/18:16
acolesclayg: i have to work offline for a couple of hours back later18:17
*** acoles is now known as acoles_away18:19
*** welldannit has quit IRC18:21
claygAkshat: i don't see any econrefused in there - just the timeouts from the container servers - that's a different problem - how many and what kind of disks do you have servicing the container work load - i can see you're using ssbench - the scenario .json would be helpful as well18:23
claygAkshat: it's quite possible the work load doesn't make sense for the hardware - what's the total rps on the write path - you might try more limited crud scearnios to find good values for isolated workloads before trying to combine them18:24
Akshatthis is the scenario json18:26
Akshat{18:26
Akshat  "name": "Small test scenario",18:26
Akshat  "sizes": [{18:26
Akshat    "name": "tiny",18:26
Akshat    "size_min": 7680,18:26
Akshat    "size_max":768018:26
Akshat  }],18:26
Akshat  "initial_files": {18:26
Akshat   "tiny" : 10018:26
Akshat  },18:26
Akshat  "operation_count": 500,18:26
Akshat  "crud_profile": [1,0,0,0],18:26
Akshat  "user_count": 118:26
Akshat}18:26
Akshathow do I check rps on write path18:26
AkshatI am only trying a PUT18:26
Akshatand its giving me the worst performace18:27
Akshathow do you switch on DEBUG logs for container-server18:27
AkshatI have 184 disks, SATA, 3TB each18:27
*** mmcardle has quit IRC18:30
*** gyee has quit IRC18:32
claygrequests/per/second - should be in the output of ssbench18:33
claygare you over-riding the user count on the command line?  what's the command you use to run this scenario?  please use paste18:33
AkshatYES18:33
claygI don't understand where the HEADs are coming from18:34
Akshatu 75 c 100 o 100018:34
Akshattps 3618:34
Akshat2 zones18:34
Akshat184 drives across 8 nodes18:34
Akshat23 drive on each node18:34
Akshatpartition power 1318:34
Akshatwhat does HEAD signify18:35
AkshatMar 27 11:31:19 dfw-appblx061-25 swift: ERROR container update failed with 10.65.53.241:6001/sdc (saving for async update later): #012Traceback (most recent call last):#012  File "/usr/local/lib/python2.7/dist-packages/swift/obj/server.py", line 194, in async_update#012    full_path, headers_out)#012  File "/usr/local/lib/python2.7/dist-packages/sw18:35
Akshatift/common/bufferedhttp.py", line 157, in http_connect#012    ipaddr, port, method, path, headers, query_string, ssl)#012  File "/usr/local/lib/python2.7/dist-packages/swift/common/bufferedhttp.py", line 189, in http_connect_raw#012    conn.endheaders()#012  File "/usr/lib/python2.7/httplib.py", line 969, in endheaders#012    self._send_output(mess18:35
Akshatage_body)#012  File "/usr/lib/python2.7/httplib.py", line 829, in _send_output#012    self.send(msg)#012  File "/usr/lib/python2.7/httplib.py", line 791, in send#012    self.connect()#012  File "/usr/local/lib/python2.7/dist-packages/swift/common/bufferedhttp.py", line 108, in connect#012    return HTTPConnection.connect(self)#012  File "/usr/lib/p18:35
Akshatython2.7/httplib.py", line 772, in connect#012    self.timeout, self.source_address)#012  File "/usr/local/lib/python2.7/dist-packages/eventlet/green/socket.py", line 60, in create_connection#012    raise error(msg)#012error: [Errno 111] ECONNREFUSED (txn: tx13a72f5fa163455a9a153-005515a1f6)18:35
AkshatMar 27 11:31:19 dfw-appblx061-25 swift: 10.65.53.241 - - [27/Mar/2015:18:31:18 +0000] "PUT /sdd/150/AUTH_72dc104eb65941ebb73cc0d3dd406022/ssbench_000013/tiny_000711" 201 - "PUT http://10.65.53.241:8080/v1/AUTH_72dc104eb65941ebb73cc0d3dd406022/ssbench_000013/tiny_000711" "txaf2d37659db149b5b9b15-005515a1f6" "proxy-server 38167" 0.7375 "-" 3784818:35
AkshatMar 27 11:31:19 dfw-appblx061-25 swift: ERROR container update failed with 10.65.53.241:6001/sdd (saving for async update later): #012Traceback (most recent call last):#012  File "/usr/local/lib/python2.7/dist-packages/swift/obj/server.py", line 196, in async_update#012    response = conn.getresponse()#012  File "/usr/local/lib/python2.7/dist-packa18:35
Akshatges/swift/common/bufferedhttp.py", line 123, in getresponse#012    response = HTTPConnection.getresponse(self)#012  File "/usr/lib/python2.7/httplib.py", line 1045, in getresponse#012    response.begin()#012  File "/usr/lib/python2.7/httplib.py", line 409, in begin#012    version, status, reason = self._read_status()#012  File "/usr/lib/python2.7/h18:35
Akshatttplib.py", line 373, in _read_status#012    raise BadStatusLine(line)#012BadStatusLine: '' (txn: tx39e47fd5cf5042feabff4-005515a1eb)18:35
Akshatthis is the debug of the same log18:36
Akshatcheck this https://gist.github.com/akshatknsl/82f7df535e85659819e918:37
AkshatI have the debug logs18:37
glangeAkshat: http://paste.openstack.org/ <-- use that next time for multi-line pastes18:38
claygAkshat: stop. pasteing. these. lines. in. channel.   - please just link to a gist18:38
claygglange: thanks :)18:38
glangeno, thank you! :)18:38
claygglange: you guys grumbling about this ec stuff over there?  You know we're going to start reviewing the merge to master next week.18:38
Akshatglange: sure18:38
claygglange: ya'll gunna even look at it?  or is there some sinister plan to come through and -2 everything trololololo18:39
glangehahah18:39
Akshathttp://paste.openstack.org/show/197210/18:40
Akshatclayg: These are the same logs in debug, they give much more detail18:40
*** annegentle has quit IRC18:40
*** annegentle has joined #openstack-swift18:41
*** Guest____ has joined #openstack-swift18:41
*** panbalag has quit IRC18:46
claygMar 27 11:31:20 dfw-appblx061-25 swift: SIGTERM received  <- are you doing like failure testing?  stopping process during benchmark?18:48
claygbecuase *that'll* log some errors :P18:48
Akshatno failure testing18:49
Akshatit was too slow18:49
Akshatso killed the process18:49
Akshatto paste you the logs18:49
*** nshaikh has joined #openstack-swift18:49
AkshatThere is a trace for container update error18:50
AkshatIt points to error in /usr/local/lib/python2.7/dist-packages/swift/obj/server.py18:50
AkshatFile "/usr/local/lib/python2.7/dist-packages/eventlet/green/socket.py", line 60, in create_connection#01218:51
AkshatI have been stuck with this since days now18:52
Akshat:(18:52
*** tsg has joined #openstack-swift18:55
*** tsg_ has joined #openstack-swift18:57
*** tsg has quit IRC19:00
Akshatclayg: what can be my next steps19:00
ctennisit looks to me like you don't have servers running on 10.65.53.241 on ports 6000 and 6001...hence the connection refused errors19:03
Akshatthey are running19:03
AkshatI verified telnet and netstat19:04
ctennisyou may need to use something like tcpdump to understand why it can't connect then19:05
ctennisperhaps you're hitting a system resource limitation19:05
Akshatcould replication be the bottleneck19:08
ctennisthere's also nothing in this log indicating connections to anything except 10.65.53.241, so if you have 8 nodes it doesn't reflect in this log19:08
ctennisthat seems unlikely to me19:08
*** nshaikh has left #openstack-swift19:09
AkshatI will try few things as suggested19:13
Akshatwill update you ctennis and clayg19:13
AkshatThanks all19:14
claygctennis: thanks19:17
AkshatJust one question19:18
AkshatI have a node with 23 disks19:18
Akshatcan a single object/container server cater to all 2319:18
ctenniswell Akshat you should run multiple workers not just a single process19:20
AkshatI have a 32 core machine and 32 workers19:20
ctennisok that will work fine19:20
*** gsilvis has quit IRC19:21
Akshatwhat is usual tps for PUT in swift19:22
AkshatI mean you have benchmarked19:22
*** gsilvis has joined #openstack-swift19:22
*** Akshat has quit IRC19:25
*** Akshat has joined #openstack-swift19:26
sweeperAkshat: over 900019:26
*** joeljwright has quit IRC19:28
openstackgerritClay Gerrard proposed openstack/swift: Make ECDiskFile require a fragment index  https://review.openstack.org/16807619:36
*** devlaps has quit IRC19:36
*** Akshat has quit IRC19:37
*** Guest____ has quit IRC19:40
openstackgerritClay Gerrard proposed openstack/swift: Add Fragment Index filter support to ssync  https://review.openstack.org/16518820:08
claygidk.... i'm really staring to like the object-recoder20:11
claygit's the truc - reconstructor truct truck truckt truct tr ct tr ct truct reconstructor reconstructor reconsturct - it's hard20:13
*** acoles_away is now known as acoles20:27
claygacoles: you're back!?20:31
claygi'm digging this make/parse_on_disk_filename man - thanks for that20:31
acolesclayg: i am just for a while. i'm just looking at your changes.20:32
claygi'm redoing the recon change now - it's also digging on it - tests are getting better20:32
claygdamnit!  the recoder change20:32
acolesclayg: i just had to take my son to cricket training and wrote some more tests for yield_hashes while i was waiting so will try to push those up20:32
acolesclayg: fixer fixer fixer!20:32
claygfixer - recoder - reconstrcutor - everything is all on the left hand - I think i need a dovark or something20:33
claygacoles: i was going to give you a hard time about writing tests during baseball practice - but I've totally been missing will's practice for like three weeks now20:34
claygi guess it's better to be there and be destracted than to onot be there :\20:34
acolesclayg: oh i wasn't there i sit outside in the car - he's 16 and doesn't want me around :P20:35
acolesclayg: so yeah you parser more bullet proof, cool20:36
acoless/you/you made/20:36
acolesclayg: dict return, cool. can we start sending dicts in ssync? i'd like that20:38
openstackgerritClay Gerrard proposed openstack/swift: Erasure Code Reconstructor  https://review.openstack.org/13187220:39
claygacoles: now that's an idea20:39
claygmaybe json or msgpack - even csv is fine i the parser on the other end can throw out trailing items20:40
acolesclayg: did you get chance to look over this (i don't expect you to have had time!) https://trello.com/c/UjVTwXj7/154-optimize-ssync-to-not-replicate-data-file-when-only-durable-is-missing20:40
claygwe should sneak that fix in now acctually20:40
acolesclayg: if we are going to change the protocol we *must* make it extensible otherwise it will have to change again to do the right thing for meta files20:41
claygacoles: well csv you can just add to the end - it works - we've been doing it with log parsing lines for years20:42
claygi hate json, we could use query string encoding, msgpack is nice because it only has byte arrays so it never screws you on unicode20:42
claygand can have non string keys20:43
claygand it has good cross platform support20:43
acolesclayg: yes, but we may need to have optional pieces like durable timestamp for EC but not there for repl so having k,v pairs is useful, although more verbose20:43
claygredbo: what's the bomb diggity serailization format for go?  surely there's something better than json the hipsters are using20:43
claygacoles: true dat20:44
claygacoles: you *know* we are changing the REPLICATION verb to SSYNC20:44
claygso.... like..... you're not going to have old ssync processes talking to the new endpoints while you UUUUUUppppgrAAde20:45
claygwe should *DO IT*20:45
acolesclayg: of course20:45
claygnotmyname: look more stuff to do like... *today*20:45
acolesis notmyname around today?20:46
claygtaxes?  i don't know why this man has to spend three days on taxes - it's like he has overseas investmnets or something20:46
claygalso - I think the deadline is in like a couple of weeks?  my wife has that stuff filed in like Janurary.20:47
acolesthree days in a taxi sounds like a hell of a journey20:47
acolesoh taxes20:47
clayglol20:47
acolesthought that was your speling agin20:47
claygacoles: so I sorta think there should be something plumbed into diskfile_from_hash that's just like "create a durable if you have this file"20:48
acolesclayg: speaking of wives, i'd better get these new tests added20:48
claygyeah i really shoulnd't be allowed to communicte in written word without a spellchecker :\20:48
* acoles goes to look who calls diskfile_from_hash20:49
openstackgerritClay Gerrard proposed openstack/swift: wip: ec reconstructor probe test  https://review.openstack.org/16429120:49
clayga'ight jenkins do your thing20:49
claygacoles: the reciever - if it has someone wanting to push it a ts then it knows the remote end has a .durable for that file - so if it also has that file/ts but not durable - when it goes to get_from_hash it could also be like and feel free to make this timestamp durable if it's not already20:50
acolesclayg: uhuh, so ssync_receiver just fixes up the durable20:50
acolesyeah, that20:51
claygit's a cheap hack - just some plumbing20:51
claygnot as good as k/v ssync protocol20:51
claygin the missing check updates20:51
claygwe really should do that20:51
claygi'll look at it - but i need to shut down an head into the office20:51
claygit's already like mid afternoon out here20:51
acolesk well i need to go reaquaint with my family20:52
claygbut like i don't know... i was doing stuff20:52
clayggood luck with that - I think I've got that on my calander for mid-april?20:52
acoleslol20:52
-openstackstatus- NOTICE: Gerrit maintenance commences in 1 hour at 22:00 UTC http://lists.openstack.org/pipermail/openstack-dev/2015-March/059948.html21:01
*** lcurtis has joined #openstack-swift21:01
mattoliverauMorning21:09
acolesmattoliverau: good morning!21:09
mattoliverauacoles: Good evening :)21:09
*** annegentle has quit IRC21:10
*** csmart has quit IRC21:13
*** csmart has joined #openstack-swift21:13
openstackgerritAlistair Coles proposed openstack/swift: Add Fragment Index filter support to ssync  https://review.openstack.org/16518821:14
acoles^^ just added tests21:14
*** gyee has joined #openstack-swift21:14
*** jrichli has quit IRC21:18
acolesmattoliverau: hey it was great to overlap with you but i a, shutting down now, have a good weekend!21:19
mattoliverauThe pleasure was mine, av a great weekend, go and enjoy your family :)21:21
*** acoles is now known as acoles_away21:22
*** thumpba has joined #openstack-swift21:35
*** mahatic has quit IRC21:40
*** annegentle has joined #openstack-swift22:04
claygwft are you doing gerrit?22:05
-openstackstatus- NOTICE: Gerrit is offline for maintenance, ETA 22:30 UTC http://lists.openstack.org/pipermail/openstack-dev/2015-March/059948.html22:05
*** ChanServ changes topic to "Gerrit is offline for maintenance, ETA 22:30 UTC http://lists.openstack.org/pipermail/openstack-dev/2015-March/059948.html"22:05
*** RayAngelone has quit IRC22:06
claygoh sure - now you tell me22:06
claygsrly, i don't know how to work now22:07
claygi don't think dvcs work the way I think they do22:07
mattoliverausigh.. thanks gerrit22:09
claygzaitcev: y u no in channel!?22:10
*** Nadeem has joined #openstack-swift22:14
torgomaticbash: line 1:  2789 Segmentation fault      (core dumped) nosetests -s test.unit.proxy.test_server:TestObjectECRangedGET.test_multiple_ranges22:14
torgomaticcan I go home now?22:14
claygtorgomatic WINS - FATALITY22:15
mattoliveraulol, a day isn't over until your code seg faults :P22:30
*** erlon has quit IRC22:31
mattoliverauWell on the plus side, gerrit seems to be back22:32
*** ChanServ changes topic to "Review Dashboard: http://goo.gl/uRzLBX | Overview Dashboard: http://goo.gl/2By1qv | EC status: https://gist.github.com/notmyname/fd006c061ccb28e8ecfc | Logs: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/"22:33
*** welldannit has joined #openstack-swift22:49
notmynamehello22:51
notmynameI'm here now22:51
notmynamenot doing taxes today. worse: I had to do a sales call22:51
notmynameacoles_away: ^22:51
mattoliveraunotmyname: moring22:53
notmynamewhat have I missed today?22:54
notmynameclayg: are we happy today? or sad?22:56
mattoliverautorgomatic is seg faulting everything so wants to go home, and clayg isn't swearing enough.. so he must be fine.22:58
*** gyee has quit IRC22:58
openstackgerritClay Gerrard proposed openstack/swift: Don't let api version be a suggestion  https://review.openstack.org/16850923:01
clayga'ight gerrit what are you doing?23:01
notmynameclayg: ah, good patch23:02
*** rdaly2 has quit IRC23:07
claygwell - maybe - half of the commit message is like "??? maybe ??? is this ???"23:10
claygglange: ^ you guys have lots of paths in logs23:10
claygok - so gerrit is back up - we can get back to work23:11
notmynamewow, did you see the ML thread "[openstack-dev] [swift] swift memory usage in centos7 devstack jobs"?23:12
claygyeah interesting23:13
claygI was thinking it was like that other issues we were tracking - but it was all RSS - so my first guess was libraies23:13
claygI honestly don't know how he did that output where he ... how did he phrase it "dug into the heap"23:14
* clayg is such a johnny at ops23:14
openstackgerritClay Gerrard proposed openstack/swift: Don't let api version be a suggestion  https://review.openstack.org/16850923:15
claygoops - forgot the bug #23:15
*** annegentle has quit IRC23:19
notmynameclayg: 400 seems to fit (and makes more sense IMO than 412) http://tools.ietf.org/html/rfc7231#section-6.5.123:26
claygso the two existing behaviors were 404 and 412 - and you choose 400?23:29
claygYeah I can see that.23:29
notmynameI'd prefer 412 over 404, but I was basing 400 on your distaste for 412 (and I think you're right according to the rfc)23:30
notmyname400 > 412 > 404 IMO23:30
*** cebruns has joined #openstack-swift23:33
notmynameclayg: I'm about to have to get on a call, but I was working on a patch for the version check23:42
notmynameclayg: do you want a gist of my WIP diff or the thing I found? or would you rather I just push over it tonight?23:43
notmynameclayg: gerrit comment left. gotta run23:47
*** lcurtis has quit IRC23:47
*** Nadeem has quit IRC23:52
claygoh you know what - meant to do lstrip - but i didn't think about vvvv123:58
claygi suppose we could just make a list of accepted version strings - if we think we can get in all the ones we care about23:59

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