Tuesday, 2016-08-09

*** hosanai has joined #openstack-swift00:01
*** ChanServ sets mode: +v hosanai00:01
*** mweshi has joined #openstack-swift00:09
*** mweshi has quit IRC00:10
*** mweshi has joined #openstack-swift00:11
*** mweshi has quit IRC00:16
*** diogogmt has quit IRC00:22
*** tqtran has quit IRC00:25
*** mingyu has joined #openstack-swift00:41
*** mingyu has quit IRC00:45
*** mmcardle has joined #openstack-swift01:02
openstackgerritSamuel Merritt proposed openstack/swift: Support multi-range GETs for static large objects.  https://review.openstack.org/35265701:03
*** cdelatte has quit IRC01:04
notmynametorgomatic: fun!01:05
torgomatic...and on that note, I'm going home :p01:08
*** klrmn has quit IRC01:09
*** mmcardle has quit IRC01:13
*** trananhkma has joined #openstack-swift01:17
*** kota_ has quit IRC01:20
*** kota_ has joined #openstack-swift01:22
*** ChanServ sets mode: +v kota_01:22
zhengyingood morning, everyone01:24
zhengyinChanServ,koat_:good morning, kota, ChanServ01:25
*** chlong has joined #openstack-swift01:27
zaitcevguys01:42
*** amitkqed has quit IRC01:43
*** amitkqed has joined #openstack-swift01:43
zaitcevDo we have people running with fast-post nowadays? object_post_as_copy=false I mean01:44
MooingLemurI'm not01:50
zaitcevI'm going to enable it for new installations.01:50
zaitcevThe question is, does the container sync work with it now?01:51
MooingLemurThat's one of the reasons I had it set to false01:51
zaitcevI see...01:51
MooingLemurI don't know if it can work with container sync now, but at installation time it didn't01:52
*** mingyu has joined #openstack-swift01:56
*** mingyu has quit IRC02:00
*** diogogmt has joined #openstack-swift02:17
*** klrmn has joined #openstack-swift02:22
*** mmcardle has joined #openstack-swift02:46
*** mmcardle has quit IRC02:49
jrichlizaitcev, MooingLemur: the latest swift does allow fast-post with container sync.  See merged patch 29573902:56
patchbotjrichli: https://review.openstack.org/#/c/295739/ - swift - Docs: Container sync does not require POST-as-COPY (MERGED)02:56
*** mingyu has joined #openstack-swift02:57
*** mingyu has quit IRC03:02
jrichlithe commit message there explains that it was patch 135380 that actually allowed for the combination to work03:02
patchbotjrichli: https://review.openstack.org/#/c/135380/ - swift - Update container on fast-POST (MERGED)03:02
*** mmcardle has joined #openstack-swift03:15
*** mmcardle has quit IRC03:16
*** tqtran has joined #openstack-swift03:22
*** acoles_ is now known as acoles03:23
*** acoles is now known as acoles_03:26
*** tqtran has quit IRC03:27
*** hurricanerix has quit IRC03:30
*** ppai has joined #openstack-swift03:57
mahatic_good morning04:01
*** chromatin has quit IRC04:05
*** klrmn has quit IRC04:08
*** links has joined #openstack-swift04:11
*** jith_ has quit IRC04:11
*** mingyu has joined #openstack-swift04:12
*** nadeem has joined #openstack-swift04:15
*** diogogmt has quit IRC04:16
openstackgerritKATO Tomoyuki proposed openstack/swift: Remove the duplicated word 'be'  https://review.openstack.org/35269404:18
*** psachin has joined #openstack-swift04:20
jrichlimahatic_: good morning!04:27
mahatic_jrichli: o/04:28
*** mingyu has quit IRC04:33
*** chrichip has joined #openstack-swift04:33
*** mingyu has joined #openstack-swift04:35
*** nadeem has quit IRC04:48
*** abhitechie has joined #openstack-swift04:52
*** abhinavtechie has joined #openstack-swift05:02
*** abhitechie has quit IRC05:02
charzkota_: just one question for swift3, did you remember v4 signature with virutal-host style work or not?05:03
*** ppai has quit IRC05:04
*** david-lyle_ has joined #openstack-swift05:11
*** david-lyle has quit IRC05:13
*** vint_bra has joined #openstack-swift05:15
*** rcernin has joined #openstack-swift05:21
*** ChubYann has quit IRC05:35
*** vint_bra has quit IRC05:36
*** ppai has joined #openstack-swift05:41
openstackgerritMerged openstack/swift: Raise 412 response on expirer  https://review.openstack.org/32690305:50
*** mweshi has joined #openstack-swift05:54
*** mweshi has quit IRC05:55
*** mweshi has joined #openstack-swift05:56
*** _JZ_ has joined #openstack-swift06:06
*** maestropandy has joined #openstack-swift06:10
*** tqtran has joined #openstack-swift06:25
*** tqtran has quit IRC06:29
*** chlong is now known as chlong|mtg06:32
*** mmcardle has joined #openstack-swift06:36
*** geaaru has joined #openstack-swift06:38
*** pcaruana has joined #openstack-swift06:39
*** mingyu has quit IRC06:40
*** mingyu has joined #openstack-swift06:40
*** silor has joined #openstack-swift06:43
*** tesseract- has joined #openstack-swift06:45
*** mingyu has quit IRC06:45
*** maestropandy has left #openstack-swift06:48
*** tqtran has joined #openstack-swift06:52
*** mweshi has quit IRC06:59
*** abhitechie has joined #openstack-swift07:05
*** abhinavtechie has quit IRC07:05
*** silor1 has joined #openstack-swift07:13
charzokay, I think that's a bug in swift307:14
*** silor has quit IRC07:16
*** silor1 is now known as silor07:16
*** oshritf has joined #openstack-swift07:18
*** daemontool has joined #openstack-swift07:21
*** rledisez has joined #openstack-swift07:25
*** daemontool_ has joined #openstack-swift07:28
*** daemontool has quit IRC07:28
*** david-lyle has joined #openstack-swift07:43
*** david-lyle_ has quit IRC07:46
*** takashi has joined #openstack-swift07:51
*** tqtran has quit IRC07:58
charzkota_: timburke https://review.openstack.org/#/c/352755/08:05
patchbotcharz: patch 352755 - swift3 - Fix 403 SignatureDoesNotMatch when use v4 signatur...08:05
*** mingyu has joined #openstack-swift08:08
openstackgerritDavanum Srinivas (dims) proposed openstack/swift: [WIP] Testing latest u-c  https://review.openstack.org/31844108:10
*** SkyRocknRoll has joined #openstack-swift08:13
*** mvk has quit IRC08:26
*** geaaru has quit IRC08:38
*** acoles_ is now known as acoles08:43
*** maestropandy has joined #openstack-swift08:48
*** geaaru has joined #openstack-swift08:51
*** mvk has joined #openstack-swift08:53
*** oshritf has quit IRC08:57
*** SkyRocknRoll has quit IRC08:59
*** maestropandy1 has joined #openstack-swift08:59
*** maestropandy1 has left #openstack-swift08:59
*** maestropandy has quit IRC09:00
*** ouchkernel has quit IRC09:02
*** ouchkernel has joined #openstack-swift09:08
*** chlong|mtg has quit IRC09:10
*** SkyRocknRoll has joined #openstack-swift09:16
*** SkyRocknRoll has quit IRC09:22
*** oshritf has joined #openstack-swift09:37
*** hosanai has quit IRC09:37
*** SkyRocknRoll has joined #openstack-swift09:40
*** chlong|mtg has joined #openstack-swift09:47
*** early has quit IRC10:06
*** early has joined #openstack-swift10:06
openstackgerritMerged openstack/swift: Remove the duplicated word 'be'  https://review.openstack.org/35269410:15
*** mvk has quit IRC10:25
openstackgerritMerged openstack/swift: Make the logger information format  https://review.openstack.org/35113210:27
openstackgerritMerged openstack/swift: [install-guide] Include environment-networking  https://review.openstack.org/34692510:27
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873610:32
*** mvk has joined #openstack-swift10:38
*** chromatin has joined #openstack-swift11:15
*** maestropandy has joined #openstack-swift11:16
*** maestropandy has quit IRC11:20
*** thebloggu has joined #openstack-swift11:26
*** thebloggu has left #openstack-swift11:27
*** thebloggu has joined #openstack-swift11:34
*** abhitechie has quit IRC11:52
*** pkovar has joined #openstack-swift12:01
*** SkyRocknRoll has quit IRC12:09
*** diogogmt has joined #openstack-swift12:14
*** trananhkma has quit IRC12:16
*** Jeffrey4l has quit IRC12:23
*** maestropandy has joined #openstack-swift12:23
*** maestropandy has left #openstack-swift12:23
*** kei_yama has quit IRC12:31
*** bill_az has joined #openstack-swift12:35
*** baojg has joined #openstack-swift12:43
*** catintheroof has joined #openstack-swift12:46
tdasilvagood morning12:47
*** baojg has quit IRC12:49
*** pkovar has left #openstack-swift12:57
*** baojg has joined #openstack-swift12:59
*** klamath has joined #openstack-swift13:00
*** klamath has quit IRC13:00
*** zul_ has quit IRC13:00
*** klamath has joined #openstack-swift13:00
*** vint_bra has joined #openstack-swift13:01
*** vinsh has quit IRC13:01
*** baojg has quit IRC13:03
*** takashi has quit IRC13:04
*** zul_ has joined #openstack-swift13:05
*** links has quit IRC13:06
*** vint_bra has quit IRC13:06
*** vint_bra has joined #openstack-swift13:15
*** permalac has joined #openstack-swift13:18
*** vint_bra has quit IRC13:20
*** diogogmt has quit IRC13:33
*** bill_az_ has joined #openstack-swift13:35
*** Jeffrey4l has joined #openstack-swift13:41
*** Jeffrey4l has quit IRC13:42
*** vinsh has joined #openstack-swift13:44
*** cdelatte has joined #openstack-swift13:59
*** jistr is now known as jistr|debug14:00
*** airdisa has joined #openstack-swift14:04
*** ppai has quit IRC14:04
*** lcurtis has joined #openstack-swift14:11
theblogguI updated an openstack swift installation (with RDO) from liberty to mitaka. Even though everything seems to work fine after the upgrade I'm getting errors in the logs (openstack-swift-proxy) about liberasurecode missing shared dependencies (dynamic linking errors) but I do have the liberasure and python-pyeclib packages installed. From what I could tell from two different bug reports it seems to be the logging handling in pyeclib that tries to lo14:16
theblogguad the backends even if you don't use them and prints an error (https://bugzilla.redhat.com/show_bug.cgi?id=1351725 https://bugzilla.redhat.com/show_bug.cgi?id=1351725)14:16
openstackbugzilla.redhat.com bug 1351725 in openstack-swift "Swift proxy log: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory" [Medium,Assigned] - Assigned to zaitcev14:16
theblogguSorry, the second link should be https://bitbucket.org/tsg-/liberasurecode/issues/28/libshssso-no-such-file-or-director14:17
*** chsc has joined #openstack-swift14:25
*** _JZ_ has quit IRC14:25
*** diogogmt has joined #openstack-swift14:26
*** asettle has joined #openstack-swift14:36
*** Jeffrey4l has joined #openstack-swift14:42
*** catintheroof has quit IRC14:47
*** catintheroof has joined #openstack-swift14:48
*** mingyu has quit IRC14:50
*** mingyu has joined #openstack-swift14:51
*** catintheroof has quit IRC14:53
*** oshritf has quit IRC14:56
*** _JZ_ has joined #openstack-swift14:58
*** hurricanerix has joined #openstack-swift14:59
*** vint_bra has joined #openstack-swift15:01
*** arch-nemesis has joined #openstack-swift15:04
*** portante has quit IRC15:08
*** portante has joined #openstack-swift15:11
*** rfinn has joined #openstack-swift15:16
*** links has joined #openstack-swift15:16
*** asettle is now known as Apsettle15:22
*** jistr|debug is now known as jistr15:23
*** catintheroof has joined #openstack-swift15:25
*** Apsettle is now known as asettle15:30
*** mingyu_ has joined #openstack-swift15:36
*** mingyu has quit IRC15:39
*** nadeem has joined #openstack-swift15:39
*** nadeem has quit IRC15:40
*** nadeem has joined #openstack-swift15:44
jrichlithebloggu: you may also be interested in https://bitbucket.org/tsg-/liberasurecode/issues/23/spurious-messages-in-syslog15:44
lcurtishello all...still trying to wade through disk i/o and rebalance contention issues15:45
lcurtiswould there be a case whereby if disk utilization above 85% for example, auditor and replicator never idle?15:46
lcurtisi am getting arguments on team that we should not be above 55% full on disks15:46
lcurtissince when we do we see handoffs occur on ingest15:46
*** pcaruana has quit IRC15:48
thebloggujrichli: yes, thank you. so there's currently no option available, in case you don't use those backends, to omit those errors right?15:49
*** rcernin has quit IRC15:50
*** tesseract- has quit IRC15:50
jrichlithebloggu: Seems to be the case.  You know as much as I do on this issue.15:52
*** psachin has quit IRC15:54
*** psachin has joined #openstack-swift15:55
*** SkyRocknRoll has joined #openstack-swift15:57
*** mingyu_ has quit IRC16:03
*** mingyu has joined #openstack-swift16:04
*** SkyRocknRoll has quit IRC16:16
*** psachin has quit IRC16:17
*** nadeem has quit IRC16:22
*** nadeem has joined #openstack-swift16:27
*** SkyRocknRoll has joined #openstack-swift16:30
*** nadeem has quit IRC16:32
*** mmcardle has joined #openstack-swift16:35
timburkethanks charz -- i'll take a look today16:39
notmynamegood morning16:39
*** rledisez has quit IRC16:39
*** nadeem has joined #openstack-swift16:40
charztimburke: thx, that's a bit wired. My thought is that should have same behavior like v2.16:40
*** asettle has quit IRC16:51
*** asettle has joined #openstack-swift16:52
*** asettle has quit IRC16:56
*** asettle has joined #openstack-swift17:05
*** mvk has quit IRC17:09
*** asettle has quit IRC17:10
*** mmcardle has quit IRC17:18
*** asettle has joined #openstack-swift17:19
*** asettle has quit IRC17:23
*** klrmn has joined #openstack-swift17:23
*** geaaru has quit IRC17:23
*** mingyu has quit IRC17:28
*** zul_ has quit IRC17:30
*** asettle has joined #openstack-swift17:32
*** zul has joined #openstack-swift17:34
*** mvk has joined #openstack-swift17:36
openstackgerritDavid Goetz proposed openstack/swift: go: make moveparts work for both kinds of ring change  https://review.openstack.org/35303817:36
*** daemontool_ has quit IRC17:36
*** asettle has quit IRC17:38
timurclayg: did we not release the new version of liberasure code and pyeclib that makes use of it?17:39
*** zul has quit IRC17:40
timurthebloggu: the new version of liberasure code (1.2.0 -- https://github.com/openstack/liberasurecode/releases/tag/1.2.0) and pyeclib (1.2.1 -- https://github.com/openstack/pyeclib/releases/tag/1.2.1) resolve the spurrious errors related to discovering the backends17:42
*** pcaruana has joined #openstack-swift17:44
*** ChubYann has joined #openstack-swift17:45
timurI guess it's now a matter of bumping the redhat packages17:45
*** asettle has joined #openstack-swift17:46
thebloggutimur: great. does these updates usually make it to the current release repositories? or will only be released with the next openstack version?17:47
timurI'm not actually sure about the release process for those :\17:48
timurI only fixed the actual code, but not sure how/when it gets packaged17:48
thebloggutimur: sure, thank you for your help. i'll probably check with the packagers (rdo in this case) then17:49
timuranytime! sounds good17:49
openstackgerritMerged openstack/swift: Fix Python 3 issues in diskfile  https://review.openstack.org/34739017:51
*** silor has quit IRC17:51
*** asettle has quit IRC17:51
*** zul has joined #openstack-swift17:52
*** asettle has joined #openstack-swift17:59
*** asettle has quit IRC18:04
*** asettle has joined #openstack-swift18:05
openstackgerritMerged openstack/swift: Fix repeated OPTIONS in swift-dispersion-report manpage  https://review.openstack.org/34991018:07
openstackgerritMerged openstack/swift: Fix gettext_ calls  https://review.openstack.org/33674318:07
openstackgerritMerged openstack/swift: NIT: fixing inconsistent naming of OpenStack Swift  https://review.openstack.org/35138818:16
openstackgerritMerged openstack/swift: Have py35 tox env match py34  https://review.openstack.org/33780218:20
timburkego torgomatic! merge it all!18:21
*** acoles is now known as acoles_18:25
*** silor has joined #openstack-swift18:26
*** thebloggu has quit IRC18:31
*** bill_az has quit IRC18:32
*** silor has quit IRC18:33
openstackgerritMerged openstack/swift: Raise ValueError if empty value coming into encrypt_header_val  https://review.openstack.org/33700018:34
*** oshritf has joined #openstack-swift18:39
*** mmcardle has joined #openstack-swift18:39
*** links has quit IRC18:40
*** david-lyle has quit IRC18:41
*** david-lyle has joined #openstack-swift18:42
*** treyd has quit IRC18:44
*** alpha_ori has quit IRC18:44
*** SkyRocknRoll has quit IRC18:45
*** alpha_ori has joined #openstack-swift18:50
*** rcernin has joined #openstack-swift18:51
*** treyd has joined #openstack-swift18:51
*** mmcardle has quit IRC18:59
*** tqtran has joined #openstack-swift19:03
*** tqtran has quit IRC19:09
*** catintheroof has quit IRC19:12
*** kragniz has joined #openstack-swift19:14
openstackgerritSamuel Merritt proposed openstack/swift: Support multi-range GETs for static large objects.  https://review.openstack.org/35265719:25
*** rfinn has quit IRC19:26
*** rfinn has joined #openstack-swift19:36
*** david-lyle_ has joined #openstack-swift19:41
openstackgerritThiago da Silva proposed openstack/swift: add reminder how to run debug func tests  https://review.openstack.org/35187319:42
*** david-lyle has quit IRC19:43
openstackgerritMerged openstack/swift: Make swift-oldies py3-compatible  https://review.openstack.org/34496319:48
*** nadeem has quit IRC20:00
*** nadeem has joined #openstack-swift20:03
*** bill_az_ has quit IRC20:06
*** david-lyle_ is now known as david-lyle20:12
*** cdelatte has quit IRC20:24
*** airdisa has quit IRC20:28
*** asettle has quit IRC20:29
*** asettle has joined #openstack-swift20:30
*** asettle has quit IRC20:30
*** asettle has joined #openstack-swift20:31
*** Jeffrey4l has quit IRC20:35
*** dfflanders has joined #openstack-swift20:35
*** Jeffrey4l has joined #openstack-swift20:36
openstackgerritDavid Goetz proposed openstack/swift: go: make moveparts work for both kinds of ring change  https://review.openstack.org/35303820:37
*** gyee has joined #openstack-swift20:37
openstackgerritNandini Tata proposed openstack/swift: Add man page for swift.conf  https://review.openstack.org/35309720:38
openstackgerritDavid Goetz proposed openstack/swift: go: make moveparts work for both kinds of ring change  https://review.openstack.org/35303820:39
*** nadeem has quit IRC20:39
*** nadeem has joined #openstack-swift20:39
openstackgerritDavid Goetz proposed openstack/swift: go: make moveparts work for both kinds of ring change  https://review.openstack.org/35303820:43
*** mmcardle has joined #openstack-swift20:43
*** mmcardle has quit IRC20:53
claygi have no idea what Alexandr Porunov on the ML is talking about - why would you want to *rename* the stats?  how do you keep a mapping of the semantic value to your new made up name?21:14
claygdoes he mean like host prefixes and stuff?  I don't know how OpenTSDB werx - isn't it just a metrics dump?21:14
claygwhat cli utility?21:14
claygtimur: i released liberasure stuff - it's awesome now21:14
claygtimur: zaitcev knows stuff about rdo21:15
claygtimur: you can even try something like this, watch21:16
claygzaitcev: when are you going to release the rdo fixes for bugzilla.redhat.com bug 1351725 (already assigned to you!)21:16
openstackbug 1351725 in lrt-crashes "lrt test found crash file _usr_lib_arm-linux-gnueabihf_indicator-network_indicator-network-service.32011.crash" [Critical,New] https://launchpad.net/bugs/135172521:16
claygyeah, no patchbot21:16
zaitcevtimur, clayg: I am responsible for the bug, but I don't have a solution.21:16
zaitcevwell, except "upgrade to latest"21:18
claygzaitcev: acctually those don't look like same syslog messages we were seeing?21:18
ahaleidk about that thread or opentsdb but i rename a load of metrics from with account in them to something human readable. like long uuid -> "glance"21:18
*** oshritf has quit IRC21:19
claygahale: and that's like a graphite config thing right?  IIRC it has that sweetness built in... but that's a good point - we do some similar stuff because our nodes report via uuid and the controller has to patch metrics to clusters21:20
zaitcevI need to look at this more seriously. I have a test cluster that was throwing some messages about Jerasure missing, but they went away with liberasurecode 1.1.0 or something like that.21:21
*** oshritf has joined #openstack-swift21:21
notmynamethere was some talk about getting rid of the warnings when known backends weren't installed21:21
ahaleoh yeah, thats all graphitey stuff, was just thinking :)(21:22
ahalehe's probably best off hacking up informant middleware or something, thats what i do when i want more metrics since never switched when swift got statsd21:22
notmynameahale: we could write a generic stats-er plugin framework for swift, and you could use whatever metrics emitter plugin you want. then you could do statsd or opentsdb or whatever21:23
claygtimur: zaitcev: oh nm, yeah that looks right21:24
ahalethat sounds cool21:24
*** rfinn has quit IRC21:25
notmynameahale: ...and when I say "swift" I really mean "all of openstack", of course21:25
ahaleoh so like you install all of oslo and end up only being able to send to gnocci ?21:26
claygahale: why you are even awake?  i hope you're drinking.21:27
ahalelol21:28
timurnotmyname: the warnings do go away with the latest, since it should no longer blindly pollute syslog with ERROR level messages. I don't know what else to do there aside from getting everyone to use the latest and greatest 1.2/1.2.1 releases21:31
*** zigo has quit IRC21:32
*** zigo has joined #openstack-swift21:35
*** admin6 has joined #openstack-swift21:40
claygdoes anyone know how gerrit works can explain what the little yellow dot next to "Parent(s)" means on patch 319387?21:49
patchbotclayg: https://review.openstack.org/#/c/319387/ - swift - swift-ring-builder output corrected for ipv621:49
clayglike it means *something* is out of date - does it *need* a rebase?21:49
*** rfinn has joined #openstack-swift21:49
timurclayg: mouse over it. alt text "not current - rebase possible"21:50
timurI think it would need to be rebased to merge if it's fast-forward only on merges?21:51
timuralthough rebases *during* the review break the delta between patchets in terrible ways :\21:51
claygtimur: i'd guess we merge --no-ff i *always* see the merge commits21:51
timuroh, then it should be ok? I think gerrit will complain if it has a merge conflict when trying to merge it in21:52
claygtimur: yeah idk, there was a comment about some diff polltion that was confusing to the reviewer - i just saw the yellow dot and I normally think that means you have to throw chicken bones at it or something21:52
timurhahahaha21:52
timur"arise chicken!"21:52
ntataclayg, so, I rebased it once when the ip validations methods got moved..21:53
pdardeauntata: that may be all well and good, but what did you do with the chicken bones? :-)21:54
claygok, so I think maybe the yellow dot is fine, but I don't understand I think shashi's comment about the previous change - but I think she was just confused - so that's ok21:56
*** mmcardle has joined #openstack-swift21:59
*** rcernin has quit IRC22:02
*** asettle has quit IRC22:04
claygntata: i still feel guilty about `header_line, print_dev_f = _make_display_device_table(builder)` :\22:05
*** diogogmt has quit IRC22:05
claygI think it *works* great - the result looks fabulous22:05
admin6Hi there, I have plenty of these logs into the object reconstructor : object-reconstructor: 10.10.2.53:6000/s03z3ecd01/34782 Unexpected response: ":ERROR: 0 '15 seconds: /srv/node/s03z3ecd01/.lock’ ». Do you know what they means?22:05
claygso normally I wouldn't care *at all* - I have no obvious idea how to make it better22:05
claygbut... i feel guilty that maybe you think "oh maybe this mess of closures and functions returning functions is what clay thinks is good looking code" - it wasn't that22:06
claygi just threw it over the wall because I was getting frustrated at how difficult it was to draw some good lines for method extraction22:07
clayganyway, sorry - i'm not sure if my point is to subtle for irce22:08
clayg*irc22:08
ntataI think it this way too - I definitely like the idea of separating _make_display_device_table rather than cluttering *that huge formatting code just to print neatly* in the method that's constructing the output22:11
claygyeah, something has to be better than nothing22:12
claygntata: ok, i'd like someone else to think about adding the stub files to the tests tree - i like that too - but it's new22:13
admin6I also have a lot of reconstruct error like this after my last rebalance : object-reconstructor: Unable to get enough responses (8/9) to reconstruct 10.10.2.54:6000/s04z4ecd08/54781/AUTH_Zoo/20160808_O1/129617/21662868/original.JPG policy#1 frag#11 with ETag 9d8bb41cac43ecf770e20906cd86153b.  Which let me think that the object is lost and can’t be reconstructed. However, I can do a GET on the object and it is perfectly valid. Could that be linked22:13
admin6the Unexpected response error?22:13
claygtimburke: you have opinions on things - patch 319387 puts files that aren't .py in test/unit/cli - you care?22:14
patchbotclayg: https://review.openstack.org/#/c/319387/ - swift - swift-ring-builder output corrected for ipv622:14
*** sebl_ has joined #openstack-swift22:14
ntataI agree! It does need some thought with gate tests22:14
claygadmin6: oh yah, that's all related, yuk22:15
claygadmin6: soo.... basically... i think reconstruction is like currently probably super busy and there's a good chance it will eventually work itself out :\22:16
claygi mean the timeout is pointing at "overloaded" - but the problem is really a efficiency issue22:16
admin6clayg: yeah the reconstructor seem to be very busy, but it is taking about 250 hours to perform a full reconstruction pass22:17
claygadmin6: do you do anything kind of partition placement monioring?  like dispersion-report or like http://docs.openstack.org/developer/swift/admin_guide.html#checking-handoff-partition-distribution22:18
claygadmin6: rofl - sorry it's not funny :'(22:18
claygit's really not funny :'(22:19
claygadmin6: how many devices do you have in the EC cluster - what was the extent of the capacity change?22:19
admin6clayg: here is my ring definition : 262144 partitions, 12.000000 replicas, 1 regions, 4 zones, 48 devices, 0.01 balance, 0.00 dispersion22:21
timburkeclayg: i'm not opposed. might want to make it more clear that these "stub" files are intended for use in test_ringbuilder (maybe have a 'test_ringbuilder' directory?) but this seems like a thing that might be nice for some of the ring rebalance tests22:21
*** oshritf has quit IRC22:22
claygtimburke: oh good point - i sorta thought the module and class name went in the file names22:23
claygoh, i had done something sorta even more stupid -> https://review.openstack.org/#/c/345674/22:24
patchbotclayg: patch 345674 - swift - crazy idea to check output (ABANDONED)22:24
claygmaybe the implict coupling of the test name and the stub file name is less useful than just assert(output, './path/to/stub') or something...22:25
claygidk22:25
claygtimburke: we can probably change it later if more files start to grow and we need better organization22:26
admin6clayg: here is the dipsersion verbose result : http://paste.openstack.org/show/552780/.  I had 32 devices with a weight of 4000 each before rebalance, and I just add 16 disk with a weight of 400 each into the last rebalance.22:26
claygok, so it's a pretty decent capacity increase when it's all said and done?  +50%22:27
claygso you haven't had a rebalance finish since you pushed out this ring yeah?  you're seeing 250 from the estimation log line?22:28
admin6clayg: yes, but only 5% more capacity for this rebalance, which seem not to much to be able to reconstruct, isn’t it?22:29
claygadmin6: yeah I think you did a good job trying to manage this as a conservative adjustment22:30
admin6clayg: yes, here a two reconstuctor log example : STACO2 object-reconstructor: 161445/202505 (79.72%) partitions of 2/12 (16.67%) devices reconstructed in 117100.77s (1.38/sec, 212h remaining)22:30
admin6STACO1 object-reconstructor: 742821/762666 (97.40%) partitions of 7/8 (87.50%) devices reconstructed in 341089.37s (2.18/sec, 16h remaining)22:31
clayghow many files/gb's are we talking about here?  How much real data is %5?22:31
*** klamath has quit IRC22:32
admin6This EC ring is currently filled with 42TB of data, so 5% means 2,1TB22:33
claygok, so it's been running 32 hours - oic, it's not *really* 80% done - it's only parsed 2/12 devices :\22:33
admin6clayg: yes, 32 hours to parse only 2 over 12 devices, so as the last 4 devices are only 10% weight of the other, it is still more than 150h to perform the full reconstruction.22:36
admin6clayg: do you have suggestion to reduce the overload of the reconstructor process? and it seems antithetical but do you have suggestion to accelerate it ?22:39
*** vint_bra has quit IRC22:40
admin6clayg; anf BTW, what exactly means the concurrency value for the reconstructor?22:40
*** vint_bra has joined #openstack-swift22:40
*** itlinux has joined #openstack-swift22:42
*** lcurtis has quit IRC22:45
*** vint_bra has quit IRC22:45
*** mmcardle has quit IRC22:45
*** itlinux has quit IRC22:46
admin6clayg: also on these ACO servers, the swift-container replicator is always taking 99% of CPU, and there are 24 (number of core on these servers) swift-container-server processes that take more than 10% CPU. is that normal?22:49
claygit's ultimately the number of jobs that an instance of the reconstructor will run at once22:54
claygwhat do you have concurrency set to?  I was going to suggest you increase it - obvs.  :D22:55
admin6clayg: ok, when I first set the concurrency to 8 (which was with the default value before) it speed up the number of partition per second up to 8. but now the concurrency is still set to 8 but the artition per second goes down to around 2/sec22:56
admin6I set it to 8  about 2 weeks ago22:57
claygadmin6: I think the default is 1?  which is too low for almost any real deployment :D22:58
admin6clayg, that’s what i discover 2 weeks ago ;-)22:58
claygadmin6: ok, so you have 8 "outgoing" syncs per node - times four nodes - that's only 32 outgoing syncs across the whole cluster22:59
claygadmin6: there's also some tunring on the incoming side22:59
claygyou have seperate replication network?22:59
claygwell... at least seperate processes (replication object servers)22:59
claygor they all talk to the same ports in the ring?22:59
clayg"replication_concurrency" - check out the notes in the sample config for the object-server23:00
admin6clayg: replication is done on same port but on a different ip address, however it currently a fake as both ip adress are on the same card plugged on a 10GB switch23:01
claygI think you have 32 outgoing *jobs* (which i *guess* will only ever need to hold a single SSYNC connection - most of the chatter is either REPLICATION requests or GETs for fragments)23:02
clayg... but if you're running the default replication_concurrency of 4 and one_per_device = True - you only have 16 slots available for those 32 jobs?23:02
claygadmin6: ok, but the *processes* it's the same object-server *process* as your cluster/proxies talk to?23:03
claygmost of our deployments use the same physical network - but it's important with ssync that it's a different object-server instance (we spin up a /etc/swift/object-server/2.conf for replication on a different port)23:03
claygeither way - you probably need to tune up replication_concurrency on the object server (which would *ideally* be a seperate process than the once your proxies/clients talk to) - and watch out for lp bug #144687323:04
openstackLaunchpad bug 1446873 in OpenStack Object Storage (swift) "ssync doesn't work with replication_server = true" [Medium,Confirmed] https://launchpad.net/bugs/144687323:04
admin6clayg: yes, I’ve only one object server instance per server23:05
admin6clayg: do you have a good link to follow about how to separate object server process? and do you also suggest me to increase the concurrency of the object reconstructor ?23:07
claygok, well just keep turning up reconstructor concurrency and object-server replication_concurrency until it a) doesn't help b) makes your clients notice23:08
*** chsc has quit IRC23:08
admin6clayg: ok, that seems a good way of finding the best concurrency value :-D23:09
claygadmin6: so the concurrency of the reconstructor and replication_concurrency need to match - they're both per server - so you *could* just try 8, 8 - 16, 16 - 32, 3223:10
claygsomewhere around device count per node I can't imagine it really getting much better - but even as high as 4x device count *might* accidently sort of keep helping23:10
claygbut at that point you have to turn off replication_one_per_device23:11
claygbe sure to report back!23:11
claygand i'm *guessing* well before that you'll have to spot and move to seperate replication servers23:11
admin6clayg: Ok; many thanks, one last question : on these ACO servers, the swift-container replicator is always taking 99% of CPU, and there are 24 (number of core on these servers) swift-container-server processes that take more than 10% CPU. is that normal?23:12
claygthis is the best doc on seperate replication servers -> http://docs.openstack.org/developer/swift/replication_network.html23:12
claygadmin6: http://docs.openstack.org/developer/swift/admin_guide.html#checking-handoff-partition-distribution is also worth a read23:13
claygthe "status" lines from the replciator/reconstructor aren't as good of a proxying during rebalance as watching the handoff parts get moved across the cluster23:13
claygso if you can monitor your handoff counts per device and sum it up across the cluster you can do a better job predicting how many are left and the rate at which they're being reoved23:14
admin6clayg: ok. I’ll try to digest all that. many thanks for your great help and expertise.23:16
claygadmin6: RE container processes - you mean like 99% of *one* cpu?  i don't have a production node handy at the moment - but those things are probably somewhat CPU busy and single thread - so mabye?23:16
admin6clayg: yes 99% of one cpu.23:17
claygidk, seems like they should be doing some cpu... are your container dbs on the object disks?  is there a lot of load in wait or all user?23:17
claygerr.. sorry some i/o23:17
claygobs.23:17
claygand np23:17
*** diogogmt has joined #openstack-swift23:18
admin6clayg: account and container db are on separated SSD devices23:19
clayghrmm... ok23:19
*** david-lyle has quit IRC23:20
admin6clayg: and this EC ring is adding about 1,2TB of new data per day, so that should load the container a bit23:21
claygcontainer load is per object not per byte (obs.) but 1TB a day is a good growth curve!  hopefully we can get this rebalance tuned to keep up - but it could be tight :\23:22
admin6clayg: yes. thats the source of my questions. being able to make the ring grow at least as far as it filled in ;-)23:24
admin6as fast23:24
*** kei_yama has joined #openstack-swift23:27
*** vinsh has quit IRC23:35
claygadmin6: fwiw i spotted checked a few nodes with decent workload and similar setup - and I don't have any container-replicators running hot - dunno the issue, you might monitor it and put it on the list to loop back too after the ingest/rebalance stuff23:39
*** david-lyle has joined #openstack-swift23:39
admin6clayg: ok. I’ll try to investigate that deeper also.23:40
*** nadeem has quit IRC23:49
*** rfinn has quit IRC23:50
*** hosanai has joined #openstack-swift23:50
*** ChanServ sets mode: +v hosanai23:50

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