Wednesday, 2024-10-23

timburkethere was another session today, mostly talking sharding, moving beyond md5 for validation, liberasurecode, and starting to ponder the implications of eventlet removal00:00
timburkei should be better about updating #openinfra-events00:01
timburkekota, no worries! rest up00:01
kotatimburke: thx again. hope the ptg goes excellent00:01
DHEI'm hoping to attend...00:17
opendevreviewMatthew Oliver proposed openstack/swift master: Added a swift-graph-shardranges cli script / tool  https://review.opendev.org/c/openstack/swift/+/77506602:35
mattoliver^ version of the shardrange graph tool that also colors deleted shardranges in red.02:37
mcapeHi All!06:52
mcapeRecently I did added some new disks to our swift cluster of ~300Tb and some 300m documents.06:52
mcapeAnd then there was a  spike of errors in the logs that looked like:  06:53
mcape [worker 1/1 pid=43347] <f+++++++++ 2f3/4b9b1ba80cb7366f0ee71ced5e9152f3/1605695055.99690.data06:53
mcapemaybe a few thousand lines like that06:53
mcapeSeems that it is rsync that is creating files on the remote replicas. 06:53
mcapeBut why this log is severity: err? It seems that it is not an error at all.06:53
opendevreviewAlistair Coles proposed openstack/swift feature/mpu: mpu: probe tests: capture_logs option for run_custom_daemon  https://review.opendev.org/c/openstack/swift/+/93309812:07
timburkemcape, presumably toward the end of all that there'll be some actual error -- when there's an error, we log all the rsync output at error12:57
timburkefwiw, you can set log_rsync_transfers=false in your object-replicator config to turn off all the transfers -- it tends to be needlessly verbose12:58
timburkewe might want to consider changing https://github.com/openstack/swift/blob/master/swift/obj/replicator.py#L416 to `if result.startswith('<') or not ret_val:`12:58
timburkemeeting time, if we want to discuss anything before the ops feedback session in an hour -- https://meetpad.opendev.org/p/swift-ptg-epoxy13:01
mattoliverBe right there13:02
mcapetimburke, thanks a lot for your answer!! 13:56
acolestimburke: let's try to make progress on this one https://review.opendev.org/c/openstack/swift/+/887908 13:59
patch-botpatch 887908 - swift - Stop using cgi.parse_header - 5 patch sets13:59
timburkeops feedback session now in https://meetpad.opendev.org/p/swift-epoxy-ops-feedback14:02
opendevreviewASHWIN A NAIR proposed openstack/swift master: refactor test for x-delete-at w/t part_num and x-open-expired  https://review.opendev.org/c/openstack/swift/+/93306115:40
opendevreviewAlistair Coles proposed openstack/swift feature/mpu: WIP mpu: don't cleanup stale replica of versioned object  https://review.opendev.org/c/openstack/swift/+/93312215:53
opendevreviewAlistair Coles proposed openstack/swift feature/mpu: mpu: probe tests: capture_logs option for run_custom_daemon  https://review.opendev.org/c/openstack/swift/+/93309816:12
opendevreviewAlistair Coles proposed openstack/swift feature/mpu: s3 compat test: null version only becomes version if overwritten  https://review.opendev.org/c/openstack/swift/+/93304116:15
opendevreviewAlistair Coles proposed openstack/swift feature/mpu: mpu-auditor: audit sessions  https://review.opendev.org/c/openstack/swift/+/93151716:16
opendevreviewAlistair Coles proposed openstack/swift feature/mpu: mpu-auditor: audit manifests  https://review.opendev.org/c/openstack/swift/+/93235216:16
opendevreviewAlistair Coles proposed openstack/swift feature/mpu: mpu: improve error response handling  https://review.opendev.org/c/openstack/swift/+/93303916:16
opendevreviewAlistair Coles proposed openstack/swift feature/mpu: mpu: cleanup after specific version is deleted  https://review.opendev.org/c/openstack/swift/+/93304016:16
opendevreviewAlistair Coles proposed openstack/swift feature/mpu: WIP mpu: don't cleanup stale replica of versioned object  https://review.opendev.org/c/openstack/swift/+/93312216:16
fulecorafao/21:02
opendevreviewTim Burke proposed openstack/swift master: Add swift-ring-info utility  https://review.opendev.org/c/openstack/swift/+/85723421:20
opendevreviewTim Burke proposed openstack/swift master: sq? ring-info: Work on builders, too  https://review.opendev.org/c/openstack/swift/+/93315621:20
opendevreviewTim Burke proposed openstack/swift master: ring-builder: Add revert subcommand  https://review.opendev.org/c/openstack/swift/+/93315721:20
timburkeDHE, i wonder if ^^^ might help with your ring-composer issues -- if we ensure the version continues to march forward even as the state is rolling back, the composer ought to still be happy21:21
opendevreviewTim Burke proposed openstack/swift master: sq? ring-info: Work on builders, too  https://review.opendev.org/c/openstack/swift/+/93315621:36
opendevreviewTim Burke proposed openstack/swift master: ring-builder: Add revert subcommand  https://review.opendev.org/c/openstack/swift/+/93315721:36
timburkeuh oh. i think i maybe needed to wait on https://review.opendev.org/c/openstack/pyeclib/+/930171 until after we had a release with https://review.opendev.org/c/openstack/liberasurecode/+/929193 ...21:49
patch-botpatch 930171 - pyeclib - Add close/destroy methods; clean up descriptors (MERGED) - 5 patch sets21:49
patch-botpatch 929193 - liberasurecode - built-in rs_vand: De-init tables only when last de... (MERGED) - 3 patch sets21:49
opendevreviewASHWIN A NAIR proposed openstack/swift master: refactor test for x-delete-at w/t part_num and x-open-expired  https://review.opendev.org/c/openstack/swift/+/93306121:59
timburkereally weird thing is that https://github.com/openstack/requirements/blob/master/upper-constraints.txt#L512 still has the old version, but the log for https://zuul.opendev.org/t/openstack/build/8ab820800bde418dbbae18721e2859de/console shows the new one22:16
timburkelooks like there's separate install_deps and install_package_deps, and the second one is running unconstrained??22:16
timburkewhy *do* we have that -U on https://github.com/openstack/swift/blob/master/tox.ini#L13 ?22:17
timburkeseems to go back like 11 years: https://github.com/openstack/swift/commit/9a2bd79022:20
clarkbI think the reason for it is to force pip to install newer packages if they are available. It was a common problem in the past for people to run a target and have it succeed but ci would fail or vice versa due to mismatches in dep installs22:20
clarkbI don't knwo if it is necessary with the use of constraints (I think it may be if you have a delta to the constraints in your venv)22:20
clarkbthe alternative would be to encourage people to use tox -r when they get unexpected results22:21
DHEOOOoo...22:35
opendevreviewTim Burke proposed openstack/pyeclib master: Only really destroy instances on new-enough liberasurecode  https://review.opendev.org/c/openstack/pyeclib/+/93316322:38
opendevreviewTim Burke proposed openstack/swift master: CI: Stop upgrading direct dependencies past constraints  https://review.opendev.org/c/openstack/swift/+/93316422:42
timburkewell, fwiw, none of cinder, glance, keystone, neutron, or nova include that -U flag (at least, not any more)22:53
timburkeat the same time, it's not like i *mind* catching (some) trouble early like happened here... maybe "test with constraints for most of the packages, but latest for direct deps" is a reasonable path to take...22:55
clarkbit is possible that changes to pip have made it unnecessary22:55
timburke11 years is a long time, and a lot of pip upgrades :-)22:55
clarkbone way to test it would be to run tox, then manually downgrade/upgrade a dep in the resulting venv then rerun tox without the -U and then redo the test with the -U and see if you get the same result22:55
clarkbyup exactly22:55
opendevreviewTim Burke proposed openstack/pyeclib master: Only really destroy instances on new-enough liberasurecode  https://review.opendev.org/c/openstack/pyeclib/+/93316323:20
opendevreviewTim Burke proposed openstack/liberasurecode master: Release 1.6.5  https://review.opendev.org/c/openstack/liberasurecode/+/93316723:42

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