Thursday, 2014-03-20

*** saschpe has quit IRC00:00
*** saschpe has joined #openstack-swift00:06
*** matsuhashi has joined #openstack-swift00:29
claygtorgomatic: well I don't know to solve the "can't delete until everything is enqueued" problem - but i'm pretty sure we should move him out of the way first thing so that he can't continue to poison the world, even if it means teaching another daemon to look for these moved-out-of-the-way-poisoned-dbs00:29
claygidk, I'll try to reserve judgement until I finish looking at https://review.openstack.org/#/c/80731/00:30
claygnope, the change to the container server makes me feel like a move-out-of-way-for-async-drain would be a win on both sides, I think a fork out of the container-auditor would be a good plan00:37
* clayg wonders why the container and obj updaters lazy load the ring...00:40
*** fifieldt has quit IRC00:47
portantenotmyname: you around?01:01
portanteregarding atlanta summit01:01
portanteare most folks flying in on monday, leaving friday?01:01
claygportante: what time to keynotes start on Monday?  I imagine some folks will show up on Sunday night01:02
portanteyes, was wondering about that01:02
claygit seems like the afternoon on the last day of the summit keeps getting pushed back later and later, i'd guess some folks will stick around until Saturday too :\01:02
claygwe did that in HK - but that was partially because of the long flight home - the other part being... Friday night in HK!01:03
portante;)01:03
portanteso clayg, are you planning on attending atlanta?01:06
portantezaitcev: you around?01:06
zaitcevportante: yes01:06
claygportante: yeah I'm planning on being there01:06
*** d89 has joined #openstack-swift01:06
portanteare you flying in sunday, leaving sat?01:06
portantezaitcev, too?01:06
zaitcevportante: flying to where?01:07
portanteatlanta01:07
portanteor are you driving from across the country?01:07
zaitcevI don't have the budget and I decided not to pay my own way in this cycle01:07
zaitcevAt least until we know if I can make hackathon01:07
portanteclayg: did you already book your travel?01:13
claygportante: not yet!01:14
portantedude, atc expires on the 21st01:14
portante;)01:14
claygportante: ?  I got my atc tickets - just haven't booked flights/hotel?01:15
portanteah, cool01:15
claygthere's no rooms "at the conference" this year is there?  it's like portland where everyone just gets rooms whereever and commutes/walks to the conference?01:16
portantethe conf center has walkway to nearby hotels, they have rooms blocked at the westin and another place01:16
claygportante: yeah it looks like we better get on that - but I don't think there's a deadline other than availibility...01:17
claygoh no... i'm wrong there's a deadline01:17
claygoh but it's in April not March01:17
claygportante: YOU'RE FREAKING ME OUT MAN!01:17
portanteso I booked the room for monday to friday, but yeah I am freaking out because fares start to rise soon01:18
claygportante: you should book all the rooms and then scalp them01:18
portanteI am cheap ol' hacker01:18
portante;)01:18
claygheh01:18
*** fifieldt has joined #openstack-swift01:22
*** nosnos has joined #openstack-swift01:25
*** dvas_ has quit IRC01:31
openstackgerritClay Gerrard proposed a change to openstack/swift: Fix changing of storage policy index  https://review.openstack.org/7253601:33
claygtorgomatic: how on earth did you ever figure out the ref syntax to push to gerrit outside of git review like that?  did you have to like look at the git review source code?  is it hiding in my .git/config somewhere? what does the "for/feature" part even mean?  what's it look like if you wanted to do that for a change against master?01:35
torgomaticclayg: I worked with gerrit before it was cool ;)01:36
claygwhoa01:36
claygaren't you on a train right now?01:36
torgomaticback in a previous job we used Gerrit, but we didn't have any fancy-pants "git-review" command, so we did it the hard way01:36
torgomaticclayg: welcome to THE FUTURE :)01:36
torgomaticbut yeah, I've got about 5-10mins of tethering before my phone overheats and craps out01:36
clayglol01:37
torgomaticso, to push for master, it's $ git push gerrit HEAD:refs/for/master/topicname (might also be refs/publish/master/topicname; I think one's deprecated)01:37
claygi don't know how you find room to bust out your laptop on the train, I can't do it on the light-rail, but bart gets croweded too01:37
torgomaticclayg: the 6:30 train in the last car usually has seats; 6:15 or earlier is right out01:38
*** chandan_kumar has joined #openstack-swift01:53
creihtclayg: https://github.com/pandemicsyn/fgerrit/blob/master/README.md01:54
* clayg prepares for a laugh01:55
creihtit is actually quite awesome01:55
*** shakamunyi has joined #openstack-swift02:00
*** nosnos_ has joined #openstack-swift02:16
*** nosnos has quit IRC02:19
*** gyee has quit IRC02:20
*** saschpe has quit IRC02:32
*** saschpe has joined #openstack-swift02:33
*** saurabh_ has joined #openstack-swift02:59
*** saurabh_ has joined #openstack-swift02:59
madhuri_clayg: Can you please have a look https://review.openstack.org/#/c/78530/ ?03:18
madhuri_clayg: I want to provide fix for the incorrect behaviour.03:19
*** chandan_kumar has quit IRC03:22
claygyou mean where sending an empty header just ignores the header?  object metadata is already "reset" on every "update"03:33
claygI could imagine a client that is setting X-Meta-Magic: do-not-care and then checking "X-Meta-Magic" in resp.headers03:34
claygin that case it would be a breaking api change if a similar client was using a newish curl with -H "X-Meta-Magic;" or a decent client that lets you send empty headers03:34
claygmadhuri_: be a decent thing to fix up in an api version bump though I think03:35
claygI only mention it as an potentially breaking change because we had similar api cleanup's bite us in the past - swift's api has been stable for a LONG time anything that's client faceing and works today is probably being used by some client somewhere03:36
claygyou can put up the patch tho; if you were wondering if some core might reject it as change in the api tho... well that's probably warranted03:36
claygdfg: glange: gholt: ^ re changing storing empty metadata headers on objects03:37
madhuri_clayg: I was just woried about whether it would have any other bad impact.03:37
claygi don't think anything in swift core relies on the behavior - hence the lack of testing for it ;)03:37
claygbut I was cool with the test being added since it would serve as a warning to anyone thinking about chaing it ;)03:38
claygjust didn't realize it'd be the same guy that wrote the test!03:38
* clayg fully admits this is just one guys opinion03:38
claygbest way to get consensus would be a working patch - not sure I can offer any guidance other than fair warning03:39
claygit's probably a trivial change if you want to take a stab at it03:39
madhuri_clayg: I am new to swift and was wondering whether such patch would be accepted or not?03:39
claygany reason for doing so?  I mean do you know of a client that's trying to do this and having a bad time because of the differences in container and object metadata?03:39
madhuri_I am neither much aware whether it is incorrect behaviour or not.03:40
claygmadhuri_: I don't have a crystal ball (not trying to be snarky!) I just don't know how others would feel - my knee jerk having been bit in the past is "no backwards incompatible changes to client facing api behavior EVAR!!!"03:40
madhuri_No, it's just that I wanted to contribute to swift ;)03:41
claygmadhuri_: if you're looking for something that folks would definately be receptive too I'd search on launchpad for open "bugs" with low-hanging-fruit tag - or just look for gaps in unit test coverage03:41
madhuri_I would be really grateful to you for that :)03:42
claygalso you can review patches, every -1 "needs a better commit message" or -1 "this needs more tests"03:42
clayg^ helps03:42
madhuri_Yeah. I will try to do that too03:43
madhuri_Thanks clayg in tonnes :)03:43
claygthis might work for the low-hanging-fruit tag -> http://goo.gl/x7ZD5S03:44
claygbenchmark it and have fun!03:44
claygmadhuri_: oh oh oh!  you know one that I would just hug someone for?03:44
claygwe have a swift-obj-info tool in bin/ that's great for objects, and I wish we had a swift-db-info tool for containers/accounts03:45
madhuri_clayg: Definiterly I will work upon it03:45
claygesp when I'm trying to see what's going on with a replica that has a .pending file in place I always end up in a repl to commit_puts - what a pita - be great to have a helpful cli that lets me "for db in $(find /srv/node*/sd*/containers -name \*.db); do swift-db-info $db --commit; done"03:46
madhuri_swift-obj-info what is it for?03:46
clayginspecting metadata on a file on disk (mostly)03:46
claygit has an option to do a md5 check03:46
*** matsuhashi has quit IRC03:47
claygoh... i said "benchmark" that link - i ment "bookmark" - dunno if that was an obvious typo or not03:47
madhuri_swift-obj-info, this idea sounds great to me.03:48
clayghrm... there's acctually a lot less low-hanging-fruit that I realized - might need to do some bug triage :\03:48
madhuri_Will start working on it today itself. I mean now.03:48
claygcool!03:48
claygzaitcev: portante: does gluster have anything like swift-obj-info?  Dunno if there's a better name for a container/account equivilant than swift-db-info?03:49
madhuri_clayg: I must say you are a great advisor :)03:49
claygi guess you could just make two tools swift-container-info and swift-account-info - probably be worth it to have most of the code rely on the broker anyways, then the bin script would just say:  swift.common.utils.display_backend_info(AccountBroker|ContainerBroker)03:50
clayggl!03:51
zaitcevclayg: sorry, I'm almost entirely clueless about what GlusterFS has in administration tool space.03:51
zaitcevAlso, it's swift-object-info, not swift-obj-info.03:51
* clayg hangs his head in shame03:52
madhuri_clayg: I have looked for it. But there is no such tool for Account/Container.03:52
claygmadhuri_: right!  I was trying to trick you into writing one for me03:52
madhuri_Sure. I would love to :)03:52
zaitcevyeah, it's sqlite3(1) time03:52
claygzaitcev: well I was thinking he might get away just using the broker?03:53
zaitcevoh03:53
claygmost of the time my for loops just sqlite3 --line $db "select * from container_stat"03:53
zaitcevpython and then import03:53
clayg^ yeah that!03:53
zaitcevwell, yes, that's what I do too03:53
zaitcevyou have to find it first with swift-get-nodes03:54
claygzaitcev: the part that gets annoying for me is when I want to also commit the .pending files; my oneliners start to take up many lines...03:54
zaitcevclayg: I see you're more serious about it than I ever was.03:55
claygzaitcev: not serious enough to acctually write the tool - but apparently serious enough to try and hound poor madhuri_ into doing it!03:56
madhuri_clayg: I will do it. It will be a good start for me.03:58
madhuri_clayg: See you later. Going to have my breakfast. Thank you :)04:03
*** saju_m has joined #openstack-swift04:12
*** haomaiwang has quit IRC04:20
*** haomaiwang has joined #openstack-swift04:20
*** otoolee has quit IRC04:22
*** otoolee has joined #openstack-swift04:22
clayghrmmmm... only managed to get 10 things into low-hanging-fruit - sorry for the lp email barrage04:25
*** matsuhashi has joined #openstack-swift04:31
claygpeluse: so that .pending_file change is turning out to be a real mess when it comes time to commit_puts - I'm going to try and benchmark a get_info call inside of put_object, but I imagine it'll be cheaper to hit the stats table during merge time (because the triggers are going to need it anyway) rather than during put_object (who currently doesn't even need to open the database)04:31
claygbenchmarking will tell...04:31
*** haomaiw__ has joined #openstack-swift04:51
*** haomaiwang has quit IRC04:55
*** zaitcev has quit IRC04:56
madhuri_clayg: there?04:58
claygi'ma say "no"04:59
madhuri_Need some help05:00
claygnp, just ask05:00
madhuri_swift-container-info must display all the information regarding a container. Right?05:00
madhuri_Like no. of objects, ring location, bytes used etc..05:01
claygmadhuri_: I'd just take everything that broker.get_info returns and put it on the screen05:01
madhuri_This need to reed from container_stat table of container sqlite db file.05:01
clayg^ side benifit of commint .pending05:01
madhuri_Ok.05:01
claygmeh... try and use the broker for a first pass if you can05:02
madhuri_.pending in sense, displaying all the pending entries in the file05:02
claygoh... maybe - I was just thinking that .get_info is going to call commit_puts_stale_ok for you anyway - not sure there's an interface to turn that off or if the tool needs one05:03
madhuri_And same for the account too?05:03
claygi think that'd be ok05:03
madhuri_But I can do that without using get05:03
madhuri_*get_info method05:03
madhuri_Rather I can use sqlite3 to do that for me05:04
claygyou might look at what get_info does - I think you'd end up writing more or less the same code that's already there - sorry if it seems trivial to just use the broker05:04
madhuri_I have looked at it but I found the same problem _commit_puts_stale_ok() :(05:05
claygwhat's the "probleme" - that it commits the .pending?  that's like probably more than 50% of what I want - I'd consider a --no-commits option to be sorta "bonus"05:07
claygbut even then I might go after it by "broker = Broker(db_file); broker._commit_puts = lambda *args, **kwargs: None"05:08
madhuri_So I will have to look for a way to turn it off when needed05:08
claygmonkey patch baby!05:08
* clayg is shooting from the hip - you do whatever looks best to you05:09
madhuri_Ok. Got it05:09
*** chandan_kumar has joined #openstack-swift05:10
*** gvernik has joined #openstack-swift05:10
madhuri_clayg: Thank you :)05:11
claygi thought you were going to get something to eat?05:11
*** gvernik has quit IRC05:12
madhuri_Ohh..05:13
madhuri_Wondering ever have you tasted Indian cuisines?05:13
* clayg loves me some pakora05:14
claygor tandoori05:15
*** chandan_kumar has quit IRC05:17
madhuri_clayg: Amazed :)05:19
madhuri_Next time, I will surely bring you pakora ;)05:19
*** nosnos has joined #openstack-swift05:19
*** nosnos_ has quit IRC05:23
claygpandemicsyn: I'm trying to benchmark this thing and got all my tcp connections ate up - so I changed /proc/sys/net/ipv4/tcp_tw_recycle to 1 <- is that insane?  it sure let me keep opening connections!05:27
claygredbo: ahale: ^05:28
*** Trixboxer has joined #openstack-swift05:29
claygpeluse: oh god, put_object is like 1/4 of the speed with a get_info call stuck in there :\  - something like 70% slower :'(05:39
claygfml05:39
*** nosnos_ has joined #openstack-swift05:49
*** nosnos has quit IRC05:51
*** haomaiwa_ has joined #openstack-swift05:57
*** ppai has joined #openstack-swift05:57
*** haomaiw__ has quit IRC06:00
*** saju_m has quit IRC06:02
*** saju_m has joined #openstack-swift06:04
*** saju_m has quit IRC06:07
*** saju_m has joined #openstack-swift06:08
*** nshaikh has joined #openstack-swift06:10
*** d89 has quit IRC06:12
*** d89 has joined #openstack-swift06:16
claygsweet, I think i cracked it06:26
claygnotmyname: it's cool - storage policies is back on!06:26
*** matsuhashi has quit IRC06:28
*** matsuhashi has joined #openstack-swift06:30
*** saju_m has quit IRC06:35
*** bvandenh has joined #openstack-swift06:59
*** bvandenh has quit IRC07:07
*** shakamunyi has quit IRC07:15
*** psharma has joined #openstack-swift07:18
openstackgerritClay Gerrard proposed a change to openstack/swift: Container Confict on obj update with wrong Storage-Policy-Index  https://review.openstack.org/7973107:29
*** bvandenh has joined #openstack-swift07:29
openstackgerritClay Gerrard proposed a change to openstack/swift: Container Confict on obj update with wrong Storage-Policy-Index  https://review.openstack.org/7973107:34
*** shakamunyi has joined #openstack-swift07:41
*** shakamunyi has quit IRC07:45
*** mrsnivvel has joined #openstack-swift07:51
*** saju_m has joined #openstack-swift07:56
*** tburnes has quit IRC08:08
*** tburnes has joined #openstack-swift08:09
*** Rock____ has joined #openstack-swift08:10
*** mmcardle has joined #openstack-swift08:26
*** nosnos has joined #openstack-swift08:33
*** nosnos_ has quit IRC08:37
*** shakamunyi has joined #openstack-swift08:42
*** shakamunyi has quit IRC08:46
*** mlipchuk has joined #openstack-swift08:49
*** nacim has joined #openstack-swift08:52
*** bada_ has quit IRC08:59
*** dvas has joined #openstack-swift08:59
*** bada_ has joined #openstack-swift09:00
*** dvas has quit IRC09:04
*** dvas has joined #openstack-swift09:15
*** tanee-away is now known as tanee09:21
*** tanee is now known as tanee-away09:21
*** tanee-away is now known as tanee09:21
*** jamieh has joined #openstack-swift09:36
*** jamieh is now known as Guest9441409:36
openstackgerritA change was merged to openstack/swift: Merge branch 'master' into feature/ec  https://review.openstack.org/8134509:38
openstackgerritA change was merged to openstack/swift: Store policy index in container_stat table  https://review.openstack.org/7170409:38
openstackgerritA change was merged to openstack/swift: move cors-test-page to literal include  https://review.openstack.org/8116809:38
*** dvas has quit IRC09:42
*** shakamunyi has joined #openstack-swift09:43
*** dvas has joined #openstack-swift09:44
*** d89 is now known as Dharmit09:47
*** shakamunyi has quit IRC09:47
*** Guest56062 has quit IRC09:51
*** taras_ has joined #openstack-swift09:51
*** dvas has quit IRC09:56
*** dvas has joined #openstack-swift09:56
*** nosnos has quit IRC09:59
openstackgerritClay Gerrard proposed a change to openstack/swift: Container Confict on obj update with wrong Storage-Policy-Index  https://review.openstack.org/7973110:02
*** nosnos has joined #openstack-swift10:09
*** bada_ has quit IRC10:15
*** Rock____ has quit IRC10:19
portanteclayg: yes, I think it does10:31
*** shakamunyi has joined #openstack-swift10:43
*** shakamunyi has quit IRC10:48
*** fifieldt has quit IRC10:49
openstackgerritClay Gerrard proposed a change to openstack/swift: Add "If-None-Match: *" support to PUT  https://review.openstack.org/8164610:52
*** chandankumar_ has quit IRC11:00
*** chandankumar has joined #openstack-swift11:00
*** dvas has quit IRC11:01
*** matsuhashi has quit IRC11:01
*** dvas_ has joined #openstack-swift11:02
*** matsuhashi has joined #openstack-swift11:24
portanteclayg: go to sleep man!11:27
*** a1|away is now known as JelleB11:29
*** dvas_ is now known as dvas11:36
*** shakamunyi has joined #openstack-swift11:44
*** shakamunyi has quit IRC11:48
*** fifieldt has joined #openstack-swift11:51
*** matsuhashi has quit IRC12:08
*** saju_m has quit IRC12:09
*** fifieldt has quit IRC12:10
*** ppai has quit IRC12:10
*** matsuhashi has joined #openstack-swift12:12
*** dvas has quit IRC12:12
*** matsuhashi has quit IRC12:18
*** JuanManuelOlle has joined #openstack-swift12:19
*** Dharmit has quit IRC12:23
*** ppai has joined #openstack-swift12:24
*** matsuhashi has joined #openstack-swift12:24
*** saju_m has joined #openstack-swift12:26
*** jairo has left #openstack-swift12:40
*** shakamunyi has joined #openstack-swift12:45
*** nosnos has quit IRC12:46
*** tongli has joined #openstack-swift12:47
*** matsuhashi has quit IRC12:47
*** shakamunyi has quit IRC12:49
*** saju_m has quit IRC12:53
*** piyush1 has joined #openstack-swift13:05
*** saju_m has joined #openstack-swift13:06
*** tdasilva has joined #openstack-swift13:09
*** zul has quit IRC13:12
*** zul has joined #openstack-swift13:15
*** psharma has quit IRC13:16
*** changbl has quit IRC13:16
*** mmcardle has quit IRC13:16
*** ppai has quit IRC13:21
*** saju_m has quit IRC13:23
*** shakamunyi has joined #openstack-swift13:32
*** dmsimard has joined #openstack-swift13:33
*** ppai has joined #openstack-swift13:33
*** PradeepChandani_ has joined #openstack-swift13:33
*** mkollaro has joined #openstack-swift13:36
*** PradeepChandani has quit IRC13:36
*** saju_m has joined #openstack-swift13:39
*** mmcardle has joined #openstack-swift13:40
*** PradeepChandani_ has quit IRC13:44
*** piyush1 has quit IRC13:45
*** PradeepChandani_ has joined #openstack-swift13:45
*** byeager has joined #openstack-swift13:46
*** byeager has quit IRC13:46
*** byeager_ has joined #openstack-swift13:46
*** saju_m has quit IRC13:48
*** jergerber has joined #openstack-swift13:58
luisbgmorning14:06
*** piyush1 has joined #openstack-swift14:14
*** tanee is now known as tanee-away14:20
*** ppai has quit IRC14:22
*** tanee-away is now known as tanee14:25
*** judd7_ has joined #openstack-swift14:37
*** judd7_ has quit IRC14:42
*** judd7_ has joined #openstack-swift14:44
*** dmsimard1 has joined #openstack-swift14:58
*** tanee is now known as tanee-away14:58
*** dmsimard has quit IRC14:59
*** judd7_ has quit IRC15:03
openstackgerritBabu Shanmugam proposed a change to openstack/swift: RADOS (CEPH) DiskFile Backend  https://review.openstack.org/6021515:07
*** judd7_ has joined #openstack-swift15:12
*** changbl has joined #openstack-swift15:18
*** d89 has joined #openstack-swift15:20
*** judd7_ has quit IRC15:20
openstackgerritA change was merged to openstack/swift: Allow pre-1970 dates in If-[Un]Modified-Since  https://review.openstack.org/8073415:20
*** Guest94414 is now known as jamie_h15:21
portanteclayg: regarding gluster-swift, there is a bin/gluster-swift-print-metadata which prints the swift metadata contents, but nothing extensive like swift-obj-info, since an ls -l on the full object name also works15:22
portanteanticw: we are working collecting the data for that, we have stood up a 3 node cluster (p/a/c/o), 10 ge front/back nics, 48 GB of memory each node, 12 1TB disks on each, gonna fill to 60%, time the auditor, install this change, time the auditor15:24
*** gyee has joined #openstack-swift15:25
*** byeager_ has quit IRC15:26
*** byeager has joined #openstack-swift15:26
*** krtaylor has quit IRC15:27
*** shakamunyi has quit IRC15:29
*** byeager has quit IRC15:30
creihtclayg: ping15:31
creihtI saw your comment about the pep8 stuff, but then it passed pep8 in Jenkins?15:31
creihtoh nm15:32
creihtI see what you did15:32
creihtsilly pep8 :/15:32
creihtclayg: thanks15:32
portantewow, clayg helps out with out saying a word, awesome15:39
portante;)15:39
portantethey call it pep8, but it is really hacking, too, right?15:40
portantecreiht:15:40
*** tdasilva has left #openstack-swift15:44
openstackgerritA change was merged to openstack/python-swiftclient: Use six.StringIO instead of StringIO.StringIO  https://review.openstack.org/7470515:47
creihtportante: heh yeah15:52
*** byeager has joined #openstack-swift15:57
creihtyay openstack politics :/15:59
*** byeager has quit IRC16:04
*** shakamunyi has joined #openstack-swift16:06
*** nshaikh has quit IRC16:10
*** shakamunyi has quit IRC16:10
*** piyush1 has quit IRC16:16
openstackgerritpaul luse proposed a change to openstack/swift: Add Storage Policy Support to Account HEAD  https://review.openstack.org/7374716:22
openstackgerritpaul luse proposed a change to openstack/swift: Container Confict on obj update with wrong Storage-Policy-Index  https://review.openstack.org/7973116:22
*** d89 has quit IRC16:25
notmynamegood morning16:29
portantemornin'16:30
notmynamewow. clayg was busy last night. I guess I shouldn't expect him in the office too soon ;-)16:30
notmynamecreiht: I think we're the last group of people to complain about poor names for things ;-)16:30
*** byeager has joined #openstack-swift16:31
creihtheh16:32
*** byeager has quit IRC16:35
*** piyush1 has joined #openstack-swift16:38
*** piyush1 has quit IRC16:44
pelusenotmyname:  yeah and hats off to you clayg, some nice work on the policy patches last night!16:55
*** changbl has quit IRC17:02
*** mkollaro has quit IRC17:04
*** mkollaro has joined #openstack-swift17:22
*** krtaylor has joined #openstack-swift17:27
*** changbl has joined #openstack-swift17:34
*** booi has quit IRC17:37
*** Trixboxer has quit IRC17:44
*** mlipchuk has quit IRC17:49
*** zaitcev has joined #openstack-swift17:51
*** ChanServ sets mode: +v zaitcev17:51
*** mmcardle has quit IRC17:53
*** mkollaro has quit IRC17:55
*** dmsimard1 is now known as dmsimard17:59
*** mkollaro has joined #openstack-swift18:05
*** nacim has quit IRC18:06
*** jamie_h has quit IRC18:06
*** jamie_h has joined #openstack-swift18:14
*** Gooch has joined #openstack-swift18:27
GoochEvening all18:27
GoochWould anyone be able to tell me where on the server running the object server service the SQLLite database(s) are stored?18:27
GoochWe have our storage nodes running the object server service with SSD boot drives for the OS and spinning disks for the data storage18:28
GoochI'd like to find out if the SQLLite DBs are stored on the SSD or the HDDs :)18:28
glangeGooch: objects don't have DBs, just containers and accounts18:30
portanteGooch: hmm, can you start by looking at your config file for "devices"?18:30
portantewhat does that say, and then check the contents of that directory18:30
portantedf it as well to see where it lives18:31
glangeGooch: you could also run a command called swift-get-nodes18:31
GoochSorry, I'm not the most experianced engineer in this department18:31
glangeno problem18:32
GoochWe have a container listing slow down issue due to the number of objects in certain containers18:32
glangedo you know how many objects in the slow container?18:32
GoochI'm trying to work out if currently the DB that holds the container listings is on spinning disk or SSD18:32
Gooch1M+18:32
glangesee what happens if you run this on a server with swift and your rings:  swift-get-nodes /some/path/container.ring.gz account container18:34
GoochDo you have an example output for that command?18:34
glangehttp://paste.openstack.org/show/73931/18:35
glangethat is what it looks like on my swift all in one18:35
GoochThanks for the output :) How would this help me determin the location of object server DBs?18:36
*** mkollaro has quit IRC18:36
glangeobjects don't have dbs18:37
glangeonly accounts/containers18:37
zaitcevdude there's an ls command right there18:37
zaitcevscroll to the bottom18:37
GoochI guess I've got an incorrect term stuck in my head. What's the name of the service that stores a database of all objects in a container?18:37
zaitcevglange: he's just confused. he needs a container DB18:37
glangezaitcev: ok18:38
glangeGooch: that is a container server18:38
GoochRighto, that sounds like the term I needed.18:38
glangeanother place you might look is your container server configs18:38
zaitcevbut I think it should be easy to find out where devices for a container servers are, even without swift-get-nodes.18:38
GoochDo you know the default configuration for where the container server stores its DBs?18:39
glangezaitcev: yeah, I was telling him that in case he wanted to look for a specifc container db eventually18:39
glangeGooch: look in /etc/swift maybe ?18:39
zaitcevrun  swift-ring-builder /etc/swift/container.builder  and it shows device names, right? Those are mounted under /srv/node, right? Then ssh and check what they are.18:39
GoochMy question can be kept super simple to avoid my infuriating  you guys with my lack of knowledge :)18:40
glangehaha18:40
zaitcevnobody is infuriated, I think18:40
zaitcevAsk away!18:40
GoochI just need to know, on a storage server that runs all services bar the proxy, if container server DBs are stored on the OS drive or the data drives18:40
Goochany help would be really appreciated.18:41
glangeit can be configured to put the db's wherever18:41
zaitcevI would 1) ssh to that server, 2) look at devices= in /etc/swift/container.conf (usually /srv/node), 3) df -k and see what's mounted where18:41
GoochI see. Do you know which configuration option is used to change that?18:41
glangedo what zaitcev is saying :)18:42
GoochOk18:42
glangebut in the container conf, it's devices = something18:42
zaitcevif it's omited, it defaults to /srv/nodes18:42
zaitcever. /srv/node18:42
Goochspinning disks are in the format /srv/node/sd*118:43
GoochWe have one SSD for boot at sda and eight spinning disks for storage at /srv/node/sd*118:43
zaitcevsounds proper18:44
GoochDoes that information help you help me find where the container server DBs are? :)18:44
zaitcevthe are probably in each of these18:44
Goochin /srv/node/sd* ?18:45
zaitcevrun  swift-ring-builder /etc/swift/container.builder, it should be in some safe place on an admin workstation, but some people put them on proxies... so wherever the builder files are at your place18:45
zaitcevthe output is like18:45
zaitcev[root@rhev-a24c-01 swift]# swift-ring-builder container.builder | head -518:46
zaitcev.....18:46
zaitcev             0       1     1    192.168.50.2  6001    192.168.50.2              6001        b1 100.00      87381   -0.0018:46
zaitcevthere's going to be a bunch of them18:46
zaitcevthis one is b1 at 192.168.50.2:600118:47
zaitcevin your case should be sdb, sdc, etc.18:47
GoochYep, I follow18:47
GoochWhat do I do with that information?18:47
zaitcevthese device names are virtual in the sense they are mount point names. see in my case b1 is not even on /dev/b1 :-)  it's just a label18:48
zaitcevso you need to find physical device18:48
zaitcevalthough usually when folks use your naming scheme they try to keep /dev/sdb mounted to /srv/node/sdb, but make sure some joker didn't swp them on you18:49
GoochI see18:49
GoochI don't need to track down the individual DB for each container18:49
GoochI just need an answer on the high level question of "are they on the SSD or on the spinning disk"18:50
*** byeager has joined #openstack-swift18:50
GoochMuch of our environment is quite "default", it's not tuned as much as I'd personally like to see18:50
zaitcevso in my case on 192.168.50.2 it's like18:50
zaitcev/dev/sdb             585775624   1081832 584693792   1% /srv/node/b118:50
zaitcevat that point I just need to discover what kind of media /dev/sdb is18:51
zaitcevhmm18:51
Goochanything in /srv/node is spinning disk. / is SSD18:51
GoochSo if you're telling me that the DBs live within /srv/node then they're on spinning disks :)18:52
zaitcevyes18:52
zaitcevwell, I was trying to remember how to look at /proc/scsi18:52
zaitcevbut in your case there's no alternative18:52
GoochSo are we, based on that info, now sure the SQLLite DBs that store container listings are stored on spinning disks?18:53
zaitcevokay, so for an excercise I cheated and used dmesg on my node18:53
zaitcevsd 4:0:1:0: [sdb] 1172123568 512-byte logical blocks: (600 GB/558 GiB)18:53
zaitcevlooking for 4:0:1:018:53
zaitcevscsi 4:0:1:0: Direct-Access     WD       WD6001BKHG       D1S2 PQ: 0 ANSI: 618:54
zaitcevlooks like a WD Black18:54
zaitcevwhich is spinning18:54
zaitcevCase Closed!18:54
GoochSo the next question then18:54
GoochHow do I move the container server and all it's SQLLite DBs from spinning disk to SSD? :)18:55
Gooch(Hint: Change all my storage nodes to SSD only is not an answer I can afford :) )18:55
zaitcevI would buy a number of SSDs that match replication + handout number (swift-ring-builder will tell what it is for you, but usually 3 + 1).18:56
Goochzaitcev: I have to go now for a break. I really appreciate your help18:56
zaitcevAttach them to nodes that will be hosting containers, fdisk, etc18:56
GoochI'll be back later tonight or maybe tommorow for sure18:56
zaitcevokay18:57
GoochThanks again dude(tte)18:57
ahalei'd probably just makdir /srv/node/ssd, not have anything mounted , disable mount check for account/container and then migrate containers over to them slowly with new rings18:57
zaitcevit's an intriguing possibility if root is large enough18:58
zaitcevwe'll poke him for ls and du outputs later, I'm curious how big those DBs are actually18:59
ahaleyeah true, it does need a decent size root, but can always add ssd later on the mounts if it gets a problem18:59
*** byeager_ has joined #openstack-swift19:06
*** byeager has quit IRC19:09
openstackgerritA change was merged to openstack/swift: Enable object versions for SAIO by default  https://review.openstack.org/8161519:19
openstackgerritA change was merged to openstack/swift: Fix race on container recreate  https://review.openstack.org/8110419:19
claygacoles-: gawd paste.openstack is slow19:28
peluseclayg/torgomatic:  both acct HEAD and 409 patches are fully rebased and ready for business19:35
* clayg really needs to look at the acct HEAD patch :\19:37
claygbut it's so big!19:37
claygcan we just punt on that?19:37
*** tdasilva has joined #openstack-swift19:45
*** vu has joined #openstack-swift19:46
openstackgerritClay Gerrard proposed a change to openstack/swift: additional functional tests for account acls  https://review.openstack.org/8007319:55
*** shri has joined #openstack-swift19:59
*** nacim has joined #openstack-swift20:03
openstackgerritClay Gerrard proposed a change to openstack/swift: Clean up Account ACL sysmeta in AccountController  https://review.openstack.org/8014020:05
*** tusharsg has joined #openstack-swift20:05
openstackgerritClay Gerrard proposed a change to openstack/swift: Harden v2 common.middleware.acl interface  https://review.openstack.org/8018820:11
claygis the ring reload time configurable?20:24
clayglike I know it's paramaterized when you create a Ring - but like is that plumbed through a conf anywhere?20:24
creihtclayg: doesn't look like it is plummed20:27
creihtwould be easy to add though20:28
claygi've never needed it, maybe it's fine20:28
claygwhat's the default like - 30?20:29
creiht1520:29
claygsweet20:29
peluseclayg:  jsut commented in github.  yeah, it would need to be plumbed but nobody requires it now and it would be easy to add20:37
peluseand since the def is 15 I didn't bother to add the plumbing at this point in time20:38
peluseclayg: the acct HEAD patch is kinda big in line count but its pretty simple and more of a small set of large chunks of code as opposed to a big pile of little changes if that helps :)20:39
claygno it doesn't help - but I am still going to need to review it i suppose20:41
peluseI tried to punt on it too but notmyname said no - we need a way to provide/report per policy usage for billing...20:44
*** jamie_h has quit IRC20:44
claygheheh - i was kidding20:45
claygbut it should *obviously* be X-Storage-Policy-Bronze-Object-Count to mirror X-Account-Object-Count rather than X-Storage-Policy-Object-Count-Bronze :D20:46
peluseI actually had it both ways at one point or another believe it or not and settled with adding the policy at the end :)20:50
notmynameback from meetings. should be here most of the rest of the day now20:52
creihtwill the default policy show up as X-Account-Object-Count?20:53
notmynamecreiht: no, the current headers will continue to mean the same thing20:54
torgomatic-Count and -Bytes-Used are sums of everything20:54
notmynameie the sum of everything20:54
creihtahh ok20:54
creihtwell that's still fine20:54
notmynamecreiht: we knew you wouldn't like that, so just didn't even try :-)20:54
creihtjust want to make sure we will not have to update billing systems with the rollout20:54
creihthehe20:55
notmynamecreiht: oh yeah. we've all got billing systems to update20:55
*** krtaylor has quit IRC20:57
pelusecreiht:  here's the patch if you're interested: https://review.openstack.org/#/c/73747/1020:57
* peluse is anxious to see clayg's review of some of his creative python in the acct HEAD patch20:58
*** nacim has quit IRC21:00
*** tdasilva has left #openstack-swift21:01
creihtpeluse: thx21:01
*** JuanManuelOlle has quit IRC21:07
*** tongli has quit IRC21:07
*** greghaynes has quit IRC21:11
claygpeluse: you're python is fine21:13
claygpeluse: that patch is trixy21:13
creihtman clayg, you have been busy21:15
notmynameI just got an email about accepted talks to the summit. I'm assuming others of you should also get some21:15
* creiht is saving his good stuff to get a ticket to paris :)21:16
notmyname:-)21:16
creihtor I might have just been lazy21:16
pelusenotmyname:  indeed21:24
pelusenotmyname:  on the QA cluster thing though, Intel has a break-out room and we can present there21:25
notmynamepeluse: ok. I also made a summit session for ti21:28
*** vu has quit IRC21:32
*** byeager_ has quit IRC22:01
*** byeager has joined #openstack-swift22:01
*** byeager has quit IRC22:05
*** dmsimard has quit IRC22:08
*** byeager has joined #openstack-swift22:14
*** sungju_ has joined #openstack-swift22:23
*** sungju- has joined #openstack-swift22:25
peluseclayg:  I'm heading out for the night - thanks a million for the feedback thus far on the rollup thing, will address those things in the morning (updated patch I mean, comments already posted)...22:27
*** sungju_ has quit IRC22:27
*** byeager has quit IRC22:28
*** byeager has joined #openstack-swift22:28
*** jergerber has quit IRC22:30
*** tburnes has quit IRC22:30
*** tburnes has joined #openstack-swift22:31
notmynamecan we have a "swift 2048"? track->sector->block->drives->inode->(X)FS->server->zone->DC->region->cluster22:31
*** byeager has quit IRC22:33
*** changbl has quit IRC22:47
*** tusharsg has quit IRC23:32
openstackgerritSamuel Merritt proposed a change to openstack/swift: Purge self.policies from Swift  https://review.openstack.org/8194023:34

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