Friday, 2015-06-26

*** annegentle has joined #openstack-swift00:00
*** petertr7_away is now known as petertr700:03
*** annegentle has quit IRC00:05
claygnotmyname: good answer on the object data cache question00:08
notmynamethanks00:08
claygnotmyname: you could have mentioned that you can turn off the fadvise thing with the config option to tune it for small objects00:09
notmynameyeah, I thought about it but left it out. I think it makes it extra confusing, especially considering how badly it's named00:10
claygnotmyname: your probably right00:10
notmynamebut yes, I specifically thought of our recent conversations on that very config as I was typing it ;-)00:10
clayg:)00:10
notmynameok, I need to grab some dinner before my next flight00:11
* notmyname out00:11
*** petertr7 is now known as petertr7_away00:13
pelusenotmyname, hey I know there's a youtube video out there (that you star in) but figured this was faster.  About how many devs and how long from T0 to get Swift developed and functioning in its first production cluster?00:29
peluseoh man00:30
pelusejust read the flight comment.... argh00:30
pelusefound it... https://www.youtube.com/watch?v=Dd7wmJCDh4w00:31
claygOMG he's so YOUNG!00:33
ctennisthat's what I was gonna say!00:33
claygbaby face00:34
claygha!  i look exactly the same -> https://www.youtube.com/watch?v=Dd7wmJCDh4w&feature=youtu.be&t=2900:35
openstackgerritClay Gerrard proposed openstack/swift: Make ssync_sender a better HTTP client  https://review.openstack.org/19545800:36
*** dmorita has joined #openstack-swift00:37
*** kota_ has joined #openstack-swift00:37
*** ChanServ sets mode: +v kota_00:37
kota_morning00:38
mattoliveraukota_: morning00:39
redboThe first commit to swift was Jun 28, 2009, but it was just me and chmouel.  gholt and chuck came in mid-august, notmyname in september, glange in november.  We started putting customers on it mid-May 2010.00:43
claygredbo: NICE!00:44
claygredbo: hey wouldn't happen to know how eventlet monkey patching works do you?00:44
redbonot really.  I looked at your gist and it was confusing.00:46
claygredbo: yeah it's sorta bullshit00:50
claygredbo: bet this kind of crap doesn't happen in go :'(00:50
redboI know, you just learn to live with however it works, or copy the whole source code into your repo and change the part you need.00:51
claygheh00:53
*** wbhuber has joined #openstack-swift00:54
openstackgerritMerged openstack/swift: go: restructure cmd/hummingbird.go  https://review.openstack.org/18893901:01
*** annegentle has joined #openstack-swift01:01
*** annegentle has quit IRC01:06
*** david-ly_ has joined #openstack-swift01:06
*** blmartin has joined #openstack-swift01:07
*** david-lyle has quit IRC01:09
*** wbhuber has quit IRC01:10
blmartinGood evening all01:15
blmartinmattoliverau, I posted all those bugfix pull requests last night before I caught some sleep. Have you had a chance to peruse them?01:18
mattoliverauI can't remember.. I think so.. Let me double check :)01:18
blmartinthanks! Sorry I kind of threw them into so many review and posted them at the same time. I'll try to even it out in the future01:19
mattoliverauMaybe not completely, I'll look at em now. And no stress, that's for all the hard work :)01:21
blmartinI stated on some of the container backend tests today. It looks like build_full_shard_trie is not used anywhere and is mostly replaced by build_shard_trie01:23
blmartindo you have grand designs for that function or is now a good time to trim the code?01:25
*** jasondotstar has joined #openstack-swift01:33
openstackgerritAlexandra Settle proposed openstack/swift: Correcting minor grammatical errors  https://review.openstack.org/19582501:35
mattoliverauasettle: ^ nice work :)01:36
asettleYES01:36
asettleWOO01:36
asettleWORKED01:36
*** gar has joined #openstack-swift01:41
*** gar has joined #openstack-swift01:41
*** jrichli has joined #openstack-swift01:42
*** amoturi has quit IRC01:45
*** jasondotstar has quit IRC01:59
kota_gerrit gate seems to get broken?02:00
kota_recent pushed patches failed at check-swift-dsvm-functional.02:02
*** doxavore has joined #openstack-swift02:02
*** aluria has quit IRC02:03
*** dosaboy has quit IRC02:04
*** wolsen has quit IRC02:05
*** wolsen has joined #openstack-swift02:05
*** dosaboy has joined #openstack-swift02:06
*** aluria has joined #openstack-swift02:06
*** jasondotstar has joined #openstack-swift02:10
asettleIt's not even working for me02:15
kota_oh, that's for docs.02:18
mattoliveraukota_: yeah, there has been a httplib2 CVE that limits the number of HTTP headers which is breaking things :(02:19
mattoliveraukota_: clay was looking into monkey patching the _MAX_HEADERS in the new httplib to solve the prob02:20
mattoliverausee scroll back if your interested02:20
kota_mattoliverau: makes me sense, thx, I'm looking at back log.02:21
asettleAh jeez there's a lot more jenkins checks than I'm used to.02:23
openstackgerritMatthew Oliver proposed openstack/swift-specs: Add Spec Lifecycle Rules to readme  https://review.openstack.org/19006602:24
*** annegentle has joined #openstack-swift02:24
kota_mattoliverau: nice02:25
mattoliveraukota_: ^^ Does that make more sense from your point of view?02:25
kota_mattoliverau: I'm looking at *now*02:25
kota_mattoliverau: perfect, thanks a lot!02:26
mattoliverauI still use the term patch in rule 4, but I think in that case it makes sense.02:26
mattoliveraukota_: no thank you :)02:26
kota_+2 added02:28
*** d0ugal has quit IRC02:29
*** d0ugal has joined #openstack-swift02:29
*** d0ugal is now known as Guest533502:30
mattoliveraukota_: thanks!02:30
*** wbhuber has joined #openstack-swift02:31
*** doxavore has quit IRC02:33
*** annegentle has quit IRC02:39
*** jasondotstar has quit IRC02:42
openstackgerritMerged openstack/swift-specs: Add Spec Lifecycle Rules to readme  https://review.openstack.org/19006602:42
kota_nice thiago, that absolutely land fast.02:44
*** lpabon has quit IRC02:47
*** asettle is now known as asettle-afk02:49
*** esker has joined #openstack-swift02:54
*** esker has quit IRC02:54
*** esker has joined #openstack-swift02:55
*** wbhuber has quit IRC02:56
mattoliverauthanks tdasilva and kota_ :)02:57
*** gyee has quit IRC02:58
*** annegentle has joined #openstack-swift03:40
*** asettle-afk is now known as asettle03:42
*** annegentle has quit IRC03:45
*** xnox has quit IRC03:47
*** sudorandom has quit IRC03:47
blmartinq03:47
blmartinwhoops, this isn't pdb03:47
*** CrackerJackMack has quit IRC03:48
*** david-ly_ is now known as david-lyle03:51
*** asettle has quit IRC03:52
*** sudorandom has joined #openstack-swift03:53
*** xnox has joined #openstack-swift03:53
*** CrackerJackMack has joined #openstack-swift03:54
charzmattoliverau04:36
mattoliveraucharz: yo04:37
*** jrichli has quit IRC04:37
blmartinoh man mattoliverau, you got to the change set before I could even post a comment. I applaud your speed04:38
charzmattoliverau: did you know where is the monkey patching (_MAX_HEADERS) for httplib?04:38
charzmattoliverau: is this https://review.openstack.org/#/c/195458/04:40
mattoliveraublmartin: what can I say, I'm obviously spying on you :P04:40
blmartinD:04:41
*** annegentle has joined #openstack-swift04:41
mattoliveraucharz: I'm not sure clayg has finished looking at it. I think he was having eventlet patching pain. knowing clayg he's probably silent in channel, not because he's sleeping but cause he's beating his head against the code.04:43
mattoliverauso no, that one isn't it.04:43
mattoliverauahh clayg sent an email to the powers that be: https://lists.secondlife.com/pipermail/eventletdev/2015-June/001213.html04:44
charzmattoliverau: got it, thanks.04:44
mattoliverauso that's probably where we are stuck atm04:45
blmartinGood luck and good night guys. I'm going to go catch some Zs.04:45
charzblmartin: nite04:46
*** blmartin has quit IRC04:46
*** annegentle has quit IRC04:46
*** SkyRocknRoll has joined #openstack-swift05:15
*** silor has joined #openstack-swift05:28
*** ppai has joined #openstack-swift05:38
hugokuoa question regarding to the fi of a partiton-disk. Is it by design to have same fi of any object's fa on the same partition-disk ?05:41
*** annegentle has joined #openstack-swift05:42
kota_hi, hugo, maybe, no?05:42
kota_all fi(s) depend on node index of the ring.05:43
kota_if the fa's partition is different each other, different disks should be assigned, AFAIK.05:44
hugokuokota_: k. same as my understand.05:45
hugokuothx05:45
hugokuoThat means which the particular fa of a fi must be on a disk which is calculated during build/rebalance ring. It's assigned at very beginning while the ring is created05:46
*** annegentle has quit IRC05:47
hugokuoso that the Example in this http://docs.openstack.org/developer/swift/overview_replication.html#hashes-pkl is impossible.   a43 - fi 2 , b23 - fi 1 . It's not gonna happen.05:48
kota_it seems failure case, right?05:51
kota_something like handoff05:51
charzkota_: make sense05:51
kota_but I'm still considering the case would be really occur.05:52
*** links has joined #openstack-swift05:55
hugokuokota_: unless inconsistency rings on different node05:55
kota_hugokuo: hmm... I guess handoff node can have this situation easily because...05:56
charzkota_: wait, I'm wrong. like hugokuo said, a43 - fi 2. that's impossible have another fi handoff will point to a43.05:57
kota_at PUT, node2 for a43 failed to connect, it will make a43 at handoff05:57
kota_and then05:57
kota_next PUT for b23, if node1 failed, it will make b23 fa at handoff05:58
kota_charz: exactly the node already had a43 doesn't allow to land another index fa for a43 unless the node is primary05:59
kota_charz: but this case is a43 and b23 objects are completely different, right?06:00
kota_charz: that's based on the path /account/container/object06:00
kota_s/that's/the hash is/06:01
hugokuothey're different object but place in same partition ID. And fi follows the device ID.06:03
kota_hugokuo: right06:04
kota_basically they are almost same fi in the primaries.06:05
kota_unless the objects are not placed handoffs06:05
hugokuohmm... if two primary devices are down, would it place two fi(different object but same partition) in same handoff node's partition06:06
hugokuoI think not tho06:06
hugokuolet me do some interesting test now06:06
kota_k, let me know someting found :)06:09
kota_it's interesting question06:09
hugokuokota_: confirmed. you are correct. The handoff device has the chance to include different fi of fa for different object. It happens while different primary device unavailable while the request be PUT in.06:20
hugokuointeresting06:20
hugokuoThat means ls06:21
kota_sounds good, thanks for your confirmation :)06:22
*** SkyRocknRoll has quit IRC06:28
*** Guest5335 is now known as d0ugal06:34
*** d0ugal has quit IRC06:34
*** d0ugal has joined #openstack-swift06:34
*** annegentle has joined #openstack-swift06:43
*** annegentle has quit IRC06:48
charzkota_: Which process will take care handoff of ec while one of primary devices is broken or unmount? reconstructor?06:57
kota_no, proxy only for now.06:58
kota_that's difference from replicated, right now.06:59
kota_proxy-server will make a handoff when primary device broken.07:00
charzkota_: ok, but that's only for new coming objects. right?07:00
kota_chars: yes07:00
kota_s/chars/charz/ sorry07:00
charzkota_: for existed objects that's no way to reconstruct fa to another handoff07:01
kota_charz: yes, at least kilo-stable.07:01
charzkota_: re-call it, that's already have a bug in lp.07:02
kota_maybe, clayg, acoles and peluse are working for that.07:02
kota_charz: i think so...07:03
*** proteusguy has quit IRC07:03
charzkota_: thank.07:03
*** proteusguy_ has joined #openstack-swift07:03
*** acoles_away is now known as acoles07:14
acolesgood morning07:15
kota_acoles: good morning :)07:16
acoleshey kota_ hows it going?07:16
cschwedeGood morning!07:16
kota_works is good but I still have cold a bit.07:17
kota_cschwede: morning07:17
acoleskota_: sorry to hear that, not nice07:17
acolescschwede: hi!07:17
kota_acoles: no worries07:17
*** bkopilov has quit IRC07:23
*** ppai has quit IRC07:29
*** rledisez has joined #openstack-swift07:38
*** proteusguy_ has quit IRC07:46
*** proteusguy has joined #openstack-swift07:46
*** therve has joined #openstack-swift07:49
therveHey07:49
therveclayg, Around? Looking at that httplib issue07:49
*** ppai has joined #openstack-swift08:12
*** kun_huang has joined #openstack-swift08:15
mattoliverauclayg: http://paste.openstack.org/show/321297/08:16
kun_huangcheck-swift-dsvm-functional failed (http://logs.openstack.org/66/195866/2/check/check-swift-dsvm-functional/bcaec5b/console.html)08:17
kun_huangit seems not a random failure08:17
kun_huangis anyone working on this?08:17
mattoliverautherve: ^^ here is a hacky way to get around the _MAXHEADERS eventlet issue (seeing as your looking at it). Its a mjor hack, but was just trying to figure out whats happening08:18
mattoliveraukun_huang: yeah we all know, there has been a patch to httplib which is breaking things08:18
mattoliveraukun_huang: we tried monkey_patching _MAXHEADERS but that doesn't work when using eventlet.. well in my testing. Hopefully we can get it fixed ASAP. Thanks for taking the time to report it :)08:20
mattoliveraukun_huang: unless your an eventlet expert then your welcome to take a shot :)08:21
mattoliverauK, I'm calling it a day, I'm suppose to take the wife out tonight, and I'll get in trouble if I dont stop working soon :P08:22
cschwedemattoliverau: have a nice evening & weekend!08:23
kun_huangmattoliverau: have a nice night08:23
thervemattoliverau, You could use eventlet.patcher.import_patched to make it a bit cleaner08:26
mattoliverautherve: cool, I know nothing about eventlet.. just playing with whats broken08:28
haypotherve: hi. have fun with monkey patching: https://lists.secondlife.com/pipermail/eventletdev/2015-June/001213.html "[Eventletdev] how to monkey patch the monkey patchers" :-)08:29
therveYeah...08:30
cschwedetherve: mattoliverau: nice, this looks like it works. based on the sample from clayg: http://paste.openstack.org/show/321301/08:31
*** ppai has quit IRC08:31
thervecschwede, +108:31
*** nexusz99 has joined #openstack-swift08:41
*** nexusz99 has quit IRC08:42
*** proteusguy has quit IRC08:42
*** annegentle has joined #openstack-swift08:44
mattoliveraucschwede: awesome, nice one!08:47
*** annegentle has quit IRC08:49
mattoliverauworks on my HTTPResponse(socket) tests too. Nice so looks like we have a work around.08:51
mattoliverauclayg: FYI - ^^ Read this section of scroll back08:52
mattoliverauK, I really need to go, wife wont wait much longer, it is friday night :) Have a great weekend all.08:53
*** joeljwright has joined #openstack-swift08:54
*** ChanServ sets mode: +v joeljwright08:54
kota_mattoliverau: great work, have a nice week end!08:54
cschwedei’m going to submit a patch for the headers thingy09:00
*** BAKfr has quit IRC09:01
*** BAKfr has joined #openstack-swift09:03
*** breitz has quit IRC09:05
*** breitz has joined #openstack-swift09:06
mattoliveraucschwede: awesome do it man! #onPhone #Don'tTellWife :P09:08
*** husanu8 has joined #openstack-swift09:09
*** jordanP has joined #openstack-swift09:10
openstackgerritChristian Schwede proposed openstack/swift: Increase httplib._MAXHEADERS to 1024  https://review.openstack.org/19594009:15
*** husanu8 has quit IRC09:18
*** kota_ has quit IRC09:19
*** dmorita has quit IRC09:20
*** husanu1 has joined #openstack-swift09:23
*** nexusz99 has joined #openstack-swift09:24
*** husanu1 has quit IRC09:28
*** nexusz99 has quit IRC09:29
*** nexusz99 has joined #openstack-swift09:33
kun_huangcschwede: failed again09:34
*** BAKfr has quit IRC09:34
kun_huanghttps://jenkins01.openstack.org/job/check-swift-dsvm-functional/495/console09:34
cschwedekun_huang: yes, but this time in the tests, the serverprocess are already ok. working on it09:34
cschwedeoh, that looks different than my local env. checking09:35
*** BAKfr has joined #openstack-swift09:39
nexusz99Q: there are only 2 options in policy_type in Storage Policies Configuration? (replication, erasure_code) then why we need policy name for duplicate policy_type? i think we only need 2 policy and share them other containers.09:40
*** annegentle has joined #openstack-swift09:45
openstackgerritChristian Schwede proposed openstack/swift: Increase httplib._MAXHEADERS to 1024  https://review.openstack.org/19594009:47
*** annegentle has quit IRC09:50
cschwedenexusz99: there might be more policy types in the future, that are neither replication nor erasure_code09:51
openstackgerritChristian Schwede proposed openstack/swift: Increase httplib._MAXHEADERS to 1024  https://review.openstack.org/19594009:55
mattoliveraunexusz99: you need policy_names because you still might use more then 1 of each type of policy, so yes duplicates. You may have a policy what will only place things in one region, you may have another that keeps more replicas then another, you may have a bunch of faster disks or ssds and all of which you can have a different policy for each of them. Or as cschwede mentioned, in the future there will most definitely be09:56
mattoliverau more policy_types.  Storage policies open up many more use cases in the same clluster.09:56
nexusz99cschwede: mattoliverau: thanks for reply. now i understand why we need policy_names. thank you!09:58
claygsys.modules['__patched_module_httplib'] is genious - kudos mattoliverau10:01
claygand cschwede & therve for the suggested cleanups10:01
cschwedeclayg: i have a wip patch up, https://review.openstack.org/#/c/195940/ - looks like the latest patchset fixes the issue10:05
mattoliverauclayg: ta, just following where you left off, got lost in eventlet code and debugged the hell out of it. And therve and cschwede for their fixing up my brute force results.. so team effort :)10:05
cschwedeclayg: hope the patch is ok for you, wanted to make some progress to unlock the gate10:05
claygcschwede: great work - i've got it checked out now10:06
cschwedeok, the gate-swift-tox-func already passed this time :) https://jenkins05.openstack.org/job/gate-swift-tox-func/882/console10:09
cschwedehope the rest succeeds also10:09
claygcschwede: omm i had to patch functests/swift_test_client too10:12
clayg:\10:12
clayglet me try again w/o10:12
cschwedewhat the… why did the commit message update used patchset #1, and not #2 as base? argh!10:14
cschwedeclayg: that was included in patchset #210:14
cschwedeclayg: let me fix that, once the test for patchset #2 finished on the gate10:14
claygyeah i love that no one even discusses dropping the test to only validate 99 user-metadata keys or somethign?10:19
clayg100 just isn't a lot10:19
claygmaybe we're all jaded - if you don't have to squint and point to count the zeros it's not a big number10:19
cschwede:/ https://jenkins04.openstack.org/job/check-swift-dsvm-functional/460/console10:23
openstackgerritChristian Schwede proposed openstack/swift: Increase httplib._MAXHEADERS to 1024  https://review.openstack.org/19594010:27
cschwedeah, that’s the patchset without the patched testclient. next try10:27
cschwedei’m still wondering why the commit msg update used patchset #1 as base, and not #2. got lost somehow...10:27
*** links has quit IRC10:36
openstackgerritCharles Hsu proposed openstack/swift: Fix reconstructor stats mssage.  https://review.openstack.org/19527510:46
*** nexusz99 has quit IRC10:48
*** nexusz99 has joined #openstack-swift10:49
*** geaaru has joined #openstack-swift10:54
*** mariusv has joined #openstack-swift11:00
*** mariusv has quit IRC11:00
*** mariusv has joined #openstack-swift11:00
*** mariusv has quit IRC11:01
*** links has joined #openstack-swift11:17
*** links has quit IRC11:19
*** nexusz99 has quit IRC11:19
*** delattec has quit IRC11:31
*** cdelatte has quit IRC11:31
*** ppai has joined #openstack-swift11:34
*** kei_yama has quit IRC11:36
*** aix has quit IRC11:41
*** annegentle has joined #openstack-swift11:47
*** annegentle has quit IRC11:52
*** aix has joined #openstack-swift12:08
*** proteusguy has joined #openstack-swift12:22
*** proteusguy_ has joined #openstack-swift12:24
*** proteusguy has quit IRC12:24
*** proteusguy_ has quit IRC12:24
openstackgerritChristian Schwede proposed openstack/swift: Increase httplib._MAXHEADERS to 128  https://review.openstack.org/19594012:26
*** doxavore has joined #openstack-swift12:28
*** aix has quit IRC12:28
*** ppai has quit IRC12:31
*** doxavore has quit IRC12:35
openstackgerritChristian Schwede proposed openstack/swift: Increase httplib._MAXHEADERS to 128  https://review.openstack.org/19594012:36
*** NM has joined #openstack-swift12:40
tdasilvagood morning!12:44
*** tellesnobrega has joined #openstack-swift12:45
*** thurloat_isgone is now known as thurloat12:59
*** tellesnobrega has quit IRC13:04
*** tellesnobrega has joined #openstack-swift13:08
*** jrichli has joined #openstack-swift13:10
*** cdelatte has joined #openstack-swift13:25
*** delattec has joined #openstack-swift13:25
cschwedeAll: patch 195940 fixes the issue on the gate. Some reviews needed though :)13:30
patchbotcschwede: https://review.openstack.org/#/c/195940/13:30
cschwedeclayg: notmyname: tdasilva: acoles: ^^^13:30
*** acampbell has joined #openstack-swift13:34
*** cazino has joined #openstack-swift13:38
acolescschwede: thanks, see my review, did i misunderstand?13:40
openstackgerritChristian Schwede proposed openstack/swift: Increase httplib._MAXHEADERS to 128  https://review.openstack.org/19594013:43
*** petertr7_away is now known as petertr713:46
tdasilvaoh, i see13:47
tdasilvaoops, wrong window13:47
*** annegentle has joined #openstack-swift13:48
cschwedeacoles: holy smoke! well, good to have you as a reviewer, thx! it’s fixed now13:49
tdasilvacschwede: are there any tests for checking the max number of headers?13:52
*** wbhuber has joined #openstack-swift13:52
*** annegentle has quit IRC13:53
cschwedetdasilva: well, no, at least not directly. but if you set the constraint to 100 you will notice that a lot of functests fail, even if you’re not using py2.7.9 or later13:53
cschwedei wanted to focus on unblocking the gate first, so my first approach were only two lines; the patch has grown a little bit ;)13:54
tdasilvaok13:54
*** annegentle has joined #openstack-swift13:55
acolescschwede: i haven't been following along - what changed to cause gate to fail?13:59
cschwedeacoles: python 2.6.9 and 3.2.6. there is a new limit of 100 headers in httplib13:59
*** proteusguy has joined #openstack-swift14:01
acolescschwede: oic. i have a vague memory of seeing this 100 limit hurt us before, but can't remember what the situation was14:01
acolescschwede: maybe it was in swiftclient. idk14:02
cschwedeacoles: i think so, it’s the same case for swiftclient. you can’t use it with more than ~ 90 metadata values; but since that’s the default of swift there won’t be many users that hit this limit14:03
acolesyup14:04
acolescschwede: did you consider making MAX_HEADER_COUNT = MAX_META_COUNT + N (e.g. N=38) rather than another configurable?14:07
acolesseems the two config options are coupled14:07
*** annegentle has quit IRC14:07
cschwedehmm, thought of it. do you mean to remove the operator setting completely? so MAX_HEADER_COUNT = MAX_META_COUNT + N is always set? or just a default if it is not set, and using a custom value if set?14:09
acoleswell, i was just concerned that human-error could set MAX_HEADER_COUNT=128 and  MAX_META_COUNT=15014:11
*** annegentle has joined #openstack-swift14:11
*** annegentle has quit IRC14:11
tdasilvaso maybe only make MAX_META_COUNT configurable and then calculate MAX_HEADER_COUNT internally14:12
tdasilvawith the constant 'N=38'?14:12
acolesand also that as swift adds new headers we may need the mAX_META_COUNT to increase but usersmay have configured the 'default' 12814:12
acolestdasilva: thats what i was wondering yes14:12
acolesthen we can increase N if needed in future without worrying that someone has actually configured a fixed value14:13
*** annegentle has joined #openstack-swift14:13
*** annegentle has quit IRC14:13
*** amoturi has joined #openstack-swift14:14
* acoles wonders what the worst case header count is for swift API14:14
peluseMooingLemur, FYI I'll be on shortly after lunch... will look for you then14:14
tdasilvaacoles, cschwede: seems like a good idea14:14
cschwedegood point. i’m also wondering about N14:14
cschwedeN=32?14:14
cschwedei somehow like 2^x numbers14:14
tdasilva:)14:14
acolescschwede: i wonder why ;)14:15
cschwedeso, in my tests the biggest amount of headers i saw was 104; that was 90 from meta_count plus some others. so if we select 32 as default we should be on the safe side, no?14:15
acolescschwede: seems reasonable.14:16
acolescschwede: tdasilva : hmmm, what about third party middleware headers?14:16
cschwedeforbid 3rd party middlewares  8)14:17
acolesyeah!14:17
*** joeljwright has quit IRC14:17
cschwedeso, a default of 32 plus the option to override this?14:17
tdasilvacschwede: well..the way for an op to override would be with MAX_META_COUNT, right?14:18
tdasilvacschwede: or do you mean for 3rd party middleware?14:18
acolesso ... max_header_count = MAX_META_COUNT + 32 + (configurable extra_header_count)14:18
acolesthat way you can't configure too low14:19
acolesbut you can increase14:19
acolesassuming we check that extra_header_count is > 014:19
cschwedethat sounds great!14:19
tdasilvabut then we are back at having two configurable options :/14:20
cschwedetdasilva: well, no? only one new, that is 0 by default, but can be increased only?14:21
acolestdasilva: yes. but at least one option cannot conflict with the other.14:21
acolestdasilva: cschwede we could even not document it :P14:22
cschwedethat will get back to us sometime14:22
acolesi was only kidding ;)14:23
tdasilvalol14:27
*** lcurtis has joined #openstack-swift14:29
*** blmartin has joined #openstack-swift14:40
*** lpabon has joined #openstack-swift14:41
blmartinGood Morning all14:41
*** jlhinson has joined #openstack-swift14:42
openstackgerritChristian Schwede proposed openstack/swift: Increase httplib._MAXHEADERS  https://review.openstack.org/19594014:43
cschwedeacoles: tdasilva: like this? I can add a test as a followup, but want to unbreak the gate first14:43
anteayadoes anyone know the status of the swift-dsvm-functional job?14:44
anteayaclayg notmyname mattoliverau ^^14:44
anteayaits status is about to change as per -qa14:44
*** jordanP has quit IRC14:45
cschwedeanteaya: we’re working on it, see patch 19594014:46
patchbotcschwede: https://review.openstack.org/#/c/195940/14:46
cschwedethe last patchset is hopefully the one that is going to be merged14:46
anteayacan someone join infra and share this information?14:47
cschwedei’ll do that14:47
anteayait is pertinent to the current conversation14:47
anteayathank you14:47
acolescschwede: +2'd14:49
tdasilvacschwede: +2+A14:49
acolescschwede: nice work14:49
cschwedeacoles: tdasilva: thx a lot!14:49
tdasilvacschwede: thank you!14:50
cschwedeanteaya: thanks for pinging us!15:04
anteayacschwede: thanks for the team work on that patch and being so responsive15:05
anteaya:)15:05
anteayalet's see if we can get all this sorted out15:05
cschwedeyes, hopefully that issue is solved real soon now. i’m keeping my fingers crossed for the running tests :)15:06
anteaya:)15:09
* anteaya also crosses her fingers15:09
*** DericHorn-HP has joined #openstack-swift15:23
*** zul has quit IRC15:28
*** zul has joined #openstack-swift15:33
*** ajiang has left #openstack-swift15:34
*** tellesnobrega has quit IRC15:34
*** minwoob_ has joined #openstack-swift15:35
*** minwoob has quit IRC15:36
*** DericHorn-HP has quit IRC15:36
*** tellesnobrega has joined #openstack-swift15:38
*** ajiang has joined #openstack-swift15:43
*** blmartin_ has joined #openstack-swift15:45
*** Fin1te has joined #openstack-swift15:46
cschwedewhat the? check-tempest-dsvm-full failed on the check job, but passed on the gate job?15:48
*** blmartin has quit IRC15:49
acoles:/15:50
cschwedeok, it was a timeout15:50
openstackgerritMinwoo Bae proposed openstack/swift: After the .durable has been written, fsync the directory.  https://review.openstack.org/18411315:50
*** amoturi has quit IRC15:55
*** zaitcev has joined #openstack-swift15:57
*** ChanServ sets mode: +v zaitcev15:57
*** gar1 has joined #openstack-swift15:57
*** gar has quit IRC15:57
* cschwede afk for ~ 2 hours, keep babysitting patch 195940 by mail16:04
patchbotcschwede: https://review.openstack.org/#/c/195940/16:04
*** Fin1te has quit IRC16:05
acolesnotmyname: clayg peluse tdasilva ^^ i gotta leave too can you keep an eye on this and recheck if necessary16:05
*** janonymous_ has joined #openstack-swift16:06
*** acoles is now known as acoles_away16:10
*** DericHorn-HP has joined #openstack-swift16:11
*** vinsh has joined #openstack-swift16:24
*** haypo has left #openstack-swift16:25
*** rledisez has quit IRC16:26
*** bill_az has joined #openstack-swift16:26
*** tellesnobrega has quit IRC16:28
*** nadeem has joined #openstack-swift16:28
openstackgerritMerged openstack/swift: Increase httplib._MAXHEADERS  https://review.openstack.org/19594016:28
*** nadeem has quit IRC16:28
*** nadeem has joined #openstack-swift16:29
*** gyee has joined #openstack-swift16:31
*** tellesnobrega has joined #openstack-swift16:35
*** petertr7 is now known as petertr7_away16:39
*** cazino has left #openstack-swift16:51
bill_azWe are experimenting with swift multi-site replication and have a few questions.  Is there anyone who has experience using this with multiple storage policies?17:02
*** tellesnobrega has quit IRC17:03
bill_aznotmyname:  I watched your "going global" video (https://www.youtube.com/watch?v=LpmBRqevuVU), and still have questions17:05
bill_aznotmyname:  We are experimenting with 2 regions, and 2 storage policies per region, default policy is local replication only, and policy 1 is replication across both regions17:06
bill_aznotemyname:  we see objects placed correctly to both regions, but the gets fail on remote site17:07
bill_aznotmyname:  call to container_info on remote site does not find container (or does not know storage policy for request) and so uses the default ring17:08
bill_aznotmyname:  is there detailed documentation available about how to configure global replication with different replication settings in several storage policies?17:09
cschwedeok, patch 195940 merged, gate is unstuck. time for the weekend :) thx everyone who helped out with that!17:14
patchbotcschwede: https://review.openstack.org/#/c/195940/17:14
anteayacould some swift type folks review this patch which removes a non-voting job from the swift gate, please? https://review.openstack.org/#/c/196134/117:21
anteayanon-voting jobs shouldn't be in the gate17:21
*** nexusz99 has joined #openstack-swift17:23
*** EmilienM is now known as EmilienM|brb17:25
*** petertr7_away is now known as petertr717:28
*** annegentle has joined #openstack-swift17:31
*** dhellmann has joined #openstack-swift17:33
*** annegentle has quit IRC17:36
*** amoturi has joined #openstack-swift17:39
*** elmiko has left #openstack-swift17:40
dhellmannI'm running into some failures with a swift functional test job on a change that shouldn't be related to swift at all. I can't seem to find actual tracebacks in the error log for the job, though. Is there anyone available familiar with the check-swift-dsvm-functional job who can give me a hand poking around?17:42
dhellmannpatch is https://review.openstack.org/#/c/195724/ and failure logs are http://logs.openstack.org/24/195724/1/check/check-swift-dsvm-functional/c60644b/logs/devstack-gate-post_test_hook.txt.gz17:43
MooingLemurpeluse: smae, I should be back between noon and 117:45
MooingLemurMST of course :P17:45
*** theoharr has joined #openstack-swift17:46
*** theoharr has quit IRC17:46
cschwededhellmann: that should be fixed by patch 195940 - could you recheck your patch?17:46
patchbotcschwede: https://review.openstack.org/#/c/195940/17:46
dhellmanncschwede: oh, cool, thanks!17:47
dhellmanncschwede: in the mean time, where would I have wanted to look for tracebacks from those test failures?17:47
dhellmannI saw the errors reported, but no tracebacks from the tests, in the console log17:48
cschwededhellmann: in the screen-s-proxy-log; in your case in http://logs.openstack.org/24/195724/1/check/check-swift-dsvm-functional/c60644b/logs/screen-s-proxy.txt.gz17:48
cschwededhellmann: „HTTPException: got more than 100 headers“17:49
dhellmanncschwede: ah, I was expecting to find the test runner reporting something more detailed about how the test had errored out (not necessarily that error about the headers, but something)17:49
cschwededhellmann: if it’s not a change in swift itself, but a swift job that fails it is most likely related to the proxy17:49
dhellmannI'll keep that in mind for next time, thanks17:50
cschwedeso in this case it was simply bad luck - python has a new limit of 100 headers, and there were tests that sent 104 headers17:50
cschwededhellmann: you’re welcome!17:50
*** EmilienM|brb is now known as EmilienM18:04
*** theoharr has joined #openstack-swift18:04
claygcschwede: great work18:09
cschwedeclayg: thx, but you deserve a big thx as well for figuring out what was broken!18:11
swifterdarrellhahaha, this reminds me of that one time when I had to go to the .h file and change #define SOME_ARBITRARY_LIMIT 1024  to   #define SOME_ARBITRARY_LIMIT 1025.  That was fun.  I miss that.18:11
*** DericHorn-HP has quit IRC18:12
*** DericHorn-HP has joined #openstack-swift18:13
*** theoharr has left #openstack-swift18:16
*** DericHorn-HP has quit IRC18:17
*** DericHorn-HP has joined #openstack-swift18:18
claygjrichli: my browser crashed - i'm sure i could dig it out of history - but if you have it handy - can you link me the unified crypto patch again?18:22
jrichliclayg: https://review.openstack.org/#/c/157907/18:26
*** nexusz99 has quit IRC18:27
*** minwoob_ has quit IRC18:27
claygmerci18:28
*** Fin1te has joined #openstack-swift18:29
*** minwoob has joined #openstack-swift18:29
jrichliclayg: things get sorta complicated in order to make functests happy :-)18:30
jrichlilike the "tail" concept we ended up going with because we couldn't be successful moving the metadata length checks18:31
claygjrichli: i thought that all worked now?18:31
*** annegentle has joined #openstack-swift18:32
jrichlithe solution you and I came up with fixed the functest we were working on, but broke another.  i will have to dig up the info.  its all recorded in the trello board18:32
claygcharz: lp bug #1468708 has me *very* confused18:35
openstackLaunchpad bug 1468708 in OpenStack Object Storage (swift) "ssync receiver get an odd SSYNC command and raise a exception" [Undecided,New] https://launchpad.net/bugs/146870818:35
*** annegentle has quit IRC18:37
*** geaaru has quit IRC18:39
openstackgerritMerged openstack/swift: Fixed Errors in Swift-Form Post middleware section rst.  https://review.openstack.org/19515418:40
*** silor1 has joined #openstack-swift18:47
*** silor has quit IRC18:48
*** annegentle has joined #openstack-swift18:51
*** Fin1te has quit IRC18:52
*** Fin1te has joined #openstack-swift19:02
claygwbhuber: you make any progress on the proxy failure test?  charz found another lp bug #1469094 that's very closely related19:03
openstackLaunchpad bug 1469094 in OpenStack Object Storage (swift) "Missing .durable files of FAs can cause rebuildable objects to be inaccessible" [High,Confirmed] https://launchpad.net/bugs/146909419:03
wbhuberclayg: i was about to unlink the disks before uploading the object, but slowly a progress overall.19:04
wbhuberperhaps charz and i can work together on the bug19:04
claygmaybe!19:05
claygminwoob: how are you doing today!?19:08
*** janonymous_ has quit IRC19:14
minwoobclayg: I submitted a patch set this morning for one that I'm trying to close up, and will be finishing up the duplicates test for the Reconstructor bug.19:18
minwoobclayg: As of now, I think I have things under control :)19:19
claygawesome!  let me know if you get stuck - or when you're ready for a review19:19
minwoobOkay. Will do.19:20
*** annegentle has quit IRC19:20
*** blmartin_ has quit IRC19:21
*** Fin1te has quit IRC19:24
jrichliclayg: I updated a trello card to explain why we went with the "tail" idea for metadata limits.  https://trello.com/c/0LUlx7Wr/26-fix-what-breaks-when-encrypter-sets-user-metadata-values-that-exceed-max-size19:25
*** linuxgeek_ has joined #openstack-swift19:26
claygtorgomatic: peluse: tdasilva: zaitcev: high priority fix for ec that's fairly trivial (IMHO) https://review.openstack.org/#/c/195457/19:31
openstackgerritClay Gerrard proposed openstack/swift: Fix ValueError in ssync_receiver  https://review.openstack.org/19545719:34
claygupdated commit to reference bug #19:34
zaitcevreloaded19:35
claygthere's some interplay of multiple issues - charz is going to have to keep digging - but that patch and it's dependency should allow him to get back on master19:35
zaitcev>>> int('')19:36
zaitcevValueError: invalid literal for int() with base 10: ''19:36
zaitcevurk19:36
claygsigh :'(19:36
zaitcevokay, I'm  not getting it. It's inside the if get():. Would both None and '' fall inside the if? I think so...19:37
claygthe valueerror in the bug log was just the disconnect - the *reason* for the disconnect was the ValueError invalid literal for int() with base 10: 'None' (which was on the other side of the connection)19:37
claygthe *reason* for the None - was the unmount19:37
zaitcevoh, it's a string that containes the word 'None19:37
clayg'None' does fall into the if - '' does not19:37
zaitcevholy mother how did that happen19:38
clayghow did what happen - the 'None'?19:38
claygputheader19:38
zaitcevoh19:38
claygand the missing test which the patch adds ;)19:38
redboI really wish wsgi defined what happens when a client disconnects early.19:39
zaitcevclayg: what about the line above? If there could be a connection without node index, could there be one without frag index? And what happens with that 'None'?19:40
claygthere should *not* be one without a frag index19:41
claygbut we shouldn't be putting 'None' on the wire19:41
claygzaitcev: why aren't you just reviewing this in gerrit ;)19:41
* clayg tires to find the line zaitcev is looking at19:41
zaitcevwell, whatever. it looks good19:42
claygzaitcev: no I think a '' default would be way better there - nice catch19:42
*** jrichli has quit IRC19:44
claygzaitcev: acctually - that would have blow up ssync on a replication policy (like you'd get if a primary device was 507'd)19:45
claygzaitcev: good fucking catch!19:45
openstackgerritClay Gerrard proposed openstack/swift: Make ssync_sender a better HTTP client  https://review.openstack.org/19545819:47
openstackgerritClay Gerrard proposed openstack/swift: Fix ValueError in ssync_receiver  https://review.openstack.org/19545719:47
claygtorgomatic: zaitcev: thanks - and sorry for the double work19:47
claygi'll ping you guys again when jenkins finishes with it - i want to rename the ssync "rsync" test to ssync "replicated" (doh!)_19:50
claygmight as well run probetests while I wait19:51
openstackgerritClay Gerrard proposed openstack/swift: Make ssync_sender a better HTTP client  https://review.openstack.org/19545819:51
openstackgerritClay Gerrard proposed openstack/swift: Fix ValueError in ssync_receiver  https://review.openstack.org/19545719:51
claygwhat is the deal with "colorama"19:55
zaitcevSCOTUS made gay marriage legal in all 50 today19:56
zaitcev(if that's what you mean)19:56
clayglol - no - that's not what I ment19:56
claygwhen i don't have colorama installed i see this trying to run nose -> /usr/local/lib/python2.7/dist-packages/nose/plugins/manager.py:395: RuntimeWarning: Unable to load plugin openstack.nose_plugin = openstack.nose_plugin:Openstack: colorama19:57
*** nexusz99 has joined #openstack-swift19:57
claygbut like - if I don't have it installed - why is it trying to load it?19:58
*** nexusz99 has quit IRC20:02
claygwho knew ->20:02
claygvagrant@saio:~$ sudo20:02
claygerr... sudo pip install --upgrade openstack.nose-plugin20:02
*** thurloat is now known as thurloat_isgone20:05
openstackgerritMinwoo Bae proposed openstack/swift: EC Reconstructor: Do not reconstruct existing fragments.  https://review.openstack.org/19327920:11
minwoobclayg: I went ahead and posted what I have for bug 1452553.20:13
openstackbug 1452553 in OpenStack Object Storage (swift) "don't rebuild existing fragments" [Critical,In progress] https://launchpad.net/bugs/1452553 - Assigned to Minwoo Bae (minwoob)20:13
claygminwoob: great!  what's not finished - can I help!20:14
minwoobclayg: It is similar to the test for the case where reconstruct_fa finds itself and does not fail.20:14
minwoobclayg: The one for duplicates is failing, though.20:14
claygminwoob: cool - i can look at it if that'd be helpful20:14
minwoobclayg: I'm still looking at it, but yeah, if you'd like to take a look at it as well, that would be great.20:15
openstackgerritClay Gerrard proposed openstack/swift: Make ssync_sender a better HTTP client  https://review.openstack.org/19545820:17
claygminwoob: i see test_reconstruct_fa_finds_duplicate_does_not_fail failing?20:19
minwoobYes -- that's the one that I just added.20:19
minwoobAnd everything else seems to be fine.20:20
claygidk - so rebuild should only need ec_ndata fragments20:21
claygminwoob: try this -> https://gist.github.com/clayg/eb77a5e69812b6ea25eb20:23
claygwell - that might not be what you were going for20:24
claygthat just changes the order20:24
claygthe broken_body is what's being rebuilt right?20:24
minwoobIn this test case, I don't think it matters which fragment is being rebuilt -- it's just to make sure that the reconstructor doesn't fail when there's 2 (or more) of the same fragment found.20:25
minwoobIt should not matter if that's even the fragment that needs to be rebuilt, right?20:25
minwoobAt least, that's what the code in the reconstructor itself checks for.20:26
*** amoturi has quit IRC20:27
minwoobTo be precise, actually, the reconstructor first checks whether the fragment to be rebuilt already exists, and then it checks for duplicates in the responses from the other nodes.20:27
clayghrmm... well if the frag_index == fi_to_rebuild it'll skip it for a different reason20:27
minwoobYeah.20:28
peluseMooingLemur, you there?20:33
minwoobclayg: In regards to the gist you posted above, it does work.20:35
claygminwoob: weeeeeelllll it *passes* - but does it test the code we're trying to test?20:37
*** annegentle has joined #openstack-swift20:37
openstackgerritMinwoo Bae proposed openstack/swift: EC Reconstructor: Do not reconstruct existing fragments.  https://review.openstack.org/19327920:38
minwoobclayg: It brings us closer, so I went ahead and updated it.20:39
MooingLemurpeluse: I am now.. it's been busier than expected :)20:39
peluseMooingLemur, BRB20:39
peluseMooingLemur, hey, you wanna call me real quick and we can catch up a bit more efficiently?20:48
MooingLemursure20:49
peluse480 554 368820:49
claygminwoob: no it's a *false* closeness ;)20:50
pelusebah, stupid IP phone isn't working20:50
MooingLemursilence20:50
MooingLemur:)20:50
peluse480 334 463020:50
claygminwoob: i think there's some pep8 failures too?20:58
minwoobclayg: The 79 characters issue ... I've fixed those.20:59
minwoobclayg: I'll upload the latest in a sec here.20:59
claygminwoob: ok - try this then -> https://gist.github.com/clayg/eb77a5e69812b6ea25eb20:59
claygafter pulling out the broken frag - we put some number of duplicates at the front of the connection list - it can't be more than parity - 1 because we can only tolerate parity missing and still rebuilt - and we're already missing the one we're rebuilding21:00
minwoobHmm... the case that I got working was for having 1 extra duplicate.21:02
minwoobIs it better to go with parity - 1?21:02
*** CaioBrentano has quit IRC21:03
claygminwoob: it's the maximum amount of failure that would tolerable - so it's a stronger test I think to push the limit - if this breaks having only duplicate would also likely break - i'm not sure if there is a strong correlation the other way21:04
claygminwoob: I didn't realize you had a fix21:04
claygminwoob: i'm sure whatever you cooked up with also be acceptable21:04
minwoobclayg: If that's the case, then I'll go ahead and test that.21:06
minwoobThe one you have does seem like a stronger test.21:09
openstackgerritMinwoo Bae proposed openstack/swift: EC Reconstructor: Do not reconstruct existing fragments.  https://review.openstack.org/19327921:12
*** theoharr has joined #openstack-swift21:16
claygtorgomatic: you around?21:16
torgomaticclayg: yeah21:17
claygsweet!21:17
claygi'm thinking about lp bug #145769121:18
openstackLaunchpad bug 1457691 in OpenStack Object Storage (swift) "Insufficient Fragments occurred on EC GET object" [High,Confirmed] https://launchpad.net/bugs/1457691 - Assigned to Bill Huber (wbhuber)21:18
claygand lp bug #146909421:18
openstackLaunchpad bug 1469094 in OpenStack Object Storage (swift) "Missing .durable files of FAs can cause rebuildable objects to be inaccessible" [High,Confirmed] https://launchpad.net/bugs/146909421:18
clayg... it's all related21:18
wbhuberclayg: how did you confirm that it's all related?21:18
claygI'm trying to think of what interfaces I might want to grow on the object-server21:18
claygwbhuber: well - i tried to convey this earlier - it's not like this was a "bug" that was missed21:19
claygwe *know* there's situations where we can have all the datas "out there" but the proxy doesn't know how to find them21:19
*** jlhinson has quit IRC21:22
anteayathis fix merged: https://review.openstack.org/#/c/19594021:23
anteayait is working to your satisfaction?21:23
*** petertr7 is now known as petertr7_away21:23
*** openstack has joined #openstack-swift21:26
torgomaticclayg: what if we had the object server convey, on GET response, the timestamps+indices of all the FAs it had *and* added a header on GET requests that would force it to a specific timestamp+index? Is that sufficient to get where you want to be?21:28
clayganteaya: wfm21:32
clayganteaya: that was *so* 4 hours ago21:33
anteayaclayg: heh21:33
anteayathanks21:33
claygtorgomatic: maybe?  I was worried when talking to a handoff we'd have to ask - what do you have - ok - can I have this one - and then later if it turns out the handoff is the *only* guy with index-2 and we asked him for index-3 :\21:33
*** DericHorn-HP has quit IRC21:34
claygtorgomatic: not that we can't ask the same guy for two things21:34
torgomaticclayg: we can run two connections to that same node though21:34
torgomaticheh, exactly21:34
claygtorgomatic: but you had one time said something like "x-if-frag-not-in-list: 0, 2, 4, 6"21:34
claygtorgomatic: where the response would be basically "sure, here's something useful"21:35
claygand in our loop we just say "while not_enough: ask_the_next_guy_for_something_useful"21:35
torgomaticclayg: yeah, that'd probably work better; that way we could have the fetchers all update a common set of what they found already21:35
claygtorgomatic: yeah definately!21:35
claygtorgomatic: ok - so but if the responses have "all the avaialables" (this is particuarlly useful when dealing with under-replicated durables)21:36
clayghow do you decide if you should ask next-primary/handoffs or go back to a node you already have a connection to?21:36
claygtorgomatic: I guess it's not super common for a node to have more than one frag21:37
claygtorgomatic: definately might have a non-durable frag and serve a stale timestamp - in that case you better go back to him21:37
openstackgerritMerged openstack/swift: Fix ValueError in ssync_receiver  https://review.openstack.org/19545721:38
claygtorgomatic: like instead of node_iter being a list you consume - we want a queue that you can stick things into21:38
torgomaticclayg: yeah, maybe we start off with continuing into the handoffs because it's easy, and if we end up with a non-trivial number of requests running out of object servers to try, then go write the backtracking code21:38
claygtorgomatic: ahhhh - good call21:39
claygminwoob: I think i'm still getting pep8 errors?21:39
*** annegentle has quit IRC21:39
torgomaticwe just have to make sure to log it and statsd it when it happens, so we can actually know something about its rate of occurrence21:40
minwoobclayg: I'll take a look at what's going on.21:40
*** annegentle has joined #openstack-swift21:40
claygtorgomatic: *another* good point!21:41
minwoobWhere do you see that?21:41
claygminwoob: locally21:41
claygminwoob: i ran vtox21:41
claygminwoob: maybe i'm confused21:41
claygminwoob: if you don't see pep8 errors - you can ignore me until jenkins makes the call21:41
claygminwoob: swift/obj/reconstructor.py:252:80: E501 line too long (88 > 79 characters)21:43
*** silor1 has quit IRC21:43
clayg^ I *think* i'm on the latest patch set?21:43
minwoobclayg: Patch set 6 is the latest. I fixed the ones that occured on one of the previous patches.21:43
minwoobclayg: Wait, that's in the reconstructor.21:44
minwoobYou're right. Let me go fix that.21:44
claygok21:44
openstackgerritGreg Lange proposed openstack/swift: go: add targeted replication  https://review.openstack.org/19625921:46
*** nexusz99 has joined #openstack-swift21:46
minwoobSo21:47
minwoobWhile running the test suite again just as a sanity check,21:47
minwoobwe should discuss how to handle the abort-reconstruct scenario, when an existing fragment is found.21:48
minwoobI think the best way to handle that would be to open up a new LP bug, and new gerrit review.21:48
minwoobSo that this current one can go ahead and get merged.21:48
minwoobI'll tackle it, but may have to do it when I get back.21:49
claygminwoob: sure np - please do see about opening a new bug - I think you might be able to just raise DiskFileError('found fragment') - let ssync skip it?21:49
openstackgerritMinwoo Bae proposed openstack/swift: EC Reconstructor: Do not reconstruct existing fragments.  https://review.openstack.org/19327921:50
*** nexusz99 has quit IRC21:51
minwoobclayg: Okay - Thanks for the head start.21:54
*** acampbell has quit IRC21:58
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873622:04
claygminwoob: patch set 7 wfm - well give folks the day to catch up - did you say you'll be out next week?22:13
*** NM has quit IRC22:14
minwoobclayg: I'm just about to step out of the office soon. I'll be back as usual on Monday, possibly online over the weekend.22:17
minwoobEither way, my next line item is the abort-reconstruction scenario.22:17
claygminwoob: oh - great - well have a nice weeked!22:17
claygminwoob: ok - please open a bug for it!22:17
minwoobclayg: Will do.22:17
claygminwoob: thanks again!22:18
minwoobclayg: Have a good weekend!22:18
*** DericHorn-HP has joined #openstack-swift22:18
*** DericHorn-HP has quit IRC22:19
*** DericHorn-HP has joined #openstack-swift22:40
*** annegentle has quit IRC22:41
*** nexusz99 has joined #openstack-swift22:58
*** annegentle has joined #openstack-swift23:01
*** nadeem has quit IRC23:02
*** nexusz99 has quit IRC23:02
*** lcurtis has quit IRC23:12
*** pgbridge has quit IRC23:12
*** ekarlso has quit IRC23:18
*** ekarlso has joined #openstack-swift23:18
*** annegentle has quit IRC23:19
*** gyee has quit IRC23:21
*** DericHorn-HP has quit IRC23:27
*** pberis has joined #openstack-swift23:33
*** pberis has quit IRC23:54
*** nadeem has joined #openstack-swift23:58
openstackgerritMerged openstack/swift: Add one more test for ssync_receiver  https://review.openstack.org/19451823:59

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