You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/06/03 09:41:17 UTC
[GitHub] [pulsar] dockerzhang opened a new issue #7153: [proxy] pulsar-proxy Caught Connection refused error
dockerzhang opened a new issue #7153:
URL: https://github.com/apache/pulsar/issues/7153
**Describe the bug**
**Version**
2.5.2 deployed by k8s helm
**To Reproduce**
Steps to reproduce the behavior:
1. kubectl exec -it statefulset/pulsar-toolset
2. execute './bin/pulsar-perf produce fl-tenant/fl-namespace/tt --rate 10000 -s 5120000 -z LZ4'
**Expected behavior**
If i produce message in pulsar-broker by pulsar-perf, it works fine.
it caught connection refused error if using pulsar-proxy in pulsar-toolset.
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [pulsar] dockerzhang edited a comment on issue #7153: [proxy] pulsar-proxy Caught Connection refused error
Posted by GitBox <gi...@apache.org>.
dockerzhang edited a comment on issue #7153:
URL: https://github.com/apache/pulsar/issues/7153#issuecomment-638567895
@sijie yes, the proxy restarted during test.
I check the log of exited proxy container, it's exited for OOM error.
I increased 2G to 8G and test again, test recovered.
Thanks @sijie , this issue can close now.
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [pulsar] sijie commented on issue #7153: [proxy] pulsar-proxy Caught Connection refused error
Posted by GitBox <gi...@apache.org>.
sijie commented on issue #7153:
URL: https://github.com/apache/pulsar/issues/7153#issuecomment-638549660
@dockerzhang was the proxy restarted during your test?
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [pulsar] dockerzhang commented on issue #7153: [proxy] pulsar-proxy Caught Connection refused error
Posted by GitBox <gi...@apache.org>.
dockerzhang commented on issue #7153:
URL: https://github.com/apache/pulsar/issues/7153#issuecomment-638567895
@sijie yes, the proxy restarted during test.
I check the log exited of proxy container, it's exited for OOM error.
I increased 2G to 8G and test again, test recovered.
Thanks @sijie , this issue can close now.
----------------------------------------------------------------
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:
users@infra.apache.org