Tuesday, 2018-03-20

*** germs has joined #openstack-swift00:01
*** germs has quit IRC00:01
*** germs has joined #openstack-swift00:01
openstackgerritMerged openstack/swift master: Support -d <devs> and -p <partitions> in DB replicators.  https://review.openstack.org/54862800:04
openstackgerritMerged openstack/swift feature/deep: container replicator _in_sync should consider deleted shard ranges  https://review.openstack.org/55387500:04
openstackgerritMerged openstack/swift feature/deep: Pass existing ranges to ContainerBroker._find_shard_ranges  https://review.openstack.org/55431000:04
openstackgerritMerged openstack/swift master: Use state when you have it  https://review.openstack.org/55392700:05
*** germs has quit IRC00:05
*** itlinux has joined #openstack-swift00:23
*** tovin07_ has joined #openstack-swift00:45
*** lifeless_ has joined #openstack-swift00:46
*** lifeless has quit IRC00:46
*** tovin07_ has quit IRC00:48
*** tovin07_ has joined #openstack-swift00:49
*** itlinux has quit IRC00:51
*** cshastri has joined #openstack-swift00:59
*** tovin07_ has quit IRC01:29
*** tovin07_ has joined #openstack-swift01:29
hugokuo  Swift does need some ways to throttle the bandwidth and diskIO for all consistency workers(auditor, replicator and reconstructor).  There's a serious problem from operator's angle of view. While there's more and more data in the cluster, consistency worker does its job pretty hard on disks. That brings the disk utilization up to 100%.01:40
hugokuoThen the new incoming requests could be affected.01:41
mattoliverauacoles: lol, long live the composter :P01:42
mattoliverauhugokuo: there is the ionice options etc01:42
mattoliverauso you can give more precidence to user traffic01:43
hugokuoI remember that now. It's worth to give it a try. I didn't use that before.  Not sure of efficiency with ionice.01:44
DHEbesides the existing io priority system, you could use control groups to limit total disk IO...01:48
openstackgerritMerged openstack/swift feature/deep: Add auto_shard option to enable or disable leader behaviour  https://review.openstack.org/55378101:59
*** germs has joined #openstack-swift02:02
*** germs has quit IRC02:06
*** wes_dillingham has quit IRC02:19
*** links has joined #openstack-swift02:40
*** itlinux has joined #openstack-swift02:42
*** psachin has joined #openstack-swift03:02
*** bkopilov has quit IRC03:08
*** cshastri has quit IRC03:16
*** cshastri has joined #openstack-swift03:31
*** kei_yama has quit IRC03:44
*** itlinux has quit IRC03:49
*** kei_yama has joined #openstack-swift04:01
*** germs has joined #openstack-swift04:03
*** germs has quit IRC04:03
*** germs has joined #openstack-swift04:03
*** germs has quit IRC04:07
*** m_kazuhiro has joined #openstack-swift04:15
m_kazuhirogood morning04:16
*** armaan has quit IRC04:17
*** armaan has joined #openstack-swift04:18
*** armaan has quit IRC04:25
*** armaan has joined #openstack-swift04:26
*** bkopilov has joined #openstack-swift04:41
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Refactor tempurl functional test's try-finally  https://review.openstack.org/55441204:56
*** armaan has quit IRC05:31
*** armaan has joined #openstack-swift05:31
*** armaan has quit IRC05:53
*** armaan has joined #openstack-swift05:54
*** armaan has quit IRC06:02
*** germs has joined #openstack-swift06:04
*** germs has quit IRC06:08
*** psachin has quit IRC06:27
openstackgerritMerged openstack/swift master: Encapsulate some general utility in utils  https://review.openstack.org/55392806:45
*** psachin has joined #openstack-swift06:47
*** neonpastor has joined #openstack-swift07:01
*** Supun has joined #openstack-swift07:08
*** d0ugal has joined #openstack-swift07:12
*** d0ugal has quit IRC07:12
*** d0ugal has joined #openstack-swift07:12
*** d0ugal has quit IRC07:21
*** rcernin has quit IRC07:23
*** rcernin has joined #openstack-swift07:24
*** rcernin has quit IRC07:24
*** armaan has joined #openstack-swift07:25
*** tovin07 has joined #openstack-swift07:31
*** pcaruana has joined #openstack-swift07:34
*** Supun has quit IRC07:45
*** m_kazuhiro has quit IRC07:48
*** hseipp has joined #openstack-swift07:48
*** d0ugal has joined #openstack-swift07:49
*** tesseract has joined #openstack-swift08:00
*** armaan has quit IRC08:02
*** germs has joined #openstack-swift08:05
*** germs has quit IRC08:05
*** germs has joined #openstack-swift08:05
*** Supun has joined #openstack-swift08:05
*** m_kazuhiro has joined #openstack-swift08:05
*** germs has quit IRC08:08
*** armaan has joined #openstack-swift08:13
*** gkadam has joined #openstack-swift08:22
*** _alastor_ has quit IRC08:30
*** _alastor_ has joined #openstack-swift08:31
acolesgood morning08:31
m_kazuhiroacoles: good morning08:32
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Add object-expirer new mode to execute tasks from general task queue  https://review.openstack.org/51738908:32
*** geaaru has joined #openstack-swift08:36
*** armaan has quit IRC08:43
*** armaan has joined #openstack-swift08:43
acolesm_kazuhiro: o/08:44
*** d0ugal has quit IRC09:02
*** jiaopengju_ is now known as jiaopengju09:02
openstackgerritKazuhiro MIYAHARA proposed openstack/swift master: Refactor tempurl functional test's try-finally  https://review.openstack.org/55441209:03
*** cbartz has joined #openstack-swift09:07
*** _glb has quit IRC09:30
*** glb has joined #openstack-swift09:31
*** armaan has quit IRC09:38
*** armaan has joined #openstack-swift09:39
olci understand that swift has not mechanisms that can guarantee that the ring is consistent, but what happens in case of inconsistency?09:43
*** Supun has quit IRC09:44
*** Supun has joined #openstack-swift09:45
*** glb has quit IRC09:50
*** glb has joined #openstack-swift09:51
*** Supun has quit IRC09:59
*** tovin07_ has quit IRC10:01
*** germs has joined #openstack-swift10:05
*** germs has quit IRC10:05
*** germs has joined #openstack-swift10:05
kei-ichiI'd like to add one thing as agenda for next swift meting. "Question about slogging unittest"10:07
kei-ichiI would like to decide policy for running unittest.10:07
kei-ichiInside from slogging unittest, many of swift libray is used like following.10:07
kei-ichi```10:07
kei-ichifrom swift.common.utils import readconf, TRUE_VALUES10:07
kei-ichi...10:07
kei-ichifrom swift.common.exceptions import ChunkReadTimeout, LockTimeout10:07
kei-ichi```10:07
kei-ichiSometimes import just a tool. --> pattern-110:08
kei-ichiBut sometimes using exception class directly. --> pattern-210:08
kei-ichiI'm now wondering should I completly copy those kind of code into slogging ?10:08
kei-ichiOr keep using this by importing from swift ?10:08
kei-ichiLet me discuss about above point in next meeting o/10:08
*** germs has quit IRC10:10
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Use state rather than subtlety to make shards of shards authoritative  https://review.openstack.org/55135610:14
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Root leader decides when shard containers shard  https://review.openstack.org/55212010:14
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Store epoch and root container in shard ranges table  https://review.openstack.org/55266810:14
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Remove unnecessary timestamp shenanigans when creating shard container  https://review.openstack.org/55213310:26
*** mvk has quit IRC10:31
*** armaan has quit IRC10:46
*** mvk has joined #openstack-swift10:46
*** cshastri has quit IRC10:56
*** m_kazuhiro has quit IRC10:59
*** rcernin has joined #openstack-swift11:02
*** Supun has joined #openstack-swift11:04
*** rcernin has quit IRC11:06
*** Supun has quit IRC11:18
*** Supun has joined #openstack-swift11:21
*** pcaruana has quit IRC11:23
*** psachin has quit IRC11:28
*** psachin has joined #openstack-swift11:34
*** armaan has joined #openstack-swift11:48
*** Supun has quit IRC11:53
*** pcaruana has joined #openstack-swift11:55
*** germs has joined #openstack-swift12:06
*** germs has quit IRC12:06
*** germs has joined #openstack-swift12:06
*** germs has quit IRC12:10
*** wes_dillingham has joined #openstack-swift12:14
*** Supun has joined #openstack-swift12:16
*** bkopilov has quit IRC12:32
*** openstackgerrit has quit IRC12:33
*** NM has joined #openstack-swift12:36
*** Fr33m1nd has joined #openstack-swift12:37
Fr33m1ndHi12:37
*** d0ugal has joined #openstack-swift12:41
*** d0ugal has quit IRC12:41
*** d0ugal has joined #openstack-swift12:41
*** Supun has quit IRC13:06
*** openstackgerrit has joined #openstack-swift13:08
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Handle exceptions in _send_shard_ranges  https://review.openstack.org/55453113:08
*** kei_yama has quit IRC13:13
*** Supun has joined #openstack-swift13:18
*** psachin has quit IRC13:21
*** armaan has quit IRC13:24
*** armaan has joined #openstack-swift13:25
*** OrionX_ has joined #openstack-swift13:26
*** OrionX has quit IRC13:30
*** bkopilov has joined #openstack-swift13:51
*** links has quit IRC13:51
*** bob_cheesey has joined #openstack-swift13:51
bob_cheeseyafternoon all, wonder if anyone could help me figure out where an object would be on disk? i've used swift-get-nodes and tracked it down to a specific dir on a device, however that dir only contains a file called 1504771716.00350.data13:52
bob_cheeseyi've checked the other locations it could be and they're the same13:53
acolesbob_cheesey: the .data file is the object file13:56
acolesthe format of the filename is <timestamp>.data13:57
bob_cheeseyah ok, i was under the impression that the file should reside on disk there13:57
bob_cheeseyas in, the filename you expect13:57
bob_cheeseyhowever i guess that doesn't work if it's in a bunch of subdirs13:57
acolesswift-object-info will show you details13:58
acolesbob_cheesey: object files don't have the name of the object, if that's what you mean13:59
bob_cheeseyacoles: yeah that's what i was expecting but i think i mis-understood what i was reading13:59
acolesbut if you run swift-object info on a .data file it will you show you the object name14:00
bob_cheeseyyup and it's what i expect14:02
bob_cheeseythanks!14:02
*** germs has joined #openstack-swift14:07
*** germs has quit IRC14:07
*** germs has joined #openstack-swift14:07
bob_cheeseyok, so following on from that question, a customer of ours somehow 'accidentally' (their words) set an expiration date on some objects14:09
bob_cheeseyfortunately they're still on disk but they can't be retrieved (obviously). is it possible to remove that metadata?14:09
*** sai_ is now known as sai-mtg14:09
*** OrionX_ has quit IRC14:11
*** germs has quit IRC14:11
*** saint_ has joined #openstack-swift14:11
acolesbob_cheesey: first, if the expiry time has passed but there is still a .data file then the object-expirer hasn't got round to deleting the object, but it will unless you stop it14:15
bob_cheeseyyup, it hasn't be deleted yet14:16
bob_cheeseythe expirer is currently disabled so it won't blitz it14:16
acolesbob_cheesey: ok that's good. there's no API means to undelete it however. I'm just thinking about how you might do it under-the-hood.14:20
*** pcaruana has quit IRC14:21
*** armaan has quit IRC14:25
*** armaan has joined #openstack-swift14:25
*** pcaruana has joined #openstack-swift14:28
bob_cheeseyok, that would be handy if it were possible. i've just gotten the list back from the customer and it's quite substantial so i'm not recovering them by hand14:28
acolesbob_cheesy: one approach (the easiest I have thought of so far) is to use swift's internal client to post new (empty) object metadata, thus clearing the x-delete-at metadata. However, that would also clear any other metadata your customer may have included with their objects (e.g. x-object-meta-<whatever>).14:34
bob_cheeseyacoles: would any metadata they've set show up with swift-object-info?14:34
acolesthe internal client can include a special header that causes the  expiry status of the object to be ignored14:34
acolesbob_cheesey: yes14:35
bob_cheeseyin which case that should work as the only thing in the user metadata dict is the delete-at header14:35
acolesin swift-object-info under section 'User Metadata:'14:35
acolesand there may be stuff in Other Metadata: section that I haven't remembered, other than X-Delete-At14:36
*** d0ugal has quit IRC14:38
bob_cheeseyok, i think they're more interested in recovering the data than anything else at the mo14:39
bob_cheeseythanks for your help!14:39
*** OrionX has joined #openstack-swift14:40
acolesbob_cheesey: I'm just trying something out...14:40
bob_cheeseyok!14:40
*** cshastri has joined #openstack-swift14:45
*** OrionX has quit IRC14:46
acolesbob_cheesey: what version of swift?14:49
*** itlinux has joined #openstack-swift14:50
acolesgoing to need 2.15.0 or later14:50
bob_cheeseyah no older than that14:50
bob_cheesey:(14:50
acoles:(14:50
bob_cheeseyi can hack together something with bash to retrieve each file and preserve the directory structure so that may be the only way of doing this14:51
acolesbob_cheesey: I'm on a call, will get back to you14:54
bob_cheeseyno worries - i'm heading off soon14:54
*** armaan has quit IRC14:57
*** armaan has joined #openstack-swift14:57
*** jistr is now known as jistr|mtg15:01
openstackgerritAlexandre Lécuyer proposed openstack/swift master: Add round_robin_iter function to common/utils  https://review.openstack.org/55458215:05
openstackgerritAlexandre Lécuyer proposed openstack/swift master: Change object_audit_location_generator() to yield for a single policy.  https://review.openstack.org/54858915:06
*** OrionX has joined #openstack-swift15:07
*** d0ugal has joined #openstack-swift15:10
*** Supun has quit IRC15:14
*** armaan has quit IRC15:19
*** armaan has joined #openstack-swift15:19
*** jistr|mtg is now known as jistr15:36
*** Supun has joined #openstack-swift15:37
olcis `swift-get-nodes -a account.ring.gz demo` well supposed to give the path where the account database of user 'demo' is located in?15:44
*** OrionX has quit IRC15:45
olccccccchkrlkdtvenlfnlfdbfhuvejjkdtjntjhenrrej15:54
acolesolc: yes15:55
timburkenote that many auth systems add an "auth prefix" so a user demo might have an account like AUTH_demo (and it's the *account* name that you'd want to pass to swift-get-nodes)15:57
acolesbob_cheesey: sorry, had meeting. FWIW this is what I came up with but it requires swift 2.15.0 https://gist.github.com/alistairncoles/722e3e8a6d7107c9fd93c1db7ff7d73c16:01
olcthanks guys, i have tested with demo, AUTH_demo and AUTH_5e55447707cd47ebb433dc24320b571f and none returns back a correct path16:01
olci'll investigate further16:02
acolesolc: by 'correct' do you mean there is not db file at the path? that may happen if the user has not yet created any containers16:02
olcby correct I mean that directory does not exist16:03
olci have created (uploaded) an object with that acound16:04
olc*account16:04
olcanyway I'll look deeper in it16:05
olcthanks16:05
*** Supun has quit IRC16:11
*** Supun has joined #openstack-swift16:12
*** Fr33m1nd has quit IRC16:20
*** gyee has joined #openstack-swift16:26
notmynamegood morning16:28
*** mikecmpbll has joined #openstack-swift16:30
notmynamemikecmpbll: oh hi. bob_cheesey was the one asking about expiry16:30
*** cshastri has quit IRC16:31
mikecmpbll👍🏼16:35
*** armaan has quit IRC16:35
acolesbob_cheesey: https://gist.github.com/alistairncoles/27c086457a1251e9f7f4b85f57a3b553 use it at your own risk of course. You might alternatively zip up all the .data files and send them back to your customer for them to upload again, without x-delete- headers :) depends on size.16:36
*** armaan has joined #openstack-swift16:36
*** joeljwright has quit IRC16:41
*** Supun has quit IRC16:44
*** gkadam has quit IRC16:47
*** mvk has quit IRC16:49
*** cschwede_ has quit IRC17:00
*** mvk has joined #openstack-swift17:03
*** cbartz has quit IRC17:06
*** mikecmpbll has left #openstack-swift17:07
*** Supun has joined #openstack-swift17:11
*** hseipp has quit IRC17:22
openstackgerritTim Burke proposed openstack/swift feature/deep: Add swift-manage-shard-ranges entry point; drop find_shard_ranges script  https://review.openstack.org/55463917:23
acolestimburke: thanks ^17:32
*** OrionX has joined #openstack-swift17:46
*** OrionX has quit IRC17:50
*** Supun has quit IRC17:53
*** Supun has joined #openstack-swift17:54
*** armaan has quit IRC18:15
*** armaan has joined #openstack-swift18:16
*** geaaru has quit IRC18:22
*** mikecmpbll has joined #openstack-swift18:24
*** gyee has quit IRC18:30
zaitcevmother of go18:32
zaitcevor god, in this case18:32
zaitcevI added +class TestECObjectControllerPP(BaseTestECObjectController, unittest.TestCase):18:33
zaitcevBasically it re-runs all the exact tests we have for Proxy, only with PUT+POST forced on18:34
zaitcevSurely PUT+POST is fully compatible, right? Well, no. Tests interfere with each other because we examine what the object server wrote into _datadir, and our object server exists across a bunch of tests.18:35
zaitcevAnd since all the files use the name "pimento"18:36
zaitcevthere is more18:40
zaitcevAssertionError: '<html><h1>Ac' != 'HTTP/1.1 201'18:40
claygWHOA, no that does not sound good :18:44
zaitcevsomeone forgot to read the response body18:49
tdasilvanotmyname: is the LOSF meeting confirmed for tomorrow?18:51
notmynametdasilva: yes18:51
tdasilvanotmyname: ack, thanks!18:52
claygFYI, if the gate will allow it to merge patch 554582 was pretty obvious18:58
patchbothttps://review.openstack.org/#/c/554582/ - swift - Add round_robin_iter function to common/utils18:58
acolestimburke: p 554639 needs test_find_shard_ranges.py deleting but we ought to preserve some of the tests19:07
patchbothttps://review.openstack.org/#/c/554639/ - swift (feature/deep) - Add swift-manage-shard-ranges entry point; drop fi...19:07
*** Supun has quit IRC19:27
*** psachin has joined #openstack-swift19:28
*** d34dh0r53 has quit IRC19:37
*** d34dh0r53 has joined #openstack-swift19:37
*** psachin has quit IRC19:44
*** wes_dillingham has quit IRC19:46
openstackgerritMerged openstack/swift master: Refactor tempurl functional test's try-finally  https://review.openstack.org/55441219:47
*** psachin has joined #openstack-swift19:48
openstackgerritMerged openstack/swift feature/deep: Add script tool to manage container db shard ranges  https://review.openstack.org/55388219:54
*** tesseract has quit IRC19:56
*** armaan has quit IRC19:57
*** armaan has joined #openstack-swift20:05
*** psachin has quit IRC20:08
openstackgerritClay Gerrard proposed openstack/swift feature/deep: Imperceptible performance improvement  https://review.openstack.org/55468620:08
*** psachin has joined #openstack-swift20:09
*** germs has joined #openstack-swift20:10
*** germs has quit IRC20:10
*** germs has joined #openstack-swift20:10
*** germs has quit IRC20:13
*** psachin has quit IRC20:14
*** openstackgerrit has quit IRC20:33
*** openstackgerrit has joined #openstack-swift20:46
openstackgerritClay Gerrard proposed openstack/swift feature/deep: Add a bit more context to errors  https://review.openstack.org/55469220:46
openstackgerritClay Gerrard proposed openstack/swift feature/deep: Imperceptible performance improvement  https://review.openstack.org/55468620:46
*** Renich has joined #openstack-swift21:01
RenichGood day. How can I get the usage data of a user?21:01
RenichI want to know how much storage is he/she using on swift21:01
RenichFor now, I have a script that parses over all all the accounts and gets theh list of containers to, subsecuaently, get the "bytes_used" for every container. This takes a long time.21:03
claygRenich: that's basically it - someone is trying to make https://github.com/notmyname/slogging an openstack managed program21:04
claygor whatever the term is for doing reviews on gerrit and hosted in git.o.o and mirrored into github.com/openstack21:04
clayganyway - it probably does about the same as your doing - but maybe with some concurrency?21:04
Renichhttp://dpaste.com/382FG6S21:05
Renichclayg: OK. I'll take a look. Thanks!21:05
claygoh... what you're doing is using the api - the slogging stuff trolls the actual on-disk databases21:05
Renichclayg: yes, I could make a parser for this using crystal ;)21:06
Renichah, OK. So one can query the DBs?21:06
Renichcool21:06
RenichI'll have to look at that code to figure it out21:07
Renichclayg: thanks a lot for the pointers!21:07
claygRenich: you know what - try what you're doing but with `object store account show`21:07
claygi think it'll give you per account aggreate bytes used in a single api request per credentials21:08
claygmight be good enough for a while21:08
openstackgerritTim Burke proposed openstack/swift feature/deep: Add swift-manage-shard-ranges entry point; drop find_shard_ranges script  https://review.openstack.org/55463921:14
Renichclayg: awesome, will do! Was trying to build the deb packages for slogging but it doesn't work. Also, issues seem too... old... Maybe it's abandoned?21:16
claygyeah... i might call it "finished" - notmyname ???21:17
Renichclayg: awesome! It shows Bytes for the account! Cool! Useful!21:17
timburkeit'll probably be a little out of date... like the container stats, only more so21:18
timburkemost likely not enough to be a problem21:18
notmynameI'm not working on slogging, but IIRC there was some `python setup.py build_deb` thing with it. talk to kei-ichi about what the current status of slogging is. he's wanting to continue work on it21:18
*** wes_dillingham has joined #openstack-swift21:22
*** itlinux has quit IRC21:31
*** NM has quit IRC21:31
RenichThanks a lot clayg,  for the help!21:44
*** germs has joined #openstack-swift22:10
*** germs has quit IRC22:10
*** germs has joined #openstack-swift22:10
*** rcernin has joined #openstack-swift22:13
mattoliverauMorning22:14
*** germs has quit IRC22:14
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Clean up stats dumped to recon cache and logged  https://review.openstack.org/55435822:21
timburkeacoles: go to sleep!22:26
openstackgerritAlistair Coles proposed openstack/swift feature/deep: Clean up stats dumped to recon cache and logged  https://review.openstack.org/55435822:28
timburkeno! no! bad acoles! sleep!22:29
*** ianychoi__ is now known as ianychoi22:32
openstackgerritPete Zaitcev proposed openstack/swift master: PUT+POST and its development test  https://review.openstack.org/42791122:37
mattoliveraulol22:40
zaitcevsorry, I had to kill pimento22:40
zaitcevhttps://review.openstack.org/#/c/427911/26/test/unit/proxy/test_server.py22:40
patchbotpatch 427911 - swift - PUT+POST and its development test22:40
openstackgerritMerged openstack/swift feature/deep: Handle exceptions in _send_shard_ranges  https://review.openstack.org/55453122:47
openstackgerritMerged openstack/swift master: Add round_robin_iter function to common/utils  https://review.openstack.org/55458222:47
*** armaan has quit IRC22:48
*** zaitcev has quit IRC22:56
*** gerardgine has joined #openstack-swift22:58
claygwhat does "kill pimeto" mean!?23:05
claygnotmyname: were you trying to get legacy-tempest-dsvm-neutron-full out of our gate tests? Is there a *not* "legacy-*" version of that test?23:13
notmynameno, I wasn't trying to get anything out of our gate23:13
notmynamethe legacy-* jobs are the ones that are still in -infra repos after the zuul v3 merge23:13
claygoh, that's helpful - thank you for that!23:14
openstackgerritMerged openstack/swift feature/deep: Use state rather than subtlety to make shards of shards authoritative  https://review.openstack.org/55135623:17
*** Anticime1 is now known as Anticimex23:29
openstackgerritTim Burke proposed openstack/swift feature/deep: Defend against sharding an expanding root container  https://review.openstack.org/55473323:40

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