Wednesday, 2018-01-17

*** bigdogstl has joined #openstack-swift00:03
*** bigdogstl has quit IRC00:09
timburkethinking about https://review.openstack.org/#/c/365371/ -- is it worth pointing out (in an UpgradeImpact, probably) that old proxies may have issues during a rolling upgrade?00:23
patchbotpatch 365371 - swift - Add support for data segments to SLO and Segmented...00:23
timburkei certainly don't think it's worth plumbing in a config option to disable the new feature until the upgrade completes (as we did for https://github.com/openstack/swift/commit/96a0e07)00:23
timburkethe closer comparison would be https://github.com/openstack/swift/commit/25d5e68 which doesn't even have the UpgradeImpact...00:23
*** bigdogstl has joined #openstack-swift00:26
openstackgerritClay Gerrard proposed openstack/swift master: DRY out tests until the stone bleeds  https://review.openstack.org/53450700:30
notmynamefirst pass of a 2.17.0 changelog done.00:41
openstackgerritJohn Dickinson proposed openstack/swift master: WIP  https://review.openstack.org/53452800:41
*** tovin07_ has joined #openstack-swift00:46
openstackgerritTim Burke proposed openstack/swift master: Add support for data segments to SLO and SegmentedIterable  https://review.openstack.org/36537100:48
*** tovin07_ has quit IRC01:00
*** tovin07 has quit IRC01:01
*** bigdogstl has quit IRC01:08
timburkeclayg: *grumble, grumble* http://logs.openstack.org/75/530175/6/check/swift-tox-py27/8099136/job-output.txt.gz#_2018-01-16_23_57_23_96885601:11
openstackgerritClay Gerrard proposed openstack/swift master: Keep object-updater stats logging consistent  https://review.openstack.org/53457901:11
claygtimburke: lol, no body!  :P01:12
timburkeyup01:13
claygI'll fully admit I only ran the unittests for the modules I though would be effected01:13
claygthat's gate!01:13
claygthanks01:14
clayg-            if resp.status_int // 100 != 2:01:15
clayg+            if resp.status_int // 100 != 2 and resp.body:01:15
claygtimburke: ^ ???01:15
claygcheating?01:15
*** tovin07 has joined #openstack-swift01:15
*** bigdogstl has joined #openstack-swift01:15
*** bigdogstl has quit IRC01:17
*** bigdogstl has joined #openstack-swift01:17
*** bigdogstl has quit IRC01:19
*** bigdogstl has joined #openstack-swift01:19
timburkeonly thing vaguely risky is that `if resp.body and resp.status_int // 100 != 2` has very different behavior...01:20
timburkebut you can totally have a 401 (or something) with an empty body (eg, because you issued a HEAD)01:21
claygsure... short-circut boolean is a thing tho... you just have to now .body is a property with a potentially expensive side effect :\01:21
timburkeso it doesn't feel much like cheating01:21
*** bigdogstl has quit IRC01:21
openstackgerritClay Gerrard proposed openstack/swift master: DRY out tests until the stone bleeds  https://review.openstack.org/53450701:22
kota_good morning01:24
claygkota_: timburke and i were working on the internal client 499 fix01:25
claygpatch patch 53017501:25
patchbothttps://review.openstack.org/#/c/530175/ - swift - Fix InternalClient to drain response body if the r...01:25
kota_yeah, i briefly looked at the irc logs01:26
kota_it looks like it got second +2?01:26
timburkekota_: おはよ01:26
kota_oh, but it failed at py27 gate01:26
kota_timburke: lol01:27
kota_timburke: おはよう, basic "good morning" needs the last "う"01:27
*** bigdogstl has joined #openstack-swift01:27
timburkebah! i was close. sorry. gotta hold it a little longer, yeah?01:28
kota_that shorter one looks much similar with baby words ;)01:29
clayg^ rofl01:30
timburkethat's about where i am :D01:30
openstackgerritMerged openstack/swift master: Update http with https  https://review.openstack.org/53411901:30
kota_does http://logs.openstack.org/75/530175/6/check/swift-tox-py27/8099136/job-output.txt.gz#_2018-01-16_23_57_23_968856 show us that we should fix a small minor point on the assertion, maybe?01:30
claygkota_: tim & I were discussing maybe just bothering to try and append the body if there *is* no body (timburke gave the very good example of a HEAD request)01:31
kota_the assertion said "Unexpected response: 503 Service Unavailable () != Unexpected response: 503 Service Unavailable "01:32
claygyeah, it was kind of a nice save - I hadn't acctually considered that not all errors will have a body01:32
kota_sounds good point, error on HEAD request will be no body?01:34
claygyeah... I *think* so?01:34
*** bigdogstl has quit IRC01:34
timburkeper https://tools.ietf.org/html/rfc7231#section-4.3.2 -- "The HEAD method is identical to GET except that the server MUST NOT send a message body in the response"01:35
kota_but anyway, i'm thinking it's safe to iterate app.iter because it will raise StopIteration immediately...01:35
timburkethough there's also a note: "A payload within a HEAD request message has no defined semantics; sending a payload body on a HEAD request might cause some existing implementations to reject the request."01:36
timburkeoh wait -- that was about requests anyway01:36
openstackgerritClay Gerrard proposed openstack/swift master: Send correct number of X-Delete-At-* headers  https://review.openstack.org/52454801:36
*** m_kazuhiro has joined #openstack-swift01:39
kota_let me look at the logs.01:39
kota_anyway, it looks like I have to update the patch for 1) fix the py27 error, 2) call close_if_possible for app iterator.01:40
kota_will do, sorry, i have another work in this morning, I'll do it in this afternoon.01:41
kota_ah...01:46
*** tovin07_ has joined #openstack-swift01:46
claygwell, let me just try fixing the and resp.body thing01:47
claygthen maybe this afternoon you can make any other needed changes or +201:47
kota_if unexpected response requires the resp.body in the new, I think the body drain in the above won't work well because iterate app_iter doesn't set the resp.body IIRC01:48
kota_so the resp.body will be empty, always.01:48
openstackgerritClay Gerrard proposed openstack/swift master: Fix InternalClient to drain response body if the request fails  https://review.openstack.org/53017501:49
kota_new patch set!?01:49
claygi just added the diff for the and resp.body fix01:50
claygwe only add the body to the log line if there is a body to add01:50
kota_oic, that was commented at the gerrit01:50
claygshould fix the test - everything else is mostly trying to solve the requirements outlined in the commit message01:50
kota_i'll try to check my understand on the resp.body specification.01:51
claygoh yeah... that's relevant https://github.com/openstack/swift/blob/master/swift/common/swob.py#L30001:55
*** SkyRocknRoll has joined #openstack-swift01:59
*** bigdogstl has joined #openstack-swift02:00
claygtimburke: good thought about moving resp = None02:01
*** bigdogstl has quit IRC02:06
m_kazuhirogood morning02:12
*** bigdogstl has joined #openstack-swift02:13
*** two_tired has joined #openstack-swift02:16
*** JimCheung has quit IRC02:38
*** gyee has quit IRC02:41
*** JimCheung has joined #openstack-swift02:57
*** JimCheung has quit IRC03:02
*** itlinux has joined #openstack-swift03:25
*** bigdogstl has quit IRC03:35
*** kei_yama has quit IRC03:43
*** kei_yama has joined #openstack-swift04:02
*** bigdogstl has joined #openstack-swift04:03
*** fishbone_ has quit IRC04:05
*** bigdogstl has quit IRC04:14
*** psachin has joined #openstack-swift04:31
*** psachin has quit IRC04:31
*** psachin has joined #openstack-swift04:33
*** bigdogstl has joined #openstack-swift04:34
*** m_kazuhiro_ has joined #openstack-swift04:34
*** m_kazuhiro has quit IRC04:37
*** bigdogstl has quit IRC04:40
*** bigdogstl has joined #openstack-swift04:43
*** m_kazuhiro_ has quit IRC04:46
*** m_kazuhiro has joined #openstack-swift04:47
*** two_tired has quit IRC04:47
*** bigdogstl has quit IRC04:47
*** links has joined #openstack-swift04:49
*** f0o has quit IRC04:52
*** f0o has joined #openstack-swift04:59
*** bigdogstl has joined #openstack-swift05:06
*** f0o has quit IRC05:11
*** bigdogstl has quit IRC05:12
kota_i got my misunderstanding at the internal client patch.05:13
*** f0o has joined #openstack-swift05:13
*** bigdogstl has joined #openstack-swift05:14
openstackgerritMerged openstack/swift feature/deep: Add copy method to ShardRange  https://review.openstack.org/53148605:15
openstackgerritMerged openstack/swift master: Add a note about the cost of COPY for setting metadata  https://review.openstack.org/53438905:15
*** m_kazuhiro has quit IRC05:17
*** chsc has joined #openstack-swift05:19
*** bigdogstl has quit IRC05:20
*** chsc has quit IRC05:28
openstackgerritMerged openstack/swift master: Let recon-cron work with conf.d  https://review.openstack.org/53269605:30
openstackgerritMerged openstack/swift master: expirer: unexpected responses don't warrant tracebacks  https://review.openstack.org/49653405:30
openstackgerritMerged openstack/swift master: Add tests for X-Backend-Clean-Expiring-Object-Queue true  https://review.openstack.org/53325405:30
openstackgerritMerged openstack/swift feature/deep: Define entries of shard range db row in one place  https://review.openstack.org/53148705:30
*** chsc has joined #openstack-swift05:35
*** bigdogstl has joined #openstack-swift05:38
*** JimCheung has joined #openstack-swift05:39
*** chsc has quit IRC05:41
*** bigdogstl has quit IRC05:43
*** JimCheung has quit IRC05:43
*** bigdogstl has joined #openstack-swift05:50
*** bigdogstl has quit IRC06:01
mattoliverauphew, /me was lost down a cloud HA bug rabbit hole that I hoped would only take me 1/2 a day so I could spend the arvo swifting.. and it's now it's 5pm.. so turned out more rabbit hole-y then I thought :(06:01
mattoliveraumaybe I can get in a review or something tonight to help move things along.06:02
kota_mattoliverau: take your time. a rabbit hole-y problem appears unexpectedly always.06:13
mattoliverauthat's true06:14
torgomaticI notice in our gate jobs that there's this swift-tox-func-post-as-copy. Since post_as_copy is now a no-op, could we kill off that job and save some test cycles?06:16
openstackgerritSamuel Merritt proposed openstack/swift master: Remove old post-as-copy leftovers from tests.  https://review.openstack.org/53463906:20
torgomaticlet's see what happens :)06:20
*** m_kazuhiro has joined #openstack-swift06:23
notmynametorgomatic: yeah, I think that would be ok06:24
mattoliverauso long as none of our stable branches need it. It should be ok. Otherwise we'd could filter out all braches but it.. but I'd need to go look... and currently my brain feels fired06:28
mattoliverau*fried06:28
openstackgerritKota Tsuyuzaki proposed openstack/swift master: Fix InternalClient to drain response body if the request fails  https://review.openstack.org/53017506:38
kota_timburke, clayg: just fix my typo clayg suggested at the old patch set. other changes all look good to me.06:39
kota_mattoliverau, notmyname, torgomatic: good catch, and I'm realizing to wonder if we would ought to backport zuul migration patch to stable branch?06:46
kota_i mean something around dc1c55c9a07c03fe85f4bcc52419a42d75ae30fa06:47
kota_https://github.com/openstack/swift/commit/dc1c55c9a07c03fe85f4bcc52419a42d75ae30fa06:47
kota_to enable zuul v3 job on stable branch.06:48
*** bigdogstl has joined #openstack-swift07:03
*** bigdogstl has quit IRC07:12
*** threestrands_ has quit IRC07:20
*** armaan has joined #openstack-swift07:22
*** kei_yama_ has joined #openstack-swift07:36
*** kei_yama has quit IRC07:38
*** armaan has quit IRC07:38
*** m_kazuhiro has quit IRC07:38
*** hseipp has joined #openstack-swift07:42
*** pcaruana has joined #openstack-swift07:48
*** pcaruana has quit IRC07:55
*** pcaruana has joined #openstack-swift07:55
*** hoonetorg has quit IRC08:10
*** bigdogstl has joined #openstack-swift08:12
*** geaaru has joined #openstack-swift08:17
*** gkadam has joined #openstack-swift08:21
*** bigdogstl has quit IRC08:21
*** hoonetorg has joined #openstack-swift08:26
*** cshastri has joined #openstack-swift08:29
*** tesseract has joined #openstack-swift08:29
*** kei_yama_ has quit IRC08:39
*** silor has joined #openstack-swift08:43
*** mvk has joined #openstack-swift08:44
*** rcernin has quit IRC08:45
*** psachin` has joined #openstack-swift08:53
acolesgood morning08:54
*** m_kazuhiro has joined #openstack-swift08:54
*** psachin has quit IRC08:54
*** cbartz has joined #openstack-swift09:00
*** tovin07 has quit IRC09:01
*** tovin07_ has quit IRC09:01
*** tovin07_ has joined #openstack-swift09:01
*** tovin07 has joined #openstack-swift09:01
*** StevenK has quit IRC09:02
openstackgerritguotao proposed openstack/swift master: Adjust the error response codes order  https://review.openstack.org/53469209:03
*** psachin` has quit IRC09:09
*** psachin has joined #openstack-swift09:13
*** StevenK has joined #openstack-swift09:17
*** bigdogstl has joined #openstack-swift09:19
openstackgerritKota Tsuyuzaki proposed openstack/swift feature/s3api: As a first step, let's skip the test if not s3api in the middleware  https://review.openstack.org/53470309:27
kota_acoles: morning09:28
*** bigdogstl has quit IRC09:30
*** cbartz has quit IRC09:31
*** cbartz has joined #openstack-swift09:34
openstackgerritAlistair Coles proposed openstack/swift master: DRY out tests until the stone bleeds  https://review.openstack.org/53450709:37
acoleskota_: o/09:40
*** rcernin has joined #openstack-swift09:40
*** SkyRocknRoll has quit IRC09:45
*** SkyRocknRoll has joined #openstack-swift09:47
*** tovin07_ has quit IRC09:53
*** mvk has quit IRC09:55
*** bigdogstl has joined #openstack-swift09:57
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Update object-expirer to use general task queue system  https://review.openstack.org/51738910:00
*** bigdogstl has quit IRC10:06
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Update object-expirer to use general task queue system  https://review.openstack.org/51738910:11
*** m_kazuhiro has quit IRC10:22
acolestimburke: thanks for moving those sharding patches along10:31
*** bigdogstl has joined #openstack-swift10:33
*** bigdogstl has quit IRC10:38
*** mvk has joined #openstack-swift10:43
*** tovin07_ has joined #openstack-swift11:02
*** tovin07_ has left #openstack-swift11:02
*** bigdogstl has joined #openstack-swift11:04
*** bigdogstl has quit IRC11:14
*** bigdogstl has joined #openstack-swift11:45
*** bigdogstl has quit IRC11:52
*** JimCheung has joined #openstack-swift12:03
openstackgerritMerged openstack/swift master: Send correct number of X-Delete-At-* headers  https://review.openstack.org/52454812:06
*** JimCheung has quit IRC12:08
*** bigdogstl has joined #openstack-swift12:13
*** rcernin has quit IRC12:14
*** bigdogstl has quit IRC12:29
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Add state and state_timestamp to ShardRange  https://review.openstack.org/53148812:31
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Set shard range state during sharding  https://review.openstack.org/53148912:31
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Don't attempt to merge root and shard listings in proxy  https://review.openstack.org/53260412:31
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Define singletons to represent min and max shard range bounds  https://review.openstack.org/53320012:31
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Simplify proxy-server getting sharded listings  https://review.openstack.org/53320112:31
openstackgerritAlistair Coles proposed openstack/swift feature/deep: only make single request for container listings  https://review.openstack.org/51275612:31
*** bigdogstl has joined #openstack-swift12:31
*** bigdogstl has quit IRC12:42
openstackgerritAlistair Coles proposed openstack/swift master: Preserve expiring object behaviour with old proxy-server  https://review.openstack.org/53474913:02
acolestimburke: torgomatic clayg: ^^ I am probably worrying too much but I think p 524548 breaks (very-)backwards compaatibility13:04
patchbothttps://review.openstack.org/#/c/524548/ - swift - Send correct number of X-Delete-At-* headers (MERGED)13:04
*** SkyRocknRoll has quit IRC13:28
*** bigdogstl has joined #openstack-swift13:29
*** silor has quit IRC13:32
*** bigdogstl has quit IRC13:40
notmynameacoles: in what way?13:56
acolesnotmyname: very old proxy servers don't send x-delete-at-container, so latest obj server won't create an expiring object record13:57
acolesvery old ~ Havana !13:58
acolesnotmyname: p 534749 is an alternative13:58
patchbothttps://review.openstack.org/#/c/534749/ - swift - Preserve expiring object behaviour with old proxy-...13:59
*** armaan has joined #openstack-swift14:03
*** bigdogstl has joined #openstack-swift14:09
*** SkyRocknRoll has joined #openstack-swift14:10
*** bigdogstl has quit IRC14:19
*** arunman has joined #openstack-swift14:31
*** bigdogstl has joined #openstack-swift14:35
*** JimCheung has joined #openstack-swift14:40
openstackgerritMerged openstack/swift master: Minor cleanup in monitoring doc.  https://review.openstack.org/53442614:43
*** JimCheung has quit IRC14:45
*** bigdogstl has quit IRC14:46
openstackgerritAlistair Coles proposed openstack/swift master: Don't make async_pendings during object expiration  https://review.openstack.org/53238314:47
openstackgerritAlistair Coles proposed openstack/swift master: check all nodes for async_pendings  https://review.openstack.org/53477414:47
acolesoops14:47
*** ianychoi has quit IRC14:48
*** ianychoi has joined #openstack-swift14:52
openstackgerritAlistair Coles proposed openstack/swift master: Don't make async_pendings during object expiration  https://review.openstack.org/53238314:57
*** itlinux has quit IRC15:07
openstackgerritAlistair Coles proposed openstack/swift master: check all nodes for async_pendings  https://review.openstack.org/53477415:09
*** bigdogstl has joined #openstack-swift15:10
*** links has quit IRC15:11
*** arunmani_ has joined #openstack-swift15:24
*** arunman has quit IRC15:25
*** bigdogstl has quit IRC15:32
*** bigdogstl has joined #openstack-swift15:40
*** bigdogstl has quit IRC15:45
*** arunmani_ has quit IRC15:48
*** arunmani_ has joined #openstack-swift15:48
*** arunmani_ has quit IRC15:53
*** itlinux has joined #openstack-swift15:57
*** silor has joined #openstack-swift16:00
*** two_tired has joined #openstack-swift16:02
*** itlinux_ has joined #openstack-swift16:04
*** itlinux has quit IRC16:06
*** two_tired has quit IRC16:08
openstackgerritAlistair Coles proposed openstack/swift master: Fix intermittent unit test failure  https://review.openstack.org/53482516:10
*** bigdogstl has joined #openstack-swift16:11
openstackgerritAlistair Coles proposed openstack/swift master: DRY out tests until the stone bleeds  https://review.openstack.org/53450716:12
*** bigdogstl has quit IRC16:21
*** silor has quit IRC16:27
*** silor has joined #openstack-swift16:28
*** chsc has joined #openstack-swift16:37
*** chsc has joined #openstack-swift16:37
*** gyee has joined #openstack-swift16:39
*** arunmani_ has joined #openstack-swift16:46
*** pcaruana has quit IRC16:46
*** bigdogstl has joined #openstack-swift16:50
*** bigdogstl has quit IRC16:55
*** silor has quit IRC16:55
*** silor has joined #openstack-swift16:55
openstackgerritMerged openstack/swift feature/deep: annotate_failure: preserve tracebacks  https://review.openstack.org/53445416:56
openstackgerritMerged openstack/swift feature/deep: Add more reasons to skip sharder probe tests  https://review.openstack.org/53114516:56
*** armaan has quit IRC16:56
notmynameacoles: after thinking on it during some meetings, I think it's probably something we should land (patch 53474917:02
acolesnotmyname: ok17:03
*** cbartz has quit IRC17:07
*** tesseract has quit IRC17:21
*** hseipp has quit IRC17:26
*** bigdogstl has joined #openstack-swift17:27
*** arunmani_ has quit IRC17:29
*** ukaynar has joined #openstack-swift17:31
*** JimCheung has joined #openstack-swift17:31
*** bigdogstl has quit IRC17:36
*** JimCheung has quit IRC17:37
*** gkadam has quit IRC17:37
*** zaitcev_ has joined #openstack-swift17:42
*** ChanServ sets mode: +v zaitcev_17:42
notmynameacoles: got delayed by YAM (yet another meeting)17:43
notmynameso I think we should land patch 534749 (or something that is functionally equivalent) because a two-year-old swift cluster isn't that old and I don't want rolling upgrades to lose expiry writes during that process17:44
patchbothttps://review.openstack.org/#/c/534749/ - swift - Preserve expiring object behaviour with old proxy-...17:44
notmynamebut I think the only major concern is what happens when there's mismatched versions in the cluster (ie during an upgrade)17:45
*** zaitcev has quit IRC17:46
acolesnotmyname: compatibility is with pre-Havana so c. 201317:48
acolesand yes concern is only when proxy is older than obj server17:48
notmynameoh17:48
notmynameI thought you said something about 2.7.0 somewhere17:49
notmynameI may have combined some memories of different conversations17:49
acolesnotmyname: nope 1.9.017:49
notmynameoh! I probably saw the .9.0 part and just *assumed* it started with a 2 ;-)17:50
acoleslol17:50
notmynameso we're talking about during the upgrade process for four-year-old cluster.17:50
notmynamein that case...17:50
notmynamecould we handle it in the release notes?17:50
notmynamewhat could we say?17:50
notmyname"if you upgrade to this version from pre-1.9.0, expiry won't work during the rolling upgrade"17:51
notmyname"...if you upgrade your storage nodes before the proxy nodes (which is what you should normally do anyway)17:51
acolesnotmyname: fwiw timburke has +2 on 53474917:52
timburke"... objects with expiration times set during the upgrade won't be scheduled for removal"?17:52
timburkeit's not that it *won't work at all*17:53
timburkeand really, it's not even "won't" it's "may not"17:53
timburkebut it *does* mean that you don't have a nice, cleanly defined window wherein you're affected. you may be finding not-properly-removed data for quite some time after your upgrade17:55
*** bigdogstl has joined #openstack-swift18:07
*** itlinux_ has quit IRC18:10
*** itlinux has joined #openstack-swift18:10
torgomaticacoles: You're right; it does. I'd managed to convince myself that it wasn't important since Swift 1.9.0 was so old, but I could easily be wrong about that.18:12
torgomaticI added a meeting agenda item to talk about checkpoint releases. It'd be nice to have those every couple of years so that we don't have an unbounded amount of backwards compatibility to think about.18:14
acolestorgomatic: havana is old enough that i don't have the t-shirt ;)18:14
*** ianychoi has quit IRC18:14
*** ianychoi has joined #openstack-swift18:15
openstackgerritMerged openstack/swift master: DRY out tests until the stone bleeds  https://review.openstack.org/53450718:15
*** bigdogstl has quit IRC18:16
*** bigdogstl has joined #openstack-swift18:22
*** bigdogstl has quit IRC18:31
*** bigdogstl has joined #openstack-swift18:39
*** __david has joined #openstack-swift18:40
openstackgerritSamuel Merritt proposed openstack/swift master: Don't make async_pendings during object expiration  https://review.openstack.org/53238318:40
*** openstackstatus has quit IRC18:40
*** openstackstatus has joined #openstack-swift18:42
*** ChanServ sets mode: +v openstackstatus18:42
*** psachin has quit IRC18:52
*** geaaru has quit IRC18:58
*** mvk has quit IRC19:02
openstackgerritTim Burke proposed openstack/python-swiftclient master: Revert "Add Constraints support"  https://review.openstack.org/53488119:03
openstackgerritTim Burke proposed openstack/python-swiftclient master: Revert "Add Constraints support"  https://review.openstack.org/53488119:14
*** bigdogst_ has joined #openstack-swift19:18
timburke^^^ seems to fix the client gate (which no one really noticed was busted because no one really submits client patches)19:19
*** armaan has joined #openstack-swift19:21
*** bigdogstl has quit IRC19:22
*** bigdogst_ has quit IRC19:26
*** bigdogstl has joined #openstack-swift19:31
*** bigdogstl has quit IRC19:36
*** silor has quit IRC19:43
*** bigdogstl has joined #openstack-swift19:48
openstackgerritSamuel Merritt proposed openstack/swift master: Preserve expiring object behaviour with old proxy-server  https://review.openstack.org/53474919:48
*** mvk has joined #openstack-swift19:50
timburkenotmyname: ok, i remember you saying that we had (some degree of) control over doc redirects -- how do i make http://docs.openstack.org/developer/swift/overview_object_versioning.html get me to https://docs.openstack.org/swift/latest/overview_object_versioning.html ?19:56
notmynametimburke: good question19:56
notmynameIIRC there's a top-level redirect definitions file we can use19:56
notmynamelet me see if I can find some doc docs19:56
timburkedoc doc doc doc19:57
notmynamehttps://docs.openstack.org/doc-contrib-guide/redirects.html19:57
notmynamemaybe? still reading19:57
*** joeljwright has joined #openstack-swift19:58
*** ChanServ sets mode: +v joeljwright19:58
notmynameyeah, I think that's how to do it19:59
*** bigdogstl has quit IRC19:59
*** cshastri has quit IRC20:06
*** gkadam has joined #openstack-swift20:10
*** ukaynar has quit IRC20:15
*** bigdogstl has joined #openstack-swift20:15
openstackgerritSamuel Merritt proposed openstack/swift master: Remove old post-as-copy leftovers from tests.  https://review.openstack.org/53463920:17
*** ukaynar has joined #openstack-swift20:19
*** bigdogstl has quit IRC20:28
*** geaaru has joined #openstack-swift20:30
openstackgerritTim Burke proposed openstack/swift master: internal_client: Don't retry when we expect the same reponse  https://review.openstack.org/53439920:37
*** corvus is now known as jeblair20:37
*** jeblair is now known as corvus20:37
openstackgerritTim Burke proposed openstack/swift master: Add container-reconciler to source doc tree  https://review.openstack.org/53494320:39
*** silor has joined #openstack-swift20:39
-openstackstatus- NOTICE: Zuul will be offline for a few minutes; existing changes will be re-enqueued; approvals during the downtime will need to be re-added.20:40
*** silor has quit IRC20:44
*** bigdogstl has joined #openstack-swift20:48
*** bigdogstl has quit IRC20:53
kota_good morning20:55
*** ukaynar has quit IRC20:55
notmynamehello kota_20:55
*** bigdogstl has joined #openstack-swift20:56
kota_hi notmyname20:56
*** m_kazuhiro has joined #openstack-swift20:56
notmynameclayg: acoles: tdasilva: cschwede: mattoliverau: kota_: m_kazuhiro: torgomatic: timburke: mathiasb: rledisez: just about meeting time courtesy ping20:59
mattoliverauTa20:59
mattoliverauMorning20:59
kota_o/21:00
m_kazuhiromorning21:00
notmynamemattoliverau: I got scared this morning. couldn't find my hotel confirmation for next week. (fortunately, I did)21:00
*** bigdogstl has quit IRC21:04
*** bigdogstl has joined #openstack-swift21:20
*** bigdogstl has quit IRC21:27
*** threestrands_ has joined #openstack-swift21:44
*** threestrands_ has quit IRC21:45
*** threestrands_ has joined #openstack-swift21:45
*** threestrands_ has quit IRC21:45
*** threestrands_ has joined #openstack-swift21:45
*** bigdogstl has joined #openstack-swift21:56
mattoliverauPhew, otherwise backpackers or a tent in a park :p21:59
joeljwrightnotmyname: if you have a second, I was working on a review for 478611 and I realised I've lost my ability to +2 because I had to change my username and email after leaving Sohonet21:59
openstackgerritSamuel Merritt proposed openstack/swift master: Improve object-updater's stats logging  https://review.openstack.org/53320721:59
kota_mattoliverau: sounds like a summer vacation21:59
kota_JK22:00
*** m_kazuhiro has quit IRC22:01
*** rcernin has joined #openstack-swift22:02
claygI think the 412 precondition failed sort of makes sense if you think of x-if-delete-at sort of like x-if-match?22:04
claygrledisez: I think getting off eventlet in the object server would be amazing22:04
claygrledisez: all eyes on zaitcev_22:04
claygacctually how is the EC PUT update thing going?  we fix that crazy headers non-sense?  there was a couple of blockers that came out of tdasilva's call that he setup - but I never looped back around (busy)22:05
timburkeclayg: sure? but it's not super useful, as the expirer -- 409 would be way more informative22:05
zaitcev_It's ready for reviews, except 1 thing22:05
claygit'd be great to have some traction on that going into the PTG - is anyone from redhat besides cschwede going to be there?22:05
zaitcev_Oh, did I miss the meeting22:05
joeljwrightzaitcev_: yeah, it just finished22:06
*** bigdogstl has quit IRC22:08
openstackgerritClay Gerrard proposed openstack/swift master: Reset state every iteration to avoid stale reference  https://review.openstack.org/53495722:09
*** bigdogstl has joined #openstack-swift22:11
openstackgerritTim Burke proposed openstack/swift master: object-server can 409 in response to x-if-delete-at  https://review.openstack.org/53495922:16
*** bigdogstl has quit IRC22:16
*** itlinux has quit IRC22:17
notmynamejoeljwright: go ahead and leave your +122:18
joeljwrightsure, no problem, I was going to +1 while I test more anyway22:19
joeljwrightnotmyname: I just noticed all the other options had gone22:19
joeljwright:)22:19
notmynamejoeljwright: FWIW your email is listed as a gmail one22:20
notmynamebut /msg me a different one and I'll set it22:20
notmynametimburke: FWIW joeljwright is having issues with his gerrit id, and I'm getting errors when I try to re-add him. treat his +1 as a +2 for now until we can resolve it with infra22:29
*** gkadam has quit IRC22:29
timburkeyeha, that was kinda gonna be my opinion regardless :-)22:29
notmynameheh, yeah :-)22:30
joeljwrighttimburke: notmyname: +1 (well, +2 really)22:30
joeljwright:)22:30
notmynamelol22:30
acolesgoodnight22:32
claygtimburke: oh.. a mock.side_effect = [503, Exception] sorta situation *would* demonstrate the bug22:32
joeljwrightgood night peeps22:34
joeljwrightnotmyname: timburke: thanks for the help with my gerrit user22:34
timburkegood night joeljwright22:34
*** joeljwright has quit IRC22:34
*** ukaynar has joined #openstack-swift22:38
*** ukaynar has quit IRC22:39
*** kei_yama has joined #openstack-swift23:02
rcerninping zaitcev_ if we are going to sync the rings,builder with scp because md5sum is different across all nodes (we dont know which is correct). We chosen the first one. Would that cause any outage in Swift? How long would it take before it would decrease I/O with around 200GB data in Swift?23:02
notmynameit could cause an outage (eg if you push a ring that's wildly different than the one used to place data)23:03
notmynamewhy do you think it will decrease IO?23:03
rcerninnotmyname: currently swift is throwing replicate errors because of the differend md5sum, as well we see cpu peaks on swift. mostly when it starts doing rsync.23:04
*** bigdogstl has joined #openstack-swift23:07
notmynameworst case, you push a wildy different ring and you lose availability of your data until replication moves everything back in place23:08
notmynamewell, that's not truly worst case. you could break your cluster more than that if you push a ring with a different part power or the wrong IPs in it or something23:09
notmynamercernin: are all of your rings different?23:09
notmynameie all the md5sums23:09
rcerninnotmyname: yes :(23:09
notmynameah23:09
notmynameI'm not gonna lie. you could be in a better situation23:10
notmynameso what to do?23:11
notmynamesome people prefer whiskey. I like tequila.23:11
notmyname;-)23:11
notmynamercernin: but in serousness, let's get you back on the happy path :-)23:12
notmynamehow were you planning to chose which ring to push to the other nodes?23:13
*** bigdogstl has quit IRC23:15
zaitcev_If only there was a tool that extracted the existing ring from *.ring.gz, then rcernin could use it to discern which builder file is the best match for the majority of the storage nodes.23:18
zaitcev_Or heck, just re-construct an approximation of a builder file23:18
rcerninnotmyname: it doesnt matter if they are all different.23:18
zaitcev_that's why I said majority23:18
notmynamezaitcev_: IIRC the builder does a pretty decent job of that23:18
rcerninso the possibility one would loose the data.23:19
zaitcev_well, you can construct the "least distance" metric and then find the closest builder23:19
openstackgerritClay Gerrard proposed openstack/swift master: Recenter builder test expectation around random variance  https://review.openstack.org/53297823:19
notmynamercernin: how many servers do you have the different rings on?23:19
*** saint_ has joined #openstack-swift23:20
rcerninzaitcev_: notmyname: recon --md5 output: http://paste.openstack.org/show/646637/23:21
notmynameso only 3 servers, but all rings are out of sync23:24
rcerninyes to my understanding of that output23:24
notmynamewere they built locally on the boxes? do you know how you got into this situation?23:24
rcernin3 servers, 2 servers doesn't match the third server md5sum23:24
rcerninnotmyname: most likely after replacing controller23:25
rcerninzaitcev_: ^^23:26
rcerninnotmyname: zaitcev_: https://bugzilla.redhat.com/show_bug.cgi?id=131086523:26
openstackbugzilla.redhat.com bug 1310865 in openstack-tripleo-heat-templates "Director might break Swift cluster when replacing / adding new nodes" [Unspecified,Closed: errata] - Assigned to cschwede23:26
notmynameis that the box where you built rings? (just guessing. there's not a "controller" component in swift, although it is used elsewhere in openstack projects)23:27
rcerninnotmyname: its tripleo, its the bug I sent I believe.23:28
rcerninnotmyname: with replacing the node, you break swift cluster.23:28
notmynamethat sounds bad23:29
openstackgerritClay Gerrard proposed openstack/swift master: Recenter builder test expectation around random variance  https://review.openstack.org/53297823:29
rcerninworkaround was to copy the *.ring.gz and *.builder to new node manually23:30
rcerninhow can we actually find the most closes builder?23:31
zaitcev_The old TripleO used to re-build the rings from scratch every time. That's why it needed to control the random seed.23:31
openstackgerritTim Burke proposed openstack/swift master: slo: Send ETag header in 206 responses  https://review.openstack.org/53332123:32
*** chsc has quit IRC23:32
zaitcev_rcernin: Since for your case *.builder used locally to produce *.ring.gz, you can just look at those on all 3 nodes by hand. Run "swift-ring-builder object.builder" with no other arguments, it shows you what's in the file.23:33
notmynameclayg: didn't you add a rebuild-builder-from-ring at some point? I didnt' see it in the ring builder usage text23:33
claygwrite_builder23:34
notmynamethanks23:34
notmynameoh, there it is :-)23:34
claygi totally want a script you can run on all the nodes to ls some datadirs and see what parts are there - then collect all those files and feed it into a script that builds a replica2part2dev table from what's on disk23:35
claygso want that23:35
claygit'd be a great ptg/hack-a-thon project23:35
claygso much fun23:35
notmynameseems like rcernin really wants that too ;-)23:35
claygit's an interesting problem because of over-replication23:36
timburkeand does some weighting by how many bytes are there...23:36
claygin your three replica ring you might have 4, 5, even maybe 14 different nodes that have *some* of a part23:36
claygtimburke: yeah counting up bytes used in each partition might be expensive - but you might get *something* out of suffix density (1 ls instead of a bazillian stats)23:37
notmynamercernin: but you've only got 200GB of data. I'm guessing that's a small percentage of your available storage?23:37
claygmaybe something with blk_stat would help - idk23:37
timburkemight need to be a two-pass sort of a thing, yeah23:38
claygscoff @ 200GB - just but a copy of every obect on every disk - done23:38
rcerninnotmyname: zaitcev_: the output of swift-ring-builder /etc/swift/object.builder is exactly same on all three nodes.23:39
notmynamercernin: (first cd to some different directory away from /etc/swift) if you `swift-ring-builder object.builder write_ring` from one of those builder files, does the resulting .ring.gz match any of the ones you have?23:42
zaitcev_Do we have the date in there somewhere? The last partition move time.23:47
zaitcev_So, they can never match23:47
rcerninnotmyname: swift-ring-builder object.builder generate the ring.gz files. Should it create it in . ?23:50
rcerninshould I check the /etc/swift/*.ring.gz?23:50
claygyeah i mean the whole md5 the rings thing came from a deployment pattern where you created *one* ring.gz and then shipped it out to the nodes - if you're deployment pattern is trying to have all the nodes deterministically create the same file on disk that's harder challenge isn't it.23:54
notmynamethe hope is that one of the md5sums you have deployed right now actually matches the output of the write_ring for the builder you have23:54
notmynameso my idea was to create a .ring.gz somewhere other that /etc/swift/ (ie don't overwrite anything) and then compare the new one with the output of swift-recon from earlier23:54
claygseems reasonable23:55
rcerninnotmyname: thats great idea actually but how can you create *.ring.gz?23:55
claygentirely possible all these files have the same replica2part2dev table and different md5's tho23:55
notmyname`cd /tmp && swift-ring-builder path/to/builder write_ring`23:56
notmynamethen you'll have a new .ring.gz in /tmp23:56
*** gyee has quit IRC23:58

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