michaeljmarshall commented on pull request #9393: URL: https://github.com/apache/pulsar/pull/9393#issuecomment-773090796
@lhotari - After running this several times on my machine, I haven't been able to reproduce the failure with the limit set to 400. Although, I also wasn't able to get the broker's CPU utilization to go above 100%, but it looks like you were, so I'm not sure what that means because you had over 100% utilization. At what point do we consider this the solution to the flaky test? Thank you for your help. As an aside, it does seem that using docker to limit CPU/mem is an option on a mac. Here is my `Dockerfile` ```Dockerfile FROM openjdk:8-jdk-slim RUN mkdir -p /usr/share/man/man1 RUN apt update && apt -y install maven ENTRYPOINT ["/bin/bash"] ``` and then I started the container: ```shell docker run --cpus=2 --memory=3g -it --entrypoint bash -v /Users/Michael:/root pulsar-test-env:0.0.0 ``` and after navigating to my `pulsar` dir, ran ```shell mvn test -Dtest=AntiAffinityNamespaceGroupTest -DfailIfNoTests=false -pl pulsar-broker ``` (Because I mounted my home to the container's home, maven worked properly so I could run the build and install outside of the container.) ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
