Open fruch opened 7 months ago
1) I think we should ignore those errors by default 2) we might want to skip this code completely in non-perf test, it's wasting time generating snapshot we never look into on all longevity runs 3) we still might need to look at the issue, since it's not clear who is holding this port, and how we go into such situation (it shouldn't happen)
I done some investigations several months ago: https://github.com/scylladb/scylla-cluster-tests/issues/6827
I done some investigations several months before: #6827
but something is off here, it shouldn't happen, it should pick a random port, i.e. use 0, and then check it.
maybe our docker python package is too old, and has issues, maybe it's good time to update it
Afair from my investigations, docker-py's containers.run()
is not changed since then.
My guess that it can happen under a heavy load. As a workaround we can start remotebrowser docker container before the monitoring stack setup when the monitoring node is pretty idle.
failed to generate snapshot inside
@latency_calculator_decorator
Jenkins run:
https://jenkins.scylladb.com/job/scylla-staging/job/karol_baryla/job/longevity-100gb-4h-cql-stress-test-tablets/4/
Logs