Tuesday, 2014-04-22

*** mwstorer has quit IRC00:09
*** matsuhashi has joined #openstack-swift00:19
*** shri has quit IRC00:44
*** h6w has quit IRC01:18
*** byeager has joined #openstack-swift01:23
*** saschpe has quit IRC01:32
*** nosnos has joined #openstack-swift01:36
*** saschpe has joined #openstack-swift01:37
*** byeager has quit IRC01:40
swillszaitcev: would you be willing to look at my ktrace output to see if you can find what's wrong?01:43
swills(ktrace output is basically the same as strace)01:44
swillsif so, see http://meatwad.mouf.net/~swills/swift.ktrace.txt.gz01:47
zaitcevswills: if my editor can survive 200 meg01:50
swillszaitcev: yeah... use less or something...01:52
swillsall the googling i have done on the exception talk about disk errors01:55
swillsbut given i'm using zfs and there are no errors reported there and using sqlite from commadn line has no problem with the file, i'm finding that hard to believe01:56
swillsoh01:56
swills    def execute(self, *args, **kwargs):01:56
swills        return _db_timeout(01:56
swills            self.timeout, self.db_file, lambda: sqlite3.Cursor.execute(01:56
swills                self, *args, **kwargs))01:56
swillsself.timeout is mentioned in the excep;tion01:57
swillsi wonder if it's simply timing out because things are too slow?01:57
swillshttp://paste.mouf.net/pastes/pi1dakl33decekf2eoe29ioh01:57
swillsis the full trace01:57
swillshttp://paste.mouf.net/pastes/l47l9ipeetqf2a7lvusadm9901:59
swillseasier to read01:59
swills#012  File "/usr/local/lib/python2.7/site-packages/swift/common/db.py", line 64, in _db_timeout01:59
*** baojg has joined #openstack-swift02:00
*** dmorita has joined #openstack-swift02:05
swillsjust ran the tests that come with my python sqlite stuff and it seems mostly OK except something related to hooks02:05
swillsi'm going to rebuild my python and sqlite and python-sqlite stuff and see if that changes anything...02:13
occupanthmph, my proxy is grabbing way more data from the object servers than it's actually serving02:15
zaitcevswills: okay, it's too much to grasp so quickly, but it appears that one thread, 60074, tries to lock the db (at line 8091316), but some other tread closes the file descriptor it was using.02:25
zaitcevswills: if would be grand if you found who closes it and why02:25
zaitcevswills: And no, it's not timing out. Your traceback reported OperationalError, so the exception was raised by sqlite3, and not the eventlet.Timeout that wraps it with with: op.02:27
*** zhiyan_ is now known as zhiyan02:30
*** praveenkumar has joined #openstack-swift02:33
swillszaitcev: oh! wow, ok02:34
swillszaitcev: what file is that?02:34
zaitcevswills: swift.ktrace.txt that I thought you asked me to examine.02:35
swillsi mean, what file is closed02:35
swillsthere are multiple db files, right?02:35
swillsi did see that bit you were talking about but didn't understand it so well02:35
zaitcevI am not knowledgeable about threading model in BSD. In Linux, threads do not share fd space unless they pass special flags to clone().02:36
zaitcevPerhaps we somehow baked that assumption in02:36
swillshttp://stackoverflow.com/questions/6296055/serializing-sqlite3-in-python02:36
swills"The Python SQLite module is not threadsafe."02:36
swillsor so it claims...02:37
zaitcevyeah02:37
swillsi wonder if it's this file /srv/node/1/containers/776/107/c20e998d06390c9dc660790b12c4b107/c20e998d06390c9dc660790b12c4b107.db02:37
zaitcevBut in our case threads are greenthreads that eventlet creates.02:37
zaitcevI'm thinking line 8089675 is the nearest same-pid open02:38
swillsi wonder about line 8089750, does the lack of wal cause the issue?02:40
*** jbs123 has joined #openstack-swift02:41
zaitcevumm no02:41
zaitcevit's EBADF02:41
zaitcevobviously something was there and then it was closed, no matter what's the name02:41
swillsoh, ok, i thought maybe i didn't have wal enabled in my build02:42
*** jbs123 has left #openstack-swift02:44
swillsok, rebuild and reinstalled python and sqlite and python-sqlite stuff02:53
swillsnope, still happening02:55
swillsso i have thread support enabled in both sqlite and python02:56
swillsgot another trace03:02
swillsoh, i think i found the process that closed it03:04
swills08d2ef729088d86e8612c1ce2b2323be is the file...03:05
swillsso i think it's the container server that's closing the file03:06
swillsout from under the container updater03:06
swillszaitcev: http://meatwad.mouf.net/~swills/swift_1.ktrace.txt.gz03:09
zaitcevhow can updater and server share the pid space?03:10
zaitcevI don't think it's possible.03:10
zaitcever, fd space03:10
swillslook in that file for 08d2ef729088d86e8612c1ce2b2323be03:11
swillsdon't worry, i'm sure i'm misunderstanding. :)03:11
openstackgerritPete Zaitcev proposed a change to openstack/swift: Plumb insecure flag to functests  https://review.openstack.org/8843803:13
*** zaitcev has quit IRC03:19
*** matsuhashi has quit IRC03:20
*** nosnos has quit IRC03:32
*** chandan_kumar has joined #openstack-swift04:02
*** chandan_kumar has quit IRC04:10
*** ppai has joined #openstack-swift04:11
*** mrsnivvel has joined #openstack-swift04:18
*** matsuhashi has joined #openstack-swift04:28
*** nosnos has joined #openstack-swift04:37
*** baojg has quit IRC04:48
*** baojg has joined #openstack-swift04:48
*** haomaiw__ has joined #openstack-swift04:49
*** haomaiwang has quit IRC04:52
*** matsuhas_ has joined #openstack-swift05:02
*** matsuhashi has quit IRC05:05
*** baojg_ has joined #openstack-swift05:10
*** baojg has quit IRC05:14
*** nshaikh has joined #openstack-swift05:55
*** haomaiw__ has quit IRC05:56
*** haomaiwa_ has joined #openstack-swift05:56
*** gyee has quit IRC05:56
*** haomaiw__ has joined #openstack-swift05:57
*** taras___ has quit IRC05:58
*** haomaiwa_ has quit IRC06:01
*** chandan_kumar has joined #openstack-swift06:02
*** matsuhas_ has quit IRC06:02
*** madhuri has quit IRC06:04
*** matsuhashi has joined #openstack-swift06:10
*** early has quit IRC06:14
*** early has joined #openstack-swift06:17
*** psharma has joined #openstack-swift06:18
openstackgerritTakashi Kajinami proposed a change to openstack/swift: Fix error log of proxy-server when cache middleware is disabled  https://review.openstack.org/8948806:43
*** chandan_kumar has quit IRC06:49
*** haomaiw__ has quit IRC06:50
*** haomaiwang has joined #openstack-swift06:51
*** chandan_kumar has joined #openstack-swift07:06
*** cheri has joined #openstack-swift07:09
*** Honghui has joined #openstack-swift07:16
*** SkyRocknRoll has joined #openstack-swift07:41
*** SkyRocknRoll has joined #openstack-swift07:41
*** mmcardle has joined #openstack-swift07:42
*** haomai___ has joined #openstack-swift07:50
*** nacim has joined #openstack-swift07:50
*** haomaiwang has quit IRC07:53
*** joeljwright has joined #openstack-swift08:04
*** jamie_h has joined #openstack-swift08:28
*** Dharmit has joined #openstack-swift08:30
*** haomai___ has quit IRC08:34
*** haomaiwang has joined #openstack-swift08:35
*** haomaiw__ has joined #openstack-swift08:45
*** haomaiwang has quit IRC08:45
*** jamie_h has quit IRC09:11
*** jamie_h has joined #openstack-swift09:12
*** chandan_kumar has quit IRC09:15
*** foexle has joined #openstack-swift09:28
*** chandan_kumar has joined #openstack-swift09:28
*** mkollaro has joined #openstack-swift09:31
*** jamie_h has quit IRC09:36
*** jamie_h has joined #openstack-swift09:36
*** jamie_h has quit IRC09:42
*** jamie_h has joined #openstack-swift09:45
*** jamie_h has quit IRC09:52
*** jamie_h has joined #openstack-swift09:53
*** chandan_kumar is now known as chandankumar09:55
*** chandankumar is now known as chandan_kumar09:56
*** dmorita has quit IRC10:35
*** Honghui has quit IRC10:38
openstackgerritYuan Zhou proposed a change to openstack/swift: Fix delete versioning objects when previous is expired  https://review.openstack.org/8820410:48
*** Trixboxer has joined #openstack-swift10:56
*** jamie_h has quit IRC10:56
*** praveenkumar has quit IRC10:59
*** jamie_h has joined #openstack-swift11:00
*** lpabon has joined #openstack-swift11:04
*** baojg_ has quit IRC11:10
*** baojg has joined #openstack-swift11:11
*** baojg has quit IRC11:16
*** lpabon has quit IRC11:27
*** mlipchuk has joined #openstack-swift11:30
*** praveenkumar has joined #openstack-swift11:39
*** mkollaro has quit IRC12:02
*** mkollaro has joined #openstack-swift12:03
*** mmcardle has quit IRC12:04
*** mkollaro1 has joined #openstack-swift12:05
*** mkollaro has quit IRC12:05
*** acorwin has quit IRC12:07
*** acorwin has joined #openstack-swift12:09
*** lpabon has joined #openstack-swift12:29
openstackgerritpaul luse proposed a change to openstack/swift: Add Storage Policy Support to Container Sync  https://review.openstack.org/8646912:30
*** bada has joined #openstack-swift12:32
*** mmcardle has joined #openstack-swift12:33
*** ppai has quit IRC12:39
*** matsuhashi has quit IRC12:43
*** matsuhashi has joined #openstack-swift12:43
*** nshaikh has quit IRC12:44
*** SkyRocknRoll has quit IRC12:45
*** matsuhashi has quit IRC12:48
*** nosnos has quit IRC12:48
*** nosnos has joined #openstack-swift12:51
openstackgerritpaul luse proposed a change to openstack/swift: Add Storage Policy Support to Recon Middleware  https://review.openstack.org/8738712:52
*** nosnos has quit IRC12:52
*** mkollaro has joined #openstack-swift13:00
*** mkollaro1 has quit IRC13:03
*** mrsnivvel has quit IRC13:17
openstackgerritNassim Babaci proposed a change to openstack/swift: Add policy engine to keystoneauth  https://review.openstack.org/8956813:21
openstackgerritNassim Babaci proposed a change to openstack/swift: Add policy engine to keystoneauth  https://review.openstack.org/8956813:26
openstackgerritpaul luse proposed a change to openstack/swift: Add Storage Policy Documentation  https://review.openstack.org/8582413:26
openstackgerritNassim Babaci proposed a change to openstack/swift: Add policy engine to keystoneauth  https://review.openstack.org/8956813:28
openstackgerritNassim Babaci proposed a change to openstack/swift: Add policy engine to keystoneauth  https://review.openstack.org/8956813:29
*** nacim_ has joined #openstack-swift13:40
*** nacim has quit IRC13:40
*** Honghui has joined #openstack-swift13:57
*** byeager has joined #openstack-swift14:02
*** psharma has quit IRC14:08
*** cheri has quit IRC14:08
*** chandan_kumar has quit IRC14:17
*** changbl has quit IRC14:18
*** mlipchuk has quit IRC14:39
*** jergerber has joined #openstack-swift14:49
*** mlipchuk has joined #openstack-swift14:54
*** Honghui has quit IRC14:57
openstackgerritgholt proposed a change to openstack/swift: TempURL: Fixed bug with \r or \n in disposition.  https://review.openstack.org/8669115:00
*** byeager has quit IRC15:03
*** byeager has joined #openstack-swift15:04
*** lpabon has quit IRC15:07
*** nacim_ has quit IRC15:10
openstackgerritpaul luse proposed a change to openstack/swift: Add Storage Policy Support to Recon Middleware  https://review.openstack.org/8738715:10
swillscreiht: mind if i bother you? :)15:11
*** kevinc_ has joined #openstack-swift15:15
creihtswills: what's up?15:15
swillscreiht: still trying to track down this issue... did the syscall trace and it seems like it's closing the sqlite file then trying to write to it or something15:16
swillshttp://paste.mouf.net/pastes/l47l9ipeetqf2a7lvusadm99 is the exception15:16
swillshttp://paste.mouf.net/pastes/l47l9ipeetqf2a7lvusadm99/raw15:16
creihthrm15:24
swillsupgrading to 1.13.1 now15:25
swillsthe trace is pretty big: http://meatwad.mouf.net/~swills/swift_1.ktrace.txt.gz15:25
swillsif you download it and look for references to 08d2ef729088d86e8612c1ce2b2323be you'll see what's going on I think15:27
swillsi don't fully understand what's going on personally15:27
*** tdasilva has left #openstack-swift15:28
swillscreiht: thoughts? i know it's hard to decipher... does it help to know i have threading enabled in both sqlite and python?15:30
creihtI don't think that should matter15:31
swillsk15:31
*** mwstorer has joined #openstack-swift15:33
*** pberis has joined #openstack-swift15:36
swillscreiht: seen anything like this before?15:36
creihtno15:36
swillsthink the idea of it being closed when it's trying to write to it makes any sense?15:37
swillswhat version of sqlite do you guys typically use?15:37
*** piyush has joined #openstack-swift15:37
swillsi'm using 3.8.4.215:38
creihtubuntu precies has 3.7.915:38
creihtI wouldn't think version differences would matter15:38
*** nacim_ has joined #openstack-swift15:38
creihtsqlite is usually pretty stable15:38
creihtI wish I was better at reading traces15:39
swillsit's not easy15:40
*** bach has joined #openstack-swift15:43
creihtswills: ok this is weird15:43
creihtswills: I found the I/O error traceback15:44
creihtat 9957315:44
swillsok15:44
creihtright above it there are quite a few15:44
creiht 98874 python2.7 RET   accept -1 errno 35 Resource temporarily unavailable15:44
creihtnot sure if that is related or not but seems suspect15:45
swillshmm, i do see some of this logged:15:45
swillssonewconn: pcb 0xfffff801006be7a8: Listen queue overflow: 193 already in queue awaiting acceptance (36 occurrences)15:45
*** pberis has quit IRC15:45
*** pberis has joined #openstack-swift15:46
swillskern.ipc.somaxconn: 12815:46
swillswhat's the linux version again?15:46
creihtwhich linux version?15:47
swillswhatever you guys are using?15:47
*** kevinc_ has quit IRC15:49
creihtoh15:49
creihtwell I'm testing on ubuntu precise right now15:49
creihtusing kernel 3.2.015:50
*** zhiyan is now known as zhiyan_15:50
swillsi wonder what resource it is that's unavailable15:52
creihthehe disk IO error pops up a lot in that trace15:53
swillsyes15:54
*** Honghui has joined #openstack-swift15:54
swillsbut that's just sqlite's way of saying *something* went wrong, I think15:54
swillsupgrading to 1.13.1 didn't change it, it seems, nor did setting kern.ipc.somaxconn=6553515:54
creihtyeah I found the first occurence of the error, and I'm not seeing the errno 35 around there15:55
*** kevinc_ has joined #openstack-swift15:56
swillshmmm, /etc/swift seems to be hard coded in a lot of places...15:57
*** joeljwright has quit IRC15:57
swillsinterestingly, i'm running the functests again and i'm seeing those exceptions but it's not causing test failures16:02
creihtheh16:02
creihtswills: are you still using a multiserver config? or did you ever switch to an saio?16:02
swillsmultiserver16:03
creihtI wonder if it would be better to try to set up just an saio to test with first16:03
*** mlipchuk has quit IRC16:03
*** mlipchuk1 has joined #openstack-swift16:03
creihtit might remove a lot of variables16:03
swillsok, but if i do that and i don't see the error, what does that prove? how does that help find the issue in this setup which is more like what the real production setup will be?16:04
openstackgerrityummy.bian proposed a change to openstack/swift: Fix redundant add operation of set in ring  https://review.openstack.org/8963016:04
creihtwell it would remove the jail variable16:05
creihtjust to make sure it isn't limiting something16:05
creihtI'm just trying to start simpler16:05
creihtbecause otherwise, I'm kind of at a loss16:05
creihtsorry16:05
swills*nod* no worries16:06
*** mlipchuk1 has quit IRC16:06
swillsperhaps i'll just give up and use Linux for this16:06
creihthah16:06
creihtwell that would make certain things easier :)16:06
swillsthing is16:06
swillsi don't trust xfs16:06
swillsi really wanted to use zfs16:06
swillsusing the jails was just an easy way to test that everything worked OK on zfs16:07
Honghuiswills, you means zfsonlinux or zfs-fuse?16:07
swillsHonghui: definitely not16:08
Honghuizfs on BSD or Solaris?16:08
swillsFreeBSD, yes16:08
creihtswills: oh I understand16:09
creihtI would like for everything to work on freebsd16:09
swillsand don't take this the wrong way, but the failure of swift on FreeBSD says more about swift than FreeBSD, for me. :)16:09
creihtjust most of us aren't really freebsd experts16:09
creihtawww16:09
creihtswills: well for what its worth, we wrote swift to work with the tools we had16:10
swillsi wonder if a different version of python would help... is 2.7 what you guys use?16:10
creihtI doubt that would change anything16:11
creihtand yes we use both 2.6 and 2.716:11
creihtmost use 2.716:11
HonghuiWe run python 2.7, swift 1.10.16:11
swillsk16:11
*** chandan_kumar has joined #openstack-swift16:11
creihtI wish the softlayer devs were around to share their experiences16:11
creihttheir the only ones that have had freebsd experience16:11
swillsthat would be cool16:12
creihtbut they ended up going with linux just because it was easier16:12
swillsperhaps they've written something up and posted it somewhere?16:12
creihtI don't recall anything16:12
swillsalso, fwiw, https://www.freebsd.org/news/status/report-2014-01-2014-03.html#FreeBSD-Host-Support-for-OpenStack-and-OpenContrail16:13
swillsbut that seems more focused on nova and such16:13
creihtyeah16:13
*** Honghui has quit IRC16:14
creihtnotmyname: you need to add freebsd to your test cluster ;)16:14
swillsi'd be happy to help with that16:15
creihtswills: but back to the saio idea, the main reason for that is that it is about the simplest way to setup swift16:16
creihtand test it16:16
creihtif it works fine there, then we can start expanding16:16
creihtto isolate where problems get introduced16:16
swillsok, i'm not 100% sure what you mean by saio16:16
creihtoh sorry16:16
creihtswift all in one16:16
swillsright16:16
swillsbut what does that mean exactly?16:16
creihthttp://docs.openstack.org/developer/swift/development_saio.html16:16
swillsdoes that mean running it in the ubuntu VM?16:17
creihtno16:17
swillsbut that page you just linked says that16:17
creihtyou would have to adapt the instruction for freebsd16:17
creihtthe idea being that you run all the services locally on different ports16:17
swillsso that would mean, what? just taking the 6 jails i have now and reconfiguring 1 so it only knows about itself?16:17
creihtwell Ideally, I would like to start with running outside of a jail to start with16:18
swillsrunning multiple copies of swift in the 1 jail? how is that different from 6 jails?16:18
swillsi can't imagine running outside the jail would change much16:19
*** changbl has joined #openstack-swift16:19
swillsusually if jails cause any issues you see it immediately, like if you try to run postgresql in a jail and forgot to deal with the shared memory stuff16:20
*** chandan_kumar has quit IRC16:20
creihtYeah the thing is, I'm kinda out of ideas16:22
*** mlipchuk has joined #openstack-swift16:22
creihtand when that happens, all I can think of is trying to remove unknowns16:22
creihtin this situation there are a lot of unknowns for me16:22
creihtmaybe someone else will chime in with a better idea16:23
creihtit is pass time for me to go to lunch now... will be back later16:24
*** nacim_ has quit IRC16:28
*** joeljwright has joined #openstack-swift16:37
*** joeljwright has quit IRC16:38
*** mlipchuk has quit IRC16:39
*** jamie_h has quit IRC16:42
*** shakamunyi has joined #openstack-swift16:43
*** mmcardle has quit IRC16:46
*** mkollaro has quit IRC16:50
*** bach has quit IRC16:51
*** mkollaro has joined #openstack-swift16:54
*** elambert has joined #openstack-swift16:58
*** shri has joined #openstack-swift17:08
*** joeljwright has joined #openstack-swift17:15
*** byeager has quit IRC17:17
*** mjfork has joined #openstack-swift17:17
swillsFAIL: testContainerListing (test.functional.tests.TestAccount)17:21
*** piyush has quit IRC17:28
*** Dharmit has quit IRC17:29
*** gyee has joined #openstack-swift17:31
*** jamie_h has joined #openstack-swift17:32
*** byeager has joined #openstack-swift17:33
*** byeager_ has joined #openstack-swift17:34
*** mnaser has joined #openstack-swift17:36
mnaserhttps://review.openstack.org/#/c/45874/ -- how can I remove the -2 here?17:36
*** byeager has quit IRC17:37
*** gyee has quit IRC17:39
*** elambert has quit IRC17:43
*** piyush has joined #openstack-swift17:44
*** piyush1 has joined #openstack-swift17:46
*** zaitcev has joined #openstack-swift17:47
*** ChanServ sets mode: +v zaitcev17:47
brianclineare there any drawbacks to moving account and/or container server processes out to their own hosts?17:48
*** piyush has quit IRC17:48
zaitcevyou have to pay for the hosts17:49
*** elambert has joined #openstack-swift17:49
*** chandan_kumar has joined #openstack-swift17:51
*** joeljwright has quit IRC17:51
*** gyee has joined #openstack-swift17:56
brianclineha.. so other than that, and the generation of additional heat17:57
ctennisbriancline, we have some customers who do that very thing, no problem17:58
brianclineanother question unrelated to that -18:01
brianclinein a scenario where a sequence of object PUTs where some take a noticeable amount longer to perform than others, what's a good place to start digging?18:02
brianclineI would assume swift-get-nodes on the object(s), if known, might be key in tracking down object server specific issues - but are there other/better places to be looking?18:04
ctennisthe swift logs on each node will contain timing information about how long the operation took, you can see if one is perhaps taking longer than others.18:04
swillscreiht: well, thanks for the help, i'm still looking at things18:04
swillstrying to understand the exception right now18:04
swillsgot a more focused trace http://meatwad.mouf.net/~swills/swift_2.ktrace.68029.txt18:08
swillshttp://paste.mouf.net/pastes/52riits78lats05n44kb5su4/raw is the exception18:09
*** acoles is now known as acoles_away18:10
*** piyush1 has quit IRC18:12
swillsand having upgraded to 1.13.1 I can use swift-container-info now: http://paste.mouf.net/pastes/9dr7llglm4dba181o5feaf3q/raw18:13
*** mkollaro has quit IRC18:15
zaitcevbriancline: Talk to someone with experience, like Chuck or Greg. But my understanding is, they rarely try to track separate requests by txid. Instead they look at macro stats for all hosts and find duff nodes that way.18:16
*** tongli has joined #openstack-swift18:19
*** krtaylor has quit IRC18:26
*** chandan_kumar has quit IRC18:29
*** rcleere has joined #openstack-swift18:30
zaitcevguys, what's the opinion on Peter's https://review.openstack.org/86710 ? It reduces the amount of skipped tests for me, because I cannot be bothered to keep constraints test.conf.18:30
zaitcevLooks like we have a significant backlog in https://review.openstack.org/#/q/status:open+project:openstack/swift,p,002c6b2c00014f9518:31
zaitcevgranted, half are WIP18:32
*** gyee has quit IRC18:35
creihtbriancline: it works pretty well18:39
creihtbut the downside is18:39
creihtthe container processes can be a bit cpu heavy18:39
creihtso when you bring those to a handfull of container specific nodes, your cpus could be a bottle neck18:39
creihtwhen you spread those out accross more machines, then you don't notice the cpu load as much18:40
creihtmnaser: I think you will have to ask the glance team :)18:40
mnasercreiht: woah, that was a big fail on my part, head was tuned to swift18:40
mnaserawkward...18:40
creihtzaitcev: yeah it seems most of us have been quite busy with our day jobs18:40
creihtmnaser: no worries man18:40
*** kevinc_ has quit IRC18:44
*** gyee has joined #openstack-swift18:46
*** openstackgerrit has quit IRC18:49
*** openstackgerrit has joined #openstack-swift18:49
dfgbriancline: a pretty cool tool to find slow object nodes is using swiftly ping -o object.ring.gz18:52
*** chandan_kumar has joined #openstack-swift18:53
brianclinecreiht: thanks for the insight -- my guess is account specific nodes likely don't suffer the same bottleneck?18:57
brianclinedfg: nice, have not seen this yet. will give it a go18:58
creihtwell we put account and containers on the same servers18:58
creihtthe problem is that the actual space required for them is so small, all if it gets concentrated to a much smaller set of servers18:58
brianclinemakes sense19:01
*** bach has joined #openstack-swift19:02
*** bach has quit IRC19:02
*** foexle has quit IRC19:05
*** bach has joined #openstack-swift19:05
*** krtaylor has joined #openstack-swift19:07
notmynamehello19:08
*** gyee has quit IRC19:11
*** bvandenh has quit IRC19:12
creihtswills: I've looked through the trace and nothing is really standing out to me19:13
creihtsorry19:14
swillscreiht: k, thanks for looking19:15
swillscreiht: i'm starting to suspect sqlite or pysqlite at this point19:15
*** chandan_kumar has quit IRC19:17
*** kevinc_ has joined #openstack-swift19:23
*** elambert has quit IRC19:31
*** shakamunyi has quit IRC19:33
notmyname"Saw a quote for a Netapp backend for OpenStack, it was eye-bulging. No wonder people love Swift so much." <-- zaitcev, I love it :-)19:35
*** bach has quit IRC19:35
*** shakamunyi has joined #openstack-swift19:35
*** bach has joined #openstack-swift19:36
zaitcevnotmyname: Apparently a part of the problem is that HA is required for Netapp that supports Glance somehow... Which is odd because you'd think a filer is a filer, so what does Glance care if it's HA or not. But anyhow Swift is better than HA anyway (symmetric).19:37
*** byeager_ has quit IRC19:37
*** byeager has joined #openstack-swift19:38
notmynamezaitcev: that does sound weird19:39
notmynamethat and something that was being tlaked about last week with glance make me think that my assumption of what glance is actually doing is incorrect19:39
*** byeager has quit IRC19:42
swillscreiht: do you know if the sqlite you use has ICU enabled?19:54
*** elambert has joined #openstack-swift19:56
creihtswills: doesn't look like it19:59
swillscreiht: k, thanks20:00
*** byeager has joined #openstack-swift20:07
*** lpabon has joined #openstack-swift20:09
*** bach_ has joined #openstack-swift20:15
*** bach has quit IRC20:15
*** shri1 has joined #openstack-swift20:18
*** shri has quit IRC20:21
*** bach_ has quit IRC20:22
*** bach has joined #openstack-swift20:23
*** Trixboxer has quit IRC20:25
swillsfound it20:26
swillshttp://sqlite.1065341.n5.nabble.com/I-O-errors-with-WAL-on-ZFS-td68390.html20:26
swillsF_ALLOCSP isn't support on ZFS20:26
*** bach has quit IRC20:27
swillscreiht: ^^20:27
creihtahh20:27
creihtthere you go :)20:28
*** tongli has quit IRC20:30
swillsnow to see if disable_fallocate = true actually works20:33
swillscrap, it's still there20:35
*** shri has joined #openstack-swift20:39
glangesomeday this will be made into a movie :)20:43
*** shri1 has quit IRC20:43
swillsheh20:47
glangeVal Kilmer will play creiht, obviously20:49
creihtlol20:50
swillsdude, that's cold20:50
claygumm.... Keanu Reeves20:50
redboglange always thinks he'll be played by edward norton.  I think edward norton is too likeable.20:56
creihtnoam chomsky20:56
zaitcevThe Sad Keanu20:57
notmynameopenstack project meeting starting now, and then I'll be doing summit scheduling stuff21:00
notmyname26% voter turnout so far for the TC election21:01
dfgthere's a TC election? who's going to buy my vote?21:01
dfgor do i get a vote?21:02
notmynamedfg: vote for me, and I'll give you a free download of swift21:02
notmynamedfg: http://lists.openstack.org/pipermail/openstack-dev/2014-April/033173.html21:03
dfgtempting...21:03
notmynamedfg: just for you I'll throw in a copy of keystone. any neutron if you're lucky21:03
notmyname*and21:03
dfgthis deal is getting less and less appealing21:04
glangenotmyname: can you make dfg's part in the swift movie bigger?  Michael Richards is playing dfg21:04
notmynameglange: he's already got a whole song and dance number about CORS21:05
dfgi was promised lines21:05
glangeand no nudity21:05
dfgwho in here can /kick glange?21:06
notmynamedfg: actually, you can :-)21:06
dfgdammit21:07
dfgnope21:07
creihtnosexcover is a very unfortunate name for a python package21:07
notmynamedfg: /msg chanserv op #openstack-swift dfg21:07
notmynamedfg: then you can kick whoever21:07
creihtand holy cow when tid test-requirements.txt get so many requirements?21:08
*** ChanServ sets mode: +o dfg21:08
*** glange was kicked by dfg (glange)21:08
dfgnice :)21:08
creihtlol21:08
*** glange has joined #openstack-swift21:08
*** ChanServ sets mode: +v glange21:08
dfgnotmyname: ok you got my vote :)21:08
notmynamelol21:08
notmynameyikes. Ironic is oversubscribed at the summit 18:421:09
notmynameswift is 22:821:10
notmyname(merely)21:10
glangeyou can reduce those ratios :)21:10
glange9:2 and 11:421:10
creihtdfg: you could just kick him in real life :)  since you sit right across from him21:10
claygI think all openstack positions should be *appointed* by dfg21:11
creihtannointed21:11
notmynameheh21:11
dfgclayg: are you trying to get my vote?21:12
notmynamehmm..maybe some sessions can be merged and just take half the time. would be tricky, I think21:12
* clayg serves at the plesure of the freaking goetz21:13
dfghaha21:13
*** bach has joined #openstack-swift21:14
notmynamegraphs: http://summit.openstack.org/cfp/topicstatus21:14
claygnotmyname: there's nothing to click on there...21:15
notmynameclayg: why's it always got to be about clicking things?21:16
claygnotmyname: sometimes it's voting on things21:16
notmynameclayg: but only if dfg approves21:17
claygi just want to see the list of talks proposed so I can lobby if I need to21:17
notmynamecan you see http://summit.openstack.org/cfp/topic/1221:17
glangeForbidden!21:17
notmynameah21:18
notmynamehttp://d.not.mn/swift_topics.png21:18
swillsso setting disable_fallocate = true seems to not work21:19
swillshacking sqlite not to support fallocate then running the tests results in a clean test run21:19
claygit's seems strange I can't filter the full list at summit.openstack.org21:19
creihtswills: I think disable_fallocate prevents swift from fallocating, not sqlite21:19
swillscreiht: oh, ok21:20
*** gyee has joined #openstack-swift21:20
creihtclayg: click on Topic21:20
creihtit will order them all, then just scroll to the swift ones21:20
swillshttp://paste.mouf.net/pastes/qqckk5e07vflkt10ufgf8o8d/raw21:20
swillsare the skips normal?21:20
creiht\o/21:20
creihtswills: yeah it will skip stuff if you don't have it enabled21:21
claygcreiht: hmph - not my fault they didn't put little arrows next to it21:21
creihtclayg: yeah obvious right? :)21:21
swillscreiht: ok, should it?21:21
swillsshould i enable something?21:21
clayga lot of those look interesting... but some of them seem like they'd be more interesting as gerrit reviews :\21:21
notmynameclayg: agreed21:21
torgomatici think db_preallocate = false is the one that turns off fallocate in sqlite21:21
swillstorgomatic: oh! interesting21:22
torgomaticer, db_preallocation21:22
torgomaticor however it's spelled; it's in the sample configs21:22
notmynamecreiht: weren't you thinking that http://summit.openstack.org/cfp/details/192 maybe should be for cross-project or somthing?21:22
creihtnotmyname: yes21:22
swillstorgomatic: it was off by default?21:22
swillstorgomatic: and I was seeing it when it was commented out21:23
claygi thought db preallocation was on by default?21:23
creihtI think those are separate things in swills' case21:23
claygi don't think's "allocate ahead of the db" and... ^ what he said21:23
torgomaticswills: yeah, looks that way... swift.common.db.DB_PREALLOCATION = config_true_value(conf.get('db_preallocation', 'f'))21:23
creihtswills: db preallocation will preallocate space on disk for the db21:23
torgomaticcreiht: oh, maybe that's something else then21:23
torgomaticplease return to your regularly scheduled ignoring me :)21:24
creihtnot change sqlite behavior21:24
creihthaha21:24
swillsk, thanks tho21:24
swillsso about the skips... should i enable something?21:24
claygcreiht: but like... sqlite doesn't work on zfs "out of the box"21:24
swillsclayg: it can't and won't ever21:24
claygswills: we don't do anything that crazy with the sqlite21:24
creihtclayg: yeah21:24
* clayg had his mind blown21:24
swillsthe idea of fallocate on a COW FS is non-sensical21:25
creihtswills: yeah sounds like you will have to do something special with sqlite21:25
swillsnonsensical even21:25
swillscreiht: i did, i hacked it's configure script to just hard define FALLOCATE off...21:25
creihtahh21:25
creihtswills: you can run .functests -v to show the names of the tests that are skipped21:26
swillscreiht: k, thanks21:27
notmynamecinder is taking that session, in order to have a cinder/glance cross-project one21:27
creihtswills: and look at swift/etc/proxy-server.conf-sample21:28
creihtthat has all the possible things that can be configured for swift21:28
swillscreiht: ah, thanks21:28
swillsso things seem to be working really well now. :)21:29
creihtswills: http://docs.openstack.org/developer/swift/deployment_guide.html21:29
swillscreiht: yep, good idea. :)21:30
creihtthat has some further docs on deployment options21:30
swillsnow i can actually move on to planning my deployment21:30
creihtswills: cool21:30
swillsthing is, we won't have a ton of locations or servers21:30
swillsor really even a ton of files21:30
swillsso having the server be redundant, using a resiliant FS like ZFS, etc. makes more sense than trying to use something like xfs and just let the sheer quantity of boxes help me21:31
creihtsure21:34
zaitcevright until the moment when the mega-node fails to assemble a pool on boot and pukes into your shoes21:35
swillszaitcev: don't get me wrong, i'm still going to have enough nodes that i have redundancy21:36
zaitcevswills: in that case you don't need ZFS to provide said redundancy21:37
swillsneed? no. want? yes.21:37
swillsplus, i don't think business would be confortable with the idea that some data on disk might be corrupted until the auditor comes along and fixes it, and we serve bad data to users for a period of time... or am i misunderstanding something?21:38
notmynameswills: that's why we have the etag. which also protects against transit errors21:39
zaitcevyes, the way proxy verifies etag21:39
zaitcevalthough I'm not sure it actually does21:39
*** lpabon has quit IRC21:39
notmynamestill it's possible to read a bad copy before it's quarantined. but then it will be quarantined because the GET verifies the integrity21:40
notmynamebut that's where the etag comes in (which needs to be checked anyway)21:40
zaitcevThis discussion happens every time when someone tries to graft Swift on top of a magical vendor solution. Or SAN. Or RAID. People never tire of this kind of thing.21:42
swillsinteresting. well, i'll have plenty of time to read and understand it all now that i've got this solved.21:42
swillszaitcev: it's all new to me personally.21:43
kevinc_We used RAID and ZFS for our swift implementation and it was a disaster, I have spent the last 6 months trying to convert everything to JBOD and XFS...21:43
notmynamekevinc_: yay :-)21:44
swillskevinc_: oh, do tell?21:44
swillsalso, why would you use both RAID and ZFS?21:44
kevinc_some servers had raid and some had zfs21:44
swillsah, ok21:44
swillsi thought you meant both at the same time, which is insane. :)21:45
swillsso what gave you trouble?21:45
kevinc_when a raid set got degraded it killed the performance for weeks while it rebuilt. ZFS on linux wasn't very stable at that point and we lost whole sets of data because it would take 1-2 weeks to mount21:46
kevinc_those were the worst problems21:46
swillshmm, ok21:47
swillswhat else?21:47
kevinc_the recommendations are there for a reason, don't try to be smarter than the devs ;)21:47
*** physcx has joined #openstack-swift21:48
creihtlol21:48
notmynamekevinc_: no, please be smarter and tell us what's wrong :-)21:48
creihtwell you can't believe everything you read on the internet :)21:48
creihtheh, and we are often wrong :)21:48
creihtwell some more than others :)21:49
swillsnot trying to outsmart anyone, just have an affinity for zfs...21:49
kevinc_:P21:49
zaitcevI do not have ZFS in use myself, but I'm enjoying CKS's gripes about it: http://utcc.utoronto.ca/~cks/space/blog/linux/21:49
physcxIs there a known problem with using chunked encoding when uploading to swift?21:50
notmynamephyscx: should work. what are you seeing?21:50
swillszaitcev: err, isn't that mostly complaining about btrfs?21:51
zaitcevchunked requires 100-continue, doesn't it?21:51
physcxmore specifically a performance problem - almost 8x faster having content-length known up front as opposed to using chunked encoding on the same files21:51
notmynamephyscx: ah, that's interesting. can you write up a simple repro so I can try it on my own swift cluster(s)?21:53
creihtlooks like saio install on ubuntu trusty works fine21:53
notmynamecreiht: cool21:53
creihtthough there is a weird issue with code coverage21:53
kevinc_well we used raidz2 zpools with v0.6.0 of zfsonlinux, i don't know about using single drive zpools with the latest version of zfs21:53
notmynamephyscx: have you changed any of the network buffer settings? if not, maybe the defaults are set poorly21:54
swillskevinc_: i plan to use SSDs for ZIL and limit ARC as well, so performance should be fine21:54
swillskevinc_: the only place i can see a potential issue is scrubbing causing performance slowdown21:54
kevinc_the performance on zfs went down when it exceeded 95% on a drive21:54
swillskevinc_: that's documented21:55
notmynamecreiht: any dependency issues? out-of-the box versions work ok?21:55
swillskevinc_: that's how ZFS works, usage over 80% slows things down, usage over 90% slows things down even more, >95% and things get crazy...21:55
creihtnotmyname: everything worked out of the box21:55
creihtthe coverage module must be newer, becuase code coverage report on unit tests isn't working correctly21:55
creihtthat's the only thing I've seen so far21:55
creihtotherwise all tests work fine21:56
swillstest_GET (test.functional.tests.TestSloTempurl) ... SKIP: TempURL and SLO not both enabled21:56
swillsah ha!21:56
kevinc_yes, i am aware of it, I am 3PB of data on zfs volumes..21:56
notmynamecreiht: does coverage go up or down? ;-)21:56
creihtlol21:56
creihtnotmyname: http://paste.openstack.org/show/76698/21:58
physcxnotmyname: http://pastebin.com/5GbmxwhA   file shown being uploaded is 205MB and in both cases completes successfully - just a performance issue21:59
claygGAWD paste.openstack.org is slow - please stop using that Drizzle crap21:59
creihtlol21:59
zaitcevphyscx, notmyname: also specify which LB is used to terminate, or if this goes to naked Swift21:59
notmynamehttps://gist.github.com/notmyname/81fe36d3b4a7102994ca21:59
notmynameclayg: ^21:59
* clayg ain't got no time for that!21:59
claygcreiht: that coverage is awesome btw22:00
creihthehe22:00
creihtif you change swift. to swift it works correctly22:00
notmynameah, interesting22:00
* notmyname plans on using http://paste.ronin.io by pandemicsyn from now on22:01
creihthehe22:01
creihtyeah I should just switch to using that22:02
zaitcevI just scp into people.redhat.com22:04
physcxzaitcev, notmyname it is using /r/n LBs libcurl4, also 16k object hunk size and client chunksize and looking manually at the syscall reads they are both performing similar number and size of reads as the default curl chunk send is 16k for us22:04
zaitcevIn a text file with UNIX newlines22:04
pandemicsynhrm i just gained 2 users....time to go raise a round of funding for my Swift Pastebin As a Web Scale Software Defined Open Service Stack..thing22:05
creihtlol22:05
notmynamepandemicsyn: percentage growth is all that matters!22:05
pandemicsynits already using Go and uses a Flat design so i got the important things covered22:06
zaitcevI prefer a House design22:06
swifterdarrellpandemicsyn: lol22:06
notmynamepandemicsyn: swifterdarrell: but is it dockerized?22:06
pandemicsynhrm, no22:07
swifterdarrellDOCKER DOCKER!22:07
pandemicsynim also still missing out on the social part22:07
creihtwow.. saio on our new performance flavors runs pretty fast :)22:07
pandemicsyni need to send you all push notifications when someone one you kinda know pastes something22:07
creihtpandemicsyn: needs keybase.io integration :)22:08
swifterdarrellpandemicsyn: SOCIAL22:08
swifterdarrellpandemicsyn: now you just need "mobile"22:08
swifterdarrellpandemicsyn: and maybe "big data"22:08
pandemicsyn"Oh you'd like to paste some python...thats an in app purchase"22:08
notmyname`keybase prove ronin_paste`22:08
creihtlol22:08
notmyname$ echo $? >1  # pandemicsyn doesn't like you22:09
*** joeljwright has joined #openstack-swift22:09
pandemicsynheh22:09
notmyname402 Payment Required22:09
notmyname^^ more like pandemicsyn ;-)22:10
pandemicsynlol22:10
pandemicsynthats the Jay Payne status code22:10
notmynamelol22:10
glangeman, it's inside joke day on #openstack-swift :)22:14
creihthehe22:14
*** jamie_h has quit IRC22:14
*** joeljwright has quit IRC22:14
zaitcevI am left out, but it's all right.22:15
shriHey guys… I have a question about the swift-ring-builder22:16
shriCan I use a hostname instead of an IP address when building the rings?22:17
physcxnotmyname: i'm headed out for the day but if anyone with a test cluster can try curl uploading a file with and without chunked encoding and see if it is horribly slower I'd appreciate it (http://pastebin.com/5GbmxwhA), i'll check back tomorrow22:18
notmynamephyscx: I'll try to leave a comment here22:18
physcxty22:18
notmynameI'm doing summit scheduling and then will be out for the rest of the week22:19
zaitcevshri: you mean like this https://review.openstack.org/8042122:19
dfgtakes a lot out of you huh22:19
shriso..its work in progress. thanks!22:20
notmynamephyscx: FWIW, no significant difference on my SAIO: https://gist.github.com/notmyname/17971ee386e7b1960eb422:25
pandemicsynso much for gaining 2 users ;)22:27
*** kevinc___ has joined #openstack-swift22:27
notmynameLimeChat has the very nice feature of multiline pastes into the input box automatically being pasted to gist.22:28
*** bach has quit IRC22:29
*** kevinc_ has quit IRC22:29
*** byeager has quit IRC22:30
*** byeager has joined #openstack-swift22:30
dfgphyscx: notmyname : i didn't really see a difference in time with Transfer-Encoding: chunked uploading a 160MB file to our staging either22:32
zaitcevAnd I don't understand what "/r/n" is supposed to mean.22:34
*** byeager has quit IRC22:34
zaitcevSounds like a board name at 4chan.22:34
notmynamecreiht: are you going to the june hackathon?22:37
creihtnotmyname: unsure22:38
creihtbut likely not22:38
creihtsince it was so close to the summit, we will likely have to split between the two22:38
notmynameah22:38
notmynamechecking since you have the most sessions proposed ;-)22:39
creihthah22:39
notmyname(which of course are all very important)22:39
creihtlol22:39
creihtI don't expect them all to get accepted22:39
creihtwas just throwing some stuff out there that I thought was important22:39
creihtsome of them might be able to be combined with others22:40
creihtor may not take up the whole time22:40
notmynameI'll try to sort them by things that deal with the community and things that will benefit more from in-person discussion. some of it, like clayg said, would be really nice to see in gerrit22:42
notmynameand we've got the "swift pod" all week, so that will be good for more BoF style things22:42
notmynameit's interesting that there were at least 4 conference sessions proposed on benchmarking swift and there are also a few summit sessions on that topic too22:44
notmyname(which is nice IMO because I think that's one big area of improvement we can work on in the coming months)22:44
*** rcleere has quit IRC22:45
*** rcleere has joined #openstack-swift22:46
notmynamenote that tomorrow's team meeting is only tentative at this point. if you volunteer to lead it, add yourself here: https://wiki.openstack.org/wiki/Meetings/Swift. If nobody does, then enjoy the week off22:46
notmynamenote also that gerrit is changing next week: http://lists.openstack.org/pipermail/openstack-dev/2014-April/033414.html22:48
*** rcleere has quit IRC22:50
notmynamedfg: scheduling is hard work! https://pbs.twimg.com/media/Bl3FlnvCUAA-Phg.jpg:large22:52
*** elambert has quit IRC22:57
notmynamepandemicsyn: if you have a chance, can you look over this patch? https://review.openstack.org/#/c/86114/ It adds swift.conf checking to recon22:58
*** elambert has joined #openstack-swift22:58
pandemicsynheh thats handy as hell, i've done that a few times23:01
claygcreiht: hallway track too - i'm looking forward to seeing you!23:04
notmynamecreiht: you say you'll be doing an audit of test coverage in swift http://summit.openstack.org/cfp/details/13323:11
notmynamecreiht: still happening? or only if that session is selected?23:11
openstackgerritPete Zaitcev proposed a change to openstack/swift: Return an error exit code if config is missing on start  https://review.openstack.org/8971523:11
notmynameseems pretty useful to have referenced somewhere23:12
*** jergerber has quit IRC23:15
notmynamezaitcev: are you going in june?23:15
zaitcevnotmyname: yes23:15
notmynamegreat!23:15
zaitcevthe management changed their mind and said it's okay to go to 2 conferences in a year23:15
notmynameportante: zaitcev: seems like the PBE discussion might be more fruitful in june than in atlanta. do you agree or disagree23:15
zaitcevnotmyname: I agree but honestly I was hoping it did not need a discussion23:16
notmynamezaitcev: well blame portante for submitting it then :-)23:16
zaitcevLook, half of it is already in. Unelss we want to back it out, what's there to discuss? I think we should just approve https://review.openstack.org/85909 and be done.23:17
zaitcevWell, we won't be because then I'll file about a dozen little shards on top of 85909, but those are technical details.23:17
*** changbl has quit IRC23:18
notmynamecreiht: how do you feel about combining "swift core principles" with "swift growing pains"?23:19
*** praveenkumar has quit IRC23:36
*** krtaylor has quit IRC23:43
occupantso I'm running grizzly (yeah, I know, we should upgrade) and I think I'm getting hit by this bug that was fixed in havana - https://bugs.launchpad.net/swift/+bug/117466023:54
occupantif I run iftop on my proxy server, I'm fetching like 1Gb/s from my object servers, but I'm only putting out like 100Mb/s of traffic.23:55
occupanthttps://bugs.launchpad.net/swift/+bug/1166198 got marked a dupe but it seems to describe what I'm seeing a bit better - lots of extra traffic that seemingly shouldn't be there.23:56
occupantthe final comment on that bug, someone says they used a patch against the havana branch on their grizzly install and it fixed things. pondering trying it myself.23:56
occupantBecause I'm getting lots of timeouts from backend connections and I'm wondering if it's not just getting overloaded.23:59

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