Thursday, 2017-09-21

*** gyee has quit IRC00:07
*** itlinux has quit IRC00:16
openstackgerritMatthew Oliver proposed openstack/swift feature/deep: sharding - Make swift-container-info shard aware  https://review.openstack.org/50558000:23
mattoliverau^^ just a rebase, but /me suspects it'll need to be rebased again soon with the merge from master patch ;)00:25
*** bigdogstl has joined #openstack-swift00:29
openstackgerritTim Burke proposed openstack/swift feature/deep: Bring us closer to master  https://review.openstack.org/50585800:31
timburkesorry mattoliverau, gonna push for the merge-from-master first :-)00:33
mattoliverauI know :)00:33
timburkethat follow-up i just pushed would be pretty nice, too00:34
timburkethough... maybe there aren't actually any conflicts00:34
mattoliverautimburke: nice!00:36
*** bigdogstl has quit IRC00:36
mattoliverauI love it when things get simpler :)00:36
* mattoliverau might go from a walk on the beach as I wait for tests to run ;)00:37
*** itlinux has joined #openstack-swift00:38
timburkeyou can go ahead and merge, but maybe wait until after the patch in the gate lands00:39
*** tovin07_ has joined #openstack-swift00:41
*** openstackgerrit has quit IRC00:41
*** openstackgerrit has joined #openstack-swift00:44
*** bigdogstl has joined #openstack-swift00:53
*** hoonetorg has joined #openstack-swift00:56
*** klrmn has quit IRC01:06
*** bigdogstl has quit IRC01:15
*** cshastri has joined #openstack-swift01:25
*** itlinux has quit IRC01:28
*** Sukhdev has quit IRC01:39
*** itlinux has joined #openstack-swift01:49
*** itlinux has quit IRC01:51
*** mingyu has quit IRC01:53
*** kota_ has quit IRC01:56
*** kota_ has joined #openstack-swift01:56
*** ChanServ sets mode: +v kota_01:56
*** kei_yama has quit IRC01:57
*** mingyu has joined #openstack-swift01:59
*** kei_yama has joined #openstack-swift02:04
*** vint_bra has joined #openstack-swift02:11
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient master: Updated from global requirements  https://review.openstack.org/8925002:17
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873602:18
*** bigdogstl has joined #openstack-swift02:25
*** bigdogstl has quit IRC02:33
*** mingyu has quit IRC02:45
*** mingyu has joined #openstack-swift02:47
*** mingyu has quit IRC02:48
openstackgerritMerged openstack/swift feature/deep: Merge branch 'master' into merge-from-master  https://review.openstack.org/50584402:49
*** gkadam-away is now known as gkadam02:55
*** janonymous has joined #openstack-swift03:00
*** vint_bra has quit IRC03:04
*** _ix has joined #openstack-swift03:10
*** Sukhdev has joined #openstack-swift03:24
*** bigdogstl has joined #openstack-swift03:31
*** bigdogstl has quit IRC03:35
*** kei_yama has quit IRC03:44
openstackgerritMatthew Oliver proposed openstack/swift feature/deep: Bring us closer to master  https://review.openstack.org/50585803:55
mattoliverau^^ fixes the pep8 error so I can merge it :)03:55
*** kei_yama has joined #openstack-swift03:59
*** bigdogstl has joined #openstack-swift04:00
*** bigdogstl has quit IRC04:11
*** silor has joined #openstack-swift04:23
*** SkyRocknRoll has joined #openstack-swift04:33
*** SkyRocknRoll has quit IRC04:34
*** bigdogstl has joined #openstack-swift04:38
*** psachin has joined #openstack-swift04:41
*** bigdogstl has quit IRC04:43
*** links has joined #openstack-swift04:43
*** SkyRocknRoll has joined #openstack-swift04:52
*** itlinux has joined #openstack-swift05:00
openstackgerritMatthew Oliver proposed openstack/swift feature/deep: Merge Shard-{Account, Container} to 1 metadata  https://review.openstack.org/50597605:01
*** pcaruana has joined #openstack-swift05:09
*** SkyRocknRoll_ has joined #openstack-swift05:15
*** SkyRocknRoll_ has joined #openstack-swift05:15
*** Sukhdev has quit IRC05:23
*** silor has quit IRC05:33
*** bigdogstl has joined #openstack-swift05:40
*** bigdogstl has quit IRC05:44
*** rmcall has quit IRC05:57
*** rmcall has joined #openstack-swift06:02
*** vito_ has joined #openstack-swift06:04
*** vito_ is now known as Guest9279606:04
*** bigdogstl has joined #openstack-swift06:05
*** rmcall has quit IRC06:06
*** bigdogstl has quit IRC06:09
*** Guest92796 has quit IRC06:25
*** rcernin has joined #openstack-swift06:28
openstackgerritMatthew Oliver proposed openstack/swift feature/deep: Use temp db and a rename for set_sharding_state  https://review.openstack.org/50600206:33
*** itlinux has quit IRC06:37
*** itlinux has joined #openstack-swift06:40
*** itlinux has quit IRC06:40
*** SkyRocknRoll_ has quit IRC06:46
*** cschwede has joined #openstack-swift06:47
*** ChanServ sets mode: +v cschwede06:47
*** SkyRocknRoll has quit IRC06:47
*** SkyRocknRoll_ has joined #openstack-swift07:00
*** SkyRocknRoll has joined #openstack-swift07:03
*** ChubYann has quit IRC07:04
*** pcaruana has quit IRC07:05
openstackgerritMerged openstack/swift feature/deep: sharding - Make swift-container-info shard aware  https://review.openstack.org/50558007:05
*** skudlik has joined #openstack-swift07:09
*** mingyu has joined #openstack-swift07:13
*** ChanServ sets mode: +o openstack07:14
*** mingyu has quit IRC07:14
*** bigdogstl has joined #openstack-swift07:17
*** tesseract has joined #openstack-swift07:19
*** bigdogstl has quit IRC07:22
*** pcaruana has joined #openstack-swift07:23
acolesgood morning07:25
*** cbartz has joined #openstack-swift07:27
acolesmattoliverau: are you still around?07:27
acolestimburke: thanks for the merge from master07:28
mattoliverauyeah, but I need to go save my wife from the toddler, mind if I go deal with the baby and get back to you in aabout and hour or so?07:30
acolesmattoliverau: no problem at all, thanks07:37
*** ypbg has joined #openstack-swift07:45
*** cschwede_ has joined #openstack-swift07:49
*** cschwede_ has quit IRC07:52
*** geaaru has joined #openstack-swift07:52
*** cschwede_ has joined #openstack-swift07:53
*** gkadam has quit IRC07:54
*** cschwede_ has quit IRC07:54
*** cschwede_ has joined #openstack-swift07:55
*** cschwede_ has quit IRC07:56
*** cschwede_ has joined #openstack-swift07:59
*** cschwede has quit IRC08:03
*** cschwede_ has quit IRC08:04
*** cschwede has joined #openstack-swift08:05
openstackgerritMerged openstack/swift feature/deep: Bring us closer to master  https://review.openstack.org/50585808:14
*** bigdogstl has joined #openstack-swift08:28
*** bigdogstl has quit IRC08:34
openstackgerritJoel Wright proposed openstack/swift master: Add Preamble and Postamble to SLO and SegmentedIterable  https://review.openstack.org/36537108:47
*** gkadam has joined #openstack-swift09:01
*** bigdogstl has joined #openstack-swift09:14
*** bigdogstl has quit IRC09:19
mattoliverauacoles: o/09:21
acolesmattoliverau: hi09:22
acolesmattoliverau: so I had a couple of questions around this patch https://review.openstack.org/#/c/505763/09:23
patchbotpatch 505763 - swift (feature/deep) - sharding: WIP make find_pivot_ranges a broker method09:23
mattoliverauoh yeah, I started making comments, but never pushed and on my other computer. opps09:24
mattoliverauoh cool, chrome has remembered them on another computer.. thats kinda scary09:24
acolesmattoliverau: the main thing was here https://review.openstack.org/#/c/505763/1/swift/container/sharder.py@90409:28
patchbotpatch 505763 - swift (feature/deep) - sharding: WIP make find_pivot_ranges a broker method09:28
acoles2 things actually: 1. should we just make sure that find_shard_ranges always gives us back the last range, so the special case is not needed and 2. what to do when creating a shard db fails09:29
mattoliverauthe initial version of the find shardranges would only find uppers, until it reached the end.. in which case the last upper to None (or now '') would be the last node.. but yeah, nothing stopping us from the finding ranges to add it.09:31
acolesworking backwards, I was thinking more about 2 and wonder if we should persist *all* the shard ranges that have been found even when we may fail to create the DBs. otherwise we'd waste all that scanning work that has been done to find the pivots09:31
*** SkyRocknRoll_ has quit IRC09:31
acolesbut that implies having some state in ShardRange to indicate that it has been found but not yet been created.09:32
mattoliverauhmm, well I agree we don't want to waste the scanning. So we make sure they're written to the shardranges table09:33
acolesyeah and in Denver we were talking about maybe having one daemon find the shard ranges and another (the replicator) process them, so persisting them as they are found would make sense for that too.09:34
mattoliveraucurrently we have an upto metadata for each index, which it updates once sharding.. if it can't and doesn't write it then this wont be updated and thus the cleave to the container will happen again.09:34
mattoliveraualthough the initial PUT wont. meaning it wont exist, but the cleave currently is a create and replicate so it will be created09:34
acoles'upto' is sysmeta on the root?09:35
mattoliverauIf we are doing cascade deletes where the shard audit will create missing containers inthe root container ranges, then this will work for missing PUTs during cleaving too09:35
mattoliverauupto on whatever container is cleaving09:35
mattoliverauso root initially, and on the shards09:35
mattoliveraujust so the nodes can coordinate. ie, I'm not finished sharding, don't unlink if my index hasn't finished cleaving otherwise we might miss data09:36
mattoliverauhowever, maybe adding a state isn't a bad idea... maybe it can be used when deleteting, marked as gone.. so we know if we need to recreate. But maybe that doesnt matter.09:38
acolesis that 'X-Container-Sysmeta-Shard-Last-%d' ?09:38
mattoliverauyup09:38
acolesgot it09:38
mattoliverauwhere %d is in index of the node.09:38
acolesyeah09:38
mattoliverauand that should persist beyond rebalances which is nice (ie. idx remains the same).09:39
acolesok, so in principle we need a way to differentiate between ShardRanges that have been found and those that have been cleaved. maybe that sysmeta does the job already, maybe we add state to the ShardRange.09:40
acolesfor now i just wanted to clarify the principle :)09:40
*** tesseract has quit IRC09:41
*** tesseract has joined #openstack-swift09:41
acolesI still need to climb the learning curve more before jumping on a solution09:41
mattoliverau+1 yeah, we need to keep track of where wrere up to.. but it gets complicated when we also want to keep track of each primary nodes progress in the off chance one contains data the others dont09:42
acolesyup09:42
acolesso another thing I noticed, when scanning for pivots, is that the 'progress' is calculated assuming container_shard_size doesn't change from one cycle to next. But it may change in config :(09:45
mattoliverauyeah.. that's a problem :(09:46
acoleswhich led to another question...when does the ShardRange object count first get updated?09:46
acolescos it seems to be zero when the range is first found09:46
mattoliverauat the moment the shardrange object count is being updated after every visit from a sharder. It sends and update to the root container.09:47
acoles(hmmm, the object count probably doesn't help cos it will change as more updates land in the shard?)09:47
mattoliverauhmm, yeah09:47
mattoliveraunothing stopping us from adding the inital count tho09:48
acolesright, that's what I wondered, whether each ShardRange needs to stash a shard_size which is its initial size. Then we can sum them to establish 'progress so far'09:49
*** mvk has quit IRC09:49
acolesor stash progress in sysmeta09:49
mattoliverauif we have the last pivot, do we need to know  the progress? we can just search until we've hit the end.. or not (hit batch)09:49
acoles^^ that works too, but the progress allows an optimisation where you can tell you're going to land past the end of the container without doing the query (if progress + shard_size > object_count)09:50
mattoliverauI can't remember what the offset will return if beyond the list.09:50
mattoliverauand maybe that was the problem09:51
mattoliverauyeah09:51
mattoliveraujust thinking out loud :)09:51
acolesme too!09:51
acolesok I'll ponder that some more.09:53
*** tovin07_ has quit IRC09:53
mattoliverauadding another field just to store counts while cleaving is annoying.09:54
acoleswe don't have to fix all this right now, I just want to build a picture of where we need to get to.09:54
mattoliverauwhen cleaving shards, the obj counts will not updated, only the ranges in the root will be.. so we can just use those counts to track09:54
mattoliverauwhen cleaving a root, we could maybe not update root range counts while cleaving09:55
mattoliverauthe progress is then easy to sum09:55
mattoliveraujust like we do for summing up ShardRanges09:55
acolesbut if all we have done is found (not yet cleaved) some ranges, then won't object counts still be zero?09:55
mattoliverauunless we put the shard_size in there09:56
acolesinto object_count?09:56
mattoliverauyeah, but dirty09:56
mattoliveraubut reusing what we have.09:56
acolesOIC09:57
mattoliveraurather then adding a feild that will exist for only a very short time in the containers liftcycle09:57
acolesyes. so we can think hard about whether that field would *ever* be useful later in the lifecycle, but I tend to agree.09:58
*** cshastri has quit IRC09:59
acolesa companion to 'X-Container-Sysmeta-Shard-Last-%d' might do it i.e. 'X-Container-Sysmeta-Shard-Progress-%d'09:59
acolesI'll try to get my head round  how 'X-Container-Sysmeta-Shard-Last-%d' is updated and think more on that10:00
mattoliverauoh yeah, thats true. we do only need to track progress upto.. not all since.. I'm over thinking10:01
acoleshow/when I mean10:01
mattoliverauyeah, cool.10:01
mattoliveraunice work finding those issues :)10:02
acolesof course, this is moot if we are only performing complete scans on smaller containers - we'll get all ShardRanges in one cycle. But I hate to punt on thinking through stuff like this and get bitten in the future.10:02
acolesone last thing...I'd like my broker find_shard_ranges to return a list of *ShardRanges*...but to construct them I need to build a shard name and that involves the node index. That would be the only reason to pass node info to the broker :( so can you remind me does the node index need to be in the name?10:06
*** kei_yama has quit IRC10:08
mattoliverauto be honest, I'm not sure having the nodeid in the name really gives us anything10:09
mattoliveraudoes it really matter who was the scanner.. and atm it should always be 010:09
mattoliveraumaybe <container>-<md5 of timestamp + pivot> is enough10:10
acoles'atm' yes. but maybe timestamp is enough?10:10
acoleslol. that!!10:10
mattoliverauyeah, lets drop the node idx.10:11
mattoliverau:)10:11
acolesdo we need <md5 of timestamp+lower+upper> *just in case another node finds different lower, same upper at same time ?!?10:12
acolesor is that overkill. IDK10:12
mattoliverautrue, but if the same container gets more then it's suppose to (in range) then misplaced object will move them and there should be less to move.10:13
acolesthere is also a rather fundamental assumption in swift about distinct timestamps ;)10:15
acolesmattoliverau: I just looked at my Canberra clock - thanks for coming back late to chat, really helped me. And today also started early for you with the meeting.10:16
*** mvk has joined #openstack-swift10:19
mattoliverauNps, thanks for all the awesome work and thought you've been putting in :)10:31
*** bigdogstl has joined #openstack-swift10:38
*** bigdogstl has quit IRC10:45
*** mat128 has joined #openstack-swift11:00
*** gkadam has quit IRC11:21
*** chlong has joined #openstack-swift11:52
*** psachin has quit IRC12:06
*** gkadam has joined #openstack-swift12:06
*** bigdogstl has joined #openstack-swift12:10
*** guimaluf has quit IRC12:25
*** MVenesio has joined #openstack-swift12:34
*** SkyRocknRoll has quit IRC12:41
*** catintheroof has joined #openstack-swift12:41
*** bigdogstl has quit IRC12:46
*** gkadam has quit IRC12:58
*** gkadam has joined #openstack-swift12:59
*** mat128 has quit IRC13:00
*** _ix_ has joined #openstack-swift13:02
*** gkadam has quit IRC13:02
*** d0ugal has quit IRC13:02
*** gkadam has joined #openstack-swift13:02
*** d0ugal has joined #openstack-swift13:03
*** _ix has quit IRC13:04
tdasilvagood morning13:11
acolestdasilva: o/13:13
*** lucasxu has joined #openstack-swift13:16
*** _ix_ has quit IRC13:21
openstackgerritJoel Wright proposed openstack/swift master: WIP: Add TLO middleware  https://review.openstack.org/49926013:29
openstackgerritJoel Wright proposed openstack/swift master: WIP: Add TLO middleware  https://review.openstack.org/49926013:36
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient master: Updated from global requirements  https://review.openstack.org/8925013:39
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873613:40
*** bigdogstl has joined #openstack-swift13:43
*** mat128 has joined #openstack-swift13:46
*** bigdogstl has quit IRC13:47
*** lucasxu has quit IRC13:54
*** lucasxu has joined #openstack-swift14:03
*** saint_ has joined #openstack-swift14:11
*** bigdogstl has joined #openstack-swift14:12
*** bigdogstl has quit IRC14:16
*** ukaynar has joined #openstack-swift14:17
*** itlinux has joined #openstack-swift14:23
*** itlinux has quit IRC14:23
*** openstackgerrit has quit IRC14:33
*** vint_bra has joined #openstack-swift14:35
*** itlinux has joined #openstack-swift14:41
*** itlinux has quit IRC14:43
*** silor has joined #openstack-swift14:49
*** _ix has joined #openstack-swift14:59
*** links has quit IRC15:07
*** bigdogstl has joined #openstack-swift15:12
*** bigdogstl has quit IRC15:17
*** bigdogstl has joined #openstack-swift15:25
*** zaitcev has joined #openstack-swift15:25
*** ChanServ sets mode: +v zaitcev15:25
*** klrmn has joined #openstack-swift15:28
*** bigdogstl has quit IRC15:30
*** bigdogstl has joined #openstack-swift15:34
*** gyee has joined #openstack-swift15:37
*** bigdogstl has quit IRC15:39
*** oshritf_ has joined #openstack-swift15:43
*** openstackgerrit has joined #openstack-swift15:43
openstackgerritRomain LE DISEZ proposed openstack/swift master: WIP: Configure diskfile per storage policy  https://review.openstack.org/44712915:43
*** bigdogstl has joined #openstack-swift15:52
*** ukaynar has quit IRC15:53
*** ukaynar has joined #openstack-swift15:53
*** bigdogstl has quit IRC15:58
*** saint_ has quit IRC16:00
*** saint_ has joined #openstack-swift16:01
openstackgerritMerged openstack/swift master: api-ref: Fix container PUT response codes  https://review.openstack.org/50248316:11
*** ukaynar has quit IRC16:11
*** bigdogstl has joined #openstack-swift16:14
*** cbartz has quit IRC16:14
*** oshritf_ has quit IRC16:14
*** bigdogstl has quit IRC16:20
timburkegood morning16:29
timburkethanks for cleaning up p 505858 for me mattoliverau!16:30
patchbothttps://review.openstack.org/#/c/505858/ - swift (feature/deep) - Bring us closer to master (MERGED)16:30
timburkeand for doing p 50597616:32
patchbothttps://review.openstack.org/#/c/505976/ - swift (feature/deep) - Merge Shard-{Account, Container} to 1 metadata16:32
timburkei was just thinking about taking that work on :-)16:32
*** bigdogstl has joined #openstack-swift16:33
timburkeit makes me wonder if X-Container-Sysmeta-Shard-Timestamp is strictly necessary... or if we could just use the ts associated with X-Container-Sysmeta-Shard-Root16:33
*** chsc has joined #openstack-swift16:39
*** chsc has joined #openstack-swift16:39
openstackgerritAlistair Coles proposed openstack/swift feature/deep: sharding: make find_shard_ranges a broker method  https://review.openstack.org/50576316:39
*** geaaru has quit IRC16:40
acolesmattoliverau: timburke ^^ I hope that is on right track16:41
*** bigdogstl has quit IRC16:42
*** itlinux has joined #openstack-swift16:45
*** tesseract has quit IRC16:50
*** rcernin has quit IRC16:52
acolestimburke: mattoliverau: got consumed by that ^^ today, I'll try to land some more of the feature branch patches tomorrow16:55
*** mvk has quit IRC17:01
*** _ix has quit IRC17:05
*** ukaynar has joined #openstack-swift17:07
*** bigdogstl has joined #openstack-swift17:12
*** bigdogstl has quit IRC17:17
*** itlinux has quit IRC17:18
*** mat128 has quit IRC17:32
notmynamegood morning17:36
*** mvk has joined #openstack-swift17:41
*** mat128 has joined #openstack-swift17:42
*** mat128 has quit IRC17:47
*** mat128 has joined #openstack-swift17:49
*** ianychoi has quit IRC17:57
*** Sukhdev has joined #openstack-swift17:57
*** ianychoi has joined #openstack-swift17:58
*** mat128 has quit IRC18:02
*** Sukhdev has quit IRC18:03
*** bigdogstl has joined #openstack-swift18:06
*** bigdogstl has quit IRC18:14
*** mat128 has joined #openstack-swift18:16
-openstackstatus- NOTICE: Gerrit OpenIDs have been accidentally overwritten and are in the process of being restored18:18
*** vint_bra has quit IRC18:19
*** vint_bra has joined #openstack-swift18:20
*** vint_bra has quit IRC18:20
*** vint_bra has joined #openstack-swift18:20
-openstackstatus- NOTICE: The Gerrit service on review.openstack.org is being taken offline briefly to perform database repair work but should be back up shortly18:24
*** ChanServ changes topic to "The Gerrit service on review.openstack.org is being taken offline briefly to perform database repair work but should be back up shortly"18:24
*** vint_bra has quit IRC18:26
*** vint_bra has joined #openstack-swift18:26
*** ChubYann has joined #openstack-swift18:30
*** silor has quit IRC18:34
*** silor has joined #openstack-swift18:34
*** silor has quit IRC18:51
*** _ix has joined #openstack-swift19:06
*** bigdogstl has joined #openstack-swift19:11
*** bigdogstl has quit IRC19:16
*** ChanServ changes topic to "Queens PTG planning https://etherpad.openstack.org/p/swift-ptg-queens | Logs: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/ | Meetings: https://wiki.openstack.org/wiki/Meetings/Swift | Review Dashboard: http://not.mn/reviews.html"19:22
-openstackstatus- NOTICE: OpenIDs for the Gerrit service have been restored from a recent backup and the service is running again; before/after table states are being analyzed now to identify any remaining cleanup needed for changes made to accounts today19:22
*** pcaruana has quit IRC19:41
openstackgerritMerged openstack/swift feature/deep: Merge Shard-{Account, Container} to 1 metadata  https://review.openstack.org/50597619:45
*** mat128 has quit IRC19:54
*** mvk has quit IRC20:05
*** mvk has joined #openstack-swift20:17
*** skudlik has quit IRC21:03
*** lucasxu has quit IRC21:04
*** catintheroof has quit IRC21:07
*** bigdogstl has joined #openstack-swift21:13
timburkehuh. our PipeMutex pretty consistently pollutes my test output when running test_utils in isolation :-/ http://paste.openstack.org/show/621660/21:16
*** bigdogstl has quit IRC21:18
*** Sukhdev has joined #openstack-swift21:28
*** _ix has quit IRC21:30
timburkealso weird: the new tests in https://review.openstack.org/#/c/506002/ run fine on their own, but fail like http://logs.openstack.org/02/506002/1/check/gate-swift-python27-ubuntu-xenial/c989f80/console.html#_2017-09-21_06_42_08_854517 if we run common/test_daemon.py:TestRunDaemon.test_run_daemon first21:30
patchbotpatch 506002 - swift (feature/deep) - Use temp db and a rename for set_sharding_state21:30
timburkethis isn't the first time that test has given me trouble: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/%23openstack-swift.2017-07-13.log.html21:31
timburkebut this time makes so much less sense :-(21:31
*** nottrobin has quit IRC21:46
*** kmARC has quit IRC21:46
*** dr_gogeta86 has quit IRC21:48
*** dja has quit IRC21:48
*** kmARC has joined #openstack-swift21:48
*** nottrobin has joined #openstack-swift21:49
*** tanee has quit IRC21:49
*** hugokuo has quit IRC21:49
*** MVenesio has quit IRC21:49
*** tanee has joined #openstack-swift21:50
*** hugokuo has joined #openstack-swift21:50
*** dr_gogeta86 has joined #openstack-swift21:53
*** dr_gogeta86 has quit IRC21:53
*** dr_gogeta86 has joined #openstack-swift21:53
*** dja has joined #openstack-swift21:56
*** _ix has joined #openstack-swift22:06
*** bigdogstl has joined #openstack-swift22:16
*** bigdogstl has quit IRC22:23
openstackgerritTim Burke proposed openstack/swift master: Stop reloading swift.common.utils in test_daemon  https://review.openstack.org/50641022:31
*** _ix has quit IRC22:39
*** bigdogstl has joined #openstack-swift22:53
*** ukaynar has quit IRC22:54
*** Sukhdev has quit IRC22:57
*** bigdogstl has quit IRC23:00
*** chsc has quit IRC23:05
*** bigdogstl has joined #openstack-swift23:06
*** bigdogstl has quit IRC23:11
timburkeso thinking about https://review.openstack.org/#/c/505321/3/swift/container/sharder.py@597 -- it doesn't look like we cache get_part_nodes in the other place we call roundrobin_datadirs -- how expensive is get_part_nodes, really?23:27
patchbotpatch 505321 - swift (feature/deep) - remove node-id, node_idx and part instance vars in... (MERGED)23:27
openstackgerritTim Burke proposed openstack/swift feature/deep: Address some lingering review comments  https://review.openstack.org/50636723:29
*** kei_yama has joined #openstack-swift23:35
*** bigdogstl has joined #openstack-swift23:41
*** ukaynar has joined #openstack-swift23:46
*** bigdogstl has quit IRC23:50
*** chsc has joined #openstack-swift23:50
*** chsc has joined #openstack-swift23:50
brianclineanyone ever seen a ring hashing collision for two distinct objects?23:55

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