Tuesday, 2021-12-07

opendevreviewMerged openstack/swift stable/xena: reconstructor: remove non-durable files on handoffs  https://review.opendev.org/c/openstack/swift/+/82009102:15
opendevreviewMatthew Oliver proposed openstack/swift master: WIP: Add global error_limiting to object-updater  https://review.opendev.org/c/openstack/swift/+/82048602:20
opendevreviewMatthew Oliver proposed openstack/swift master: Refactored errorlimited out of proxy + global cache  https://review.opendev.org/c/openstack/swift/+/82031302:43
opendevreviewMatthew Oliver proposed openstack/swift master: Add global error_limiting to object-updater  https://review.opendev.org/c/openstack/swift/+/82048602:43
opendevreviewMatthew Oliver proposed openstack/swift master: Refactor memcache config and MemcacheRing loading  https://review.opendev.org/c/openstack/swift/+/82064802:43
*** redrobot8 is now known as redrobot10:20
opendevreviewAlistair Coles proposed openstack/swift master: updaters: use replication network  https://review.opendev.org/c/openstack/swift/+/82040210:26
opendevreviewAlistair Coles proposed openstack/swift master: Unit test logging of object updater timeouts  https://review.opendev.org/c/openstack/swift/+/82085511:55
opendevreviewAlistair Coles proposed openstack/swift master: updater: Add timing stats  https://review.opendev.org/c/openstack/swift/+/81973211:57
opendevreviewAlistair Coles proposed openstack/swift master: Unit test logging of object updater timeouts  https://review.opendev.org/c/openstack/swift/+/82085511:57
mattg33Hello, I was curious on expected account-reaper behavior after deleting an account and if there is a way to be able to tell when all data for the account has been reaped. When I issue a delete on a swift account, I see HEAD requests on the account then return 410 Gone.  Testing with debug logging I can see that after passing the delay_reaping time I see the reaper report my test object is deleted, HEAD requests against the account still return 4115:06
manuvakery1 Hi in my swift-proxy pipeline ceilometer midlleware is present right before proxy-server 15:43
manuvakery1[pipeline:main]15:43
manuvakery1pipeline = catch_errors gatekeeper healthcheck proxy-logging cache etag-quoter formpost tempurl crossdomain s3api container_sync bulk ratelimit authtoken s3token keystoneauth staticweb container-quotas account-quotas slo dlo versioned_writes symlink proxy-logging ceilometer proxy-server15:43
manuvakery1because of this s3api and staticweb calls measurements are not getting emited by ceilometermmiddleware.  By the time the request reaches the ceilometer middleware the env.get('swift.source') will be set to S3/SW.  I  updated the pipeline as follows 15:43
manuvakery1[pipeline:main]15:43
manuvakery1pipeline = catch_errors gatekeeper healthcheck proxy-logging cache etag-quoter formpost tempurl crossdomain ceilometer s3api container_sync bulk ratelimit authtoken s3token keystoneauth staticweb container-quotas account-quotas slo dlo versioned_writes symlink proxy-logging  proxy-server15:43
manuvakery1Now s3 call measurements are emited by ceilometermiddleware. Just want check if any possible downside to this15:43
manuvakery1timburke__: whats your view on this15:46
timburke__manuvakery1, that looks sane -- you may want to move bulk left as well, though (depends on whether you want to measure the bulk requests or the subrequests)21:46
timburke__like "... tempurl crossdomain bulk ceilometer s3api ..."21:47
opendevreviewClay Gerrard proposed openstack/swift master: Finer grained ratelimit for updater  https://review.opendev.org/c/openstack/swift/+/82096223:21

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!