Tuesday, 2017-04-11

*** Administrator_ has quit IRC00:04
*** Administrator_ has joined #openstack-swift00:05
*** mvk has quit IRC00:12
*** dja_ is now known as dja00:16
*** catintheroof has quit IRC00:19
*** chsc has quit IRC00:21
*** mvk has joined #openstack-swift00:25
*** cdelatte has joined #openstack-swift00:30
*** cdelatte has quit IRC00:30
*** mvk has quit IRC00:34
*** mvk has joined #openstack-swift00:34
mattoliverauIf we auto include dlo, we should def auto include slo especially if it's what we keep recommending over dlo :)00:48
timburkeeither way, client still ought to be robust to it not being in the pipeline, and definitely shouldn't go confusing things by sending what's essentially a sysmeta header00:50
*** mvk has quit IRC00:51
*** zhurong has joined #openstack-swift00:55
mattoliverautimburke: yeah, totally.00:56
mattoliverauif it aint there, don't use it00:57
*** mvk has joined #openstack-swift01:03
*** gyee has quit IRC01:04
*** m_kazuhiro has joined #openstack-swift01:08
m_kazuhirogood morning01:08
*** mvk has quit IRC01:10
mattoliveraum_kazuhiro: morning01:10
*** mvk has joined #openstack-swift01:10
m_kazuhiromattoliverau: morning!01:10
*** klrmn has quit IRC01:12
kota_good morning01:15
kota_welcome back timburke01:15
timburkethanks kota_! and good morning01:16
timburkegood morning m_kazuhiro!01:16
m_kazuhirotimburke: good morning!01:16
kota_timburke: and thanks for looking at patch 454447 but it was squashed up into patch 45417401:16
patchbothttps://review.openstack.org/#/c/454447/ - swift - Fix StopIteration if no more nodes in DB Replication01:16
patchbothttps://review.openstack.org/#/c/454174/ - swift - Container drive error results double space usage o...01:16
kota_timburke: sorry, i should have abandoned the patch before you had wasted time for it.01:17
mattoliveraukota_: morning01:17
kota_mattoliverau: morning01:17
timburkekota_: not much time :-) and i think i like how that patch dealt with it... i just need to look at tests01:18
timburkeit just always feels a little weird to deal in StopIterations explicitly01:18
kota_timburke: yup, that have a little history we had discussion how we could imporove/cleanup the code01:19
kota_timburke: but for now, IMO, we want to fix a bug (or some bugs) with small changes and *want* to try to cleanup/refactor all db_replicator iteration01:20
kota_after bug fixes01:20
kota_the patch 454174 actually fixes two bugs, a) stop to bleed the db can be located every drives b) stop to raise bare StopIteration when we ran out of devices (i.e. no more handoffs)01:22
patchbothttps://review.openstack.org/#/c/454174/ - swift - Container drive error results double space usage o...01:22
kota_and it seems clayg is trying to fix some test refactoring at patch 45489801:22
patchbothttps://review.openstack.org/#/c/454898/ - swift - Fix default FakeRing max_more_nodes01:22
*** JimCheung has quit IRC01:31
*** Sukhdev has quit IRC01:33
kota_thanks mattoliverau to looki at that!01:35
mattoliveraukota_: nps, patch looks small and clean. And pretty much fixes the bleeding in the way clay and I both did in the bug :)01:36
*** gmann has joined #openstack-swift01:46
gmannnotmyname: can you check query/answer for bulk delete request - https://review.openstack.org/#/c/409634/801:48
patchbotpatch 409634 - tempest - Separate object-storage bulk operation service cli...01:48
gmannnotmyname: query url would not contain any path to list of objects to be deleted right? its in request body what i understood from code- http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/user-guide/source/cli-swift-bulk-delete.rst#n1601:49
openstackgerritTim Burke proposed openstack/python-swiftclient master: Tolerate RFC-compliant ETags  https://review.openstack.org/45548801:52
openstackgerritTim Burke proposed openstack/python-swiftclient master: Skip checksum validation on partial downloads  https://review.openstack.org/45548901:52
kota_it looks Boston Summit Forum has been scheduled01:55
kota_and all proposed sessions for swift look there01:56
* kota_ is looking at http://lists.openstack.org/pipermail/openstack-dev/2017-April/115174.html01:57
mattoliveraukota_: yeah, one of them twice!01:58
mattoliveraubut yeah, looks like it's all in there01:58
mattoliverauNow I just have to hope I can make it to boston.. otherwise, timburke will need to handle sharding for me01:58
* timburke hides01:59
kota_mattoliverau: I hope you will be there ;-)01:59
mattoliverautimburke: good choice ;)02:00
mattoliveraukota_:  +102:00
*** chsc has joined #openstack-swift02:02
*** chsc has joined #openstack-swift02:02
*** SkyRocknRoll has joined #openstack-swift02:03
*** chsc has quit IRC02:07
timburkemattoliverau: doesn't the logger.error already rather imply ERROR?02:08
timburkei'd be partial toward removing it from the other locations, but that'd probably muddy the patch a bit02:09
mattoliverauyes it does, but the line below also has it.. so consistency02:09
mattoliverauor remove ERROR on the other lines is fine too :P02:09
mattoliverauexactly02:09
mattoliveraubut really rewording would be nice, and make consistent.. easiest is to add the ERORR, and then wouldn't potentially muddy any translations, if that is in fact how gettext works ?02:10
timburkei was actually thinking that pushing an ERROR version and then another patch to strip them all out would cause some needless churn for the translators, but then, i've never really had to deal with i18n much...02:13
*** catintheroof has joined #openstack-swift02:16
mattoliverauwell, we could at least raise the patch and then ask in 118n, we could always abandon if it causes too much work. or maybe they wont care, update the po files, but translations _may_ stay the same, depends on how the translation tracks log changes.02:18
timburkei think if we land the string change fairly quickly after the critical fix, it comes out a wash for them? *shrug*02:19
timburke...and then there's the question of whether we're going to get on the http://lists.openstack.org/pipermail/openstack-dev/2017-March/114191.html bandwagon...02:22
timburkebetween that and clayg's well-reasoned response on https://review.openstack.org/#/c/318989/ i wonder whether *anything* should be marked for translation in swift, but we should start translating *swiftclient* instead...02:26
patchbotpatch 318989 - swift - Mark more end-user-facing strings for translation02:26
timburkeunless we want to get some Accept-Language support going... ugh.02:26
timburkewell, anyway, i oughta get going before my wife starts to wonder what happened to me02:29
timburkegood night everybody!02:29
*** catintheroof has quit IRC02:34
*** catintheroof has joined #openstack-swift02:35
*** catintheroof has quit IRC02:40
*** klrmn has joined #openstack-swift02:54
*** SkyRocknRoll has quit IRC03:31
*** edisonxiang has joined #openstack-swift03:33
*** gkadam has joined #openstack-swift03:39
*** gkadam is now known as gkadam-afk03:44
*** chlong has quit IRC03:47
*** SkyRocknRoll has joined #openstack-swift03:49
*** m_kazuhiro_ has joined #openstack-swift04:00
*** dfflanders_ has joined #openstack-swift04:01
*** m_kazuhiro has quit IRC04:02
*** chsc has joined #openstack-swift04:03
*** chsc has joined #openstack-swift04:03
*** Dinesh_Bhor has quit IRC04:07
*** gkadam-afk is now known as gkadam04:11
*** SkyRocknRoll has quit IRC04:11
*** Sukhdev has joined #openstack-swift04:14
notmynamehello, world04:15
mahaticnotmyname: o/04:16
mahaticgood morning04:16
notmynameI finally made it to Ann Arbor (bunch of delays getting out of SFO), but now it'd after midnight, so I was just checking what had happened today04:16
* mahatic learns where Ann Arbor is04:18
*** psachin has joined #openstack-swift04:31
*** Dinesh_Bhor has joined #openstack-swift05:11
*** Sukhdev has quit IRC05:12
*** klrmn has quit IRC05:12
*** rcernin has joined #openstack-swift05:15
kota_mahatic: morning, notmyname: good... midnight?05:21
* kota_ learns where Ann Arbor is too05:21
mahatickota_: o/05:24
*** cshastri has joined #openstack-swift05:33
*** psachin has quit IRC05:34
*** ChubYann has quit IRC05:38
*** zaitcev has quit IRC05:46
*** spotz is now known as spotz_zzz05:46
*** spotz_zzz is now known as spotz05:48
*** jaosorior_away is now known as jaosorior05:55
*** chsc has quit IRC05:56
*** adriant has quit IRC06:02
*** sudorandom has quit IRC06:29
*** sudorandom has joined #openstack-swift06:30
*** psachin has joined #openstack-swift06:31
*** chsc has joined #openstack-swift06:38
*** chsc has joined #openstack-swift06:38
*** chsc has quit IRC06:46
*** tesseract has joined #openstack-swift06:47
*** mgagne has quit IRC06:52
*** JimCheung has joined #openstack-swift07:00
*** m_kazuhiro_ has quit IRC07:04
*** winggundamth has joined #openstack-swift07:04
*** JimCheung has quit IRC07:04
*** pcaruana has joined #openstack-swift07:06
mathiasbgood morning!07:10
*** geaaru has joined #openstack-swift07:26
mattoliveraumathiasb: morning07:31
acolesgood morning07:47
mattoliverauacoles: morning07:49
openstackgerritPavel Kvasnička proposed openstack/swift master: Container drive error results double space usage on rest drives  https://review.openstack.org/45417407:50
acolesmattoliverau: hi how's things? you gotta get to Boston now :)07:53
mattoliveraulol, yeah, sharding is scheduled.. so lets cross fingers :)07:53
*** ianychoi has quit IRC07:54
*** m_kazuhiro has joined #openstack-swift07:54
mattoliverauI'm all good. I easter this week and the in-laws are coming up as it's school holidays.. so I have a feeling I'll be a little distracted this week. But good07:54
kota_acoles: morning07:54
mattoliverauacoles: how are things with you?07:54
*** ianychoi has joined #openstack-swift07:54
acoleskota_: hi07:55
acolesmattoliverau: good thanks, got a long weekend coming up for Easter here too. And the sun is still shining!07:56
mattoliverau\o/ nice. Cyclone up north has cleared up, so we're back to nice beach weather here.. so easter is shaping up nicely here too :)07:57
mattoliverauk, I'm going to go do the normal baby dinner, bath, bed rutine. bbl08:01
acolesfun time!08:01
*** dfflanders_ has quit IRC08:03
*** cbartz has joined #openstack-swift08:07
mahaticacoles: good morning08:07
acolesmahatic: o/08:08
mahaticI haven't gotten around much on this - https://review.openstack.org/#/c/449310/, but do have some comments in draft. Looks like there has been much progress!08:08
patchbotpatch 449310 - swift - Add id to RingBuilder to differentiate rings in co...08:08
acolesmahatic: thanks, all comments welcome. that will hopefully squash into the parent but I thought it helpful to leave it separate while things are changing08:09
mahaticacoles: yeah, latter seems better for now08:10
*** ianychoi has quit IRC08:20
*** bikmak has joined #openstack-swift08:20
kota_acoles, mahatic: I'm also just about looking at the patch progress08:20
*** ianychoi has joined #openstack-swift08:21
kota_sorry, I didn't have a time to look at in recent 2 days, I'll check the recent difference tomorrow morning08:21
kota_i think, we can use uuid published at the save and it seems ok to verify for preventing same uuid in the component rings, right?08:22
* kota_ had quick veiw08:22
acoleskota_: NP. I tried to address the comments around using an ID. And I found a bug in compose_builder08:22
kota_acoles: for patch 441921?08:22
patchbothttps://review.openstack.org/#/c/441921/ - swift - Add Composite Ring Functionality08:22
acoleskota_: yes, assign uuid when saving is the safest way to guarantee the id is persisted08:23
* kota_ assuming the *yes* is to re: when uuid will be made.08:23
acoleskota_: for now I left the UUID patch as a follow on, but just for clarity so we can see what is changing. It should be squashed when we are happy.08:24
acoleskota_: you assume correctly :)08:24
kota_acoles: ok, awesome progress. thanks08:24
acoleskota_: I hope to work some more on https://review.openstack.org/#/c/453827/ soon.08:25
patchbotpatch 453827 - swift - WIP Add CompositeRingBuilder class08:25
kota_acoles: yup, that's fantastic too08:26
*** ianychoi has quit IRC08:35
*** ianychoi has joined #openstack-swift08:38
*** derekjhyang has joined #openstack-swift08:43
openstackgerritjunboli proposed openstack/swift master: Fixed get ring name from recon cli  https://review.openstack.org/44844908:48
*** openstackgerrit has quit IRC09:03
*** kei_yama has quit IRC09:49
*** kei_yama has joined #openstack-swift09:51
*** PavelK has joined #openstack-swift10:06
*** m_kazuhiro has quit IRC10:07
*** zhurong has quit IRC10:10
*** zhurong has joined #openstack-swift10:11
dewanee_anyone has experience in integrating swift and keystone roles? Apparently if a user has read/write access to a container belonging to a project but no other rights he/she cannot delete multiple files10:27
dewanee_just one at a time10:27
dewanee_which is ridicolous10:28
*** ianychoi has quit IRC10:36
*** ianychoi has joined #openstack-swift10:38
*** kei_yama has quit IRC11:22
*** mvk has quit IRC11:49
*** ianychoi has quit IRC12:21
*** ianychoi has joined #openstack-swift12:26
*** gkadam has quit IRC12:40
*** PavelK has quit IRC12:48
*** stradling has joined #openstack-swift12:48
*** zhurong has quit IRC12:54
*** winggundamth has quit IRC13:12
*** RobGThai has joined #openstack-swift13:14
*** RobGThai has quit IRC13:15
*** RobGThai has joined #openstack-swift13:15
RobGThaiHi guys, I have issue with Swift Proxy failing upload request a lot.13:15
RobGThaiHas anyone got similar experiences before?13:16
*** JimCheung has joined #openstack-swift13:17
*** gabor_antal has quit IRC13:19
*** gabor_antal has joined #openstack-swift13:20
*** JimCheung has quit IRC13:21
*** Dinesh_Bhor has quit IRC13:22
*** Dinesh_Bhor has joined #openstack-swift13:24
*** _JZ_ has joined #openstack-swift13:25
*** mvk has joined #openstack-swift13:33
*** JimCheung has joined #openstack-swift13:33
*** JimCheung has quit IRC13:37
*** vint_bra has joined #openstack-swift13:42
*** SkyRocknRoll has joined #openstack-swift13:51
*** flwang has quit IRC13:57
*** ianychoi has quit IRC14:05
*** jaosorior is now known as jaosorior_away14:06
*** ianychoi has joined #openstack-swift14:06
*** flwang has joined #openstack-swift14:10
*** silor has joined #openstack-swift14:17
*** chlong has joined #openstack-swift14:21
-openstackstatus- NOTICE: latest base images have mistakenly put python3 in some places expecting python2 causing widespread failure of docs patches - fixes are underway14:27
*** jordanP has joined #openstack-swift14:28
*** SkyRocknRoll has quit IRC14:35
*** jordanP has quit IRC14:37
*** edisonxiang has quit IRC14:38
*** edisonxiang has joined #openstack-swift14:39
*** jordanP has joined #openstack-swift14:39
*** cshastri has quit IRC14:40
-openstackstatus- NOTICE: we have rolled back centos-7, fedora-25 and ubuntu-xenial images to the previous days release. Feel free to recheck your jobs now.14:48
*** ianychoi has quit IRC14:48
*** ianychoi has joined #openstack-swift14:52
*** jlvillal_pto is now known as jlvillal14:52
*** SkyRocknRoll has joined #openstack-swift14:58
*** klrmn has joined #openstack-swift15:01
*** rcernin has quit IRC15:05
hugokuomorning ~!15:21
*** xinli has joined #openstack-swift15:25
*** psachin has quit IRC15:25
*** joeljwright has joined #openstack-swift15:25
*** ChanServ sets mode: +v joeljwright15:25
*** joeljwright has quit IRC15:26
*** joeljwright has joined #openstack-swift15:27
*** ChanServ sets mode: +v joeljwright15:27
timburkegood morning15:27
joeljwrighttimburke: hey15:28
*** chlong_ has joined #openstack-swift15:29
*** chlong has quit IRC15:32
*** geaaru has quit IRC15:37
* timburke should go look at that pre-/post-amble patch again...15:39
*** neonpastor has joined #openstack-swift15:39
joeljwrighttimburke: yes please!15:39
joeljwright:D15:39
*** vinsh has quit IRC15:43
*** vinsh has joined #openstack-swift15:43
*** chlong has joined #openstack-swift15:43
*** tonanhngo has joined #openstack-swift15:47
*** Administrator_ has quit IRC15:51
*** Administrator_ has joined #openstack-swift15:52
timburkedewanee_: i'm starting to regret having done https://review.openstack.org/#/c/190887/ ... the trouble is that when there are enough objects, python-swiftclient switches from per-object deletes to bulk deletes in an effort to minimize WAN requests. however, the authorization gets confused since that involves a POST to the account15:53
patchbotpatch 190887 - python-swiftclient - Use bulk-delete middleware when available (MERGED)15:53
timburkei'm thinking i should revisit the idea of having a --bulk option and requiring that users opt-in to the bulk-delete behavior15:53
*** vinsh_ has joined #openstack-swift15:57
dewanee_timburke, that's actually a useful feature but at the same time it can give the issues I was writing about before15:58
*** jistr is now known as jistr|mtg15:59
dewanee_what would then be the minimum permission needed to have it work?16:00
*** vinsh has quit IRC16:00
dewanee_we know it works as admin or however you want to call the role16:01
*** ianychoi has quit IRC16:07
timburke:-/ looking at the bulk-delete code, i'm not actually sure what went wrong -- it seems to just translate the one account POST into a whole bunch of object DELETEs, each of which should individually be authorized. is bulk left of auth in the proxy pipeline?16:08
timburkeeither way, i should see about getting a patch up to require a flag to trigger bulk deletes, and in the mean time, you can do some manual batching, or downgrade to swiftclient<3.0.0, or (if you feel like hacking up swiftclient a bit) find _should_bulk_delete in service.py and have it always return False16:09
*** ianychoi has joined #openstack-swift16:12
*** d0ugal has quit IRC16:18
*** gyee has joined #openstack-swift16:25
*** JimCheung has joined #openstack-swift16:28
*** pcaruana has quit IRC16:29
*** jistr|mtg is now known as jistr16:37
*** chsc has joined #openstack-swift16:41
*** joeljwright has quit IRC16:45
claygtimburke: patch 190887 took seven months to get merged; and 4 core reviewers and a couple of other folks; and you're saying it may not have been the best idea to add the behavior in the first place?16:45
patchbothttps://review.openstack.org/#/c/190887/ - python-swiftclient - Use bulk-delete middleware when available (MERGED)16:45
clayg... or you just mean the part to make it "automatic"16:45
claygmost of the code would have been the same even if it was --explicit?16:45
RobGThaiQuick question, should I use SwiftService in python-swiftclient to write an API for user to upload file into Swift?16:47
claygoh, it's all torgomatic's fault "I'd prefer not having two ways to delete things; what about adding this stuff to the normal "swift delete" command and using bulk ops if available and single requests otherwise?"16:47
timburkeclayg: the automatic part. torgomatic's comment of "The --bulk flag could be good, but I don't see it as essential." may have been off the mark16:48
claygRobGThai: yeah, SwiftService is totally supported and even documented!  https://docs.openstack.org/developer/python-swiftclient/service-api.html16:48
RobGThaiI have a problem using it in production.16:48
RobGThaiIt tried to create container every request.16:48
claygRobGThai: joeljwright I'm sure would love you to give it a spin, report bugs, provide feedback and *gasp* patches for docs and missing features/bugs!16:48
claygRobGThai: what kind of request?16:49
RobGThaiCausing Account sync to fail because it's locking a lot.16:49
clayg... account sync ...16:49
RobGThaiAt least that's what the error seems to say.16:50
RobGThaiIs that something related? Or is it something completely different?16:51
*** winggundamth has joined #openstack-swift16:53
*** stradling has quit IRC16:54
cbartzHello. Anyone here for reviewing patch 454716 ? Thx....16:57
patchbothttps://review.openstack.org/#/c/454716/ - swift - Allow DLO PUT to prefix-based tempurls16:57
*** mgagne has joined #openstack-swift17:00
claygRobGThai: well, post some code in a gist or something - i'm not sure what error you're seeing or from where?17:00
claygRobGThai: there may be an option to restructure the calls so you get only the requests you want17:01
*** stradling has joined #openstack-swift17:02
RobGThaiThere's a way?17:02
RobGThaiclayg https://gist.github.com/RobGThai/42eba4c73f78ee48c9c92e76231ac42f17:03
RobGThaiIt's pretty straight forward, really.17:04
timburkei don't think there is a way to avoid the container PUT through the service api -- although i'd totally +2 a patch to add an option to bypass it! https://github.com/openstack/python-swiftclient/blob/3.3.0/swiftclient/service.py#L1427-L143717:04
*** cbartz has quit IRC17:07
dewanee_if you are curious that's what the proxy reply: cold-k4-30 proxy-server: xxx.xxx.xxx.xxx 10.129.31.231 11/Apr/2017/17/04/45 DELETE /v1/AUTH_6169dd64a7ed498581cee5abff0c6cd7/user%3Fbulk-delete%3D1 HTTP/1.0 40317:08
dewanee_if a user has the ability to create containers and manage acl it works17:09
dewanee_but that's what we wanted to avoid in production17:09
dewanee_I don't know if it makes more sense this way..17:10
timburkedewanee_: is there any logging from auth_token or keystoneauth middlewares? another option would be to just remove bulk from the pipeline; the client will only try it we see bulk delete is available17:11
timburkei'll also try to reproduce locally later, but i'm afraid i'm a bit tied up at the moment...17:11
*** ChubYann has joined #openstack-swift17:15
RobGThaiThe reason I wanted to avoid doing that is because the LockTimeout.17:19
RobGThaiI'm under impression that PUT container causing account to sync/replicate.17:20
dewanee_timburke, I'll try to provide some additional info next week. Bye all17:25
*** mvk has quit IRC17:25
timburkedewanee_: sounds good. hopefully some of the suggestions will help in the meantime17:25
*** tesseract has quit IRC17:26
*** stradling has quit IRC17:50
*** mvk has joined #openstack-swift17:57
*** stradling has joined #openstack-swift18:10
*** Sukhdev has joined #openstack-swift18:26
*** mgagne_ has joined #openstack-swift18:35
*** mgagne_ is now known as Guest8931718:35
claygRobGThai: I'm not sure the locktimeout is strictly "because" of the PUT container requests... are you running your account and container databases on the same devices as the object data?  rotational media?  (i.e. NOT ssds)18:35
claygRobGThai: anyway, you *can* give self.service.upload a list of *multiple* objects - in that case there should only be the *one* PUT container (which should be fast/cheap)18:37
claygoh... sorry you're already giving it "A list of treasure to upload"18:37
RobGThaiWe are using it to back end-user upload tho.18:38
claygso yeah, i'm not sure the single container PUT is really so much of an error - the *client* doesn't see LockTimeout - what is the problem from the client side?18:38
RobGThaiSo bundling multiple files isn't really the option.18:38
RobGThaiIt took too long then timeout18:38
RobGThaiLike over a minute.18:39
claygoic, the container create tries to update the account syncronously ... maybe you need to tune the account/container workers?18:39
RobGThaiBy tuning you mean account sync worker?18:40
RobGThaiWe currently set it to 32 on our 16 CPU node.18:41
claygdoes that particulary account have many millions of containers or something?18:41
RobGThaiWe created about 100 containers per day.18:42
claygthe syncronous account update on container put should timeout after node_timeout - you could tune down the container node_timeout - but honestly even on spinning disks I don't think i've seen accounts hit timeouts much18:43
RobGThaiRight now it's about tens of thousand at most18:43
clayg10-100K is *fine*18:43
claygprobably many 100K is fine - even on spinning disk - but if the disks are the same as the object disks - it just depends on the client access and ongoing replication18:44
RobGThaiEven if I have around 20K files upload per day?18:44
RobGThaiWe separated objects into itsown disk.18:45
claygwith containers that have 4M - 10M rows or more - when they have to stop adding entries to .pending and insert them into the index it can make the request slow (which can cause other updates to that container to hit the locktimeout trying to add entries to the .pending)18:45
claygthe same process holds for the account - but it's much less common - the cardinality of objects in containers tends to be many order of magnitude greater than the cardinaility of containers in the account18:46
clayg... but everyone's data schema is different - so I just thought i'd ask18:46
*** Guest89317 has quit IRC18:46
RobGThaiThe maximum number of file in one container is about 150K.18:47
clayganyway - your worker count sounds fine - you could try to increase it if you have a particularlly high request count - but it sounds like maybe it's just disk i/o contention in general (which eventlet servers hate, grrr)18:47
claygRobGThai: 150K is fine!18:47
claygRobGThai: so but you have objects & accounts & containers all on the same disks yes?18:47
RobGThaiAccount & container on one with object on another.18:48
claygoh... that's good!18:48
claygand the one disk (per node?) that is for account & container are... ssd or rotational?18:49
RobGThaiYes, rotational disk.18:49
RobGThaiOne account/container disk and ten object disks per node.18:50
RobGThaiNo RAID.18:50
claygthat should be a pretty good setup from my experience - i'm sorry you're having trouble :\18:54
claygOTOH, I'm not sure I would expect there would "never" be locktimeout on the accounts & containers - but I would expect you to see it *more* on containers than accounts - so that's weird maybe18:55
RobGThaiWe also see it on containers.18:56
RobGThaiWe didn't expect a perfect scenario though. It just unable to serve our 150K uploads per day right now.18:57
claygwell - it could mean your request rate to that layer is generating more iops than those spindles want to support - esp if you only have same number of devices as replicas :\18:57
claygwell - that part is weird - even if a udpate fails here and there it should only take *seconds* to timeout at most - and you *could* tune those down18:57
RobGThaiWe have 4 nodes with 3 replica.18:58
clayg... but the requests should *finish* regardless, and that work load seems pretty nominal available resources :\18:58
RobGThaiEverything I read so far seems to be saying that.18:58
RobGThaiCould it be happening to a specific version?18:59
RobGThaiWe are on Mitaka.19:00
claygwell... idk - it could be close-ish - 150K ops is a ~ hundred a second yeah?  with write amplification across three spindles... each sqlite update is going to be a couple of disk iops at best (read/modify/write page)19:00
claygupdating to a later version always helps19:00
clayghas the load been ramping up over time?  did you use to see less timeouts?  either way if you expect usage to increase over time...19:01
claygi need to step away - the timeout is telling you the databases are hitting some contention and they're busy - you can throw hardware at it - you can try to tweak/tune - you can try to change the access pattern19:01
RobGThaiThe load has been about the same since the last two months AFAIK.19:01
clayg... and it only recently started?  if it was fine then it went south something changed :P19:02
claygsorry, i really need to step away - i'm not 100% sure the issue is any more complicated than load at this point tho - GL!19:02
RobGThaiThanks clayg. Appreciate the help.19:02
*** openstackgerrit has joined #openstack-swift19:18
openstackgerritOpenStack Proposal Bot proposed openstack/python-swiftclient master: Updated from global requirements  https://review.openstack.org/8925019:18
*** mgagne_ has joined #openstack-swift19:18
*** mgagne_ is now known as Guest436619:19
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873619:20
*** mgagne has quit IRC19:24
*** Guest4366 is now known as mgagne19:25
*** mgagne has quit IRC19:25
*** mgagne has joined #openstack-swift19:25
*** winggundamth has quit IRC19:29
timburkebug or feature? doing a DELETE with ?multipart-manifest=delete to something that's not an SLO doesn't delete anything19:32
timburkethe dlo case may be a bit special, but it'd be kinda nice if i could have a single client request to delete an object, and if it's an SLO, to clean up the segments while we're at it19:33
*** ianychoi has quit IRC19:34
*** ianychoi has joined #openstack-swift19:35
*** pxwang has joined #openstack-swift19:51
*** silor has quit IRC19:54
*** RobGThai has quit IRC20:00
*** brnelson has joined #openstack-swift20:18
claygtimburke: sounds like a bug to me?  do you get a 4XX of some kind I guess?20:27
timburkeclayg: nope! because we're piggy-backing off the bulk deleter, i guess? 200 OK, with 400 Bad Request needing to be parsed out of the *body*20:28
* clayg has a conniption20:30
timburkelooks something like http://paste.openstack.org/show/606201/20:30
*** SkyRocknRoll has quit IRC20:31
claygdo you suppose it's always been like that - or some kind of regression?  I think maybe we shouldn't have hi-jacked DELETE in this way :\20:32
claygthat's probably come up before tho20:32
claygTFW after 5 mins troubleshooting a partition placement hash mis-match issue through backend logs and with swift-get-nodes you realize the original path just had a typo :'(20:42
*** vint_bra1 has joined #openstack-swift20:47
*** dmellado has quit IRC20:48
*** vint_bra has quit IRC20:50
brnelsonI'm sure we all have stories like that.  And it's even more fun when you're stumped and ask a coworker for advice on the problem, and they instantly spot the typo.20:56
*** stradling has quit IRC21:01
*** pxwang has quit IRC21:03
*** chlong has quit IRC21:09
*** chlong_ has quit IRC21:09
*** catintheroof has joined #openstack-swift21:19
*** catintheroof has quit IRC21:21
*** catintheroof has joined #openstack-swift21:21
openstackgerritTim Burke proposed openstack/swift master: Update reno for stable/ocata  https://review.openstack.org/43478521:58
claygtimburke knows how to reno!22:03
timburkemaybe? i guess we'll see what happens. does make me a little sad that https://review.openstack.org/#/c/455439/ isn't landed though...22:05
patchbotpatch 455439 - openstack-infra/project-config - swift: Skip long running dsvm jobs for unrelated c...22:05
claygtimburke: I hear in zuul3 we get to have that stuff in our own repo!22:06
claygtdasilva: do you know someone to poke to help timburke with patch 45543922:07
patchbothttps://review.openstack.org/#/c/455439/ - openstack-infra/project-config - swift: Skip long running dsvm jobs for unrelated c...22:07
timburkeyay, more yaml!22:07
claygyaml is the best22:07
clarkbfwiw we are trying to avoid those rules, they create constant confusion "why do not get any test results" or "why isn't my change merging"22:10
* clayg bests clarkb already posted more details on the review22:11
clarkbno, I haven't22:11
* clayg owes me a dollar :'(22:11
clarkbbasically the current situation is correct and hard to break at the expense of generating a few extra tests here and there22:11
claygi'm not sure if you mean '-1 don't do this' or '+1 meh, we have another thing that will make this so much more awesome you don't even..."22:12
claygah, so the first22:12
clarkbits more +0 current setup is correct, proposed change will potentially break you when you end up in situation where no tests run22:12
claygyou should *totally* put that on the review so timburke can abandon22:12
clarkbI can right the +0 :)22:12
claygoic, idk, sounds bad, if you have experience that says we don't want what we think we want ... oh yeah maybe that's a +022:13
claygtimburke: do you follow why no tests running would be bad?  maybe clarkb can guide you.  I think the says running dsvm on doc changes is *fine*22:13
clarkbclayg: posted22:15
timburkei think i follow -- if you write so many of these rules that some changes don't trigger any tests *at all*, there's nothing for zuul to verify, so you'll never get a +1/+2, so it'll never merge22:17
clarkbcorrect22:17
timburkestill seems like it might be worth it when specifically scoped to the hour+ jobs, but if we're worried about people coming along later wanting to prevent unit tests from running on doc-only changes or the like, maybe it's best to not even have the precedent22:17
clarkband this happens often enough people show up in the infra channel and we spend time debugging only to have a sad when we discover it22:17
clarkband then I try to get them to undo the rules they have and they don't want to then I get extra sad :)22:18
clarkbbut if you have a specific use case or concern beyond generic wasted use cases ahppy to reconsider22:18
timburkejust the wall time. all the other jobs complete in <10 mins, those ones can be as long as an hour22:19
clarkbtimburke: I found what I think is an actual functional issue with it so I -1'd. I'm happy to +2 if thats fixed and you want to reduce rtt but won't go too crazy on optimizing when all the jobs run22:23
timburkeclarkb: good call. i was mainly cribbing from others -- but i guess cinder, designate, horizon, etc. don't have tox targets hit by the dsvm tests?22:27
clarkbtimburke: or if they do they are in error. Not sure which :)22:27
clarkbtimburke: but not all projects have set up their functional tests that way so possible its not actually a problem for them22:27
timburkecool. i'll go abandon22:29
clarkbI'm happy to put it in if the argument is reducing turn around (I wasn't sure how much time would be saved)22:30
timburkethe good news is, https://review.openstack.org/#/c/434785/ has already produced http://docs-draft.openstack.org/85/434785/2/check/gate-swift-releasenotes/af9ae98//releasenotes/build/html/ !22:30
patchbotpatch 434785 - swift - Update reno for stable/ocata22:30
clarkbbut as a general rule ya I prefer to avoid skip ifs22:30
claygtimburke: and the version # on http://docs-draft.openstack.org/85/434785/2/check/gate-swift-releasenotes/af9ae98//releasenotes/build/html/current.html is wrong because EmilienM didn't get to add the magic commit in the gitlog?22:32
timburkehmm... then maybe i'll scope it more tightly (*only* the doc trees) and hope that the improved turn-around time leads to better docs since fixes will seem "cheaper"22:32
timburkeclayg: not sure22:36
timburkehuh. nova's version number on https://docs.openstack.org/releasenotes/nova/unreleased.html seems kinda insane -- a 15.0.0.0 RC when 15.0.2 was released as part of ocata?22:37
mattoliveraumorning22:37
*** xinli has quit IRC23:17
timburkehuh. that's a new one for me: http://logs.openstack.org/85/434785/2/check/gate-swift-tox-xfs-tmp-func-post-as-copy-ubuntu-xenial/052bd6a/console.html#_2017-04-11_22_02_36_45300123:17
*** vint_bra1 has quit IRC23:23
*** kei_yama has joined #openstack-swift23:29
*** catintheroof has quit IRC23:29
*** catintheroof has joined #openstack-swift23:30
*** catintheroof has quit IRC23:30
*** tonanhngo has quit IRC23:36
*** chsc has quit IRC23:37
*** tonanhngo has joined #openstack-swift23:43
*** jamielennox is now known as jamielennox|away23:48
*** tonanhngo has quit IRC23:48
*** jamielennox|away is now known as jamielennox23:51

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