Wednesday, 2017-06-07

*** adriant has joined #openstack-swift00:19
claygtimburke: had you already confirmed that apache mod proxy won't handle passing expect 100 continue responses from the proxied app to the client?00:26
timburkeclayg: i haven't done any real investigation into apache and 100-continue00:27
claygtimburke: I managed to get the testFileSizeLimit request going through to swift - and I'm getting the 413 error logged - but apache is still taking it's own damn time to respond with 40000:27
claygsorry I thought I saw you say something yesterday - thanks00:27
timburkethat was pure spitballing00:27
claygwell good fucking guess genius - I think that's more or less the problem ;)00:28
timburkeso what all did you do to get it to 413?00:28
claygjust feed it more bytes00:28
timburkeah, sure -- get it to have enough in its buffer to flush and send data to swift. remind me: as part of the 413, does swift send a connection: close and immediately hang up?00:30
claygbut it's not just tests -> https://gist.github.com/clayg/8a0eb56c8984c0cf9b58bb5a409aedf800:30
timburkei wonder if apache is trying to be "nice" and keep the data flowing, with the assumption that the client wants to pipeline another request...00:31
claygyeah idk... swift isn't sending Connection: close - there's a bunch of ML postings and things about apache and expect: 100-continue support - it's possible swift or the request could be changed to make it work?00:33
timburkewhat do we do if you try to pipeline requests and the first one is too big? does eventlet throw away $content_length bytes, or does it assume that the client never sent any of them? 'cause one of those is still http and the other isn't00:36
claygthis is weird, I took the timeout out again, swift has logged the 413, apache has logged the 400, but the test is still hung waiting on the response?  Maybe http_client is being particularly stupid and annoying?00:36
timburkehave you tried sending *all* the bytes?00:36
claygfuck no :p00:37
claygwe should close the connection after we respond 4xx after expect: 100-continue - that's the only correct behavior00:37
*** lucasxu has joined #openstack-swift00:42
*** lucasxu has quit IRC00:44
*** itlinux has joined #openstack-swift00:45
*** lucasxu has joined #openstack-swift00:45
*** lucasxu has quit IRC00:47
kota_morning00:47
kota_clayg: thanks for your ack for mahatic's patch. I'll be back to the patch today00:48
kota_notmyname: that https://review.openstack.org/#/c/439572/  is my priority today00:48
patchbotpatch 439572 - swift - Limit number of revert tombstone SSYNC requests00:48
notmynamekota_: thanks!00:48
kota_notmyname: to tell truth, I saw the comment from clayg briefly and i'm feeling what i can do is just pushing my +2 +A00:50
*** lucasxu has joined #openstack-swift00:50
kota_but before doing so, I want to look up it again00:50
notmyname:-)00:50
*** ukaynar has joined #openstack-swift00:51
kota_clayg: for https://review.openstack.org/#/c/439572/, can i update the commit message and give +A for that? I think current commit message is lack to describe what actually the patch want to improve00:51
patchbotpatch 439572 - swift - Limit number of revert tombstone SSYNC requests00:51
kota_but I want to modify only just a commit message even we could accept the number of sync nodes as current00:52
*** zhengyin has joined #openstack-swift00:54
notmynamekota_: I'm ok with you updating the commit message and adding your +2/+A to a patch00:54
claygNo worries.00:54
kota_notmyname, clayg: thanks, probably i can finish up the patch!00:55
*** itlinux has quit IRC00:55
*** itlinux has joined #openstack-swift00:56
*** itlinux has quit IRC00:56
*** lucasxu has quit IRC00:56
*** lucasxu has joined #openstack-swift00:58
*** lucasxu has quit IRC01:05
*** tovin07_ has joined #openstack-swift01:05
openstackgerritLingyong Xu proposed openstack/swift master: Using assertIsNone() instead of assertEqual(None)  https://review.openstack.org/47152201:08
openstackgerritThiago da Silva proposed openstack/pyeclib master: Release 1.5.0  https://review.openstack.org/47152401:11
*** gyee has quit IRC01:25
*** zhurong has joined #openstack-swift01:28
clarkbbtw I think the two changes to simplify the swift functional test setup finally merged and applied so if you notice any weirdness in the gate func test let me know. But I tested it and it should be happy01:31
notmynameclarkb: thank you01:31
*** itlinux has joined #openstack-swift01:39
*** itlinux has quit IRC01:45
*** chlong has quit IRC01:50
openstackgerritMerged openstack/swift master: Using assertIsNone() instead of assertEqual(None)  https://review.openstack.org/47152201:55
*** itlinux has joined #openstack-swift01:57
*** itlinux has quit IRC02:05
kota_clayg: still?02:09
*** mingyu has joined #openstack-swift02:14
kota_clayg: I added a thought for https://review.openstack.org/#/c/439572/02:21
patchbotpatch 439572 - swift - Limit number of revert tombstone SSYNC requests02:21
kota_clayg: I basically agree with your thought we can have less primaries than k to push the tombstone if we assume primary partners can propagate the tombstone asap02:22
kota_and it looks to work as you expected when *no ec duplication case*02:23
kota_however, in my final review, I found another corner case, I don't suppose it's in your expectation so I still wanna get your opinion that.02:24
kota_ec_duplication is much durable (can be readable if a few frags are not available), (probably) we've expected02:25
kota_than we expected02:25
*** zhurong has quit IRC02:30
*** mat128 has quit IRC02:36
*** mat128 has joined #openstack-swift02:39
openstackgerritHieu LE proposed openstack/swift master: OSprofiler in OpenStack Swift  https://review.openstack.org/46831602:43
timburkeclayg: interesting... try something like this02:44
timburkecurl -H content-length:999999999999 -X PUT -d 1234 http://saio:8090/v1/AUTH_test/test-container/big -X PUT -d 1234 http://saio:8090/v1/AUTH_test/test-container/little02:44
timburke(maybe throw in a -v)02:45
*** mat128 has quit IRC02:47
*** mat128 has joined #openstack-swift02:48
*** links has joined #openstack-swift02:52
*** mat128 has quit IRC02:52
*** itlinux has joined #openstack-swift03:22
*** mingyu has quit IRC03:27
*** mingyu has joined #openstack-swift03:29
*** mingyu has quit IRC03:33
*** winggundamth has joined #openstack-swift03:34
*** winggundamth has quit IRC03:37
openstackgerritLingyong Xu proposed openstack/swift master: Using assertIsNone() instead of assertEqual(None)  https://review.openstack.org/47157003:37
*** winggundamth has joined #openstack-swift03:42
*** ukaynar has quit IRC03:43
*** psachin has joined #openstack-swift03:44
*** mingyu has joined #openstack-swift03:46
*** mingyu has quit IRC03:50
*** aselius has quit IRC03:55
*** kei_yama has quit IRC03:57
*** zhurong has joined #openstack-swift04:00
*** kei_yama has joined #openstack-swift04:01
*** hoonetorg has quit IRC04:29
*** zhurong has quit IRC04:30
*** adriant has quit IRC04:35
*** kei_yama has quit IRC04:35
mahaticclayg: thanks for your comments on patch 439572!04:35
patchbothttps://review.openstack.org/#/c/439572/ - swift - Limit number of revert tombstone SSYNC requests04:35
mahatichmm I didn't get a notification04:36
*** adriant has joined #openstack-swift04:39
*** zhurong has joined #openstack-swift04:40
*** adriant has quit IRC04:40
*** adriant has joined #openstack-swift04:41
*** hoonetorg has joined #openstack-swift04:46
*** itlinux has quit IRC04:49
*** mingyu has joined #openstack-swift04:50
*** mingyu has quit IRC04:55
*** pcaruana has joined #openstack-swift04:56
*** zhengyin has quit IRC05:06
*** zhengyin has joined #openstack-swift05:07
*** pcaruana has quit IRC05:14
*** bkopilov has joined #openstack-swift05:14
kota_mahatic: how do you think of the number of primary nodes to push the tombstone?05:15
*** kei_yama has joined #openstack-swift05:20
*** skudlik has joined #openstack-swift05:32
*** cshastri has joined #openstack-swift05:43
mahatickota_: thanks for your comments as well. I just read them. I'm still thinking on the EC duplication case05:49
*** qwertyco has joined #openstack-swift05:50
zaitcevmahatic: https://wiki.openstack.org/wiki/Meetings/Swift does not have your meeting, could you please remind me what time it starts?05:51
kota_mahatic: thanks, exactly, (replicas - k + 1) may be too many primaries... not sure.05:52
mahaticzaitcev: hi, it's on the right column 0700. We've agreed on having a diff chair each time for this meeting (alphabetically). So acoles is going to chair the next one05:53
mahaticzaitcev: please feel free to update the page with topics, if you have any05:53
mahaticzaitcev: next one is on June 14th05:54
zaitcevmahatic: thank you, I see the time in the column header now05:54
*** winggundamth has quit IRC06:05
openstackgerritLingyong Xu proposed openstack/swift master: Using assertIsNone() instead of assertEqual(None)  https://review.openstack.org/47157006:06
*** jaosorior_away is now known as jaosorior06:11
openstackgerritKota Tsuyuzaki proposed openstack/swift master: Follow up for account quota exclude containers patch  https://review.openstack.org/47159206:12
*** bkopilov has quit IRC06:17
*** rcernin has joined #openstack-swift06:21
*** cshastri has quit IRC06:33
*** hseipp has joined #openstack-swift06:40
*** saltsa has quit IRC06:40
*** cshastri has joined #openstack-swift06:49
*** mingyu has joined #openstack-swift06:52
*** saltsa has joined #openstack-swift06:53
*** mingyu has quit IRC06:54
*** klrmn has quit IRC06:57
*** afazekas has quit IRC07:01
*** afazekas has joined #openstack-swift07:01
*** mingyu has joined #openstack-swift07:01
*** mingyu has quit IRC07:02
*** mingyu has joined #openstack-swift07:02
*** pcaruana has joined #openstack-swift07:03
*** tesseract has joined #openstack-swift07:11
*** cshastri has quit IRC07:17
*** bkopilov has joined #openstack-swift07:20
*** oshritf has joined #openstack-swift07:21
*** geaaru has joined #openstack-swift07:21
*** cshastri has joined #openstack-swift07:34
*** mingyu has quit IRC07:35
openstackgerritKota Tsuyuzaki proposed openstack/swift master: WIP: use config_number method instead of node_id + 1  https://review.openstack.org/47161307:45
*** rcernin has quit IRC07:52
*** rcernin has joined #openstack-swift07:52
*** cbartz has joined #openstack-swift07:55
rlediseznotmyname: nothing you missed, alecuyer just had no time to work on it. it's still on todo list07:56
rledisezclayg: reconstructor concurency, right now I run 1 REVERT process + 1 SYNC process for N devices (N being 1 or 3 depending on the IO load I observe). in config file I set concurrency=107:58
openstackgerritKota Tsuyuzaki proposed openstack/swift master: Follow up for affinity config per policy  https://review.openstack.org/46792008:15
openstackgerritChristopher Bartz proposed openstack/swift master: Exclude containers for account quota  https://review.openstack.org/41423208:18
acolesgood morning08:21
acoleskota_: hi! did you change patch 467920 or just rebase?08:21
patchbothttps://review.openstack.org/#/c/467920/ - swift - Follow up for affinity config per policy08:21
kota_acoles: hi, just rebased08:22
kota_acoles: sorry not yet checking your comments08:22
acoleskota_: ok. oh, I just saw your comment on gerrit :)08:22
kota_acoles: :)08:22
acoleskota_: would be good to get that merged, and not have too many 'follow-up' patches hanging around08:23
kota_acoles: yup, maybe i will have more time to look at my patches tommorow08:23
acoleskota_: ok08:26
*** mingyu has joined #openstack-swift08:36
*** cshastri has quit IRC08:40
*** mingyu has quit IRC08:41
openstackgerritKota Tsuyuzaki proposed openstack/swift master: Use config_number method instead of node_id + 1  https://review.openstack.org/47161308:44
*** zhurong has quit IRC08:47
*** kei_yama has quit IRC08:49
*** jamielennox is now known as jamielennox|away08:50
*** cshastri has joined #openstack-swift08:54
*** cshastri has quit IRC08:55
*** cshastri has joined #openstack-swift08:56
*** mvk has joined #openstack-swift08:57
kota_https://review.openstack.org/#/c/471613/ is for timburke08:58
patchbotpatch 471613 - swift - Use config_number method instead of node_id + 108:58
kota_timburke: it seems like we already have the mapping helper method from node to config number, that is wisdom of our predecessors08:59
*** zhurong has joined #openstack-swift09:02
*** mingyu has joined #openstack-swift09:04
*** jamielennox|away is now known as jamielennox09:10
*** qwertyco has quit IRC09:14
cbartzkota: Thx for your review. Would you like to take a look over patch 454716 ?09:29
patchbothttps://review.openstack.org/#/c/454716/ - swift - Allow DLO PUT to prefix-based tempurls09:29
openstackgerritLingyong Xu proposed openstack/python-swiftclient master: Drop py34 target in tox.ini  https://review.openstack.org/47168509:43
*** zhurong has quit IRC09:51
*** qwertyco has joined #openstack-swift09:55
*** mvk has quit IRC09:55
*** mingyu has quit IRC10:00
*** mingyu has joined #openstack-swift10:00
*** psachin has quit IRC10:08
*** silor has joined #openstack-swift10:08
*** psachin has joined #openstack-swift10:09
*** psachin has quit IRC10:09
*** mvk has joined #openstack-swift10:27
*** tovin07_ has quit IRC10:29
openstackgerritAlistair Coles proposed openstack/swift master: Improve domain_remap docs  https://review.openstack.org/47171210:35
*** kong has joined #openstack-swift10:38
*** zhengyin has quit IRC11:08
*** zhengyin has joined #openstack-swift11:11
*** psachin has joined #openstack-swift11:40
*** mingyu has quit IRC11:43
*** zhengyin has quit IRC11:49
openstackgerritLingxian Kong proposed openstack/swift master: Write-affinity aware object deletion  https://review.openstack.org/47015811:57
openstackgerritOpenStack Proposal Bot proposed openstack/swift master: Updated from global requirements  https://review.openstack.org/8873612:01
*** chlong has joined #openstack-swift12:02
*** mat128 has joined #openstack-swift12:08
*** tovin07 has joined #openstack-swift12:44
*** klamath has joined #openstack-swift13:26
*** links has quit IRC13:30
*** chlong has quit IRC13:43
*** mingyu has joined #openstack-swift13:47
*** mingyu has quit IRC13:51
*** zhurong has joined #openstack-swift13:54
*** gkadam has joined #openstack-swift13:58
*** gkadam has quit IRC14:13
claygrledisez: 1 or 3 depending on observed io sounds pretty sophisticated!?14:13
claygrledisez: is it always 1 revert per drive?  Is the tuning for sync "drives_per_worker"?  Or do you just have a high/low mode?14:15
*** zhurong has quit IRC14:17
cbartztimburke: Could you please take a final look over patch 414232 ? Thx.14:18
patchbothttps://review.openstack.org/#/c/414232/ - swift - Exclude containers for account quota14:18
*** mingyu has joined #openstack-swift14:25
*** jaosorior is now known as jaosorior_away14:31
*** lucasxu has joined #openstack-swift14:44
*** cshastri has quit IRC14:45
*** mingyu has quit IRC14:49
*** mingyu has joined #openstack-swift14:52
openstackgerritAlistair Coles proposed openstack/swift master: Update Global EC docs with reference to composite rings  https://review.openstack.org/46801114:58
*** mat128 has quit IRC15:00
openstackgerritThiago da Silva proposed openstack/liberasurecode master: re-org of README  https://review.openstack.org/47181315:00
*** cebruns has quit IRC15:00
*** psachin has quit IRC15:01
*** cebruns has joined #openstack-swift15:02
*** aselius has joined #openstack-swift15:02
*** mingyu has quit IRC15:11
*** rcernin has quit IRC15:11
*** skudlik has quit IRC15:13
*** ujjain has joined #openstack-swift15:20
*** ujjain has joined #openstack-swift15:20
*** qwertyco has quit IRC15:23
*** chlong has joined #openstack-swift15:27
*** cbartz has quit IRC15:29
*** lucasxu has quit IRC15:30
*** klrmn has joined #openstack-swift15:33
*** itlinux has joined #openstack-swift15:34
*** gyee has joined #openstack-swift15:41
*** itlinux has quit IRC15:42
*** Sukhdev has joined #openstack-swift15:58
*** gkadam has joined #openstack-swift16:04
*** klrmn has quit IRC16:08
timburkegood morning16:13
claygtimburke: so you're going to track down the thing with closing the connection harder/better on 413?16:13
*** oshritf has quit IRC16:19
*** hseipp has quit IRC16:22
*** mat128 has joined #openstack-swift16:27
*** lucasxu has joined #openstack-swift16:28
*** mat128 has quit IRC16:29
rledisezclayg: by "observed io", i mean i checked the state of my cluster and i updated the value manually. nothing fancy :)16:33
claygphew16:33
claygand what is the value exactly?  like how is it plumbed?  does it effect "devices_per_worker" for SYNC only or REVERT too?16:34
*** tesseract has quit IRC16:34
claygI'm also a little curious what exactly your plumbing looks like for handoff_only revert/sync - i'm guessing it's a little different than upstream?16:36
*** chsc has joined #openstack-swift16:36
*** chsc has quit IRC16:36
*** chsc has joined #openstack-swift16:36
*** Sukhdev has quit IRC16:42
*** silor1 has joined #openstack-swift16:45
*** ediardo has quit IRC16:45
*** silor has quit IRC16:46
*** silor1 is now known as silor16:46
*** itlinux has joined #openstack-swift16:50
notmynamegood morning16:59
timburkeclayg: http://paste.openstack.org/show/611748/ will fix it... i think it should be a sane way to go about it, too? i can't imagine a situation where we *wouldn't* want to immediately close the connection after sending a 41317:00
timburkewithout it, connection's just kinda sitting there; netstat looks like17:03
timburketcp        0      0 saio:8090               192.168.8.1:63408       ESTABLISHED17:03
timburkei'll wait a while, see if that changes17:04
claygidk, feels a little buried... in the status *setter* - magic integer value?  but i haven't looked for a better place... if you think that's really the best maybe it's fine17:06
claygisn't there some places in swob where we already have some sort of "finalize" kind of thing that makes sure some important headers are filled in and sane for various responses... idk, like 'content-length' or accept something something?17:07
*** geaaru has quit IRC17:08
rledisezclayg: "value" is the number of device per process. eg: If I have 36 devices and I choose 3, i'll have 12 REVERT and 12 SYNC process, 3 devices for each. (looks like concurrency is working in auditor)17:09
rledisezyes it's different than upstream. I have 2 params for reconstructor: —revert-only and —sync-only. And I pass the list of devices with —device17:10
*** mvk has quit IRC17:10
timburkeclayg: _response_iter? maybe...17:11
*** klrmn has joined #openstack-swift17:11
claygso it's not *quite* like auditor - auditor would say "concurrency = 12" (which should maybe be "workers", but w/e) then if you had 36 devices you get 3 devices per worker.17:12
claygrledisez: which makes sense to me... but doesn't sound like exactly how you want to be thinking about it?  I think i'm ok with either way with a slight preference to whatever we think is easier to understand17:13
clayger... easier to *explain* or document or whatever17:13
acolesclayg: timburke iirc swob.Response._response_iter does a bunch of 'finalize.-like stuff17:14
*** skudlik has joined #openstack-swift17:14
acolestimburke: oh, you found it :)17:14
rledisezclayg: tbh, i chose the easiest way to implement, not especially the best way. i never though of upstream when i wrote it. it's mainly an init-script stuff, the patch in the reconstructor itself is very short17:17
claygrledisez: ok well - upstream is going to get support for something *like* this and it would be super great if it landed in a condition where you could consume/migrate to it?  So if you wanna have input into the design/implementation now is your chance!17:18
rledisezi feel like defining how much device per process is easier to understand, because you don't have to know how many devices have each of your servers. it will auto adapt the number of process. but I guess everybody know use a config management like puppet & co, so may be not a valid point17:18
claygworst case scenario is I implement something "close" to what you're doing and you opt to not use it and prefer to keep doing your own thing leading to more bifrication17:18
*** ChubYann has joined #openstack-swift17:19
rledisezyeah, i don't want that neither17:19
rledisezclayg: did i miss a link to etherpad or review about that?17:20
*** ChubYann has quit IRC17:20
*** ChubYann has joined #openstack-swift17:20
*** ChubYann has quit IRC17:21
rledisezwhat really matters to me is to separate REVERT and SYNC. SYNC jobs are really slow, so I don"t want to slow down my rebalances because of that17:21
*** ChubYann has joined #openstack-swift17:21
claygno, i haven't finished writing it yet17:21
claygof course!17:21
*** itlinux has quit IRC17:24
claygit's not obvious to me I want to run the same # of sync and revert workers either17:24
*** ChubYann has quit IRC17:25
*** ChubYann has joined #openstack-swift17:26
*** mat128 has joined #openstack-swift17:27
rledisezI actually have this possibility in my implementation, but never used it for now17:27
rledisezdoesn't mean it's a bad idea, just that my cluster is not in situation it would really make sense17:29
*** rcernin has joined #openstack-swift17:31
openstackgerritThiago da Silva proposed openstack/pyeclib master: update to README  https://review.openstack.org/47187217:46
*** silor has quit IRC17:51
*** itlinux has joined #openstack-swift17:54
*** hseipp has joined #openstack-swift17:58
*** gkadam has quit IRC17:59
*** itlinux has quit IRC18:05
*** hseipp has quit IRC18:07
*** itlinux has joined #openstack-swift18:11
*** hseipp has joined #openstack-swift18:19
*** hseipp has quit IRC18:19
*** tonanhngo has joined #openstack-swift18:20
*** qwertyco has joined #openstack-swift18:33
*** Sukhdev has joined #openstack-swift18:37
*** qwertyco has quit IRC18:47
openstackgerritClay Gerrard proposed openstack/swift master: Don't rehash primaries in reconstructor handoffs_only mode  https://review.openstack.org/42840818:55
*** itlinux has quit IRC19:00
*** itlinux has joined #openstack-swift19:00
claygi feel like it should be useful/reasonable to have more than one reconstructor per-disk if you're in a hurry and perhaps less sensitive than rledisez to front end latency - but I can also see running *less* workers than the number of disks.  Maybe the option is workers_per_disk = 0.33 or something...19:06
claygsync_workers_per_disk and handoff_workers_per_disk maybe?19:06
*** rcernin has quit IRC19:17
*** mat128 has quit IRC19:32
*** rcernin has joined #openstack-swift19:35
timburkehow much do we care that the @wsgify decorator breaks functional tests? it bit me in https://review.openstack.org/#/c/449394/, it bit Tovin in https://review.openstack.org/#/c/468316/, and it would have bit cbartz in https://review.openstack.org/#/c/414232/ if account_quotas was left of auth19:37
*** klrmn has quit IRC19:37
patchbotNo data found for patch 44939419:37
patchbotNo data found for patch 46831619:37
patchbotNo data found for patch 41423219:37
*** klrmn has joined #openstack-swift19:38
timburkealso, when it bites, the failure is not at all obvious: http://logs.openstack.org/94/449394/3/check/gate-swift-dsvm-functional-ubuntu-xenial/cfa35d9/console.html.gz#_2017-05-19_02_59_21_62933119:41
tdasilvaanybody else seeing a lot of gerrit errors?19:46
timburkepatchbot certainly did :-)19:53
*** Sukhdev has quit IRC20:02
-openstackstatus- NOTICE: The Gerrit service on review.openstack.org is being restarted now to clear some excessive connection counts while we debug the intermittent request failures reported over the past few minutes20:06
notmynamekota_: timburke: tdasilva: so you think https://review.openstack.org/#/c/414232/ is a good idea? (regardless of code quality, it's good to have that feature in swift?)20:15
patchbotpatch 414232 - swift - Exclude containers for account quota20:15
timburkenotmyname: i'm still torn20:15
tdasilvanotmyname: hard to say, it is such a use-case specific feature...I think cbartz has a use case for this, but maybe we can ask him to discuss in one of the swift meetings ???20:17
tdasilvanotmyname: but it would be hard for me to tell him that no, he should not do that. so I'm ok supporting it, documenting and then it is up to deployers how they want to use it.20:18
notmynameyeah, I can understand that position. and that's why, like timburke, I'm torn. I don't want to tell anyone that their use case is invalid (it's not), and I understand the one given in the commit message20:19
notmynamebut that's not the same thing as wanting to commit to maintaining it forever20:19
notmynameaccount quotas are such a weird thing, given swift's eventual consistency on them, so adding more conditions doesn't seem like the best way to get an "allowed here but not there" sort of use20:20
notmynameif I had a customer asking for something similar, I'd probably recommend tracking quotas outside of swift itself20:21
notmynameanyway, that's why I'm torn on it20:21
notmynamebut the longer we don't say "no" on a patch, the harder it is to eventually say no. just because we've all spent that much more time on it (especially the author!)20:22
tdasilvawell...but what are you maintaining? I share the feeling of keeping users from shooting themselves in the foot, but you are always going to have some of that. operators are able to create 1-replica systems for example20:22
notmynamesure20:22
notmynameI mean maintaining the logic of the feature in the future20:22
notmynamejust like any other feature in swift20:22
tdasilvayeah yeah, that's what i mean. the logic of the feature is really not the hard part to maintain right20:23
timburke(indeed, with composite rings, we now have a perfectly valid use-case for one-replica rings)20:23
tdasilvait's more the: 'man I started using this thing, and I didn't know what I was doing, and now look what i got"20:23
notmynamesure, and I can't (with a straight face) argue against this because of additional complexity when we just landed composite rings? ;-)20:23
tdasilvaheh20:24
notmynamebut at the same time, we *should* argue against adding features that are best implemented outside of swift itelse20:24
tdasilvanotmyname: right, so back to that...honest question: why is it better to implement outside? don't you fall into the same issue?20:25
timburke...like having account quotas at all?20:25
tdasilvai mean, you are getting the data from swift to implement it, so you have the issue of eventual conssitency all the same20:25
notmynameI don't like having quotas in swift. :-)20:25
timburkemy point was more that by satisfying one use-case, we may be laying the groundwork for other interesting features that we haven't even thought of yet20:26
notmynameIMO quotas are much better implemented when they're tightly integrated with auth and billing20:26
tdasilvanotmyname: isn't keystone doing quotas?20:26
tdasilva:)20:26
notmynametimburke: definitely! those are the sorts of things that *should* be added to swift. the building blocks so that deployers can build cathedrals20:26
notmynametdasilva: well, they're talking about it a lot. and yes, I like that better :-)20:27
tdasilvatimburke: cough cough.. let's land symlinks ;)20:27
timburkelike https://review.openstack.org/#/c/342857, which can get you that scratch space20:27
patchbotpatch 342857 - swift - Add defaulter middleware20:27
timburkeyes! or symlinks! i need to find time to look at that again...20:27
tdasilvatimburke: just came across your 'data protection' gist the other day...20:28
timburketdasilva: yeah, that'd be *so* much happier with symlink-backed versioning. still gotta think harder about what to do for the expirer...20:30
timburke...and object names that are close to the length limit...20:32
*** pcaruana has quit IRC20:53
*** pcaruana has joined #openstack-swift20:53
mattoliverauMorning, just an FYI, wife is sick this morning so I'll be at meeting but might be somewhat distracted looking after Lucy at the same time.20:57
kota_good morning20:57
kota_mattoliverau: take care of your wife and daughter20:58
notmynamemattoliverau: no worries. we'll just get lucy to pick up a few patches20:58
*** m_kazuhiro has joined #openstack-swift20:58
notmynameswift team meeting time in #openstack-meeting20:59
*** klamath_ has joined #openstack-swift21:10
*** klamath has quit IRC21:10
*** pcaruana has quit IRC21:16
*** klamath has joined #openstack-swift21:23
*** seongsoocho_ has joined #openstack-swift21:24
*** cargonza_ has joined #openstack-swift21:24
*** Sukhdev has joined #openstack-swift21:25
*** jarbod___ has joined #openstack-swift21:26
*** mtreinish has quit IRC21:29
*** cargonza has quit IRC21:29
*** seongsoocho has quit IRC21:29
*** torgomatic has quit IRC21:29
*** adriant has quit IRC21:29
*** f0o has quit IRC21:29
*** dja has quit IRC21:29
*** jarbod has quit IRC21:29
*** klamath_ has quit IRC21:29
*** hoonetorg has quit IRC21:29
*** edausq has quit IRC21:29
*** seongsoocho_ is now known as seongsoocho21:29
*** cargonza_ is now known as cargonza21:29
*** torgomatic has joined #openstack-swift21:29
*** ChanServ sets mode: +v torgomatic21:29
*** f0o has joined #openstack-swift21:30
*** mtreinish has joined #openstack-swift21:30
*** dja has joined #openstack-swift21:30
*** hoonetorg has joined #openstack-swift21:30
*** edausq has joined #openstack-swift21:30
*** rcernin has quit IRC21:44
openstackgerritLingxian Kong proposed openstack/swift master: Write-affinity aware object deletion  https://review.openstack.org/47015821:44
*** lucasxu has quit IRC21:45
*** catintheroof has joined #openstack-swift21:47
kota_clayg: so the point is "once > k fragments are replaced with tombstones it's not possible to service the request [2]."22:02
kota_you said on the patch22:02
claygkota_: I recognize that (k + 1) * duplication won't *always* hit enough nodes to *guarantee* you would over-write enough fragments to prevent a stale read - but... realistically... those nodes probably have tombstones already... I still think it's not about tombstone propagation as much as "realistically sure if we remove this tombstone some other primaries have it"22:02
claygI think I'd need to draw a table to understand "replicas - (k + 1)" vs "(k + 1) * duplication"22:03
kota_ok, if that is. just m+1 is small enough?22:03
claygany number > 3 and < replicas is an improvement22:03
kota_currently (m+1) * dup we are pushing22:03
claygI don't know what the "perfect" answer is22:03
kota_yup, me too.22:04
claygI think the change says "(k + 1) * d" - where k is data frags?22:04
claygoh... wait22:04
kota_no m+122:04
claygyou're right "(m + 1) * d"22:04
kota_and m is the number of parity fragments22:05
claygso yeah, pretty good chance in the duplicated case that could hit well below the number needed to prevent stale read22:05
*** m_kazuhiro has quit IRC22:05
claygi still like that it's smaller22:05
claygmax(3, replicas / 2) maybe!?22:05
claygidk22:05
acolesrledisez: I'll try to catch you tomorrow in EU time to discuss that ssync/expired object bug some more22:06
kota_if *in design* duplicate case could hit stale read well, just (m + 1) would be small enough i felt22:06
claygrledisez: acoles: I think letting the reconstructor reconstruct is the best thing - make sure the fetch frags guy sends x-backend-replication header and make sure object server responds inspite of the metadata22:06
kota_if we want to prevent the stale read as possible, we should go to (replicas - k + 1)22:07
kota_always kill enough number of frags that is not decode-able22:07
kota_so i didn't find the *intended* desing yesterday22:08
acolesclayg: that would at least save us reasoning about the consistency corner cases that might arise from doing nothing22:08
claygacoles: i like i!22:09
clayg*it22:09
* kota_ is feeling (replicas - k + 1) is too many though22:09
*** klamath has quit IRC22:10
acolesclayg: would you vote for using x-backend-replication header or a new header e.g. x-ignore-delete-at22:10
claygkota_: I see what you're saying about (replicas - k + 1)22:10
claygkota_: I'm ok with that tho22:10
claygif later we decide for the duplicated case it's too expensive we can drop it down again22:11
claygit's a big improvement over what's there for ec duplciation = 1 IMHO22:11
clayglet's do it!  (?)22:11
claygacoles: ugh, not x-ignore-delete-at I don't think :\22:11
kota_kk22:11
claygsmaller surface area on the api I think22:12
claygbut w/e works22:13
*** Sukhdev has quit IRC22:20
kota_whooa???22:23
kota_once, I tried to change the number of nodes22:23
kota_the test says # of replicas = 6, # of part nodes = 6, but # of ec_ndata... 10!?22:24
acolesclayg: got iy22:24
acolesit*22:24
kota_weird statement...22:25
kota_it looks like misconsistency between testing storage policy and fabricated_ring22:27
kota_clayg: it seems like I need more time to fix it but I'll push the newer version (to change the number of primaries as (replicas - k + 1) with overwritten on the patch today22:28
* kota_ have to prepare breakfast for his kids22:29
*** itlinux has quit IRC22:31
*** chlong has quit IRC22:32
*** itlinux has joined #openstack-swift22:42
*** skudlik has quit IRC22:45
*** catintheroof has quit IRC22:46
*** vint_bra has quit IRC22:47
*** itlinux has quit IRC22:54
claygtimburke: where's that follow up with config number cleanup stuff - which i know have context for :)22:59
timburkeclayg: it's to do with kota_'s comments at https://review.openstack.org/#/c/302494/9/test/probe/test_db_replicator.py@8923:00
patchbotpatch 302494 - swift - Sync metadata in 'rsync_then_merge' in db_replicator23:00
timburkeiirc23:01
claygyeah i know - that's the context I have now have - don't have the patch tho...23:01
timburkeoh, gotcha. https://review.openstack.org/#/c/471613/23:01
patchbotpatch 471613 - swift - Use config_number method instead of node_id + 123:01
*** openstack has joined #openstack-swift23:14
openstackgerritClay Gerrard proposed openstack/swift master: Cleanup db replicator probetest  https://review.openstack.org/47195723:22
*** kei_yama has joined #openstack-swift23:29
*** chsc has quit IRC23:39
claygnotmyname: patch 470158 is shaping up pretty good - I'm not even sure it's ready already - need to look at it again real soon (tm)23:46
patchbothttps://review.openstack.org/#/c/470158/ - swift - Write-affinity aware object deletion23:46
notmynameclayg: yay!23:46
claygdoes anyone know the author's nick?23:47
notmynameI do not23:48
*** tonanhngo has quit IRC23:54
openstackgerritClay Gerrard proposed openstack/swift master: Limit number of revert tombstone SSYNC requests  https://review.openstack.org/43957223:58

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