Abacn commented on issue #24021: URL: https://github.com/apache/beam/issues/24021#issuecomment-1309427424
> > On the other hand @Amar3tto could you please check the rabbitmq instance leaking issue? > > Yes, I will take a look. Found the latest performance run https://ci-beam.apache.org/view/PerformanceTests/job/beam_PerformanceTests_SparkReceiver_IO/39/ does not leave persistent rabbitmq workloads on k8s cluster. The leak is either probabilistic or due to execution outside the jenkins (those workloads had default namespace "rabbit-test" and "default" instead of named after task ID). The issue is mitigated for now. Thanks for your attention. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
