Monday, 2019-11-04

*** timburke_ has joined #openstack-swift00:54
*** ChanServ sets mode: +v timburke_00:54
*** timburke_ has quit IRC00:58
*** timburke_ has joined #openstack-swift01:13
*** ChanServ sets mode: +v timburke_01:13
*** nanzha has joined #openstack-swift01:27
*** nanzha has quit IRC02:36
*** nanzha has joined #openstack-swift02:37
*** timburke_ has quit IRC02:55
*** timburke_ has joined #openstack-swift02:55
*** ChanServ sets mode: +v timburke_02:55
*** timburke_ has quit IRC03:10
*** timburke_ has joined #openstack-swift03:18
*** ChanServ sets mode: +v timburke_03:18
*** tkajinam has joined #openstack-swift03:18
*** timburke_ has quit IRC03:19
*** psachin has joined #openstack-swift03:21
*** timburke_ has joined #openstack-swift03:22
*** ChanServ sets mode: +v timburke_03:22
*** timburke_ has quit IRC03:27
*** timburke_ has joined #openstack-swift03:31
*** ChanServ sets mode: +v timburke_03:31
*** timburke_ has quit IRC04:05
*** timburke_ has joined #openstack-swift04:09
*** ChanServ sets mode: +v timburke_04:09
*** timburke_ has quit IRC04:14
*** tkajinam has quit IRC04:19
claygWhoa! IRC working.04:42
*** timburke_ has joined #openstack-swift04:55
*** ChanServ sets mode: +v timburke_04:55
*** psachin has quit IRC04:59
*** timburke_ has quit IRC05:00
*** timburke_ has joined #openstack-swift05:01
*** ChanServ sets mode: +v timburke_05:01
*** timburke_ has quit IRC05:06
*** timburke_ has joined #openstack-swift05:09
*** ChanServ sets mode: +v timburke_05:09
*** timburke_ has quit IRC05:10
*** timburke_ has joined #openstack-swift05:16
*** ChanServ sets mode: +v timburke_05:16
*** timburke_ has quit IRC05:16
*** timburke_ has joined #openstack-swift05:16
*** ChanServ sets mode: +v timburke_05:16
*** timburke_ has quit IRC05:39
*** timburke_ has joined #openstack-swift06:15
*** ChanServ sets mode: +v timburke_06:15
*** timburke_ has quit IRC06:20
*** timburke_ has joined #openstack-swift06:20
*** ChanServ sets mode: +v timburke_06:20
*** alexlecuyer-ch has joined #openstack-swift06:24
*** timburke_ has quit IRC06:31
*** timburke_ has joined #openstack-swift06:40
*** ChanServ sets mode: +v timburke_06:40
*** timburke_ has quit IRC06:44
*** alexlecuyer-ch has quit IRC06:48
*** timburke_ has joined #openstack-swift06:53
*** ChanServ sets mode: +v timburke_06:53
*** nanzha has quit IRC07:00
*** nanzha has joined #openstack-swift07:10
*** timburke_ has quit IRC07:30
*** timburke_ has joined #openstack-swift07:31
*** ChanServ sets mode: +v timburke_07:31
*** timburke_ has quit IRC07:43
*** timburke_ has joined #openstack-swift07:43
*** ChanServ sets mode: +v timburke_07:43
*** timburke_ has quit IRC07:51
*** timburke_ has joined #openstack-swift08:12
*** ChanServ sets mode: +v timburke_08:12
*** alexlecuyer-ch has joined #openstack-swift08:15
*** alexlecuyer-ch has quit IRC08:20
*** alexlecuyer-ch has joined #openstack-swift08:20
*** tesseract has joined #openstack-swift08:24
*** pcaruana has joined #openstack-swift08:30
*** timburke_ has quit IRC08:46
*** timburke_ has joined #openstack-swift08:49
*** ChanServ sets mode: +v timburke_08:49
*** alexlecuyer-ch has quit IRC08:52
*** alexlecuyer-ch has joined #openstack-swift08:59
*** alexlecuyer-ch has quit IRC08:59
*** alexlecuyer-ch has joined #openstack-swift08:59
*** alexlecuyer-ch has quit IRC09:08
*** alexlecuyer-ch has joined #openstack-swift09:19
*** alexlecuyer-ch has quit IRC09:21
*** timburke_ has quit IRC09:27
*** timburke_ has joined #openstack-swift09:33
*** ChanServ sets mode: +v timburke_09:33
*** timburke_ has quit IRC09:37
*** timburke_ has joined #openstack-swift10:01
*** ChanServ sets mode: +v timburke_10:01
*** timburke_ has quit IRC10:05
*** timburke_ has joined #openstack-swift10:17
*** ChanServ sets mode: +v timburke_10:17
*** timburke_ has quit IRC10:18
*** rdejoux has joined #openstack-swift10:51
*** timburke_ has joined #openstack-swift11:26
*** ChanServ sets mode: +v timburke_11:26
*** timburk__ has joined #openstack-swift11:27
*** ChanServ sets mode: +v timburk__11:27
*** timburke_ has quit IRC11:30
*** timburk__ has quit IRC11:32
*** timburke_ has joined #openstack-swift11:36
*** ChanServ sets mode: +v timburke_11:36
timburke_hrm. looks like the lower-constraints py2->py3 transition affects stable branches, too: https://review.opendev.org/#/c/690738/11:43
patchbotpatch 690738 - swift (stable/rocky) - Fix quarantine when object path is not a directory - 1 patch set11:43
openstackgerritTim Burke proposed openstack/swift stable/train: pin lower-constraints to run against python 2.7  https://review.opendev.org/69281011:50
openstackgerritTim Burke proposed openstack/swift stable/stein: pin lower-constraints to run against python 2.7  https://review.opendev.org/69281111:50
timburke_aaaand merge conflict on rocky :-/11:51
tdasilvathat's weird that it was changed to run py3 on stable branches too11:52
tdasilvai can understand master, stable branches seems like a mistake11:52
*** nanzha has quit IRC12:02
*** timburke_ has quit IRC12:05
*** nanzha has joined #openstack-swift12:10
*** timburke_ has joined #openstack-swift12:27
*** ChanServ sets mode: +v timburke_12:27
*** timburke_ has quit IRC12:31
*** FlorianFa has joined #openstack-swift12:36
*** nanzha has quit IRC13:02
*** nanzha has joined #openstack-swift13:02
*** henriqueof has joined #openstack-swift13:26
openstackgerritMerged openstack/swift stable/train: pin lower-constraints to run against python 2.7  https://review.opendev.org/69281014:10
*** nanzha has quit IRC14:48
*** nanzha has joined #openstack-swift14:55
*** mugsie has quit IRC15:02
*** mugsie has joined #openstack-swift15:05
*** dosaboy has quit IRC15:10
*** dosaboy has joined #openstack-swift15:50
*** dosaboy has joined #openstack-swift15:50
*** dosaboy has quit IRC15:51
*** dosaboy has joined #openstack-swift15:52
*** dosaboy has quit IRC15:53
*** dosaboy has joined #openstack-swift15:55
*** gyee has joined #openstack-swift16:03
*** nanzha has quit IRC16:33
*** mvkr has quit IRC16:48
*** mwheckmann has joined #openstack-swift16:54
mwheckmannhello. Does anyone know under what circumstances a container DB (i.e a container listing) will get out of sync and list objects that were deleted? (we confirmed the object deletions through the logs). This was with 2.13 BUT while we were in the middle of upgrading the storage nodes to 2.21. I'm not entirely sure that the upgrade had anything to do with it though. These were with segment17:14
mwheckmannobjects from an application that uses the DLO Direct API (so basically just like regular objects).17:15
*** gregwork has joined #openstack-swift17:38
*** pcaruana has quit IRC18:08
*** pcaruana has joined #openstack-swift18:08
*** tesseract has quit IRC18:53
*** mwheckmann has quit IRC19:33
*** mwheckmann has joined #openstack-swift19:34
*** mwheckmann has quit IRC19:35
*** alexlecuyer-ch has joined #openstack-swift19:47
*** alexlecuyer-ch has quit IRC20:28
*** mwheckmann has joined #openstack-swift21:10
*** pcaruana has quit IRC21:30
*** timburke_ has joined #openstack-swift21:42
*** ChanServ sets mode: +v timburke_21:42
*** mvkr has joined #openstack-swift21:56
mattoliveraumwheckmann: how out of sync? When an OP sits the object server, ie a PUT or DELETE. Then the object server will attempt to update the container server. If it fails, due to load, or timeout or whatever, it'll write it to async pending and the object-updater will pick it up and update the container servers async. So there can be a lag sometimes depending on what's happening in your cluster.22:23
mattoliverau*hits22:23
mattoliveraualso morning22:24
mattoliverauhow's the summit/ptg going?22:24
timburke_rledisez, alecuyer: hmm... https://github.com/docker/distribution/pull/122922:25
timburke_mattoliverau: it's going well! did the project update and ops feedback yesterday, met a new operator or two22:25
mattoliveraunice!22:25
timburke_https://etherpad.openstack.org/p/PVG-swift-ops-feedback22:26
mwheckmannmattoliverau, that is exaclty my understanding as well. Out of sync in the sense that we have a handful of objects in a very large container DB that did not get marked as "deleted".22:26
mwheckmannLike I said, this started while we were upgrading from 2.13 -> 2.21.22:26
mwheckmannThe objects themselves no longer exist in their respective partitions. Only the ts files are there.22:27
timburke_mwheckmann: just one replica, or all replicas of the container DB? how's your async pending count and object-updater cycle time?22:27
mwheckmannAll replicas of the container DB yes.22:27
mwheckmanntimburke_: I'll have to check that.22:28
mattoliverauif a delete has made it to one replica of the container, it should propergate. As timburke suggests, the async pending might not have fired or had trouble firing.22:30
mattoliverauif only there was a way to shard up these large container db.. so they'd repond quickly and now slow down22:30
mattoliverau:P22:30
mwheckmannCould be because of not doing the clean "swift-init rest stop" during the upgrade?22:31
mwheckmannIt's a relatively busy container.22:31
mwheckmann(the container DBs are on SSD BTW)22:32
mattoliverauthe object-updaters will attempt to update the dbs. but if the container is busy may timeout or fail and try again next cycle. So checking the object updater cycle time and stats might give us a clue.22:33
mattoliverauor if your updaters aren't running22:34
timburke_fwiw, something along the lines of `find /srv/node/*/async_pending/ -type f | wc -l` should get you the current async pending count for a node22:36
mwheckmannThe object updaters are running. Our swift-recon stats are broken since upgrade (we also moved to running in containers). I'll try what timeburke_ suggests22:37
mwheckmannI have to go. But at first glance async_pending's are non-existant. Last week during the upgrade there were quite a few of them though. I'll have to dig deeper22:40
mwheckmannI'll checl later on.22:40
*** mwheckmann has quit IRC22:41
mattoliverautimburke: cool, some good feedback from the session. So my take after a brief glance. Teiring sounds like it will be useful feature or maybe at least policy migration. And maybe make sure expiring objects can target versions in the new versioning API :)22:41
mattoliverauconsistant directory listings.. well they'll be more consistant in healthy clusters. If everyone used sharding (ie auto sharding was eventual on all the time, on day) then that'll hopefully help somewhat.22:43
mattoliveraumaybe one day revisit partpower increase (2.0) where there is less op intervention and downtime to consistency engine.22:45
timburke_poor guy had a part power of 10 for ~1000 disks :-(22:49
mattoliverauoh wow22:57
*** mwheckmann has joined #openstack-swift23:09
*** timburke_ has quit IRC23:23
mwheckmanntimburke_: there is a lot of object expiry in this cluster and we had scale out the expirers during our upgrade, I wonder if that was putting more pressure on the container servers.23:45
mwheckmannasync_pendings are non-existant for the storage policy that was affected.23:45
mwheckmannIt looks like the expiry has caught and all is calm now.23:46

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