Wednesday, 2017-10-04

*** jistr has quit IRC00:00
*** jistr has joined #openstack-swift00:01
*** mat128 has quit IRC00:05
timburkewe should go land https://review.openstack.org/#/c/441520/ so i can stop cherry-picking it every time i want to work with a modern s3 client...00:09
patchbotpatch 441520 - swift - Use swift3's check_signature function00:09
*** lnxnut has joined #openstack-swift00:11
*** stewie925 has quit IRC00:12
openstackgerritTim Burke proposed openstack/swift master: Clean up SLO tests and docs  https://review.openstack.org/50930500:17
openstackgerritTim Burke proposed openstack/swift master: Let clients request heartbeats during SLO PUTs  https://review.openstack.org/50930600:17
kota_good morning00:20
*** lnxnut has quit IRC00:21
*** gyee has joined #openstack-swift00:36
*** itlinux has joined #openstack-swift00:36
mattoliveraukota_: morning00:39
kota_mattoliverau: o/00:50
*** itlinux has quit IRC00:58
*** cshastri has joined #openstack-swift01:05
*** vint_bra has quit IRC01:07
*** vint_bra has joined #openstack-swift01:07
*** mingyu has joined #openstack-swift01:07
*** lnxnut has joined #openstack-swift01:18
*** mingyu has quit IRC01:28
*** lnxnut has quit IRC01:29
*** mingyu has joined #openstack-swift01:31
*** itlinux has joined #openstack-swift01:35
*** vint_bra has quit IRC01:40
*** itlinux has quit IRC01:42
*** gyee has quit IRC01:47
*** tovin07_ has joined #openstack-swift01:51
openstackgerritMerged openstack/swift feature/deep: make broker get_shard_range_rows private  https://review.openstack.org/50911101:52
openstackgerritMerged openstack/swift feature/deep: minor follow up on cleave unit tests  https://review.openstack.org/50910901:52
openstackgerritMerged openstack/swift feature/deep: Use temp db and a rename for set_sharding_state  https://review.openstack.org/50600201:56
*** catintheroof has joined #openstack-swift02:03
*** catintheroof has quit IRC02:19
*** mingyu has quit IRC02:22
*** mingyu has joined #openstack-swift02:22
*** lnxnut has joined #openstack-swift02:26
*** catintheroof has joined #openstack-swift02:29
*** lnxnut has quit IRC02:36
zaitcevtorgomatic poke03:00
zaitcevtorgomatic: Where can I find the patch that allows to use linkat with in-memory tracking? Is there a review number?03:01
*** catintheroof has quit IRC03:09
*** itlinux has joined #openstack-swift03:23
*** abhitechie has quit IRC03:26
*** itlinux has quit IRC03:31
*** itlinux has joined #openstack-swift03:32
*** lnxnut has joined #openstack-swift03:34
*** gkadam has joined #openstack-swift03:39
*** itlinux has quit IRC03:41
*** lnxnut has quit IRC03:44
*** zaitcev has quit IRC03:44
*** kei_yama has quit IRC03:49
*** kei_yama has joined #openstack-swift04:03
*** alenavolk has joined #openstack-swift04:05
*** SkyRocknRoll has joined #openstack-swift04:12
*** SkyRocknRoll has quit IRC04:12
*** tristanC has quit IRC04:16
*** tristanC has joined #openstack-swift04:23
*** alenavolk has quit IRC04:28
*** alenavolk has joined #openstack-swift04:32
*** alenavolk has quit IRC04:33
*** alenavolk has joined #openstack-swift04:34
*** alenavolk has quit IRC04:34
*** alenavolk has joined #openstack-swift04:35
*** alenavolk has quit IRC04:35
*** alenavolk has joined #openstack-swift04:36
*** alenavolk has joined #openstack-swift04:37
*** alenavolk has quit IRC04:38
*** kei_yama has quit IRC04:39
*** wes_dillingham has quit IRC04:39
*** wes_dillingham has joined #openstack-swift04:40
*** lnxnut has joined #openstack-swift04:40
*** wes_dillingham has quit IRC04:41
*** wes_dillingham has joined #openstack-swift04:41
*** wes_dillingham has quit IRC04:41
*** wes_dillingham has joined #openstack-swift04:42
*** wes_dillingham has quit IRC04:42
*** wes_dillingham has joined #openstack-swift04:43
*** wes_dillingham has quit IRC04:43
*** wes_dillingham has joined #openstack-swift04:43
*** wes_dillingham has quit IRC04:44
*** wes_dillingham has joined #openstack-swift04:44
*** wes_dillingham has quit IRC04:45
*** wes_dillingham has joined #openstack-swift04:45
*** wes_dillingham has quit IRC04:45
*** wes_dillingham has joined #openstack-swift04:46
*** wes_dillingham has quit IRC04:46
*** wes_dillingham has joined #openstack-swift04:47
*** wes_dillingham has quit IRC04:47
*** wes_dillingham has joined #openstack-swift04:47
*** wes_dillingham has quit IRC04:48
*** wes_dillingham has joined #openstack-swift04:49
*** kei_yama has joined #openstack-swift04:57
*** lnxnut has quit IRC05:06
*** klrmn has joined #openstack-swift05:07
*** alenavolk has joined #openstack-swift05:11
*** psachin has joined #openstack-swift05:15
*** early has quit IRC05:16
*** early has joined #openstack-swift05:16
*** lnxnut has joined #openstack-swift05:33
*** abhitechie has joined #openstack-swift05:36
*** lnxnut has quit IRC05:37
openstackgerritHCLTech-SSW proposed openstack/swift master: Any inputs on the proposed fix.  https://review.openstack.org/50933805:41
*** wes_dillingham has quit IRC05:42
*** ChubYann has quit IRC05:42
*** f0o has quit IRC05:48
*** portante has quit IRC05:53
*** ndk- has quit IRC05:55
*** kei_yama has quit IRC06:03
*** oshritf has joined #openstack-swift06:10
*** abhitechie has quit IRC06:14
*** alenavolk has quit IRC06:20
*** portante has joined #openstack-swift06:21
*** ndk_ has joined #openstack-swift06:21
*** rcernin has joined #openstack-swift06:30
*** lnxnut has joined #openstack-swift06:34
*** pcaruana has joined #openstack-swift06:48
openstackgerritMatthew Oliver proposed openstack/swift feature/deep: unit tests for _misplaced_objects  https://review.openstack.org/50925606:52
mattoliverauacoles: ^^ thats just a rebase. I left some comments on the patchset before.. nothing really as a blocker.06:53
*** spectr has quit IRC06:54
*** spectr has joined #openstack-swift06:55
*** lnxnut has quit IRC06:57
mattoliverauSo whose around for the 0700 swift meeting?06:58
mahaticmattoliverau: o/07:00
mattoliverauacoles said he might make it. I wonder if kota_ is around07:00
psachinmattoliverau: o/07:00
kota_o/07:01
mattoliveraucool, well lets wait in the actual meeting channel then :)07:01
*** skudlik has joined #openstack-swift07:01
acolesgood morning07:01
mahaticacoles: morning!07:02
*** cbartz has joined #openstack-swift07:03
*** m_kazuhiro has joined #openstack-swift07:05
*** skudlik has quit IRC07:08
*** skudlik has joined #openstack-swift07:08
*** skudlik has left #openstack-swift07:09
*** cbartz has quit IRC07:10
*** geaaru has joined #openstack-swift07:12
*** tesseract has joined #openstack-swift07:16
*** kei_yama has joined #openstack-swift07:16
*** cbartz has joined #openstack-swift07:24
*** cbartz has quit IRC07:39
*** cbartz has joined #openstack-swift07:39
acolesmattoliverau: I have one quick question for you on sharding07:47
acolesmattoliverau: whenever we cleave or move misplaced objects, we should be moving deleted object rows, correct? we'll need the history of deletion in shard containers until reclaim age passes07:49
mattoliverauoh yeah, yes we should. I'm not sure it's currently doing that. We don't want to loose a potential delete.07:50
mattoliveraubut we don't need to propergate the deletes we make after deleting them after they moved.07:50
acolesmattoliverau: right, I thought so and have a bunch of TODOs in tests to confirm deleted rows are moved07:51
mattoliveraubut that could make misplaced objects harder, and to timburke07:51
mattoliveraus point07:51
acolesyou mean, when we delete the 'source' row in root container after that row has been moved to shard?07:51
mattoliverauif we mark misplaced object rows as deleted, will be pick them up the next cycle07:52
mattoliverauyeah07:52
acolesoic, yeah in the misplaced objects table that could be tricky07:53
acolesthe read only root object table should be ok though07:53
acoleswe only cleave once07:53
mattoliveraucurrently we only move objects where deleted=0 I think.. but then we may potentually miss a delete07:54
acolesI think that is correct based on my tests ^^07:54
mattoliverauyeah, readonly, not an issue, just misplaced in the holding table07:54
*** f0o|away has joined #openstack-swift07:54
acolesor misplaced outside of shard range in shard container07:54
mattoliverauyeah07:54
mattoliveraudo we need to add some mark to indicate moved objects, marking as deleted might not be enough.07:56
acolesso should we just remove the misplaced row once it has been relocated?07:56
mattoliverautrue07:56
mattoliverauso long as we're happy they've moved.. but in the current code, thats the assumption07:56
mattoliverauso yeah, that works :)07:56
acolesyep we need to be careful to know when rows have successfully moved, but once they have been they can be dropped I think07:57
acolesok thanks mattoliverau, have a good evening07:58
*** m_kazuhiro has quit IRC07:58
*** f0o|away is now known as f0o08:00
mattoliverauacoles: nps, thank you08:01
*** lnxnut has joined #openstack-swift08:28
*** lnxnut has quit IRC08:47
*** kei_yama has quit IRC08:50
*** lnxnut has joined #openstack-swift09:45
*** lnxnut has quit IRC09:56
openstackgerritAlistair Coles proposed openstack/swift feature/deep: unit tests for _misplaced_objects  https://review.openstack.org/50925610:01
*** tovin07_ has quit IRC10:06
*** klrmn has quit IRC10:32
*** mingyu has quit IRC10:34
*** tesseract has quit IRC10:40
*** abhitechie has joined #openstack-swift10:44
*** tesseract has joined #openstack-swift10:44
*** lnxnut has joined #openstack-swift10:53
*** spectr-RH has joined #openstack-swift10:59
*** mat128 has joined #openstack-swift11:00
*** abhitechie has quit IRC11:01
*** spectr has quit IRC11:02
*** lnxnut has quit IRC11:03
*** mjseger has joined #openstack-swift11:06
mjsegermattoliverau: are you around?11:06
*** cshastri has quit IRC11:11
mattoliveraumjseger: kinda, bit busy tonight so not really near a computer11:18
mjsegerok, np. we can talk tomorrow. looks like with 150M objects spread out over Ks of containers I'm seeing 1/2 the PUT rates. drilling deeper now.11:21
*** oshritf has quit IRC11:30
*** lnxnut has joined #openstack-swift12:00
*** lnxnut has quit IRC12:11
*** mjseger has quit IRC12:12
*** ianychoi has quit IRC12:25
*** ianychoi has joined #openstack-swift12:26
*** gkadam has quit IRC12:50
*** spectr-RH has quit IRC13:00
*** pcaruana has quit IRC13:02
*** lnxnut has joined #openstack-swift13:08
*** mat128 has quit IRC13:11
*** spectr-RH has joined #openstack-swift13:12
*** pcaruana has joined #openstack-swift13:15
*** spectr-RH has quit IRC13:16
*** spectr-RH has joined #openstack-swift13:16
*** lnxnut has quit IRC13:17
*** chlong_ has joined #openstack-swift13:22
*** lnxnut has joined #openstack-swift13:23
*** catintheroof has joined #openstack-swift13:24
*** mat128 has joined #openstack-swift13:27
*** mingyu has joined #openstack-swift13:34
*** mingyu has quit IRC13:39
*** wes_dillingham has joined #openstack-swift13:41
*** vint_bra has joined #openstack-swift14:09
*** d0ugal has quit IRC14:10
*** d0ugal has joined #openstack-swift14:13
*** d0ugal has quit IRC14:13
*** d0ugal has joined #openstack-swift14:13
*** pcaruana has quit IRC14:33
*** wes_dillingham has quit IRC14:34
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Include deleted objects when moving misplaced objects  https://review.openstack.org/50949614:36
*** spectr-RH has quit IRC14:41
*** spectr has joined #openstack-swift14:42
*** pcaruana has joined #openstack-swift14:45
*** wes_dillingham has joined #openstack-swift14:49
*** cbartz has quit IRC14:54
*** lnxnut_ has joined #openstack-swift14:56
*** lnxnut has quit IRC14:58
*** jrichli has quit IRC14:59
*** jrichli has joined #openstack-swift15:03
*** ChanServ sets mode: +v jrichli15:03
*** rcernin has quit IRC15:13
*** silor has joined #openstack-swift15:18
*** silor has quit IRC15:20
timburkegood morning15:21
*** thurloat has quit IRC15:22
*** silor has joined #openstack-swift15:24
*** wes_dillingham has quit IRC15:25
*** psachin has quit IRC15:25
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Eliminate _generate_object_list method  https://review.openstack.org/50950815:26
*** pcaruana has quit IRC15:28
*** chsc has joined #openstack-swift15:28
*** chsc has joined #openstack-swift15:28
*** tesseract has quit IRC15:29
*** gyee has joined #openstack-swift15:29
*** chsc has quit IRC15:34
*** guimaluf has joined #openstack-swift15:41
*** SkyRocknRoll has joined #openstack-swift16:26
openstackgerritTim Burke proposed openstack/swift feature/deep: Add shard_ranges table on failed writes, not reads  https://review.openstack.org/50835516:36
*** chsc has joined #openstack-swift16:39
*** chsc has joined #openstack-swift16:39
*** thurloat has joined #openstack-swift16:44
*** zaitcev has joined #openstack-swift16:45
*** ChanServ sets mode: +v zaitcev16:45
*** alenavolk has joined #openstack-swift16:48
*** thurloat has quit IRC16:49
notmynamegood morning16:56
guimalufhi guys, I'm checking my swift-recon output and there is nothing in the updater times metric... Is this normal? Acctualy most of my metrics are 017:02
notmyname(I haven't validated this, so only based on old memories...) are you running the swift-recon-cron?17:03
guimalufnotmyname, probably not... :(17:06
guimalufI run in my dev storage nodes but no metrics so far17:06
*** klrmn has joined #openstack-swift17:09
notmynameah. the cron is only for async pendings. https://docs.openstack.org/swift/latest/admin_guide.html#cluster-telemetry-and-monitoring17:09
guimaluf[updater_last_sweep] low: 0, high: 0, avg: 0.0, total: 0, Failed: 0.0%, no_result: 0, reported: 217:14
guimalufthis is even happening with 8 nodes17:15
guimalufhttp://10.1.1.139:6000/recon/updater/object: {'object_updater_sweep': 0.020959138870239258}17:20
guimalufseems like the value is just out of display range..?17:20
*** wes_dillingham has joined #openstack-swift17:20
guimalufhmmm I've data for containers!17:23
guimalufso what this metric does really means?17:24
*** SkyRocknRoll has quit IRC17:31
*** thurloat has joined #openstack-swift17:37
*** itlinux has joined #openstack-swift17:49
*** itlinux has quit IRC17:53
*** itlinux has joined #openstack-swift18:04
*** itlinux has quit IRC18:12
claygso.. the weird follow on patch to draw attention to the patch that has a -1 review and failed zuul?18:15
claygwe should probably have some sort of plan/delegation for who can review that patch - if they author is committed to finishing a solution that meets the design requirements of the maintainers it *would* be great to have something for delayed account un-delete that works!18:16
claygthis is patch 50780818:16
patchbothttps://review.openstack.org/#/c/507808/ - swift - Add ability to undelete an account.18:16
claygis... *today* bug triage day again?  do we do that *every* wednesday?18:17
clayg... i didn't put it on my calendar18:17
claygnotmyname: wait, this still says 9/27 - is there 2100 meeting today?18:17
claygi was going to put the undelete patch on there... maybe pete's PUT+POST patch?18:18
guimalufhi guys, what updater_sweep value really means on swift-recon output?18:25
*** chsc has quit IRC18:27
*** chsc has joined #openstack-swift18:29
notmynameclayg: yes! please update the meeting agenda18:38
claygguimaluf: cycle time of the last finished swift-*-updater daemon?18:40
claygthis is container or object?  container-updater is the thing that tells account db's how many objects/bytes - object-updater is the thing that makes async updates of object put/delete make their way into the container layer for sure (eventually)18:41
guimalufclayg, is it in seconds?18:41
claygoh... yeah units there are pretty stupid annoying - sometimes they're in minutes - i'd just have to look through the docs/code18:42
claygwhere have you been looking?18:42
guimalufcouldn't find any meaningful doc explaining swift-recon output18:42
guimaluflooking just at recon output18:43
guimalufhttp://192.168.55.109:6001/recon/updater/container: {'container_updater_sweep': 20.479094982147217}18:43
claygmight be in docs for "telemetry"?18:43
claygcode is here-ish -> https://github.com/openstack/swift/blob/master/swift/container/updater.py#L18418:44
claygmaybe something... https://docs.openstack.org/swift/latest/admin_guide.html#cluster-telemetry-and-monitoring18:45
guimalufI was following this telemetry guide18:46
guimalufbut no clear information inside :(18:46
claygif you can make a specific burn down of information that you had to track down a documention bug report would be super helpful - https://bugs.launchpad.net/swift (super double bonus points if you include any answers you were able to find along the way)18:46
claygok, well the code seems to be using the return value of time.time directly with no / 60 conversation - so you can safely assume it's in seconds18:47
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Don't lose timestamp info when moving misplaced objects  https://review.openstack.org/50958918:48
acolestimburke: mattoliverau  I've got a little chain of patches going on misplaced objects, this is the last ^^18:49
guimalufclayg, ty!18:49
*** ChubYann has joined #openstack-swift18:49
acolestimburke: mattoliverau we probably need a similar fix for cleave, but one step at a time ;) there is a TODO already in the tests to remind us18:50
*** geaaru has quit IRC18:50
timburkethanks acoles! thoughts on the comments for remove_objects? looks like we'll need to respin that patch anyway to fix the doc build18:51
claygguimaluf: np, pay me back by taking whatever notes you're gathering and thinking about how they could have been conveniently presented on that doc link I posted earlier - then put your thoughts/notes in a bug report.  I'd really appreciate your contribution to OpenStack swift!  Let me know if you bug into any other stumbling blocks - good luck.18:51
*** alenavolk has quit IRC18:58
openstackgerritTim Burke proposed openstack/swift master: Stop clearing params for account_autocreate responses  https://review.openstack.org/50959419:01
timburke^^^ looks like i tried too hard to not change tests in patch 44939419:02
patchbothttps://review.openstack.org/#/c/449394/ - swift - Move listing formatting out to proxy middleware (MERGED)19:02
guimalufclayg I'll take some time to do this!19:15
*** chlong_ has quit IRC19:16
openstackgerritJan Zerebecki proposed openstack/swift master: Fix swift-ring-builder set_weight with >1 device  https://review.openstack.org/50960619:32
openstackgerritSamuel Merritt proposed openstack/swift master: Step 1: make DiskFileWriters able to hang around  https://review.openstack.org/50960719:34
torgomaticzaitcev: https://review.openstack.org/50960719:34
patchbotpatch 509607 - swift - Step 1: make DiskFileWriters able to hang around19:34
zaitcevtorgomatic: thank you19:36
*** Sukhdev has joined #openstack-swift19:39
*** Sukhdev has quit IRC19:51
guimalufclayg, I hope to be able to fix this: https://bugs.launchpad.net/swift/+bug/1721380 :)20:01
openstackLaunchpad bug 1721380 in OpenStack Object Storage (swift) "Admin guide have unclear swift-recon output details" [Undecided,New]20:01
claygguimaluf: oh wow, that'd be even *better*  - if you've never built swift docs before you might find it's easier to get things up in going in a vm instead of trying to find somewhere you can install sphinx... https://docs.openstack.org/swift/latest/associated_projects.html#developer-tools20:31
*** mat128 has quit IRC20:53
kota_good morning20:59
notmynamegood morning20:59
notmynamemeeting time in #openstack-meeting21:00
*** m_kazuhiro has joined #openstack-swift21:00
notmynameclayg: torgomatic: acoles: ping21:01
acolestimburke: re remove_objects - great points, just replied on patch 50949621:15
patchbothttps://review.openstack.org/#/c/509496/ - swift (feature/deep) - Include deleted objects when moving misplaced objects21:15
acolestimburke: I will spin it tomorrow but more than happy if you want to fix my bads before then21:16
timburkeacoles: thanks. fwiw, a sqlite repl and `explain query plan` go a long way for me :-)21:16
*** silor has quit IRC21:25
*** wes_dillingham has quit IRC21:27
*** wes_dillingham has joined #openstack-swift21:27
*** wes_dillingham has quit IRC21:27
*** wes_dillingham has joined #openstack-swift21:28
*** wes_dillingham has quit IRC21:28
*** wes_dillingham has joined #openstack-swift21:30
*** wes_dillingham has quit IRC21:30
*** wes_dillingham has joined #openstack-swift21:30
*** wes_dillingham has quit IRC21:30
*** wes_dillingham has joined #openstack-swift21:32
*** wes_dillingham has quit IRC21:32
*** wes_dillingham has joined #openstack-swift21:33
*** wes_dillingham has quit IRC21:34
*** wes_dillingham has joined #openstack-swift21:35
*** wes_dillingham has quit IRC21:35
*** wes_dillingham has joined #openstack-swift21:37
*** wes_dillingham has quit IRC21:37
*** wes_dillingham has joined #openstack-swift21:37
*** wes_dillingham has quit IRC21:38
*** wes_dillingham has joined #openstack-swift21:39
*** wes_dillingham has quit IRC21:39
*** wes_dillingham has joined #openstack-swift21:40
*** wes_dillingham has quit IRC21:40
*** catintheroof has quit IRC21:41
* notmyname will be back online later today21:49
mattoliveraunotmyname: o/ hope all is well21:50
* kota_ is too, going to find his breakfast.21:50
notmynameyeah, nobody in the hospital or anything like that ...21:50
* rledisez will go to bed now…21:51
rledisezhave a good day or night all21:51
kota_good night rledisez!21:51
acolesrledisez: good night21:51
claygtimburke: I guess I should just out and say I think you should always return 202 with heartbeat=on21:52
claygyou can't turn on heartbeat=on w/o a code change - so make the code change more straight forward21:52
claygclients don't want no if statements21:52
acolestimburke: lol @ 'coward'21:53
clayg^ IMHO obvs.21:53
timburkeclayg: does the client know that it's talking to a new-enough cluster?21:54
*** m_kazuhiro has quit IRC21:54
torgomatictimburke: a client smart enough to check /info does21:55
timburkei know it *can* (i expose the yield_frequency in /info), but swiftclient (for example) generally avoids that extra request21:55
claygtimburke: that's an interesting point... but I don't think we should assume that a client *has* to support fallback21:55
clayglike level 0 client would be do the best right thing for the current version of swift - we want to make that as easy as possible to find out what is the best practices (i.e. use heartbeat=on, it's fun and easy!)21:56
clayglevel 1 client might try to understand that some old deployments of swift are crappy and try to make useful error messages "umm... idk if this old ass swift is going to work, someone said one time it didn't, you should tell your ops to upgrade"21:57
clayglevel 2 client maybe knows enought about swift internals to start to reason about a path to fallback and maintain compatibility - but YOU more than anyone know that is not for the feint of heart - there be dragons21:58
claygi'd love to just make the heartbeat 202 with status in the body be "what you get" but agree for backwards compat that's be probably pretty impossible :'(21:58
claygtimburke: I could be wrong!?21:59
timburkeyeah, see, the one client that i want to give support for this like *right now* -- swift3 -- is that level 2 guy, so that's mostly where i'm thinking :P21:59
not_meHi! I'm trying to understand why object-replication on one of geo replicated ring is slow.22:00
timburkei'd be OK with always flipping to 202. but the client will still need to look for 4XXs both as the primary status *and* in the body22:00
not_meobject-server 5436/5964 (91.15%) partitions replicated in 3900.03s (1.39/sec, 6m remaining)22:00
claygoic, ok - well if you already have the fallback code *written* it probably doesn't have to change even if you make the heartbeat behavior less unpredictable22:00
*** wes_dillingham has joined #openstack-swift22:00
not_meOur other rings replication takes around 100s to complete. object-server 32340/32340 (100.00%) partitions replicated in 102.91s (314.26/sec, 0s remaining)22:01
claygtimburke: oic... does it *have* to be that way?  maybe we should say heartbeat=on returns 202 with the status in the body?  I'm not sure that's better... but at least they could assume resp != 202 ==> ERROR TIME22:01
timburkesince auth comes before slo, i'ma say yes, it has to be that way22:02
not_meI'm unsure where to look at this point. 1 partition/second seems extremely slow.22:02
claygnot_me: sounds like that one server is doing more actual work (moving bytes) todo?  or it's gummed up on a slow disk...22:02
claygtimburke: good point about auth!22:03
claygtimburke: errors can come from *anywhere* - they must check the status22:03
timburkemaybe it's worth it to have status != 202 -> error, but i'm also not real happy with the idea that one-and-only-one status code can be success22:04
not_meAll the nodes in this ring takes between 5000 and 9000s to complete their object-replication pass. There are only 18 nodes in this ring and 100 devices.22:04
timburkei could go either way. maybe it'd be simpler to always 20222:05
claygi just think people writing clients are going to tend towards making it work the one time they tested it - so keeping behavior consistent leads to less client bugs (and less client authors made an un-deterministic behavior in the swift api)22:05
not_meobject.builder, build version 23422:05
not_me16384 partitions, 9.000000 replicas, 9 regions, 18 zones, 100 devices, 0.07 balance, 100.00 dispersion22:05
claygtimburke: maybe i'm looking for you to give a good reason it *should* be variable?  I had assumed it had something to do with "looks more like resp w/o heartbeat=on" - which to me sounded like a recipe for trouble - what's the info I'm missing?22:06
claygnot_me: have you read this section on counting handoff parititons on geo clusters?  https://docs.openstack.org/swift/latest/admin_guide.html#checking-handoff-partition-distribution22:07
not_meThe weird part is that I can't see any actual data being moved. The replication pass seems to be wasting its time checking very slowly, without having to transfer anything22:07
not_meI haven't, reading now!22:08
claygare the concurrency settings consistent across the configs?  can you turn on debug logging and check timing info on REPLICATE requests?22:08
claygnot_me: something like this might help too -> https://gist.github.com/clayg/5d3b3ca13dea15f6a48efaa3cea92d7d22:09
claygbut... idk... iostat might be your best bet - are the disks on that node under heavy utilization?  or worse lots of await for far to few iops?  maybe check smartctl22:10
not_meWhat do you mean by concurrency settings?22:25
not_me[object-replicator]22:27
not_me concurrency = x22:27
not_meright?22:27
claygyeah I think that's the big one... it can have a big impact on the number of disk/parts that are "working"22:35
*** wes_dillingham has quit IRC23:05
*** wes_dillingham has joined #openstack-swift23:12
*** mingyu has joined #openstack-swift23:16
*** vint_bra has quit IRC23:17
*** vint_bra has joined #openstack-swift23:17
*** vint_bra has quit IRC23:21
*** kei_yama has joined #openstack-swift23:26
*** chsc has quit IRC23:32
* notmyname back23:51

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