Thursday, 2017-10-05

*** gyee has quit IRC00:04
not_meThank you for your answers clayg!00:17
claygnot_me: oh - did you figure something out?00:18
claygWell... keep at it. Let us know what you figure out!00:21
not_meI reduced the replication pass time by 10 by increasing the object-replicator concurrency from 2 to 1600:23
not_mefrom 1.4 partition/sec to 11.27 partition/sec00:24
not_meI'm still trying to understand this better though. I'm still unclear on why it's still slower than my other rings.00:26
*** vint_bra has joined #openstack-swift00:38
*** tovin07_ has joined #openstack-swift00:48
*** mingyu has quit IRC01:02
*** mingyu has joined #openstack-swift01:03
*** vint_bra has quit IRC01:05
*** cshastri has joined #openstack-swift01:05
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient master: Updated from global requirements  https://review.openstack.org/8925001:12
openstackgerritMerged openstack/swift feature/deep: unit tests for _misplaced_objects  https://review.openstack.org/50925601:13
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873601:13
*** wes_dillingham has quit IRC01:24
*** hoonetorg has quit IRC02:02
*** afazekas has quit IRC02:02
*** afazekas has joined #openstack-swift02:02
*** hoonetorg has joined #openstack-swift02:03
*** stewie925 has joined #openstack-swift02:11
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient master: Updated from global requirements  https://review.openstack.org/8925002:44
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873602:45
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient master: Updated from global requirements  https://review.openstack.org/8925003:15
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873603:17
*** abhitechie has joined #openstack-swift03:26
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient master: Updated from global requirements  https://review.openstack.org/8925003:36
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873603:37
*** gkadam has joined #openstack-swift03:37
*** tonyb has quit IRC03:42
*** two_tired has joined #openstack-swift03:46
*** links has joined #openstack-swift03:48
*** tonyb has joined #openstack-swift03:56
*** klrmn has quit IRC03:59
*** SkyRocknRoll has joined #openstack-swift03:59
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient master: Updated from global requirements  https://review.openstack.org/8925004:05
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873604:07
*** abhitechie has quit IRC04:12
*** jamielennox has quit IRC04:14
*** jamielennox has joined #openstack-swift04:18
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient master: Updated from global requirements  https://review.openstack.org/8925004:22
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873604:23
*** two_tired has quit IRC04:29
*** abhitechie has joined #openstack-swift04:31
*** gyee has joined #openstack-swift04:33
*** mingyu has quit IRC04:34
*** mingyu has joined #openstack-swift04:35
*** mingyu has quit IRC04:39
*** mingyu has joined #openstack-swift04:44
*** chlong_ has joined #openstack-swift04:50
*** psachin has joined #openstack-swift05:01
*** gyee has quit IRC05:05
*** abhinavtechie has joined #openstack-swift05:12
*** abhitechie has quit IRC05:12
*** SkyRocknRoll has quit IRC05:30
openstackgerritTim Burke proposed openstack/swift feature/deep: Include deleted objects when moving misplaced objects  https://review.openstack.org/50949605:35
openstackgerritTim Burke proposed openstack/swift feature/deep: Eliminate _generate_object_list method  https://review.openstack.org/50950805:35
openstackgerritTim Burke proposed openstack/swift feature/deep: Don't lose timestamp info when moving misplaced objects  https://review.openstack.org/50958905:35
timburkeacoles: haven't actually looked at p 509589 yet; will take a look tomorrow though05:36
patchbothttps://review.openstack.org/#/c/509589/ - swift (feature/deep) - Don't lose timestamp info when moving misplaced ob...05:36
*** ChubYann has quit IRC05:41
*** SkyRocknRoll has joined #openstack-swift05:46
*** dhellmann has quit IRC05:56
*** dhellmann has joined #openstack-swift05:58
*** alecuyer has quit IRC06:06
*** rledisez has quit IRC06:06
*** alecuyer has joined #openstack-swift06:07
*** rledisez has joined #openstack-swift06:07
*** chlong_ has quit IRC06:13
*** rcernin has joined #openstack-swift06:24
*** spectr has quit IRC06:34
*** spectr has joined #openstack-swift06:34
*** zaitcev has quit IRC06:48
*** zaitcev has joined #openstack-swift06:55
*** ChanServ sets mode: +v zaitcev06:55
*** silor has joined #openstack-swift06:57
*** abhinavtechie has quit IRC07:04
*** abhitechie has joined #openstack-swift07:04
*** cbartz has joined #openstack-swift07:06
*** tesseract has joined #openstack-swift07:07
*** pcaruana has joined #openstack-swift07:08
*** silor has quit IRC07:21
*** abhitechie has quit IRC07:47
*** geaaru has joined #openstack-swift07:49
*** abhitechie has joined #openstack-swift07:51
*** abhitechie has quit IRC08:08
*** spectr has quit IRC08:09
*** spectr has joined #openstack-swift08:10
*** abhitechie has joined #openstack-swift08:16
*** spectr has quit IRC08:17
*** spectr has joined #openstack-swift08:18
openstackgerritMerged openstack/swift feature/deep: Include deleted objects when moving misplaced objects  https://review.openstack.org/50949608:24
openstackgerritMerged openstack/swift feature/deep: Eliminate _generate_object_list method  https://review.openstack.org/50950808:24
*** abhitechie has quit IRC08:25
*** oshritf has joined #openstack-swift08:44
acolesmattoliverau: thanks for this comment https://review.openstack.org/#/c/509508/1/swift/container/sharder.py@1297, makes sense now!09:09
patchbotpatch 509508 - swift (feature/deep) - Eliminate _generate_object_list method (MERGED)09:09
acolesI copied it to a trello card (low priority) for us to consider the business of the PUTs lying in pending file for a period of time09:10
acoleshttps://trello.com/c/P3ZgtFBV/108-check-shard-range-put-path-to-other-containers09:11
acolestimburke: NP thanks for getting all the others in that chain merged!09:12
openstackgerritAlistair Coles proposed openstack/swift feature/deep: remove unused method  https://review.openstack.org/50972309:17
acolestimburke: I'm feeling more courageous today ^^ :P09:18
*** mvk has quit IRC09:28
openstackgerritKota Tsuyuzaki proposed openstack/swift master: Follow up for symlink implementaion  https://review.openstack.org/50914909:28
*** mvk has joined #openstack-swift09:47
*** janonymous has quit IRC09:49
acolesI have created a 'low hanging fruit' label on https://trello.com/b/z6oKKI4Q/container-sharding and marked a few cards09:50
acolesnotmyname: ^^09:50
acolesgo to Show Menu->Filter Cards09:51
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Don't lose timestamp info when moving misplaced objects  https://review.openstack.org/50958909:58
*** tovin07_ has quit IRC10:09
*** HCLTech-SSW has joined #openstack-swift10:35
HCLTech-SSWHi10:36
rledisezhi HCLTech-SSW10:36
HCLTech-SSWwe have posted few observations over the gerrit10:37
rledisezyeah, i got the notification, i'll have a look this afternoon10:40
rledisezHCLTech-SSW: btw, what timezone are you from?10:41
*** abhitechie has joined #openstack-swift10:41
HCLTech-SSWrledisez: We are from IST timezone10:43
*** spectr has quit IRC10:54
*** HCLTech-SSW has quit IRC11:03
*** kei_yama has quit IRC11:24
*** cshastri has quit IRC11:40
*** ianychoi has quit IRC11:46
*** f0o has quit IRC12:02
*** f0o has joined #openstack-swift12:19
*** f0o has quit IRC12:33
kota_acoles: still?12:33
*** f0o1 has joined #openstack-swift12:34
*** f0o1 has quit IRC12:35
kota_it seems acoles not here now.12:36
kota_it's ok, will ping tommorow again12:36
*** f0o1 has joined #openstack-swift12:37
*** f0o has joined #openstack-swift12:37
openstackgerritMerged openstack/swift feature/deep: remove unused method  https://review.openstack.org/50972312:38
*** f0o1 has quit IRC12:44
*** links has quit IRC12:44
acoleskota_: sorry I was away for lunch12:49
kota_acoles! no worries12:50
*** catintheroof has joined #openstack-swift12:50
*** catintheroof has quit IRC12:51
*** catintheroof has joined #openstack-swift12:51
kota_acoles: quick question. could we use content-type field for specific middleware use case?12:52
kota_e.g. i'm trying to think of using content-type for symlink likely Content-Type: application/symlink; target=/acc/cont/obj12:53
acoleskota_: do you mean overwrite a client content-type or append to the end of the client content-type?12:53
kota_yup12:53
kota_ah12:53
kota_overwrite a client content-type12:53
kota_only when it's symlink request12:54
kota_symlink=put12:54
*** gkadam has quit IRC12:54
kota_and add the note for docs absolutely.12:54
acoleskota_: I just looked to see if SLO does similar with the manifest, but I think not12:55
kota_any reasons?12:56
*** gkadam has joined #openstack-swift12:57
acoleskota_: content-type can be updated on a POST12:58
acolesI think12:58
kota_oh12:58
kota_exactly12:58
kota_hmm...13:00
acolesso anything added to content-type on PUT must be also added on POST13:00
acoleswe have special case in object server to handle swift_bytes that is appended by slo to content-type but I would not recommend repeating that pattern13:01
acoles but, symlink POST is weird anyway, so maybe?13:01
*** gkadam has quit IRC13:02
*** spectr has joined #openstack-swift13:02
acoleskota_: what is your goal?13:02
kota_acoles: lol but i think we cannot find if the POST is against to symlink or not. It's not guranteed.13:03
kota_acoles: the reason I thought it, is...13:03
kota_https://review.openstack.org/#/c/232162/59/swift/common/middleware/symlink.py@29713:04
patchbotpatch 232162 - swift - Symlink implementation.13:04
*** abhitechie has quit IRC13:05
kota_I'd like to avoid to use etag space to keep symlink path info.13:05
kota_hmm... m_kazuhiro commented something, not yet checked.13:05
kota_and IF we want to know if the object is symlink or not in object listing API (i.e. GET container), content_type seems to be better place I thought.13:08
kota_not sure if we REALLY want the symlink info at object listing though.13:09
kota_acoles: and i thought you know more about content-type handling than me :)13:09
kota_that's why I asked you, acoles13:09
*** SkyRocknRoll has quit IRC13:10
acoleskota_: the goal makes sense13:10
acoleswe did append to etag for encryption, need to remind myself what we did there13:10
acolesetag has the advantage of only being set on PUT13:10
kota_oic13:11
kota_it cannot be updated by POST13:11
kota_however, it's also risky for symlink because if the middleware pulled out (removing from pipeline), no middleware translate the hash appendix (symlink info) anymore?13:13
kota_i think, the reason why encryption could do it, is encryption should not be removed once it was deployed, yeah?13:13
acolescorrect13:14
kota_or, if no special use case for now, removing the staff for now to land it, and then, thinking of how to implement when it is needed later <- it seems good approach to me.13:16
kota_though we need to ask to primary users, m_kazuhiro, tdasilva, and maybe timburke?13:17
openstackgerritMerged openstack/swift master: Add account_autocreate=true to internal-client.conf-sample  https://review.openstack.org/50744713:17
kota_and from the comment, m_kazuhiro doesn't have strong requirement for now... hmmm13:18
acoleskota_: but if the symlink info is not in listing in first version then a client can never assume it is in listing so client will always need to check the object :(13:19
* kota_ have to think about the use case and risk if we don't set the info for object listing.13:19
kota_acoles: sure, that could be painful13:19
acolesI guess if symlink is added to the listing then a client can be optimised when it finds info in listing13:19
kota_and should it be into hash space in your opinion?13:20
acolesif the concern is symlink middleware being removed from pipeline, is there a case to have the gatekeeper for example always clean up etag response headers (truncate to length of etag)...hmmm..that scares me13:21
acolessplit on ; would be safer13:21
acoleskota_: I need to understand better symlink POST - if it is not possible to POST to a symlink without it ceasing to be a symlink, then maybe content-type is ok to override13:22
acoles...but swift_bytes was a pain, because it mixes data-state with content-type and the two can change at different times13:24
kota_acoles: oops. true.13:24
kota_sigh, I wonder if i could make object-server could handle the POST, like if it's symlink (diskfile has X-Symlink-Target), drop content-type change for container-update.13:26
kota_probably, I need to dig out and learn swift_bytes and their logics.13:26
kota_thx acoles, that was helpful!13:27
acolesproblem is object server may not have up to date .data file so may not know it should drop the content-type from the update13:27
acoleskota_: swift_bytes is a bad pattern13:28
kota_ok13:28
acolesX-Object-Sysmeta-Container-Update-Override-Size=swift_bytes would be better if we could rewrite history :)13:29
kota_acoles: sometimes, we wonder if we had rewrite history ;)13:29
kota_like PUT+POST for EC :/13:30
kota_had be able to13:30
kota_ah, we wish? no sense for my English.13:31
acolesprobably 'wish' but both are funny :)13:31
kota_i wish i were a bird <- it's the easiest example, students learn at schools.13:32
kota_acoles: thanks teacher ;)13:32
acolesi wish I knew the answer ;)13:33
kota_k, anyway, thanks and being offline to prepare to go my bed ;)13:34
acolesgood night kota_13:34
kota_good night.13:34
*** spectr has quit IRC13:40
*** chlong_ has joined #openstack-swift13:46
*** spectr has joined #openstack-swift13:57
*** spectr has quit IRC14:07
*** spectr has joined #openstack-swift14:08
openstackgerritAlistair Coles proposed openstack/swift feature/deep: include deleted objects when cleaving  https://review.openstack.org/50979314:23
*** vint_bra has joined #openstack-swift14:37
*** oshritf has quit IRC14:45
*** gyee has joined #openstack-swift14:51
*** wes_dillingham has joined #openstack-swift14:52
*** oshritf has joined #openstack-swift15:00
*** cbartz has quit IRC15:02
*** mat128 has joined #openstack-swift15:05
notmynamegood morning15:20
*** MVenesio has joined #openstack-swift15:23
*** oshritf has quit IRC15:28
*** chinkara has joined #openstack-swift15:28
*** MVenesio has quit IRC15:34
*** cbartz has joined #openstack-swift15:35
*** MVenesio has joined #openstack-swift15:36
*** chsc has joined #openstack-swift15:36
*** chsc has joined #openstack-swift15:36
*** chinkara has quit IRC15:38
*** pcaruana has quit IRC15:39
timburkegood morning15:45
*** spectr has quit IRC15:51
timburkeacoles: kota_: X-Object-Sysmeta-Container-Update-Override-Size=swift_bytes would mess up our account/container bytes-used bookkeeping -- there just isn't a good answer on SLO sizes in container listings :-(15:52
acolestimburke: right. don't worry, it wasn't a serious suggestion.15:53
timburkehey, rewriting history's easy -- just a `git push -f` away ;-)15:54
*** chsc has quit IRC16:11
*** cbartz has quit IRC16:12
*** rcernin has quit IRC16:13
*** rcernin has joined #openstack-swift16:13
*** psachin has quit IRC16:14
*** rcernin has quit IRC16:14
*** klrmn has joined #openstack-swift16:14
*** janonymous has joined #openstack-swift16:25
*** tesseract has quit IRC16:29
*** geaaru has quit IRC16:29
*** mvk has quit IRC16:33
*** abhitechie has joined #openstack-swift16:33
*** abhitechie has quit IRC16:35
*** abhitechie has joined #openstack-swift16:35
*** abhitechie has quit IRC16:36
*** abhitechie has joined #openstack-swift16:37
*** abhitechie has quit IRC16:38
openstackgerritTim Burke proposed openstack/swift feature/deep: Add Container Sharder to source docs  https://review.openstack.org/50983016:38
*** abhitechie has joined #openstack-swift16:39
*** SkyRocknRoll has joined #openstack-swift16:48
*** SkyRocknRoll_ has joined #openstack-swift16:49
*** tesseract has joined #openstack-swift16:50
*** abhitechie has quit IRC16:51
*** abhitechie has joined #openstack-swift16:51
*** abhitechie has quit IRC16:54
*** abhitechie has joined #openstack-swift16:54
*** chsc has joined #openstack-swift17:01
*** chsc has joined #openstack-swift17:01
*** abhitechie has quit IRC17:04
*** abhitechie has joined #openstack-swift17:05
*** silor has joined #openstack-swift17:11
*** tesseract has quit IRC17:22
*** abhitechie has quit IRC17:24
*** SkyRocknRoll_ has quit IRC17:30
*** mvk has joined #openstack-swift17:32
*** mingyu has quit IRC17:37
*** mingyu has joined #openstack-swift17:41
*** SkyRocknRoll_ has joined #openstack-swift17:42
thurloatwhat process cleans up deleted objects if an object server were off when the object was deleted initially?17:42
thurloatis that the auditor's job?17:43
notmynamereplicator17:44
*** mingyu has quit IRC17:46
thurloatso it comes across an object after scan that it knows it shoudln't have, looks it up and sees it should be toast, then cleans up?18:01
openstackgerritAlistair Coles proposed openstack/swift feature/deep: split merge_items into merge_objects and merge_shard_ranges  https://review.openstack.org/50985718:01
openstackgerritAlistair Coles proposed openstack/swift feature/deep: add post-sharding object PUT to probe test  https://review.openstack.org/50985818:04
notmynamethurloat: the tombstone files are replicated, and if the tombstone is newer than the object data, the object data is unlinked18:08
openstackgerritAlistair Coles proposed openstack/swift feature/deep: remove support for +/- relative object_count in shard updates  https://review.openstack.org/50986018:10
timburkethurloat: when the DELETE request comes in, whichever object servers are available write down "tombstones" and unlink any data they had for the name. those tombstones hang around for some period of time (the reclaim_age; defaults to one week). from there, it's like notmyname said -- the tombstones get replicated and replace any data on nodes that missed the original DELETE18:11
timburkeacoles: if you keep sending more patches for me to review, i'll never get around to submitting another address-some-review-comments patch! :P18:13
acolestimburke: sorry :( I *am* reviewing your doc patch right now18:13
timburkethanks. should be pretty quick18:14
openstackgerritMerged openstack/swift feature/deep: Don't lose timestamp info when moving misplaced objects  https://review.openstack.org/50958918:14
timburkei just need to crank through and set a new high-water mark for myself18:14
acolesoh, that reminds me... mattoliverau can you lease look at patch 509860 - it's removing code that I couldn't see being used by I'd really value your blessing on that18:15
patchbothttps://review.openstack.org/#/c/509860/ - swift (feature/deep) - remove support for +/- relative object_count in sh...18:15
claygthurloat: FWIW SwiftStacks default object reclaim age is more like 1 mo - if you have a node "down" for a long time the the tombstones can get reclaimed while the node holding the data is down and re-introduce the dark data!18:15
acolestimburke: the doc build failed for me with some picky block quote error, I'll try to fix18:15
timburkebah18:15
claygthurloat: If you have a node out longer than reclaim age you should have already taken it out of rings - and you need to reintroduce it to the cluster and fresh new capacity18:15
clayg*as fresh...18:16
acolestox -e docs is so opinionated these days18:16
acolesshould just be happy we have docs18:16
openstackgerritMerged openstack/swift feature/deep: include deleted objects when cleaving  https://review.openstack.org/50979318:16
clayglol18:16
thurloatclayg: thanks for all the info. looks like it might be in my best interest to bring reclaim_age down a bit18:17
thurloatat least temporarily18:17
clayg*down*??  do you have a lot of old tombstones?18:17
clayglike default is 1 wk, but IMHO 4 wk is a better default (*increate value by factor of 4*) - but maybe IME unless you're a dedicated Swift operations team you don't want to have to be super responsive to hardware outages and tend to not DELETE data once it's in Swift - YMMV18:19
thurloatyeah i have a bunch that I'd like cleaned up in the near term. i'll likely take your advice after the fact to increase the value once all is calm18:21
claygoic, right on - good luck18:24
thurloatthanks, need it ;)18:24
claygthere was also an old swift bug that caused some hashdirs to get sort of ... stale and they'd just have a bunch of older than reclaim age tombstones in them - that was finally fixed tho - by mahatic acctually IIRC (hi mahatic!  HOPE you're sleeping!)18:25
thurloatoh that's interesting18:25
thurloatez keyword to search the git log for?18:25
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Add Container Sharder to source docs  https://review.openstack.org/50983018:26
timburkehttps://github.com/openstack/swift/commit/321bb91 i think?18:27
timburkemaybe18:28
acolestimburke: go aheaad and hit +A on 509830 if you're happy with my tweaks - passed locally for me now18:28
acolesgood night18:28
timburkegood night acoles!18:29
thurloatnice timburke, thanks. definitely applies to me.18:29
clayg*YES* it was mahatic !18:30
claygthanks timburke18:30
claygoh... wait no ... not that one I think...18:30
claygboom!  still mahatic tho!  https://github.com/openstack/swift/commit/81d4673674febdbe0bba6e27a6d24739456eb3c418:31
*** SkyRocknRoll_ has quit IRC18:33
*** janonymous has quit IRC18:34
*** ChubYann has joined #openstack-swift18:40
*** chlong_ has quit IRC18:44
*** chlong_ has joined #openstack-swift18:59
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient master: Updated from global requirements  https://review.openstack.org/8925019:01
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873619:02
thurloatoh great clayg thanks again!19:13
openstackgerritTim Burke proposed openstack/swift feature/deep: Address review comments  https://review.openstack.org/50988419:36
*** bill_az has joined #openstack-swift19:37
*** chlong_ has quit IRC19:44
*** wes_dillingham has quit IRC20:12
*** stewie925 has quit IRC20:18
*** mat128 has quit IRC20:35
brianclineis there any worrisome/risky reason that the ring builder doesn't let you move devices from one zone to another?20:35
*** catintheroof has quit IRC20:56
*** MVenesio has quit IRC20:57
claygbriancline: not in my opinion21:18
claygso... obviously doing that can have an effect on dispersion - and as a result some parts might want to move after you do it21:18
claygand maybe a *lot* of parts depending on the topology and what exactly you're moving where21:19
claygthe pathological case is *every* part-replica on the device needs to go back to the region/zone/server it was on21:19
claygbut... w/e21:19
claygrebalance is good at that21:19
claygand there's a better than even chance most of the time it'll be *fine*21:19
claygrezone it, rebalance, push rings, bob's your uncle21:20
claygi've done it "by hand" - the data-structures don't give a %^& - there's just no native support from the cli21:20
claygyou should *totally* add it!21:20
clayg;)21:20
*** rcernin has joined #openstack-swift21:22
*** silor has quit IRC21:26
timburkei feel like it could be particularly handy if you start out with a smallish cluster then decide to add a second region by physically moving existing servers to the new DC21:47
claygikr!?21:47
claygtimburke: no worries briancline will save us21:47
*** bill_az has quit IRC22:00
*** rcernin has quit IRC22:06
mattoliveraumorning22:37
*** wes_dillingham has joined #openstack-swift22:51
brianclinelol23:00
brianclineyeah, I can give it a go. I've done it by hand recently for a one-off node and was fairly straightforward, and now need to do it for a few more23:01
claygyeah if you could just re-imagine the whole swift-ring-builder cli interface that'd be *great*23:02
brianclineoh sure!23:02
brianclineI'll add that right after my tests ;)23:04
clayg;)23:04
mattoliveraulol23:13
brianclinewould also like to add a patch so that the builder's internal version number gets included in the ring.gz as well23:20
brianclinemakes it a lot easier for a machine to explicitly match a ring back to a specific builder23:21
clayg^ acoles torgomatic one of these days we're just going to distribute builders23:22
claygI bet we could serialize them such that you could open then and have a builder (and all it's extra bloat) or just open it and have the replica2part2dev table and the devs list for minimal memory footprint in workers23:23
claygthe problem sure is *not* the on-disk space, and there's no arguing it'd be *convenient* to the extra info23:24
*** abhitechie has joined #openstack-swift23:24
brianclinewondered about that. figured memory footprint when you've got beaucoup workers was maybe why23:25
*** chsc has quit IRC23:29
claygyeah - but one integer isn't going to make a difference23:29
claygthe builders *do* have some largish datastructures that you only need for rebalance that can bloat up the runtime - but it's not really the metadata - we just recently had a conversation about "well... if it's nice to have *this* piece; what about *this* one?  when do you stop?  should we just distribute the whole builder?"23:31
*** kei_yama has joined #openstack-swift23:34
mattoliverauclayg: +1. it would make life easier and loosing a builder file an obsolete problem.. just need to make sure we can only load what we need as a ring and we should be good :)23:44
brianclineoh yeah, def not worried about the version number. probably no more than a 1MB difference in total across all my clusters23:44
mattoliveraui remember discussing it was it PTG or Boston.. can't remember, but good idea23:45
brianclinei've never timed it - would loading something like a 2^20 builder take a lot longer than the ring?23:46
brianclinelike to a point where object workers (in python) would show a brief but noticeable bit of latency, i mean23:47
*** vint_bra has quit IRC23:55
claygneat!23:56

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