TheNotary opened a new issue #9579: URL: https://github.com/apache/pulsar/issues/9579
**Describe the bug** When docker compose is used to orchestrate the standalone pulsar service along with a python consumer and producer client, there is an apparent buffering for messages before the client receives them. **To Reproduce** Steps to reproduce the behavior: 1. clone down https://github.com/TheNotary/pulsar-latency-test 2. use `docker-compose up -d standalone` to boot the standalone pulsar service 3. Use `docker-compose up python_pulsar_consumer` to start a pulsar consumer 4. In terminal 2, use `docker-compose up -d python_pulsar_producer && docker attach pulsar-latency-test_python_pulsar_producer_1` to start and attach tty to the producer 5. In terminal 2, press enter to send 10 messages to pulsar 6. Notice that the consumer terminal will not report seeing those messages until you submit a good 100 messages by pressing enter > 10 times (each enter fires of 10 messages). **Expected behavior** One would expect that a single message from a producer would reach a consumer within the same day, even if additional messages were not sent. **Screenshots** If applicable, add screenshots to help explain your problem. **Desktop (please complete the following information):** - OS: OSX 10.15.7 - Docker 3.1.0 - Pulsar 2.7.0 **Additional context** When the same python consumer executes outside of docker, it works without the buffering effect. Very peculiar. ---------------------------------------------------------------- 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]
