Thursday, 2017-02-09

*** eranrom has quit IRC00:02
kota_back to online at office00:03
kota_and re-starting to add reconstructor tests and address to acoles comments00:04
openstackgerritMerged openstack/swift master: IO Priority support on the AArch64 architecture  https://review.openstack.org/42378300:16
*** stradling has joined #openstack-swift00:18
*** mmotiani_ has joined #openstack-swift00:21
*** mmotiani_ has quit IRC00:21
*** sams-gleb has joined #openstack-swift00:31
*** sams-gleb has quit IRC00:36
*** stradling has quit IRC00:38
*** mmotiani_ has joined #openstack-swift00:40
*** stradling has joined #openstack-swift00:46
*** caiobrentano has joined #openstack-swift00:48
*** caiobrentano has quit IRC00:49
notmynameI'm working on a list of "top 3 features of ocata" right now. I'll drop something in here when I have it written up00:50
notmynamefor comment00:50
*** dja has quit IRC00:53
*** caiobrentano has joined #openstack-swift00:53
*** dja has joined #openstack-swift00:54
*** stradling has quit IRC01:19
*** _JZ_ has quit IRC01:33
*** caiobrentano_ has joined #openstack-swift01:47
*** winggundamth has joined #openstack-swift01:49
*** caiobrentano has quit IRC01:50
*** tanee_away is now known as tanee02:17
*** Jeffrey4l has quit IRC02:17
*** Jeffrey4l has joined #openstack-swift02:20
*** sams-gleb has joined #openstack-swift02:32
*** sams-gleb has quit IRC02:36
*** tongli has quit IRC02:50
*** caiobrentano has joined #openstack-swift02:51
*** caiobrentano_ has quit IRC02:51
*** openstackstatus has quit IRC02:58
*** htruta has quit IRC02:59
*** htruta has joined #openstack-swift02:59
*** mmotiani_ has quit IRC03:02
*** openstackstatus has joined #openstack-swift03:02
*** ChanServ sets mode: +v openstackstatus03:02
*** psachin has joined #openstack-swift03:03
*** mmotiani_ has joined #openstack-swift03:11
*** JimCheung has quit IRC03:11
*** JimCheung has joined #openstack-swift03:12
*** JimCheung has quit IRC03:16
*** bkopilov has quit IRC03:19
*** bkopilov_ has quit IRC03:19
*** caiobrentano has quit IRC03:20
sanchitmalhotraHi... Is anyone using ceilometermiddleware with swift here?03:21
sanchitmalhotraCan we specify more than one host for RabbitMQ, like we used to do it earlier using rabbit_hosts parameter?03:22
claygnotmyname: you should put "AArch64 support" on there03:26
*** links has joined #openstack-swift03:33
*** sams-gleb has joined #openstack-swift03:34
jrichliclayg: one of the troubled probetests succeeds if we simply remove the assertion here https://github.com/openstack/swift/blob/master/test/probe/test_reconstructor_revert.py#L21103:38
jrichlibut is there a reason that assertion is there?  I dont really know why it was saying the x-backend-timestamp couldn't be present03:38
*** sams-gleb has quit IRC03:39
jrichlii looked through the changes that were involved in the merge to see if I could tell why that timestamp would now be present.  it wasn't clear to me.03:40
*** JimCheung has joined #openstack-swift03:43
*** JimCheung has quit IRC03:48
*** SkyRocknRoll has joined #openstack-swift03:58
*** mmotiani_ has quit IRC03:59
*** psachin has quit IRC04:00
*** mmotiani_ has joined #openstack-swift04:05
*** si1ver has quit IRC04:10
*** klrmn has quit IRC04:14
*** tqtran has quit IRC04:17
*** psachin has joined #openstack-swift04:24
*** sams-gleb has joined #openstack-swift04:37
*** sams-gleb has quit IRC04:42
*** bkopilov_ has joined #openstack-swift04:48
*** bkopilov has joined #openstack-swift04:49
*** dja has quit IRC04:52
*** mmotiani_ has quit IRC05:04
jrichliclayg: in trying to understand the assertion that we *may* be able to remove now, I looked at the old patch that added it : patch 21802305:07
patchbothttps://review.openstack.org/#/c/218023/ - swift - Fix purge for tombstone only REVERT job (MERGED)05:07
jrichliand I noticed in the commit message it mentioned "... they sync tombstones with other handoffs to fill in for the primaries"05:09
jrichliwhich did sound conflicting with a recent change of patch 42544105:10
patchbothttps://review.openstack.org/#/c/425441/ - swift - Do not revert fragments to handoffs (MERGED)05:10
jrichliI was just curious about how sync'ing tombstones is related to the fragment reverts05:11
*** mmotiani_ has joined #openstack-swift05:12
jrichliwell, what i mean is, it seems like in the past we depended on some reverting to 'other handoffs', but now we have removed that05:24
*** SkyRocknRoll has quit IRC05:37
*** dmorita has quit IRC05:40
*** dmorita has joined #openstack-swift05:42
*** dmorita has quit IRC05:46
*** winggundamth has quit IRC06:04
*** dmorita has joined #openstack-swift06:05
*** dmorita has quit IRC06:09
*** tqtran has joined #openstack-swift06:15
*** tqtran has quit IRC06:19
*** kmARC_ has joined #openstack-swift06:29
*** ediardo_ has joined #openstack-swift06:30
*** ediardo has quit IRC06:33
*** kmARC has quit IRC06:33
*** ntata has quit IRC06:33
*** ediardo_ is now known as ediardo06:33
*** ntata has joined #openstack-swift06:33
*** kmARC_ is now known as kmARC06:33
*** sams-gleb has joined #openstack-swift06:38
*** SkyRocknRoll has joined #openstack-swift06:39
kota_jrichli: sounds take a progress06:42
kota_jrichli: maybe as you notice, wheter the x-backend-timestmp is in or not depends on the ts is in the disk06:42
kota_https://github.com/openstack/swift/blob/master/swift/obj/server.py#L922-L92306:42
*** sams-gleb has quit IRC06:43
kota_i don't look at the probe test yet but the expected situation would be deleting the ts but not -> causes the failure06:43
kota_maybe?06:43
kota_recently we have a patch to stop to revert to handoff agressively, IIRC06:44
*** mmotiani_ has quit IRC06:50
*** foexle has joined #openstack-swift06:55
*** mmotiani_ has joined #openstack-swift06:58
*** rcernin has joined #openstack-swift07:00
*** tesseract has joined #openstack-swift07:11
*** ChubYann has quit IRC07:19
*** sams-gleb has joined #openstack-swift07:24
*** sams-gle_ has joined #openstack-swift07:25
*** sams-gleb has quit IRC07:25
*** foexle has quit IRC07:25
*** joeljwright has quit IRC07:27
*** ChubYann has joined #openstack-swift07:31
*** pcaruana has joined #openstack-swift07:36
*** MooingLemur has quit IRC07:44
*** ChubYann has quit IRC07:48
*** rledisez has joined #openstack-swift08:10
*** silor has joined #openstack-swift08:14
*** silor1 has joined #openstack-swift08:19
*** silor has quit IRC08:21
*** silor1 is now known as silor08:21
*** JimCheung has joined #openstack-swift08:34
*** mmotiani_ has quit IRC08:37
*** mmotiani_ has joined #openstack-swift08:38
*** geaaru has joined #openstack-swift08:42
*** mmotiani_ has quit IRC08:42
*** rcernin has quit IRC08:50
*** glb1 has joined #openstack-swift08:57
*** winggundamth has joined #openstack-swift08:58
*** openstackgerrit has quit IRC09:03
*** glb1 has quit IRC09:04
*** glb1 has joined #openstack-swift09:04
*** cbartz has joined #openstack-swift09:05
*** rcernin has joined #openstack-swift09:06
*** oshritf has joined #openstack-swift09:07
*** cbartz has quit IRC09:08
kota_It looks maybe I'm closing to finish to address all existing comments on ec duplication patch09:10
kota_Now running tests in my local09:10
psachinping #openstack-swift. I was trying 'swift tmpurl' I followed http://docs.openstack.org/developer/swift/api/temporary_url_middleware.html. But when I try to download object from tmpurl it throws '401 Unauthorized: Temp URL invalid'09:13
*** Jeffrey4l has quit IRC09:17
*** Jeffrey4l has joined #openstack-swift09:17
*** jordanP has joined #openstack-swift09:21
*** reedip has joined #openstack-swift09:22
reediphi guys , I have a query09:23
*** dja has joined #openstack-swift09:27
reedipIf Swift and Ceilometer are communicating, and if swift has a request, which it sends to ceilometer. But Ceilometer is not there on the network anymore therefore the Swift rquest is not forwarded to ceilometer. Would the request from Swift be hanged ?09:28
psachinreedip: It should timeout I guess09:30
reedippsachin : this is a behavior which one of our team members noticed in stable/mitaka09:31
*** openstackgerrit has joined #openstack-swift09:32
openstackgerritKota Tsuyuzaki proposed openstack/swift master: EC Fragment Duplication - Foundational Global EC Cluster Support  https://review.openstack.org/21916509:32
*** cbartz has joined #openstack-swift09:34
psachinreedip: The request hangs without an error?09:35
reedippsachin : any idea about the timeout value?09:35
*** JimCheung has joined #openstack-swift09:35
reedippsachin: no the request hangs indefinetly, without an error, on the screen. Let me check the logs once though.09:35
*** JimCheung has quit IRC09:35
*** Shashikant86 has joined #openstack-swift09:43
*** dja has quit IRC09:44
*** acoles_ is now known as acoles09:45
acoleskota_: thanks for new version of global EC patch, I will do my best to review again today.09:45
*** dja has joined #openstack-swift09:45
acoleskota_: but sorry, after today I am on vacation until middle of next week.09:46
kota_acoles: oh, okay. Thanks for great reviews and it's ok for your best. your eyes/comments always be helpful to me.09:51
kota_acoles: and please enjoy your vacation ;-)09:51
kota_acoles: are your going to somewhere to stay?09:52
acoleskota_: thanks! and like clayg said in meeting, we are committed to get this merged whether before or after release, thanks for all your work on it09:52
openstackgerritAlistair Coles proposed openstack/swift master: Fix misleading hash invalidations test comments  https://review.openstack.org/42720509:55
*** csmart has joined #openstack-swift09:56
*** dja has quit IRC09:56
*** dosaboy has quit IRC09:56
csmart\o09:57
*** dja has joined #openstack-swift09:57
csmartFinally found time to connect up via riot.im09:57
*** dosaboy has joined #openstack-swift09:58
*** SkyRocknRoll has quit IRC09:59
*** dosaboy has joined #openstack-swift10:00
*** SkyRocknRoll has joined #openstack-swift10:02
*** dja has quit IRC10:03
*** Shashikant86 has quit IRC10:05
kota_ok, I'm going to be back home earlier than other working days in this week. but I can be responsive if my bouncer kicks me10:11
kota_please feel free to comment/ping me.10:11
*** Shashikant86 has joined #openstack-swift10:13
*** tqtran has joined #openstack-swift10:17
*** tqtran has quit IRC10:22
*** sams-gleb has joined #openstack-swift10:26
*** links has quit IRC10:27
*** sams-gle_ has quit IRC10:28
*** pcaruana has quit IRC10:32
*** pcaruana has joined #openstack-swift10:33
*** links has joined #openstack-swift10:40
cnfcsmart: riot is yet another slack / hipchat / ... ?10:50
cnfwow, what a bad website10:51
*** sams-gleb has quit IRC11:02
*** sams-gleb has joined #openstack-swift11:02
*** SkyRocknRoll has quit IRC11:05
*** sams-gleb has quit IRC11:07
csmartcnf: riot is an implementation of matrix.org - an open, distributed, federated (slack-like) chat protocol11:35
*** kei_yama has quit IRC11:35
openstackgerritJoel Wright proposed openstack/swift master: Add Preamble and Postamble to SLO and SegmentedIterable  https://review.openstack.org/36537111:36
*** caiobrentano has joined #openstack-swift11:39
openstackgerritAlistair Coles proposed openstack/swift master: Fix race when consolidating new partition  https://review.openstack.org/42633611:47
*** JimCheung has joined #openstack-swift11:51
*** sams-gleb has joined #openstack-swift11:55
*** links has quit IRC11:55
*** JimCheung has quit IRC11:55
*** cbartz has quit IRC11:56
*** cbartz has joined #openstack-swift11:58
*** oshritf_ has joined #openstack-swift11:59
kota_Gate failed!?12:00
*** oshritf_ has quit IRC12:01
*** oshritf_ has joined #openstack-swift12:02
*** PavelK has joined #openstack-swift12:02
kota_Er, perhaps related to quorum changes12:03
*** oshritf has quit IRC12:03
kota_No, it looks it gets on GET.12:04
*** links has joined #openstack-swift12:07
*** SkyRocknRoll has joined #openstack-swift12:11
*** JimCheung has joined #openstack-swift12:11
*** psachin has quit IRC12:12
*** JimCheung has quit IRC12:16
*** psachin has joined #openstack-swift12:18
*** bkopilov has quit IRC12:24
*** bkopilov_ has quit IRC12:24
cnfcsmart: so yet another chat thing :P12:43
*** links has quit IRC12:50
kota_back to online to check the gate failure12:54
*** klamath has joined #openstack-swift13:01
*** klamath has quit IRC13:01
*** klamath has joined #openstack-swift13:02
*** mmotiani_ has joined #openstack-swift13:02
*** oshritf_ has quit IRC13:06
*** oshritf_ has joined #openstack-swift13:07
*** stradling has joined #openstack-swift13:09
*** psachin has quit IRC13:13
*** psachin has joined #openstack-swift13:33
*** Shashikant86 has quit IRC13:37
kota_ok, make sense13:38
kota_the assertion should be wrong13:38
kota_it could be less or equal to 14 in my calculation13:38
kota_i think it's not related to my ec duplication, it should happen on master but it seems freaky13:40
openstackgerritKota Tsuyuzaki proposed openstack/swift master: EC Fragment Duplication - Foundational Global EC Cluster Support  https://review.openstack.org/21916513:41
kota_my idea added to the gerrit. I think no more failure happens in the gerrit. It should be robust.13:52
*** oshritf_ has quit IRC13:53
*** bkopilov_ has joined #openstack-swift14:01
*** bkopilov has joined #openstack-swift14:01
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873614:01
*** mmotiani_ has quit IRC14:06
*** mmotiani_ has joined #openstack-swift14:17
*** dmorita has joined #openstack-swift14:18
*** tqtran has joined #openstack-swift14:19
*** mmotiani_ has quit IRC14:21
*** mmotiani_ has joined #openstack-swift14:21
jrichlireedip: are saying that ceilometer has made a request to swift, and it disconnects before the response is returned from swift?14:22
jrichlireedip: if so, you may want to comment on https://bugs.launchpad.net/swift/+bug/166215914:22
openstackLaunchpad bug 1662159 in OpenStack Object Storage (swift) "TCP leak between proxy and object-server on client disconnection" [Undecided,New]14:22
*** tqtran has quit IRC14:23
*** dmorita has quit IRC14:24
*** mmotiani_ has quit IRC14:24
*** dmorita has joined #openstack-swift14:24
*** oshritf_ has joined #openstack-swift14:29
*** Shashikant86 has joined #openstack-swift14:30
jrichlireedip: actually, I just read you comment again.  I am confused because you were expecting a response, but it sounds as if ceilometer, the client, disconnected.14:31
*** catintheroof has joined #openstack-swift14:31
*** ChatSharp has joined #openstack-swift14:40
*** ChatSharp has left #openstack-swift14:40
jrichlikota_: thank you for the input!14:43
*** JimCheung has joined #openstack-swift14:48
*** JimCheung has quit IRC14:48
*** dmorita_ has joined #openstack-swift15:00
*** dmorita_ has quit IRC15:00
*** dmorita has quit IRC15:04
*** ChatSharp has joined #openstack-swift15:12
*** ChatSharp has left #openstack-swift15:12
*** Shashikant86 has quit IRC15:12
*** sams-gleb has quit IRC15:13
*** sams-gleb has joined #openstack-swift15:14
*** sams-gleb has quit IRC15:18
*** _JZ_ has joined #openstack-swift15:24
*** sams-gleb has joined #openstack-swift15:35
*** Shashikant86 has joined #openstack-swift15:36
*** Shashikant86 has quit IRC15:38
*** abqkawi1000 has joined #openstack-swift15:59
abqkawi1000Quick question about *.conf, *.gz, *.builder files.  Given a controller, a proxy/account/continer box and an object box:  What should the contents of each /etc/swift be?  Do all files need to be on all boxes?16:00
timburkeclayg: you can't see me right now, but i'm squinting very hard at you16:04
acolescschwede_: I left some comments on patch 337297, but I am now on vacation until after the release date so can't follow up - sorry!16:08
patchbothttps://review.openstack.org/#/c/337297/ - swift - Add support to increase object ring partition power16:08
cschwede_acoles: alright, just saw the mail notification - thanks a lot for reviewing it, i will follow up soon and push a new patchset!16:08
cschwede_acoles: enjoy your vacation!16:09
timburkeabqkawi1000: both boxes will need all *.ring.gz files. none of them *need* the builder files; you could actually do all of your ring-building on some separate admin box and push them out from there if you like. the conf files come down to whatever you need to have running -- so mostly the object-*.conf files on the object box, and {proxy,account,container}-*.conf on the other one. swift.conf has to be on all of them; memecache goes wi16:09
timburketh the proxy; others... i might need to defer to someone else on16:09
cschwede_acoles: oh, will you join the Atlanta PTG?16:09
abqkawi1000timburke:  gotcha....makes sense.  Also do I need to start any swift services on the controller?16:11
timburkeabqkawi1000: at minimum, you'll want the proxy, account, container, and object servers running on the appropriate boxes. this allows the client-facing API to function at all. to ensure the proper health of your cluster, all the other background daemons should be running, too. so, account-auditor, account-reaper, account-replicator on any boxes running account-server; container-auditor, -reconciler, -replicator, -updater on the contain16:17
timburkeer-server box, etc.16:17
abqkawi1000timburke:  Ok great, thanks for you help.16:18
timburkepsachin: did you ever get help on your tempurl issue? i'm wondering if you may have been trying the new prefix-based tempurls, which were a rather recent addition -- not many clusters would support them yet, and i would expect the ones that don't to fail with that message16:19
acolescschwede_: np, the nits really are nits, don't need to fix them, but I am curious about the strategy for knowing when relinking has been 100% successful16:19
acolescschwede_: yes i'll be at PTG :)16:19
cschwede_acoles: yay, best news of the day!16:20
acolescschwede_: just out til middle of next week16:20
cschwede_acoles: i'll need a new patchset anyways, because of the probe test issue. mattoliverau actually fixed it, it seems (thx Matt!)16:20
acolesnice16:21
*** caiobrentano_ has joined #openstack-swift16:23
*** caiobrentano_ has quit IRC16:23
*** caiobrentano has quit IRC16:26
*** caiobrentano has joined #openstack-swift16:27
*** JimCheung has joined #openstack-swift16:31
*** klrmn has joined #openstack-swift16:31
*** rcernin has quit IRC16:32
*** JimCheung has quit IRC16:35
*** chsc has joined #openstack-swift16:37
*** chsc has joined #openstack-swift16:37
*** mmotiani_ has joined #openstack-swift16:52
*** PavelK has quit IRC16:53
notmynamegood morning16:56
*** stradling has quit IRC16:59
*** tqtran has joined #openstack-swift17:01
*** dmorita has joined #openstack-swift17:01
*** glb has joined #openstack-swift17:04
*** dmorita has quit IRC17:05
*** catintheroof has quit IRC17:06
*** catintheroof has joined #openstack-swift17:07
*** catintheroof has quit IRC17:11
*** tesseract has quit IRC17:18
*** jordanP has quit IRC17:30
*** pcaruana has quit IRC17:30
*** geaaru has quit IRC17:31
*** joeljwright has joined #openstack-swift17:32
*** ChanServ sets mode: +v joeljwright17:32
*** caiobrentano has joined #openstack-swift17:35
*** silor has quit IRC17:36
claygkota_: patchset 55 looks good at first glance!  I may get to spend more time with it this afternoon, or tomorrow17:43
*** Administrator__ has joined #openstack-swift17:43
claygjrichli: sounds good to me - is there a fix for the probetest up?17:44
* clayg hopes timburke is squinting because of my crack about AArch64 <giggles>17:46
*** zhugaoxiao has quit IRC17:46
jrichliclayg: after learning some about this, I am not so sure we can simply remove that assertion.17:48
jrichliclayg: it seems like that is the way we determine if there was a tombstone or not: timestamp is added if there was a tombstone17:48
claygjrichli: boooooo17:48
jrichliclayg: and in the test, it says that tombstone should have been reverted back to primary.  this shows that is not happening.17:49
claygsure that's true it's like 404 "with feeling"17:49
*** mmotiani_ has quit IRC17:49
jrichliclayg: but you think it's ok that this tombstone remains on the  handoff even though the primary is back?17:49
claygzohno!  we can't just be leaving tombstones around on the floor!?  is everything broke!N???!!!!1117:49
claygno, i mean if the primary is up i don't see why the tombstone wouldn't make it's way out to the primary17:50
jrichliclayg: I would need somebody to verify my understanding ... I am like just now parsing the code17:50
claygjrichli: i think if there is *another* frag in the partition - then the sync job would just point to the primary for that index - if it's up - it should get the tombstone17:50
claygjrichli: if there are *no* frags in the partition the handoff doesn't know *where* to send the tombstones in the part - so I think it sends it to all primaries17:51
clayghow did we get a tombstone on a handoff anyway?17:51
claygjrichli: so probetests don't reset your environment when they fail17:52
claygjrichli: after it stops - go poke around on disk17:52
claygstart up your object servers17:52
claygrun the reconstrucotor like `swift-init object-reconstructor once --no-daemon --verbose --config X' where X is a node#/config#17:52
*** mmotiani_ has joined #openstack-swift17:53
claygor `swift-init object-reconstrucotr once -nv -c X`17:53
claygthen see if you think the damn thing is doing what it is supposed to17:53
claygi like `find /srv/node*/sdb*/object* -name \*.data` to see wtf is going on17:53
jrichliclayg: how did we get a tombstone on handoff: my understanding is that the primary is taken down, then delete is requested.17:53
claygor... \*.ts17:53
claygdelete doens't really do the connects the same way PUT does - the tombstone should just not get written to any downed primaries17:54
jrichliclayg: i have looked at disk afterwards.  when the case succeeds, there is one less tombstone on disk than when the test fails.17:54
claygas long as enought (k + 1) response so that a read shouldn't work - i think we 2XX17:54
jrichliclayg: but then how is the delete recorded?17:55
claygthis is EC right?  am I crazy?17:55
jrichlioh, right17:55
*** dmorita has joined #openstack-swift17:55
claygno - don't let me confuse you - i might be crazy!17:55
*** dmorita has quit IRC17:56
jrichliI think I gotta take a break and eat lunch!  my brain needs sugar :-)  i'll keep looking.17:56
*** oshritf_ has quit IRC17:56
*** caiobrentano has quit IRC18:02
*** rledisez has quit IRC18:04
*** winggundamth has quit IRC18:04
*** jordanP has joined #openstack-swift18:11
*** jordanP has quit IRC18:12
*** zhugaoxiao has joined #openstack-swift18:15
*** Administrator__ has quit IRC18:18
notmynameI'm struggling with the "marketing phrasing" of new features in swift. I don't feel like "things were pretty terrible and sometimes surprising it worked at all, but now things are probably a little bit less terrible" is a particularly good thing to say to press18:18
*** SkyRocknRoll has quit IRC18:23
notmynamewhen I write about closing bugs that corrupted data, I feel like it's similar to saying, "last week was great! I had a 37% lower chance of kicking puppies" (ok, that's great, but how often were you kicking puppies before??!)18:24
*** joeljwright has quit IRC18:26
*** catintheroof has joined #openstack-swift18:26
*** dmorita has joined #openstack-swift18:26
*** dmorita has quit IRC18:28
*** dmorita has joined #openstack-swift18:28
*** psachin has quit IRC18:30
*** ChubYann has joined #openstack-swift18:40
*** cbartz has quit IRC18:54
*** cbartz has joined #openstack-swift18:54
*** cbartz has quit IRC18:54
*** caiobrentano has joined #openstack-swift19:06
* acoles away til 15th19:19
*** acoles is now known as acoles_19:21
*** caiobrentano has quit IRC19:26
*** caiobrentano has joined #openstack-swift19:27
notmynamethis is an amazing email, and something the entire openstack community needs to consider http://lists.openstack.org/pipermail/openstack-dev/2017-February/111894.html19:30
*** wer has quit IRC19:34
*** wer has joined #openstack-swift19:35
*** JimCheung has joined #openstack-swift19:40
*** tonanhngo has joined #openstack-swift19:43
*** dja has joined #openstack-swift19:48
openstackgerritMerged openstack/swift master: Fix misleading hash invalidations test comments  https://review.openstack.org/42720519:53
*** JimCheung has quit IRC19:54
*** JimCheung has joined #openstack-swift19:55
notmynameok, I submitted the "top features and upcoming goals" survey for swift19:56
notmynamewhile I consider many of the internal improvements to be the most significant, much of what is asked for has to do with end-user impact19:56
timburkeend user impact: your data are safe19:57
*** Jeffrey4l has quit IRC19:57
notmynameso what I put down is (1) "significant improvements to durability and correctness of data" (includes stuff like the repl/recon improvements, elimination if .durable, etc) (2) tempurl common prefix and (3) last-modified on container listings19:58
*** Jeffrey4l has joined #openstack-swift19:58
notmynameI wanted to put down the part-power increase, but I'm not 100% sure it will land (I never am until it actually *does* land), so I didn't mention it19:58
notmynameas part of this, and as normal, I was asked to identify the "themes" that are in ocata and what we'll be focusing on in pike and queens.19:59
claygheyoh!19:59
notmynameand as normal, i put down that we focus on reliability, scalability, and manageability. and I de-emphasized interoperability, security (at least until we do more with crypto), and user experience20:00
notmyname(those are the 6 themes I can choose from. I can't say my own)20:00
timburkenotmyname: slo concurrency? your PUTs are faster!20:00
claygwhat?20:01
notmynametimburke: indeed. yet another that I like20:01
timburkeoh, and hey! you can do multiple ranges now!20:01
timburkeslos are great20:01
claygqueens :P20:01
notmynametimburke: but "things you expected to work well, now work well-er" is harder to explain to a non-tech audience than "here's a new shiny" ;-)20:01
notmynametimburke: I made a call :-)20:01
*** JimCheung has quit IRC20:01
tdasilvanotmyname: that is a really nice email, especially the part about help. I think that can apply to all openstack projects20:10
notmynametdasilva: I wonder how many wrong expectations we've set up in openstack. openstack started as this commercial joint venture thing, so projects are sortof measured (and live and die) by how much corporate patrons contribute to them20:12
notmynametdasilva: which means it would be very very hard for a smaller project that is awesomely useful but doesn't have paid employees working on it to be considered successful (much less actually successful by the metrics the TC puts out)20:13
notmynamelike, that doesn't seem "normal" in the broader open-source world20:13
*** tonanhngo has quit IRC20:17
tdasilvanotmyname: OTOH, I can also understand how it is also a challenge. Since the big-tent, there are now 100s of projects in openstack and it is natural that not all of them "survive". So how does one differentiate a small but useful project, from one that is small and not very useful project20:17
*** tonanhngo has joined #openstack-swift20:20
notmynamethat only matters if "openstack" is this one big thing that's gotta be deployed all together. in that case, keeping the "bad" projects in has significant negative cost20:20
notmynamehowever if openstack provides components for cloud infrastructure that don't need to be co-installed or can be consumed a-la-cart, then the cost is much less20:21
-openstackstatus- NOTICE: Restarting gerrit due to performance problems20:21
*** tonanhngo_ has joined #openstack-swift20:21
notmynameso if there's only a couple of people contributing to designate, but it's a stable project providing good utility, then that's great! keep it in! (and of course hope that as more people use it, more hands come on to help carry the load)20:22
notmynamebut if there's only a couple of people contributing to designate and the project navigator (ie foundation marketing) therefore says "not mature" or it becomes impossible to meet TC "community goals", then that's bad IMO20:23
*** tonanhngo has quit IRC20:24
*** tonanhngo_ has quit IRC20:26
notmyname /lunchtime20:30
*** tonanhngo has joined #openstack-swift20:35
*** MooingLemur has joined #openstack-swift20:37
csmart/breakfast time20:38
*** JimCheung has joined #openstack-swift20:40
*** JimCheung has quit IRC20:45
*** silor has joined #openstack-swift20:47
tdasilvajrichli, clayg: i'm having to go back almost 30 days to see probe tests working :(20:48
notmynametdasilva: in the qa cluster?20:48
tdasilvano, in my dev. environment20:49
notmynameoh ok20:49
notmynamestill bad, just bad in a different way20:49
jrichlitdasilva: I have been focused on only one of the tests: test_delete_propagate.20:50
jrichlitest_delete_propagate was introduced from fc09dda Merge "Better optimistic lock in get_hashes"20:50
jrichliis that what you are seeing for that one as well?20:50
tdasilvajrichli: i saw this fail: test_main (test.probe.test_replication_servers_working.TestReplicatorFunctions in b5530f4620a0a9ba6b9011c68a93b6e1ef92823320:52
tdasilvajrichli: so I took a big jump back to 0590d20fccd0ca2202c6246eb6b213115427f237 and tests pass, so now i'm going to work my way back20:53
jrichlitdasilva: oh, ok.  nice work!  keep me posted.  i am still focused on understanding/fixing test_delete_propagate :/20:56
claygjrichli: did you fix everything!?20:56
jrichliclayg: lol.  I am glad you seem to have hope for me yet :-)20:57
jrichliI had a long lunch at the pancake house.  is that a good excuse?20:57
*** dja has quit IRC21:01
tdasilvajrichli: the "funny" part is that when i checkout the "Better optimistic lock in get_hashes" commit, i saw 4 tests fail :/21:03
*** silor1 has joined #openstack-swift21:04
*** silor has quit IRC21:04
*** silor1 is now known as silor21:04
jrichlitdasilva: the initial commit aa71d7e is different then the merged one at fc09dda.  which one are you speaking of?21:06
jrichliit is the diff between those two that I am currently focused on.21:06
jrichliif i understand right, the patch as it was tested before it merged passed - at least this one test.  but then when it was merged with what had transpired on master, that is when things didnt work together.21:07
tdasilvajrichli: yep, I tested fc09dda21:08
jrichlii guess that is why you cant just test a patch with git -d review <>.  you have to rebase, then test.21:08
tdasilvayep21:09
*** caiobrentano has quit IRC21:21
*** caiobrentano has joined #openstack-swift21:22
*** JimCheung has joined #openstack-swift21:26
*** caiobrentano has quit IRC21:27
*** JimCheung has quit IRC21:32
*** JimCheung has joined #openstack-swift21:33
*** Jeffrey4l_ has joined #openstack-swift21:35
*** Jeffrey4l has quit IRC21:35
*** JimCheung has quit IRC21:38
mattoliverauMorning21:47
claygmattoliverau: *incorrect* ;)22:00
claygmattoliverau: Afternoon22:00
notmynamefirst line of an email I just got: "How would you like a free consult for an oil change for your IT systems?"22:08
notmynameI'll admit that I haven't changed my oil in *any* of my servers yet22:08
*** silor has quit IRC22:08
mattoliverauLol22:09
*** mmotiani_ has quit IRC22:13
*** sams-gleb has quit IRC22:21
*** sams-gleb has joined #openstack-swift22:22
*** sams-gleb has quit IRC22:26
*** abqkawi1000 has quit IRC22:34
*** dja has joined #openstack-swift22:39
jrichliclayg: I think that for test_delete_propagate, its revealing that an extra tombstone file can be left on a handoff because delete_reverted_objs is not getting called when it should for a ts.22:41
clayg*weird*22:46
claygso like you can watch that test put your saio in a weird state - then no matter how much you run your daemons it doens't get right?22:46
clayglike a for-realzy bad!?22:46
*** mmotiani_ has joined #openstack-swift22:48
jrichliah: so the following condition will NEVER be true given the code: https://github.com/openstack/swift/blob/master/swift/obj/reconstructor.py#L65622:59
jrichlisyncd_with is only incremented in a loop over sync_to nodes now.   the looping used to be over something different23:00
jrichliused to be "for node in dest_nodes"23:01
timburkejrichli: yeah, it'd chain that with the handoff iter23:01
jrichliclayg: i will run reconstructor23:01
timburkeclayg: i guess https://review.openstack.org/#/c/425441/ should have taken out that test?23:02
patchbotpatch 425441 - swift - Do not revert fragments to handoffs (MERGED)23:02
timburkeor at least fixed it up :-( sorry i didn't catch that earlier23:02
jrichlii got to learn a lot from investigation :-)23:03
claygtimburke: jrichli: yeah I assumed something like that but I hadn't looked at the test yet (waiting to see what jrichli comes up with!)23:05
claygoh... so it *is* a bug?23:05
*** gabor_antal has quit IRC23:05
claygwhy wouldn't synced_with be == to len(job['sync_to'])23:06
claygtimburke: taken out the "test" or taken out the "conditional"23:06
*** gabor_antal has joined #openstack-swift23:07
jrichliclayg: oh, right.  it could hit when = to.  i am not saying it right.  we miss 2 loops here.  i gotta think more to explain that.23:08
*** cebreidian has joined #openstack-swift23:10
timburkein the test, we shut down two primaries, repair the first, run reconstructor. so there's still one down primary that we can't sync with -- previously we would send it to another handoff, but now it sits tight23:13
*** chsc has quit IRC23:13
claygtimburke: yeah - by design - stupid probetest needs updating - seems stright forward23:13
*** mmotiani_ has quit IRC23:14
claygassert it *is* sitting tight - then fix the downed primary and assert the revert23:14
claygsounds like a baller test to me23:14
*** gabor_antal has quit IRC23:15
*** gabor_antal has joined #openstack-swift23:17
jrichliyes, so the primaries being down is why we dont get == to23:19
jrichlii mean the one primary23:20
jrichliclayg: ok, i will work on that patch if its ok i might take longer than others23:21
timburkedo it! it'll be great :-)23:24
clayg*so great*23:25
*** nikivi has quit IRC23:32
*** nikivi has joined #openstack-swift23:34
jrichliwell, i guess that is just switching the assert, right?  we arleady assert the revert in that test after primary is restored23:38
*** mmotiani_ has joined #openstack-swift23:39
*** mmotiani_ has quit IRC23:39
*** mmotiani_ has joined #openstack-swift23:40
*** mmotiani_ has quit IRC23:42
*** mmotiani_ has joined #openstack-swift23:42
timburkejrichli: yeah -- might be worth running reconstructor on that "second" handoff again and seeing that the tombstone goes away? i could go either way; we already watch that happen on the "first" handoff23:42
jrichlitimburke, clayg: but what about the check that has >= when only == could happen? should that not be changed somehow?23:43
timburkei'm partial toward leaving it as >= -- seems less failure prone (a la https://review.openstack.org/#/c/399237/) if we go back and change our minds23:44
patchbotpatch 399237 - swift - Avoid infinite loop while placing parts (MERGED)23:44
jrichliok, i think i still have to stew over that part.  but i will probably upload a patch before tomorrow.  gonna break now though.23:50

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